RabidHaMsTeR.Org

Forgot to mention a new bug I found while R4 is loading and you hit a key on the keyboard it errors with a (Illegal operation/R4.exe has encountered a problem). So yes it happens in 9x and XP.

In checking prior versions looks like it crept in with something you did from 0v17 forward. (0v18,19,1v00 errors, no problems w/0v17 and earlier)

Update> Doesnt matter whether you start it through the WA plugin or directly from R4.exe any key press results in an error and close.

Any chance that a triple-buffer version could be fired off if it was something simple like adding a line to the init code? I'd like to see if it works on the nVidia hardware as well, since the Dets don't have a triple-buffer option to enable. :b That or anyone know a third-party Detonator tweak to force it on?

No, the r4 sync just limited the frames.. but didn't match the screen sync so you get occasional 'tear' if you're watching for it. In the Radeon triple/vsync/framelimit solution, it just kept the models/scenes/effects from moving too fast (I assume.. didn't try it with the R4 limiter off and triple buffer on).
Which honestly was really handy, if that's what kept it at a decent rate.

I may boot the other machine and try it again. In the meantime, did you see the same thing happen on your machine, Teleguise?

Still wondering why there's such a HUGE stall when the new PBuffers are added. It's weird. Almost like it's trying to kick everything over to system RAM or something. Perhaps I'll try turning off the AGP window; force it to use only the on-card memory..

Er, that last one was me. Didn't realize it'd logged me out.