-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vsync option is creating a problem with controller input. #31
Comments
I will try to get another build out by year 6 |
Time is now! It appears that the Dx9 commit has introduced incredible input / rendering lag. There is online game ship movement-stuttering that might be related to the Dx9 version. It is my opinion that the Dx9 project was submitted and merged before it was finished and proven functional. Consequently, we have been playing with a dysfunctional game ever since. What is needed is a true Dx7 version brought up to date without the commit that doofus & KGJV submitted. After the original commit, VS was able to build both the Dx7 and Dx9 version of the game allowing those who were crippled by Dx9 to use Dx7 instead. Shortly thereafter, a merge took place and the option to build the Dx7 was removed. BT has created a Dx7 rendering version of the R7 game however, it still contains the Dx9 stuff and exhibits the same problems so it appears that it isn't the rendering engine causing this problem. Anyhoo, KGJV has rebuilt TRAC on github (somewhat) and it seems possible that the Dx7 version could be ported forward bypassing the Dx9 merge altogether. |
Are you seriously suggesting that DirectX 7 should be used? |
Obviously I am. It's do-able, it can run parallel to the Dx9 version and we would have a functional game once again. |
This is now being done at FAO. The current non Dx9 based on build 248 works perfectly and doesn't exhibit the imposed lag the Dx9 project brought. |
sweet |
Even with the option to toggle vsync turned to "on", it does not return the behavior back to normal as was in R4.
I repeated Imago's step to revert this option to it's pre R5 state and my 5 year joystick issue disappeared. Sorry for blaming you all these years Imago,...it turns out that you had the solution all along.
Please see:
http://trac.alleg.net/changeset/622/allegsvn
Oh, and the 2048 setting in wintrek.cpp needs set back to 512 when the vsync thing is corrected.
The text was updated successfully, but these errors were encountered: