Page 1 of 1

I don't recommend using -d3d for recordings

Posted: Thu May 29, 2003 11:24 am
by Haze
its known to break the timing on several games completely and since it affects playback obviously has subtle effects on the timing in everything, this is caused by a bug which we haven't managed to locate therefore I think anything recorded with -d3d should be invalid, it could be changing more than meets the eye.

Posted: Thu May 29, 2003 11:44 am
by Chad
that's not a bad idea, so far any zlk recording i playedback with -d3d seems to work. But that doesn't say anything about a monster recording twice the length where there might be a problem we can't see that Haze thinks might be there. I guess you have to question what benefits you get from -d3d and see if they can be achieved elsewhere. For me all it does is ghost up the image, though i haven't tried -d3d -nofilter yet.

Posted: Thu May 29, 2003 7:08 pm
by zlk
Invalidate all my version 68 recordings because I used d3d? :cry:

I recorded 7 inps using d3d. Only three of them require d3d to be enabled to playback correctly. I really don't want to play enduro racer ever again. To be honest, I don't want to play any of the games I recorded in 68 ever again either. :lol:

For my version 69 recordings I have not used d3d to record, nor will I for future recordings. I learned my lesson with people having playback troubles with enduro racer and vicious circle.

RE

Posted: Thu May 29, 2003 7:38 pm
by QRS
I don´t think you need to delete thos recordings John! As long as they playback with the d3d thingie, and you say so in the description.

Just don´t use it on future recordings until the 'bug' is solved :)

Posted: Thu May 29, 2003 11:06 pm
by mahlemiut
For Vicious Circle and other games that use CHDs, it would be a good idea to remove/rename the .dif file before recording and playback.

Posted: Sat May 31, 2003 11:14 am
by Kale
mahlemiut wrote:For Vicious Circle and other games that use CHDs, it would be a good idea to remove/rename the .dif file before recording and playback.
Probably they enter into NVRAM stuff...