PleasantCheese / glidehqplusglitch64

Automatically exported from code.google.com/p/glidehqplusglitch64
0 stars 0 forks source link

Vertical Syncrinization (Vsync) wont work in newer versions of Glide64 #22

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

Have Glide64 Napalm 1.1 or higher is the only known circumstance.
Napalm 1 (perhaps older?) doesn't have the problem.

What is the expected output? What do you see instead?

With Vsync checked in the options I would expect it to work, however it
does not. In moments of movement and camera panning the screen tears quite
a bit.

What version of the product are you using? On what operating system?

As stated above, on Glide64 Napalm 1.1 or higher, vsync doesn't appear to
work, however on Napalm 1 (perhaps older?) vsync appears to function. I am
using Windows 7 Ultimate 32bit with Project 64 1.7.0.49.

Please provide any additional information below.

I have done many tests to rise to this conclusion, I have tested all
versions newer then Napalm 1 (and Napalm 1 itself), have attempted to force
vsync on within the Nvidia control panel (making sure to turn it off after
tests with it on were concluded [note, I did have triple buffer force on
for all tests of forcing vsync on in general]). The overall settings were
fairly consistent between all tests (taking into account version specific
settings), also in the Nvidia control panel anti-aliasing was force to 16Q
on all tests, and anisotropic filtering was forced at 16 as well. My
monitor can only support 60Hz and 75Hz, both produce the same results,
however I'm forced to use 75Hz on Napalm 1.

My computer's specifications are as follows:

CPU - AMD 3800+ Dual Core 2Ghz overclocked* to 2.3Ghz or 2.4Ghz (I must
state that my computer is a upgraded Dell Dimension E521 what limits my
ability to overclock at all). FSB set to 230 or 240 from 200, not other
settings have been changes

GPU - Nvidia Geforce 8600 GT overclocked* by 20% with latest drivers (Core
clock set to 648 from 540, shader clock set to 1250 from 1188, and memory
clock set to 840 from 700, all other hardware settings default).

Soundcard - Soundwave 7.1 PCI with none standard drivers (
http://code.google.com/p/cmediadrivers/ )

RAM - 2Gbs (4 seprate chips or 512Mbs each, two that came with computer) of
DDR2 DIMM ram

Motherboard - Nvidia Nforce4 6150 LE**

Harddrive - Western Digital 320GB Hard Drive

Monitor - Came with my Dell, LCD display, only works at 60Hz and 75Hz.
(Sorry, that's all the information I have about it). On 75Hz color quality
degrades slightly but noticeably.

Operating system - Windows 7 Ultimate 32bit

Everything else is stock for a Dell Dimension E521

*Overclocks have been tested stable far before this problem occurred, in
the case of the CPU I sometimes set the FSB to 240 for a extra boost but is
slightly unstable but poses no true problems; FSB set to 230 is completely
stable.

**This model came with computer, but has been replaced once by identical
model by warranty (something fried in it, not sure what).

That's about all I can tell you, sorry.

Original issue reported on code.google.com by Sisims...@gmail.com on 26 Dec 2009 at 10:13

GoogleCodeExporter commented 8 years ago

Original comment by mudl...@tpg.com.au on 27 Dec 2009 at 8:16

GoogleCodeExporter commented 8 years ago
I have the exact same problem. But the difference is i have a Radeon HD 4870.

Original comment by m.suss...@gmail.com on 5 Jan 2010 at 6:06

GoogleCodeExporter commented 8 years ago
Cannot reproduce on my system sorry.

Original comment by mudl...@tpg.com.au on 5 Jan 2010 at 8:05

GoogleCodeExporter commented 8 years ago

Original comment by mudl...@tpg.com.au on 17 Feb 2010 at 1:43

GoogleCodeExporter commented 8 years ago
Now I can reproduce. 

I am pulling my hair out: the code looks fine for Vsync....

Original comment by mudl...@tpg.com.au on 2 Mar 2010 at 6:25

GoogleCodeExporter commented 8 years ago
Which games are you having this problem?  
I would like to try these games if I have them.  
I am using 1964 and it only improves performance and yet to see any tearing.

I set V-sync in nVidia Control Panel to "Use the 3D application setting" and 
triple
buffering to "On".

Original comment by pokefan0...@gmail.com on 13 Mar 2010 at 2:01

GoogleCodeExporter commented 8 years ago
I am quite sure V-sync is working and it is quite obvious when it is checked 
for Resident II which see a reduction in the amount of tearing from screen 
change.

Original comment by pokefan0...@gmail.com on 30 Aug 2010 at 3:38

GoogleCodeExporter commented 8 years ago
So is this still valid?

Original comment by ExtremeD...@gmail.com on 18 Aug 2011 at 12:47

GoogleCodeExporter commented 8 years ago
Being the one who originally posted this, I can say that on my computer it no 
longer happens, but I have basically replaces every part of my computer since I 
first posted this, so it seems that it was a very specific problem few people 
will ever have or has been fixed. Since it seems to be too difficult to find 
the problem, it might be better for everyone in terms of spent time if this 
issue is closed, but that's my opinion because of the difficulty to fix, if 
anyone is still effected by this then it's a small very rare problem that might 
never be fixed. Not being a developer, it's not my call I just got the email 
because of your post and it reminded me of the issue and I wanted you to know 
that at least for me the problem is no longer a problem. 

Original comment by Sisims...@gmail.com on 19 Aug 2011 at 2:52

GoogleCodeExporter commented 8 years ago
I had the same issue with my ATI Radeon HD3850, the regular 'vsync' option in 
the plugin haven't enabled vsync, tearing was still there. However I just 
enabled it in the ATI Catalyst Control Center and now it works fine.

Original comment by fix94.1 on 8 Jan 2012 at 2:28

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
The problem has to do with Windows 7 and the Aero extensions. When Aero is 
disabled Vsync no longer functions and when it is enabled Vsync functions as 
expected.
I have tested this on two separate Windows 7 x64 based systems; one an AMD 
based and the other Intel based. Both use Nvidia graphics cards.

Original comment by proskel...@gmail.com on 18 Aug 2012 at 8:52