RabidHaMsTeR.Org

Seems like the lock bug is still there... have no idea what's causing this, if it might be a particular scene or fader, or possibly R4 managing to mung up some texture memory that the Radeons use to store the desktop or somesuch.
In any case, after swapping to fullscreen, any attempt to switch back to windowed mode or exit the program results in screen-garbage that's clearly R4 in nature... specifically, the font table. Doesn't appear that the Radeon thinks it crashed, as the GPU recover doesn't kick in. System remains responsive, though 'blind' operation is neccessary to shut down and restat safely.

On the up side, at least for the last couple of run-throughs, no slowdown was noticed on transitions except when allocating new pbuffers.. which was a freeze of 1-5 seconds. :b

REALLY getting tempted to just grab a R9200 Pro and ship it over to you, Gordon.. that or pick up a cheapass GF3 (if I can find one).

ok. i'm not sure why the FPS graph would be flat. The impression i got from triple-buffers was as i mentioned before - its how all previous things i've seen have worked. What was the framerate at? and did the scenes run normal speed, or were they extra fast?

As i explained before though, R4 doesn't wait for vsync for each scene while rendering. If it did, the framerate would be 1/3 (since the fade is a scene too) not 1/2, and just adding an overlay would instantly halve it too. I also know exactly what the R4 code is and all it does is try to get the *metered* framerate constant. That is, what you see in the top-left is what it uses to keep a constant rate. I hasten to add that its fine on my PC too. with any kind of vsync.

The problem is probably task scheduling, but its not R4 based. Probably what happens is R4 loops, waiting for the correct time and asking windows for messages, but windows detects its being asked for messages very often and so gives R4 a lower priority. When R4 does go to do something complex it doesn't have enough CPU time for it, and windows doesn't change back quick enough.

Also... 2048x2048 pbuffers on 1600x1200 is actually quite stupid. If it fails or crashes, or does anything at all odd when the pbuffers are above 512x256 then i really don't want to know

I knew I saw it... That darn combined 3d menu screwin w/me again. I need to hack that default to Open GL!

I take a look later and see what if anything changes w/R4.

(Talesin)
Update:> That combined menu bugged me for the last time, if interested you can change it back to Old Skool w/seperated tabs off the advanced menu simply change:

HKLM\SOFTWARE\ATI Technologies\Desktop\0001\
Binary value '3D' from a 01 to 00