48 minutes ago, GSalden said:

It might stop working tomorrow when I have to install the update from today.

No - there are two types of update. One applies to the binary and the other the content. The binary update is done from the Xbox or ms store app. This will probably break the mod. The other update of the content is done within the msfs app.  This will not break the mod. Note that sometimes both types of update are made simultaneously’. In fact a binary update e.g. SU14 is almost certainty followed by a content update. But a content update can be made independently. 
 

The update at the time of this post is content only so no issues with mod.

 

*actually to be pedantic there are 2 types of content update. Mandatory where some core content is updated for all users and optional which only applies if you have downloaded that optional content. 

Edited December 19, 20232 yr by boez
Clarity

2 hours ago, RALF9636 said:

- You can even have several different installations of the app with different settings each. Just copy the main folder of the app and then start the exe from the copy. So I have one installation for the Fenix where the TLOD goes from 0.8 on the ground to 3.0 at FL240 in ten steps (with an FPS adaption value of 0.3

Would you be kind enough to share your Fenix config just so myself and others can get an idea on how to correctly edit the file

Many thanks in advance

There is a GUI ... maybe you should really really not use it.

Let's give the dev a break.

First he should support VR now you want him to support Beta versions.

He said he developed this for his own purposes. Generously he shared it with us. Let's be happy with that and hope he keeps it compatible with the official sim updates.

 

11 minutes ago, RJC68 said:

Would you be kind enough to share your Fenix config just so myself and others can get an idea on how to correctly edit the file

Many thanks in advance

I have done that already. Look at page 6 of this thread.

And of course you primarily should make your changes in the GUI.

 

Edited December 19, 20232 yr by RALF9636

30 minutes ago, RALF9636 said:

I have done that already. Look at page 6 of this thread.

And of course you primarily should make your changes in the GUI.

Thank you,

It is actually pretty straight forward.

If SU15 breaks it, it shouldn't be to difficult to find out where Fragtality lives. The other 20 or 30 or so of us in this thread can then go and protest outside his house until he agrees to fix it if we promise to go away.🤔

45 minutes ago, RALF9636 said:

Let's give the dev a break.

First he should support VR now you want him to support Beta versions.

He said he developed this for his own purposes. Generously he shared it with us. Let's be happy with that and hope he keeps it compatible with the official sim updates.

 

Maybe we should buy the developer a coffee for sharing this with us.

Thank you for giving us this amazing tool Fragtality

24 minutes ago, FBW737 said:

If SU15 breaks it, it shouldn't be to difficult to find out where Fragtality lives. The other 20 or 30 or so of us in this thread can then go and protest outside his house until he agrees to fix it if we promise to go away.🤔

Perhaps opt out of the beta team and hope that there won’t any small updates that brake compatibility…

 

My son found out the VR offset; it's 0x114 instead of 0xC

 

               addrTLOD = MemoryInterface.ReadMemory<long>(moduleBase + 0x004B2368) + 0x3D0;
//               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0xC;
               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0x114;
               addrOLOD = addrTLOD + 0xC;

Build a new exe and it works for both VR Lods

Edited December 19, 20232 yr by roland_lfor

9 minutes ago, roland_lfor said:

My son found out the VR offset; it's 0x114 instead of 0xC

 

               addrTLOD = MemoryInterface.ReadMemory<long>(moduleBase + 0x004B2368) + 0x3D0;
//               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0xC;
               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0x114;
               addrOLOD = addrTLOD + 0xC;

Build a new exe and it works for both VR Lods

Great Job! 😃

But you still only got the second Place 😜

first is yours of course sir 🙂

14 minutes ago, roland_lfor said:

My son found out the VR offset; it's 0x114 instead of 0xC

 

               addrTLOD = MemoryInterface.ReadMemory<long>(moduleBase + 0x004B2368) + 0x3D0;
//               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0xC;
               addrTLOD = MemoryInterface.ReadMemory<long>(addrTLOD) + 0x114;
               addrOLOD = addrTLOD + 0xC;

Build a new exe and it works for both VR Lods

Has this passed Quality Assurance? 🤔

27 minutes ago, Greazer said:

Has this passed Quality Assurance? 🤔

I don't know what you mean exactly, but it works fine on my side. It's enough for me as a quality evidence.

Edited December 19, 20232 yr by roland_lfor

6 hours ago, navyseal111 said:

I cannot possibly change the TLOD value to 2.5, it just changes to 250 and kills the game. What's funny is that the value of 1.5 works absolutely fine.

Maybe you should try to set the value to 250 or the highest value you will use in game menu first?