Can this be installed at the same time as the other version?

Just now, abennett said:

Can this be installed at the same time as the other version?

Yes it can. It installs to a different directory under the same Roaming sub directory.

Just don't run them both at the same time, which is not actually possible if you run the new app second as it detects whether the original app is currently running. It is possible to start the new app before the original one and the original one won't flinch because 0.3.7 is not aware of this new app's existence (0.3.8 will). It's just best to not run two app like this at the same time, so just be aware of this latter possibility.

Awesome, will give it a go.

 

One more question, sorry! 
 

How does the FPS target work with Frame Gen?

Not sure whether to set it to real native sim frames, or how many I want when frame gen is working.

Also I wonder what will happen with this when for example you click on a non MSFS application whilst FG is running. For example using navigraph on a second monitor. This stops FG working so the FPS would half. Would be bad if the TLOD kept changing because you clicked off screen, I guess in that case it would be easier to have it linked to real frames rather than FG frames, if that makes sense.

 

12 minutes ago, abennett said:

How does the FPS target work with Frame Gen?

Not sure whether to set it to real native sim frames, or how many I want when frame gen is working.

I use frame gen and set it to native fps. 

12 minutes ago, abennett said:

Awesome, will give it a go.

 

One more question, sorry! 
 

How does the FPS target work with Frame Gen?

Not sure whether to set it to real native sim frames, or how many I want when frame gen is working.

Also I wonder what will happen with this when for example you click on a non MSFS application whilst FG is running. For example using navigraph on a second monitor. This stops FG working so the FPS would half. Would be bad if the TLOD kept changing because you clicked off screen, I guess in that case it would be easier to have it linked to real frames rather than FG frames, if that makes sense.

 

Yes, I opened Pandora's box when I implemented FG detection in DynamicLOD_ResetEdition as it creates as many new problems as it solves. MSFS2020_AutoFPS uses the same detection code but I just haven't tested it out yet, so it would be good if you can let me know if those issues happen (which I'd say they will!).

If so, in the interest of keeping the new app as simple as possible, I may just disable the FG detection and users can just deal with the FPS only showing half what you are getting when MSFS has the focus, but at least the FPS target will be accurate.

 

Yeah I think this would be better. 

For example I would probably set something like 30 native knowing I’ll then get 60 with FG.  And then id still be happy with it at just 30 fps and keeping the LODs when I’m on another application.

This would be better than setting a target of 60 with it taking FG into account and then every time I click on second monitor or a different program it chopping the LOD to have to get twice as many FPS to get the target of 60 without FG helping it.

 

Hope that makes sense!

6 minutes ago, abennett said:

Yeah I think this would be better. 

For example I would probably set something like 30 native knowing I’ll then get 60 with FG.  And then id still be happy with it at just 30 fps and keeping the LODs when I’m on another application.

This would be better than setting a target of 60 with it taking FG into account and then every time I click on second monitor or a different program it chopping the LOD to have to get twice as many FPS to get the target of 60 without FG helping it.

 

Hope that makes sense!

I can't remember whether I fixed this or not in DynamicLOD_ResetEdition. Too much coding in the last few days 😄

Edit: Yes I think I fixed that so that FG is only detected if you are running DX12, not in VR, and MSFS is the focussed window, otherwise it is considered off.

Edited February 16, 20242 yr by Reset XPDR

3 hours ago, Reset XPDR said:

If anyone would like to help me out by trialing my new MSFS2020_AutoFPS concept demo, which you can find here, and providing feedback, I would much appreciate it. A detailed description of the functionality developed so far is provided at this link.

 

 

@Reset XPDR

First of all: I would AGAIN like to thank you for this new Tool, AutoFPS!

I have tested it extensively this morning and it works like a charm. My FPS was so stable and I could follow the "changes in TLOD" so smooth and so "self explained"

I have tested this with the new MSFS BETA and in ocmbination with my 7900X3d RTX 4090 and with, as well without, VR (Varjo Aero) in a scenario, where I knew my FPS will hover "around" the target FPS, in my case 45, to keep VR smooth (1/2 of 90Hz HMD refreshrate)

Here in EDDF Scenery I have photogrammity as well procedural Buildings/Objects and so I could really good see how this impacts the "drawing" lines (TLOD Distances)

Its another MUST have addon and also my prefered one above the DynLod Reset Tool you have developped.

I have ONE further wish:

I would like to set my own FIX OLOD value. The tool fixes it on 125. Is that right? Regardless of my OLOD PC or VR OLOD settings, right?

In my case, and maybe the VFR flyers too, I would prefer to change that value, as a fix value, to a distance (OLOD) what my maschine is capable to handle as OLOD objects (also the details on Streets that are drawn are OLOD) look better when flying over them at 5000 feet for instance with 150 or 175 instead of 125. 

Are you planning and willing to change that? That would be awsome!

THANKS a lot and now I will fly with your new Tool! AutoFPS! So great!

Cheers, Marcus (from EDDF) 

Edited February 16, 20242 yr by mpo910

I guess I’ll just give it a try and see what happens. But it sounds like as it is, as soon as FG stops running because MSFS isn’t the focused application, it will reduce the LOD to try and get the same FPS as I was getting with FG running.

51 minutes ago, abennett said:

Also I wonder what will happen with this when for example you click on a non MSFS application whilst FG is running. For example using navigraph on a second monitor. This stops FG working so the FPS would half. Would be bad if the TLOD kept changing because you clicked off screen, I guess in that case it would be easier to have it linked to real frames rather than FG frames, if that makes sense.

Just tried it and it does exactly what you predicted. I may be able to tweak the code to manage this particular scenario. Stay tuned.

7 minutes ago, mpo910 said:

I have ONE further wish:

I would like to set my own FIX OLOD value. The tool fixes it on 125. Is that right? Regardless of my OLOD PC or VR OLOD settings, right?

In my case, and maybe the VFR flyers too, I would prefer to change that value, as a fix value, to a distance (OLOD) what my maschine is capable to handle as OLOD objects (also the details on Streets that are drawn are OLOD) look better when flying over them at 5000 feet for instance with 150 or 175 instead of 125. 

Are you planning and willing to change that? That would be awsome!

As currently implemented, the app doesn't set your OLOD at all, rather it just reads what you already had it set to and that value remains static unless you go into MSFS settings and change it yourself. ie. there is nothing stopping you setting your OLOD to what ever you like, the app just displays the current setting. As such there is nothing that need changing for this. Does that make sense?

Edited February 16, 20242 yr by Reset XPDR

2 minutes ago, Reset XPDR said:

unless you go into MSFS settings and change it yourself.

During my flight I did went into the MSFS Settings and changed my OLOD to 150, the AutoFPS was not showing the new set value. 

I did not test if it was maybe still detecting it and handling it as well (so just not showing).

Do I need to restart the app to take advantage of the new set value? I tested it in VR  mode active.

 

Edited February 16, 20242 yr by mpo910

5 minutes ago, mpo910 said:

During my flight I did went into the MSFS Settings and changed my OLOD to 150, the AutoFPS was not showing the new set value. 

I did not test, if it was maybe still detecting it and handling it as well (so just not showing).

Do I need to restart the app to take advantage of the new set value? I tested it in VR  mode active.

 

The danger of reusing existing code is that sometimes it does something like this that you did not expect. Turns out the original app only needed to read PC mode OLOD because whenever it set them it set both VR and PC so checking both was not necessary. Now that OLOD is left alone, I should also read VR OLOD when in VR, which will fix your issue completely. I will fix this for the next release. Great pickup!

BTW, in the interim, MSFS is using the new OLOD you set in VR, it's just that the app is not displaying it correctly, so be confident that you are using the right OLOD.

Edited February 16, 20242 yr by Reset XPDR

17 minutes ago, Reset XPDR said:

I will fix this for the next release.

Thanks for looking into it! Much Appreciated!

2 minutes ago, mpo910 said:

Thanks for looking into it! Much Appreciated!

Already fixed. Will be in the next release.