What pains me most in this regard, is the original Prey, which is a game that I love, but which uses an even older version of id Tech 4. I think it is unfortunate that some of these awesome shooters are hard or impossible to fix for high frame rates, since these types of games benefit immensely from it.
#QUAKE 4 VS DOOM 3 HOW TO#
It might also be helpful to take a deeper look at how the problem was tackled in the BFG edition and maybe get some inspiration for how to do it. Now, I think your best bet is to adjust the constants and by hand just try to fix every additional problem that occurs. This also makes sense, because, as far as I know, the BFG edition was developed from the original source code, with some backported featured from id Tech 5. The latter uses a different mechanism than the original, but it is still not the same as what can be seen in Quake 4. Unfortunately, neither the Doom 3 nor the Doom 3 BFG code features this implementation.
#QUAKE 4 VS DOOM 3 MOD#
The mod hooks these functions and adjusts their returns according to the FPS limit that was configured by the user. This makes it possible to adjust everything on the fly. These functions are called every frame from the engine and seem to be used throughout the code to calculate the corresponding timings. In that game, the above constants were merged into two additional functions in idCommonLocal, which I called GetUserCmdHz and GetUserCmdMsec, because they basically return computed values for the aforementioned constants. The version of id Tech 4 that Quake 4 uses is more advanced than what was released for Doom 3 which makes sense considering it came out a few years later. As far as I know, this would be the way to go to adjust the frame rate limit. You are all on the right track and already discovered the USERCMD_HZ and USERCMD_MSEC constants. I am afraid the solution I used for Quake 4 is not applicable to Doom 3. Hi there, I am the author of the Quake 4 Tweaker mod.
0 kommentar(er)
