truth5678 wrote:Post a video of the "tearing" and specs of the monitor/video/OS.
Late reply but better than never xD
And the problem is still there so..
Watch any Blood video of this list: https://www.youtube.com/playlist?list=PLQmYRU … XU_Oc8zzN-jPZGc
All videos have tearing. You can try to catch it while pausing the video. Here an example frame:
http://abload.de/img/unbenannt1789rskz.png
It doesnt disturb ME so much, but it disturbs a video encoder. Blood is good compressable, but for youtube quality every way more compressable saves more quality on them. And a video with tearing will degrade video encoding efficiency.
My monitor should be irrelevant, because its not monitor tearing if the tearing is still on a recorded video file, but:
Its a NEC PA302W-BK-SV (30", 2560x1600, 60hz)
OS is a windows 7 x64 ultimate.
I use dosbox svn daum of this site: http://ykhwong.x-y.net/
output is at direct3D and the vga device is the vesa_nolfb. CPU cycles is set to automatic.
Blood runs with a maximum of 70fps, vsync with 60hz doesnt help. If vsync at 70hz would help I dont know. But I dont think so. And the fps rate is good, but a flat 70.0000 is not that common with emulation I would say. its swapping around 60 and 70.
And I believe I mentioned it already earlier but again:
Why the renderer does IDLE if there is no action on the screen? It is really really annoying for recording software. Because they idle then too until they get a new frame. Especially if you want to end the recording, you have to move the mouse before closing the recording if the renderer is idling, because otherwise if dosbox doesnt send any frame anymore the video encoder of course closes the file at the last received frame, means an earlier closed video than wanted. Also it is bad while recording when the renderer does idle.
Why you do that? Make it please at least optional. Or is it a behaviour of the direct3D output and I have to tell that the devs of the ykhwong daum svn version?