IF YOU HAVE ISSUES WITH VIEW DISTANCE STAYING LOW:
Make sure you set your desired maximum View Distance in the mod's script settings - it will override whatever you put into the ingame or launcher View Distance fields. To get the equivalent DFPSO value for OpenMW's distant land view distance, multiply the number you used before by 7168. Example: 5 cells view distance in launcher * 7168 -> 35840 maximum view distance for DFPSO.
It's kind of strange. The mod is working, but also not really. The view distance is automatically reduced, but the FPS don't change at all — only when I manually lower the view distance do the FPS go up. What exactly could be the problem here?
I use Openmw 0.49. I'm using the default settings of the mod, and when the framerate drops, the view distance is visibly reduced — but without any FPS gain. However, if I manually lower the view distance through the in-game menu, the FPS increase significantly. I'm no expert, but it seems like everything is still being rendered in the distance, just with some fog placed over it.
Any plan on the upcoming updates to adding this feature? On pc this can be ignored since UI didn't take much on screen. But on mobile the pop up is jarring lol
So far this appears to compete with limitless scaling in terms of performance, without the additional energy cost. Good Job! Do you have recommended settings?
Recommended settings are tough to speak about without knowing your specific setup, since a lot of recommendations depend on things like your refresh rate, what your "average" perf looks like, how heavy your mod setup is and so on. The guidelines in the description are meant to give a rough idea and I can only repeat them here: Put your target and tolerance such that the perf in non-stressed areas exceeds them, use the lowest "change per frame" value you're comfortable with, put your gridlist threshold somewhere it doesn't trigger often.
I have not investigated that mod extensively but from what I understand it does most of the same thing as DFPSO in a different way. I assume using both together would lead to issues, and since they overlap in intent and functionality I don't see why you'd want to pair them either... DFPSO of course doesn't have a secondary .exe file to run alongside the game, so it is easier in that sense, but MFPSO offers some more direct control over VD if that's more appropriate for your use case. Feel free to sound off if you encounter any issues running them together that I can fix on DFPSO's side though!
Pulling down the view distance does work and increases fps once it's done adjusting view distance, but it also introduces large stutters when moving around and especially in and out of Old Ebonheart. Is this something you can fix by tweaking the settings? I havent been able to.
tested this as well, I have a 6 cell distance, set it to 43008 in the optimiser settings, also tested in Old Ebonheart., also using the total overhaul modlist from modding-openmw.com. I get a lot of stuttering, and the view distance drops to around 2 / 3 cells, with huge pop ins. even places like Balmora and Vivec, the view distance isn't that far, and it stutters a lot when adjusting the view distance.
got a decent rig, 3070 geforce card, 16 gig of ram. with a 10 gen intel. So for the time being I have disabled the mod. maybe the mod could be improved upon, or openmw itself, buut right now, I get less stuttering without the mod then I do with it.
I assume both of you are using the OpenMW version? What you're describing sounds like the view distance changes are happening too aggressively in your setups, which leads to stutter, doubly so if you're on a mod setup where significantly more stuff is being drawn in the first place (like Overhauls). This is a fundamental issue to some degree as neither engine were designed with real time view distance changing in mind, but you may be able to alleviate the problem by changing some settings in DFPSO: 1. Increase the Tolerance around your target framerate. 2. Disable Delta Awareness so stutters don't then exacerbate the problem, leading to a feedback loop. 3. Decrease Change Per Frame by a lot so changes aren't as large.
Since I assume you're running otherwise standard settings you could also decrease the Gridlist Threshold to make DFPSO simply not do anything in more areas of the game. Let me know if these tweaks do anything for you, otherwise feel free to DM me a screenshot of your settings so I can test myself.
Hi! Great mod! But i have mutiple issues like: L864_-1[newDFPSO.lua] onFrame failed. Lua error: [string "newDFPSO.lua"]:193: attempt to call field 'getRealFrameDuration' (a nil value) stack traceback: [string "newDFPSO.lua"]:193: in function <[string "newDFPSO.lua"]:191> L864_-1[newDFPSO.lua] onFrame failed. Lua error: [string "newDFPSO.lua"]:193: attempt to call field 'getRealFrameDuration' (a nil value) then the list repeats indefinitely. I have no idea what is going on wrong, but I've set the View Distance settings according to the recommendations. Maybe it's because I'm using OpenMW 0.48.0, I'm not sure, I haven't seen any clear version requirements.
Is there a feature missing that you're specifically waiting for? I use version numbers mostly to signify milestones I consider important during development, not as relating to distance to full release. I'm currently not actively developing more features for either version so don't be afraid to just jump in rn and let me know if there's something still missing ;) I work on this very much in bursts, either when inspiration strikes or I get a specific feature request that I think it feasible and within the scope of the mod.
Not at all, I was referring to the latest version of OpenMW itself. I would like to upgrade to it when a more or less stable version is released. Although I'm not sure if my device will support it, but I'll hope for the best.
Weird request, but is it possible to add an option to target memory usage instead of FPS? I don't care so much about what the framerate is, but I do care about the game crashing.
A cursory glance at the API makes it look like this could be possible for the MGE version, don't see a way for OpenMW. If you are on MGE I'll be looking into this.
Not at all, I was referring to the latest version of OpenMW itself. I would like to upgrade to it when a more or less stable version is released. Although I'm not sure if my device will support it, but I'll hope for the best.
60 comments
Make sure you set your desired maximum View Distance in the mod's script settings - it will override whatever you put into the ingame or launcher View Distance fields. To get the equivalent DFPSO value for OpenMW's distant land view distance, multiply the number you used before by 7168. Example: 5 cells view distance in launcher * 7168 -> 35840 maximum view distance for DFPSO.
DFPSO OpenMW requires 0.49 RC6!
I'm using the default settings of the mod, and when the framerate drops, the view distance is visibly reduced — but without any FPS gain.
However, if I manually lower the view distance through the in-game menu, the FPS increase significantly.
I'm no expert, but it seems like everything is still being rendered in the distance, just with some fog placed over it.
got a decent rig, 3070 geforce card, 16 gig of ram. with a 10 gen intel. So for the time being I have disabled the mod. maybe the mod could be improved upon, or openmw itself, buut right now, I get less stuttering without the mod then I do with it.
1. Increase the Tolerance around your target framerate.
2. Disable Delta Awareness so stutters don't then exacerbate the problem, leading to a feedback loop.
3. Decrease Change Per Frame by a lot so changes aren't as large.
Since I assume you're running otherwise standard settings you could also decrease the Gridlist Threshold to make DFPSO simply not do anything in more areas of the game. Let me know if these tweaks do anything for you, otherwise feel free to DM me a screenshot of your settings so I can test myself.
L864_-1[newDFPSO.lua] onFrame failed. Lua error: [string "newDFPSO.lua"]:193: attempt to call field 'getRealFrameDuration' (a nil value)
then the list repeats indefinitely.stack traceback:
[string "newDFPSO.lua"]:193: in function <[string "newDFPSO.lua"]:191>
L864_-1[newDFPSO.lua] onFrame failed. Lua error: [string "newDFPSO.lua"]:193: attempt to call field 'getRealFrameDuration' (a nil value)
I have no idea what is going on wrong, but I've set the View Distance settings according to the recommendations. Maybe it's because I'm using OpenMW 0.48.0, I'm not sure, I haven't seen any clear version requirements.
released. Although I'm not sure if my device will support it, but I'll
hope for the best.
The biggest issue with the original engine is that hard memory limitation. Having a safeguard like this would be fantastic!