Connection seems fine! Where is the log file located?

2 minutes ago, Cpt_Piett said:

Connection seems fine! Where is the log file located?

That's good to hear!

Log is in %appdata%\DynamicLOD_ResetEdition\log, which is usually C:\Users\<username>\AppData\Roaming\DynamicLOD_ResetEdition\log. Open the file with today's date.

2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address TLOD VR: 0x28AF762043C / 2795879138364 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address TLOD: 0x28AF7620334 / 2795879138100 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address OLOD VR: 0x28AF7620448 / 2795879138376 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address OLOD: 0x28AF7620340 / 2795879138112 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address CloudQ: 0x28AF7620378 / 2795879138168 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address CloudQ VR: 0x28AF7620480 / 2795879138432 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address VrMode1: 0x28AF7620318 / 2795879138072 

19 minutes ago, Cpt_Piett said:

2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address TLOD VR: 0x28AF762043C / 2795879138364 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address TLOD: 0x28AF7620334 / 2795879138100 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address OLOD VR: 0x28AF7620448 / 2795879138376 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address OLOD: 0x28AF7620340 / 2795879138112 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address CloudQ: 0x28AF7620378 / 2795879138168 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address CloudQ VR: 0x28AF7620480 / 2795879138432 
2024-02-15 00:31:30.374 [DBG] [ MemoryManager:MemoryManager      ] Address VrMode1: 0x28AF7620318 / 2795879138072 

The bit above it where it shows offsetModuleBase eg.

2024-02-15 07:02:01.012 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368
2024-02-15 07:02:01.116 [DBG] [ MemoryManager:MemoryManager      ] Boundary tests passed - memory writes enabled

You are running 0.3.7 right? They look like old codes that do not check out 😄 (In case my humour has been lost on you,  I am laughing at my own Star Wars joke about your forum name's character, not at you. ) ie. it should say MemoryManager:GetMSFSMemoryAddre not MemoryManager:MemoryManager for those lines.

Edited February 15, 20242 yr by Reset XPDR

0.3.6 actually, didn't know there was a newer version. No entries with offsetModuleBase in the log. I'll download 0.3.7 and report back!

0.3.7 (also connecting properly in SU15 beta): 

2024-02-15 00:56:46.757 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
2024-02-15 00:56:46.793 [DBG] [ MemoryManager:MemoryManager      ] Boundary tests passed - memory writes enabled 

21 minutes ago, Reset XPDR said:

They look like old codes that do not check out

Ah, good one! 😄

Edited February 15, 20242 yr by Cpt_Piett

4 minutes ago, Cpt_Piett said:

0.3.7 (also connecting properly in SU15 beta): 

2024-02-15 00:56:46.757 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368 
2024-02-15 00:56:46.793 [DBG] [ MemoryManager:MemoryManager      ] Boundary tests passed - memory writes enabled 

Ah, good one! 😄

Excellent. Turns out SU15 didn't change the memory map, but I'm still glad I put in the auto offset search functionality in case it didn't.

Thanks for the valuable feedback!

Phew

The new AutoLOD variant of DynamicLOD_ResetEdition is coming along well. The design criteria has been to keep it as simple as possible, but still allow some key parameters to be set. In doing so, I have found that OLOD changes make very little difference to FPS and, when regularly changing automatically like this program does, it can actually increase stutters, so I have pared this version down to only adjust the two settings that have the biggest impact on FPS, namely TLOD when CPU-bound and Cloud Quality when GPU-bound. This may distress some who would also like to adjust OLOD and if that is you then the original DynamicLOD_ResetEdition will still be updated and there to fulfill your wildest LOD-adjusting dreams.

Basically, you will set a target FPS and a tolerance percentage band for the app to activate when outside of. You set a TLOD minimum and maximum and a TLOD step max for both up and down. Until I get GPU load detection working, cloud quality will be disabled, so that's about it for now setting wise.

The auto logic I have written will trigger when your FPS goes outside the target FPS by more than the set tolerance. Whether TLOD actually changes and by how much depends what flight state your aircraft is currently in. If you are on the ground and stopped, the auto function will work quickly at double the TLOD Step Max until it gets close to achieving your target FPS. Once you start moving on the ground, your TLOD will lock until you either stop again or are in the air.

Once in the air, TLOD can now change but on a sliding scale from 0 to the TLOD Step Max rates when you cross 1000 ft AGL to minimise the chance of stutters on takeoff. From there it will continuously adjust TLOD as required at the TLOD Step Max rates to maintain your FPS target until you descend through 1000 ft AGL when the sliding scale reduction cuts in again, this time to minimise the chance of stutters on landing. On landing roll and until you stop, your TLOD will remain locked. That's pretty much it.

I've tested it quite a bit today in the LA area and it was working quite well. On the ground with a lot of traffic, my TLOD was down as low as 70 to maintain FPS target but as soon as I took off out to sea the TLOD steadily climbed towards 300. Turning back towards the city and the airport saw the TLOD slowly dwindle down towards around 120 for landing. All the while my FPS was relatively steady around my target FPS and the TLOD adjustments were as smooth as I have experienced with DynamicLOD_ResetEdition.

Anyway, the code is still very experimental but the results so far are promising. Here's two screenshots showing the same scenario at KSEA, one with no AI traffic and the other with FSLTL loaded, showing the automatic reduction in TLOD to maintain close to 40 FPS.

Edited February 15, 20242 yr by Reset XPDR

Can you just confirm how the step max value works please? Like in this example with it set to 5.

Edited February 15, 20242 yr by abennett

4 hours ago, Reset XPDR said:

This may distress some who would also like to adjust OLOD and if that is you then the original DynamicLOD_ResetEdition will still be updated and there to fulfill your wildest LOD-adjusting dreams.

Lol! Although I suffer from chronic tweaking syndrome, I might actually prefer the AutoLOD version due to its simplicity. Thanks 🙏 for your ongoing work on this!!

7 hours ago, abennett said:

Can you just confirm how the step max value works please? Like in this example with it set to 5.

It is very similar to what's in DynamicLOD_RestEdition, whereby this setting restricts LOD changes to this rate per second, with a setting for both up and down directions. New in this version is a doubling mode to get you more quickly to the right TLOD when on the ground and stopped. Also, it is not optional with AutoLOD as this is a required mechanism to get automation to work.

Edit: In saying this, I just realised the setting is not so much a max, but a nominal rate once within reasonable range of your FPS tolerance. As such, I've since removed the word Max from the label.

Edited February 15, 20242 yr by Reset XPDR

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.

9 hours ago, Reset XPDR said:

It is very similar to what's in DynamicLOD_RestEdition, whereby this setting restricts LOD changes to this rate per second, with a setting for both up and down directions. New in this version is a doubling mode to get you more quickly to the right TLOD when on the ground and stopped. Also, it is not optional with AutoLOD as this is a required mechanism to get automation to work.

Edit: In saying this, I just realised the setting is not so much a max, but a nominal rate once within reasonable range of your FPS tolerance. As such, I've since removed the word Max from the label.

Default it is set to 5. Is that working for all ac ? Using 2 gives more slow/smooth transitions if am correct.

But how to know what is the best for your ac ? Some fly small GA ac and others fly jetliners…

 

54 minutes ago, GSalden said:

Default it is set to 5. Is that working for all ac ? Using 2 gives more slow/smooth transitions if am correct.

But how to know what is the best for your ac ? Some fly small GA ac and others fly jetliners…

 

In my testing, 5 seems a good balance for all aircraft types I have tried (Caravan through to Concorde!). I am considering a speed related adjustment so that at faster speeds the rate is reduced because the scenery is loading changing quicker as you traverse it even without a TLOD change, and vice versa, but I haven't had cause to implement it yet.

Edited February 16, 20242 yr by Reset XPDR