3 hours ago, baxterbj said:

Thanks for this wonderful product.

But I'm having difficulty trying to get the latest version running.

I've uninstalled the old version and and reinstalled the new version of 6 hours ago.

I copy the file to my DYNAMICLOD folder, run as administrator and it comes up with the old version of 0.3.7

I've totally removed old version 0.3.7 test from roaming.

What am I doing wrong?

 

Regards BJ from Oz

Unless you are switching over from Fragtality's DynamicLOD any version to my DynamicLOD_ResetEdition any version, which install to different directories, there is no need to uninstall an older version before you install a new one. In fact, you will lose any config settings by uninstalling an older version first as it deletes the entire app directory including your config file, so if you want to keep your config you are best off not uninstalling first.

It doesn't matter which version of my you want to use, the process is the same. Download the installer for the version you want to use, run the installer, choose your autostart option. Tthen when installation is complete either start MSFS and the app should start about halfway through the loading process if you chose one of the autostart options or ff you didn't, just click on the DynamicLOD_ResetEdition icon it should have placed on your desktop. No copying files or running as administrator should be required.

Edited February 8, 20242 yr by Reset XPDR

7 hours ago, Reset XPDR said:

Run the installer associated with the one you want to remove/delete and there is a remove option on the first window. That's the cleanest way.

Easy, thanks for that.  

On 2/7/2024 at 1:54 AM, MNORM said:

Anyone else getting a permanent TLOD: 0  OLOD: 0  displayed in the box in version 3.6? Previous versions worked but this one doesn't seem to change the values as I fly.

For anyone else who experiences this issue, the problem turned out to be a conflicting older version of Mobiflight installed that needed to be removed, then the DynamicLOD installer reinstalled the latest version and fixed the issue.

Latest 0.3.7-test version (08Feb24 2100Z) can be found here with:

• FG detection - enhanced to show correct FPS drop when MSFS window loses focus and FG gets disabled while ever MSFS is not the focused app (normal FG behaviour).
• Log file cleanup - disabled Mobisim exit code that causes spurious exceptions and log file entries until I can work out what the issue is, hopefully with @Fragtality's assistance as the issue is present in his versions too. Nil impact to MSFS or app functionality as it only happens when exiting MSFS where neither program no longer cares about previously shared variables anyway.

I am getting close to formal release of 0.3.7. I just want to see if I can get some auto update checker on app start functionality working but if it gets too hard I'll just roll it into a future release.

I have received some feedback on 0.3.7-test and nothing app breaking has been reported. If I don't get any reports of the boundary test failing on anyone's setup, ie. seeing the message Simulated memory boundary test failed - please notify ResetXPDR! ), then I will be activating the memory read only limitation in the release version if the boundary test has failed. As such, speak now if you have seen this message at any time.

 

Mr Reset, your an absolute Legend  and we here are very lucky to have you , thank you very much Sir on behalf of this community  for all the hard work you are doing !, this will not be forgotten 

Please have some sleep !

21 minutes ago, sonny147 said:

Please have some sleep !

Haha, I do get plenty of sleep. I am retired, so this is a labour of love that I do mainly in the daytime, in Australia, and mostly when I am in cruise mode of a flight I would be doing anyway. Also, I have been invigorated by learning a new programming language and development environment. I was initially doing this for self interest but it turned out other people liked what I did and here we are today!

Things will likely be slowing down after 0.3.7 release as I believe I will have covered most essential functionality people are after and the app will be robust enough to survive a major change to the MSFS memory map, so it will be down to nice to have's on my functionality wishlist. I will however be keeping an eye on SU15, as it is reportedly changing memory handling and could therefore break this app, so hopefully people on the SU15 beta will alert me if anything does break and I'll see what I can do to fix it, preferably before SU15 formal release.

Edited February 8, 20242 yr by Reset XPDR

your a Star , enjoy your retirement , 6 years to go for me ,thank you for your work !

6 hours ago, Reset XPDR said:

Latest 0.3.7-test version (08Feb24 2100Z) can be found here with:

• FG detection - enhanced to show correct FPS drop when MSFS window loses focus and FG gets disabled while ever MSFS is not the focused app (normal FG behaviour).
• Log file cleanup - disabled Mobisim exit code that causes spurious exceptions and log file entries until I can work out what the issue is, hopefully with @Fragtality's assistance as the issue is present in his versions too. Nil impact to MSFS or app functionality as it only happens when exiting MSFS where neither program no longer cares about previously shared variables anyway.

I am getting close to formal release of 0.3.7. I just want to see if I can get some auto update checker on app start functionality working but if it gets too hard I'll just roll it into a future release.

I have received some feedback on 0.3.7-test and nothing app breaking has been reported. If I don't get any reports of the boundary test failing on anyone's setup, ie. seeing the message Simulated memory boundary test failed - please notify ResetXPDR! ), then I will be activating the memory read only limitation in the release version if the boundary test has failed. As such, speak now if you have seen this message at any time.

 

I had a good day coding so here is the latest, and likely final, 0.3.7-test version with what is listed above and:

• Update checker - I am pretty confident I have the new update available checker code functioning correctly and just need a couple of people to verify that it detects 0.3.6 as the latest formal release and that the update link takes you to my github latest release page here, which is currently 0.3.6. Please let me know if the link does not open in your browser and take you to the right page. Your app window will look like this up until you are in a flight then it will be replaced with what was there about PC mode and MSFS version compatibility like before:
  
  
  
  When 0.3.7 gets formally released you should see a message telling you to update from the test version, like this:
   
• 
   
• Compatibility checker - since I have had no reports of incompatibility messages in all the 0.3.7 test releases, I have gone ahead and made the read only restriction on detected incompatibility function active instead of message only up until now. Pending no reports of this actually activating with the current MSFS version, this code will go live when 0.3.7 gets formally released in a few days. Again, speak now if it bites you in this test version! This is what read only restricted mode will look like, noting LODs and clouds should be changing but are not:
  
  

 

Edited February 9, 20242 yr by Reset XPDR

Any feedback on the latest 0.3.7-test version I posted yesterday?

The main thing I want to know is whether at least one of you is seeing this screen and the update link takes you to my github latest release page here, which is currently 0.3.6.

I had an incompatable version with the one from yesterday ( first time any issues ) so went back to one before . iam flying now can try again  if you like ?

I had an epiphany today that if the app can now check that the current MSFS memory addresses are still valid, but if they weren't why can't it also use that same check to find where they moved to and then use them without skipping a beat! I have coded it up and ran a mock test where the app tried to use the old offset in the muumimorko version, that no longer works in that app because the offset changed a couple SUs ago thus breaking it, and it detected the issue, found the correct offset, saved it in the config file and the app carried on functioning. It works!

What this means in simple terms is that when SU15 comes out, this app should continue working even if Asobo changes the memory map in a way like they have previously. IMO, this is a significant advance on the "poke and hope" method used by all previous versions of my, and my fellow predecessor developers', app as it not only provides protection again such an external change, but also the ability to recover from it without user intervention.

Anyway, I am excited about it and hope you are too. The code is a bit fresh to put out there just yet, but I do hope to put out a final test version with it in it very soon.

4 minutes ago, sonny147 said:

I had an incompatable version with the one from yesterday ( first time any issues ) so went back to one before . iam flying now can try again  if you like ?

Yes, that would be good. Can you message me the associated log file. Thanks.

dont think i can , i went into app data and deleted the whole folder , i have now re installed the 0.3.7 test version which you posted at 05.33 yesterday morning i would send you a screen shot but dont know how on avsim . if you post your very latest version i can try that iam not doing anything else 

4 minutes ago, sonny147 said:

dont think i can , i went into app data and deleted the whole folder , i have now re installed the 0.3.7 test version which you posted at 05.33 yesterday morning i would send you a screen shot but dont know how on avsim . if you post your very latest version i can try that iam not doing anything else 

If you've reinstalled it, just run it until you get the error message, quit it then go to your C:\Users\<username>\AppData\Roaming\DynamicLOD_ResetEdition\log and open the latest log file, copy all text and paste in a PM to me.