Shots from NextGL1.3

[Adair]

In game shot.

__________________

WindowsXP pro | ASUS A7N8X Nforce2 motherboard | Athlon XP 1700+(1.46 Ghz)
IBM 40GB 7200rpm | 512Mb DDR PC3000 | Leadtek geforce4 Ti4400 | SB live X-gamer
16x DVDrom & 4x4x24x CDrewriter | Enermax EG465 (430watt power supply)

[NickK]

Did you try using the "fast MDEC" option? It might speed up the MDECs a bit! :)

Also, about the GT2 and trails. That's only because the back buffer is never cleared. Still working on that. Thanks for the pics! :)

__________________
[sig=54]
[sig=253]

[Adair]

Originally posted by Raziel
Did I hear Soul Reaver?

Yep and its working great with ePSXe. I just started playing it for the first time. Actually I need to start over. I just realized you're supposed to go to the teleport rooms before saving.


NickK,
The Mdecs play fine, its just the 3D rendered cutscenes that are very slow. I'll try it anyway though just in case.

BTW here's a shot from Silent Hill. I guess you probably have a ways to go before you implement something like mask bit.

[Adair]

And here's a shot from Bushido Blade 2. It all looks plays great except the grey shadows and the Mdecs dont play at all. Just a blank screen with sound.

[NickK]

Cool Hey, could you do me a favor? Try turning on the extended "real time" debug output and re-run some of the games that were giving you problems/slow downs. Check the console window frequently, and see if any info is dumped there. Because if a page removal or CLUT change occurs, then you'll see it there. (Which can slow down the rendering a lot.)

Thanks!

__________________
[sig=54]
[sig=253]

[NickK]

Currently investigating a major slow down problem in Reloaded. Could be the source of your problems too

__________________
[sig=54]
[sig=253]

[Adair]

Originally posted by NickK
Cool Hey, could you do me a favor? Try turning on the extended "real time" debug output and re-run some of the games that were giving you problems/slow downs. Check the console window frequently, and see if any info is dumped there. Because if a page removal or CLUT change occurs, then you'll see it there. (Which can slow down the rendering a lot.)

Thanks!

Sure, it's the least I could do. Hey I can't code my own plugin, but I'm glad to help how I can. It won't even begin to measure up to the amount of time you put into your plugin. So its a deal, you pull your polygons together and I'll stop the kittens, Okay? I'll put up some findings tomorrow since I got a day off.

---

Last edited by Adair; September 17th, 2001 at 06:22..

[NickK]

Originally posted by Adair

So its a deal, you pull your polygons together and I'll stop the kittens, Okay?

Sure! It's a deal

__________________
[sig=54]
[sig=253]

[Adair]

Here's all I could get out of GT2. I think the info got cut off at the top because the DOS box can only show a certain number of lines. Also I included the error details just in case they're useful. The info I was getting when browsing through the game menus all seemed pretty normal till I clicked on a car dealership. That's when I got this...

CLUT change on texture page 10. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 12. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 10. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 10. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 12. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 10. (CLUT 2 bit -> CLUT 0 bit)
CLUT change on texture page 10. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 0 bit -> CLUT 2 bit)
CLUT change on texture page 12. (CLUT 2 bit -> CLUT 0 bit)

---------------------------
[NextGL] Texture Cache info
---------------------------
15 page(s) used of 32
10 sub pages(s) used
~6.40MB of VRAM used
~0.26MB of VRAM used reported by the memory manager

Page: 14, Intersections: 1458. 1458 are quad(s), 0 are triangle(s)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~

EPSXE140 caused an invalid page fault in
module GPUNEXTGL_MMX.DLL at 0177:017c33e0.
Registers:
EAX=ff5088c8 CS=0177 EIP=017c33e0 EFLGS=00010202
EBX=00000000 SS=017f ESP=00b1fc60 EBP=0181ad02
ECX=01994240 DS=017f ESI=00000001 FS=3b2f
EDX=00041dc4 ES=017f EDI=0186f59b GS=0000
Bytes at CS:EIP:
89 44 11 fc 75 d1 8b 6c 24 5c 8b 4c 24 1c 8b 44
Stack dump:
00b1fca8 0191f708 0191f6dc 000000dc 00000500 0181ad02 017c72a4 00007672 0000000a 00000007 00000280 00000000 00000000 00000034 01aea700 01aebac0

[NickK]

Thanks for the useful info! I've actually recently discovered a similiar error when in the BIOS, and I've already have an idea on how to fix it :) I'm getting GT2 soon anyway, so I'll be able to fix any problems that are releated to that game as well. If you find anything else that's interesting, please tell me! Thanks again! :)

__________________
[sig=54]
[sig=253]

[NickK]

Check it out! I just got GT2 working!

__________________
[sig=54]
[sig=253]

[NickK]

And Tekken 3

__________________
[sig=54]
[sig=253]

[Adair]

Hi, I haven't read the boards in a couple of days.
You're making great progress on your GPU. I'll be sure to test out my games with your new versions in the future when my shedule allows me to.