Pellape Posted February 5, 2021 Share Posted February 5, 2021 Is 0.01 the fastest we can set a fQuestDelayTime to be? I mean, my fps never gets above 100 for sure, but if I want a quest script to suddenly run full speed, should I not try 0.001? ;) I know some claims to run the game over 100 fps... I could even try 0.000001 ;) but when the quest is not in use, I set it to 5 and even stop it from running maybe... Link to comment Share on other sites More sharing options...
DrakeTheDragon Posted February 5, 2021 Share Posted February 5, 2021 I'm not sure what will happen, if you set it to values below of what your game can supply. But I doubt it'll be anything else but skipping those runs which would otherwise start while another one is already running. Link to comment Share on other sites More sharing options...
qwertyasdfgh Posted February 5, 2021 Share Posted February 5, 2021 Scripts will not run more than once per frame, so setting fQuestDelayTime to such low value is basically pointless. Link to comment Share on other sites More sharing options...
Pellape Posted February 5, 2021 Author Share Posted February 5, 2021 (edited) I know. :smile: But what I want to know is really which is the lowest fQuestDelayTime you have ever set? In one way it doesn't matter as when the loops kicks in, they will use the CPU speed anyway and run like Flash!!!! :wink: I hope... Edited February 5, 2021 by Pellape Link to comment Share on other sites More sharing options...
KatsAwful Posted February 6, 2021 Share Posted February 6, 2021 Its the lowest float value possible, which for Oblivion would be insanely small Link to comment Share on other sites More sharing options...
Maskar Posted February 6, 2021 Share Posted February 6, 2021 You could indeed set fQuestDelayTime to a very small value and would still not run more than once a frame. In menumode it's possible to get very high fps. I easily get above 800 when not capped. In LINK I set it to 0.001 for some menus to make sure the sliders work as intended, as 0.01 wouldn't be low enough. Usually you should however keep the value as high as possible, especially in gamemode. Link to comment Share on other sites More sharing options...
Pellape Posted February 6, 2021 Author Share Posted February 6, 2021 (edited) Thanks for the input Maskar. :smile: I decided to set this new quest to run every second when it is not in use and I set the timer to 0.005 when the sorter starts, as this is my quest for a new dynamic chest sorter I wrote about in my WIP. As it use several while/loop 's when scanning stuff, it will not matter anyway what we set. As soon as it is done, it goes back to 1 second. To optimize performance further, I could simply stop the quest to run when it is not in use and start it when it needs to start doing what it is made to do in the first place. I think you do that as well in some of your quests in MOO if I recall right. Edited February 6, 2021 by Pellape Link to comment Share on other sites More sharing options...
Recommended Posts