8 minutes ago, Ixoye said:

Has anyone tested how low you can go in LOD on the ground before you see a deterioration?

On the taxiway I use 50 and to be honest don't notice much difference but everyone is going to be different etc due to pc specs

16 minutes ago, Ixoye said:

Has anyone tested how low you can go in LOD on the ground before you see a deterioration?

 

7 minutes ago, Brocky120 said:

On the taxiway I use 50 and to be honest don't notice much difference but everyone is going to be different etc due to pc specs

I also wouldn't go lower than 50. You don't really see a difference at the airport itself, but whenever there is a mountain range in sight from the airport the low TLOD really starts showing below 50-70.

 

3 hours ago, Noel said:

That looks great except at that size low frame rate will be vastly more discernable than will smaller screen sizes, which has to do w/ the amount of movement per frame displayed.  Maybe in a few more years...

If I can maintain 30fps it's brilliant, partly because you don't need to pan much around the virtual cockpit so it's only the scenery moving (not quickly) outside. You're right tho...if it gets down into the 20s then it is noticeable.

 

Which comes back to my original comment to you about why tools like this are important.

1 hour ago, roland_lfor said:

I may have a look at the code see if I understand something, then if I can extend it to VR.

Would be extremely grateful if you could figure this out! I really do believe it would be a game changer for VR users. 
 

Like Marc said above, if you need any help with testing or anything else give me shout, would be more than willing to offer whatever help I can. 

This Mod was the best Christmas present ever, I will save 200+€, I have no need for a 4090 as it seems right now 👍

2 hours ago, roland_lfor said:

I may have a look at the code see if I understand something, then if I can extend it to VR.

I'd wager a guess and say it's the memory offset in MemoryManager.cs that needs to be changed for VR. 

16 minutes ago, JacquesBrel said:

I'd wager a guess and say it's the memory offset in MemoryManager.cs that needs to be changed for VR. 

The Dev did mention ‘Offsets/Pointers’ in the reply to me on his GitHub page where I raised the issue. He said if I figured out the Offsets/Pointers, to let him know. 

I have no idea about coding but where can I find this MemoryManager.cs you mention? And will I need anything other than Notepad+ to make the changes required? 
 

Thanks for the help!

 

 

Oh my ... look at the Mess I've created 😅 Where do I start ...

First, don't forget this would not even exist without muumimorko and his/her MSFS_AdaptiveLOD - all Credits to him/her. I just copied the Core-Mechanic to a From that I'm more familiar with and suits my Needs better. And reverse-enginereed/calculated my Way through it to get the changed Offsets after the SimUpdate.

Then, it is basically the same Theme as with all of my Tools: I've created the Tool that I wanted and needed. Like everything else, I've shared it to the Public since I see no Reason to lock it away (especially when I'm taking the Idea from another Open Source Tool). It is about Sharing. Look at what some People do in the Reigns of freeware Liveries and Sceneries - or even whole Planes.
The Description is deliberately short and deterrent (my English is quite okay for a non-native Speaker, if I want to 😜). As it was already explained by others it takes a risky Approach. It writes directly to the Memory (like a "Trainer") which poses a bann-worthy Behavior. 
The User really should know what he/she is doing there before going ahead. I don't want to be bothered and certainly not be responsible for anyone's Problems using it.
It is just not intended for the average Joe/Jane out there.
Hope that explains the Mindset a bit better behind the Conflict between "openly shared" and "Readme says not to use it".

That being said: I certainly won't never recommend anyone using it with this Background. Use it at your own Risk, don't complain to me. But as I said initially, I don't code for the Purpose of having a good Joke 😉
There will be zero Support. Already have enough Headaches with other Tools, so please don't open Issues when closing a Window and closing a Program confuses you 😅

As for the Future: don't expect much Evolvement. It does already what is supposed to do.
I had thoughts of copying the Installer over, because it basically uses the same "Skeleton" as FenixQuartz, Fenix2GSX and WorkingTitle2GSX. (Although that would be working against it being deterrent to average Joe & Jane^^)
Seeing the hot-mess it created, I may look into the VR Settings - although I'm already nerved to do Stuff I don't have any Benefit from for People being fancy again 🤪. (And this would not be "fixing" something, because there is nothing "broken".)

14 minutes ago, Fragtality said:

Oh my ... look at the Mess I've created 😅 Where do I start ...

First, don't forget this would not even exist without muumimorko and his/her MSFS_AdaptiveLOD - all Credits to him/her. I just copied the Core-Mechanic to a From that I'm more familiar with and suits my Needs better. And reverse-enginereed/calculated my Way through it to get the changed Offsets after the SimUpdate.

Then, it is basically the same Theme as with all of my Tools: I've created the Tool that I wanted and needed. Like everything else, I've shared it to the Public since I see no Reason to lock it away (especially when I'm taking the Idea from another Open Source Tool). It is about Sharing. Look at what some People do in the Reigns of freeware Liveries and Sceneries - or even whole Planes.
The Description is deliberately short and deterrent (my English is quite okay for a non-native Speaker, if I want to 😜). As it was already explained by others it takes a risky Approach. It writes directly to the Memory (like a "Trainer") which poses a bann-worthy Behavior. 
The User really should know what he/she is doing there before going ahead. I don't want to be bothered and certainly not be responsible for anyone's Problems using it.
It is just not intended for the average Joe/Jane out there.
Hope that explains the Mindset a bit better behind the Conflict between "openly shared" and "Readme says not to use it".

That being said: I certainly won't never recommend anyone using it with this Background. Use it at your own Risk, don't complain to me. But as I said initially, I don't code for the Purpose of having a good Joke 😉
There will be zero Support. Already have enough Headaches with other Tools, so please don't open Issues when closing a Window and closing a Program confuses you 😅

As for the Future: don't expect much Evolvement. It does already what is supposed to do.
I had thoughts of copying the Installer over, because it basically uses the same "Skeleton" as FenixQuartz, Fenix2GSX and WorkingTitle2GSX. (Although that would be working against it being deterrent to average Joe & Jane^^)
Seeing the hot-mess it created, I may look into the VR Settings - although I'm already nerved to do Stuff I don't have any Benefit from for People being fancy again 🤪. (And this would not be "fixing" something, because there is nothing "broken".)

Well, I and many others thank you for bringing the tool back to life, and I appreciate that ultimately you adjusted it for yourself for your own needs thus you don't want any headaches of support but also feel that it should be shared public.

There are many clever people out there like yourself who perhaps one day will look deeper into this or similar programs.

 

20 minutes ago, Fragtality said:

FenixQuartz, Fenix2GSX and WorkingTitle2GSX

Like you say, nothing is "broken." Yet, your tools improve the experience in MSFS.

Thank you!

1 hour ago, Divij said:

The Dev did mention ‘Offsets/Pointers’ in the reply to me on his GitHub page where I raised the issue. He said if I figured out the Offsets/Pointers, to let him know. 

I have no idea about coding but where can I find this MemoryManager.cs you mention? And will I need anything other than Notepad+ to make the changes required? 

MemoryManager.cs is in the DynamicLOD subfolder: https://github.com/Fragtality/DynamicLOD/blob/master/DynamicLOD/MemoryManager.cs

You will need Visual Studio to compile the code. And to figure out the VR offset you will need some tool to poke around in the MSFS memory.

1 hour ago, Fragtality said:

Oh my ... look at the Mess I've created 😅

Well thanks very much for the mess. Best Mess I've ever seen. I could dig around in this and understand a little of what I see but I certainly couldn't even begin to do something like this. I though briefly about how difficult it would be a couple of years ago. Its not difficult to figure out that there is a mountain of difference in performance between TLOD 400 and TLOD 100 on the Ground but not a hill of beans difference in visuals that I can see. I've always felt it was the most annoying thing in MSFS and P3D and FSX but you sure have cured it and I'm happy to take the risk. Its gonna explode! MS cant ban all of us!🤔🤣

Edited December 18, 20232 yr by FBW737

MS / Asobo have shown themselves to be (sometimes) receptive to input, so why not ping them about it? Unlikely much will happen over the end of the year, but....

In

2 hours ago, Fragtality said:

Oh my ... look at the Mess I've created 😅 Where do I start ...

First, don't forget this would not even exist without muumimorko and his/her MSFS_AdaptiveLOD - all Credits to him/her. I just copied the Core-Mechanic to a From that I'm more familiar with and suits my Needs better. And reverse-enginereed/calculated my Way through it to get the changed Offsets after the SimUpdate.

Then, it is basically the same Theme as with all of my Tools: I've created the Tool that I wanted and needed. Like everything else, I've shared it to the Public since I see no Reason to lock it away (especially when I'm taking the Idea from another Open Source Tool). It is about Sharing. Look at what some People do in the Reigns of freeware Liveries and Sceneries - or even whole Planes.
The Description is deliberately short and deterrent (my English is quite okay for a non-native Speaker, if I want to 😜). As it was already explained by others it takes a risky Approach. It writes directly to the Memory (like a "Trainer") which poses a bann-worthy Behavior. 
The User really should know what he/she is doing there before going ahead. I don't want to be bothered and certainly not be responsible for anyone's Problems using it.
It is just not intended for the average Joe/Jane out there.
Hope that explains the Mindset a bit better behind the Conflict between "openly shared" and "Readme says not to use it".

That being said: I certainly won't never recommend anyone using it with this Background. Use it at your own Risk, don't complain to me. But as I said initially, I don't code for the Purpose of having a good Joke 😉
There will be zero Support. Already have enough Headaches with other Tools, so please don't open Issues when closing a Window and closing a Program confuses you 😅

As for the Future: don't expect much Evolvement. It does already what is supposed to do.
I had thoughts of copying the Installer over, because it basically uses the same "Skeleton" as FenixQuartz, Fenix2GSX and WorkingTitle2GSX. (Although that would be working against it being deterrent to average Joe & Jane^^)
Seeing the hot-mess it created, I may look into the VR Settings - although I'm already nerved to do Stuff I don't have any Benefit from for People being fancy again 🤪. (And this would not be "fixing" something, because there is nothing "broken".)

Mate, thank you for your hard work!! These sorts of tools (I use Fenix2GSX on every flight) are hugely useful and beneficial to the flight sim community. This one in particular is amazing and has been called for from Asobo for a long time.

 

Please keep up the great work!!

where is the link to actually dl the file? not seeing it....