-
Notifications
You must be signed in to change notification settings - Fork 43
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
E3M3 Fiend stuck at any other framerate than 144 #240
Comments
This occurs in Quakespasm as well. I think it might even be in WInquake, but I'd have to check |
If it's in WinQuake, unless it's an obvious bug, then it's probably desirable to retain it. Without further analysis it's possible that it might even be a QC bug, or a content bug, rather than an engine bug, in which case it may be dubious to try fix it engine-side. |
That bug has been around for ages. Lower your max fps to like 50 and the fiend wont get stuck. |
Since I remembered that I saw this bug some loooong time ago more than once, I just tested it in DOS Quake 1.08 and WinQuake and it's present in both. |
Feels like people are maybe missing the point, possibly including the reporter. |
Not necessarily, its even bugged in WinQuake. |
Right, meaning it should continue to be bugged at 144 fps in Ironwail, which it isn't. |
As the title suggests, if the game runs at an other frame rate, the Fiend stays stuck after the button sequence:
1691161172700393.webm
The text was updated successfully, but these errors were encountered: