I see nothing in the last couple of pages that break AvSim rules.

22 minutes ago, craigeaglefire said:

Let’s be clear here,

this is a memory ‘hack’,

You must be fun at parties...

On a positive note, I have my radio buttons communicating their status properly with the rest of the app, so its full steam ahead for the VFR / IFR flight mode terminology and associated functionality.

45 minutes ago, craigeaglefire said:

Let’s be clear here,

this is a memory ‘hack’,

Are you aware this is how FSUIPC was created many years ago? It takes a very clever person to disassemble a executable and analyse the contents. The original UIPC was created by Adam Zofran and then Pete Dowson developed his version from the work Adam had done.

He asked Microsoft for help but none was forthcoming. He battled on because with every new version variables were broken so work had to start again. Eventually after many years the Aces team decided to cooperate and Pete's life became a lot easier.

Without that effort flight sim 25+ years ago wouldn't have become what it is today. The development work passed to Pete's son John. These are very clever people whom we should all be very grateful to whatever sim you fly.

@Reset XPDR
 

Couldn’t resist myself so I am currently in a flight from Amsterdam to Nice.Lots of Live AI ac ( Psxtraffic) and Live weather. Using the latest beta.

 

At startup the tLOD was 135.

 

After checking and unchecking tLOD min + the tLOD stated to drop

 

Till it settled for 50.

Everything was smooth. From taxi to take off.  Currently I am half an hour into the flight and the App is working perfectly.

The current version is also working on a multi monitor setup as it checks the framerate from the main window. 

Any idea why ( on both pc’s the tLOD started at 135 (server) and 150 (client) ?
 

 

 

Edited March 13, 20242 yr by GSalden

 

8 minutes ago, GSalden said:

Everything was smooth. From taxi to take off.  Currently I am half an hour into the flight and the App is working perfectly.

The current version is also working on a multi monitor setup as it checks the framerate from the main window. 

Any idea why ( on both pc’s the tLOD started at 135 (server) and 150 (client) ?
 

 

I'm am pleased to hear it is working for you now. Re different starting TLODs, one app is in non-expert mode and the other two are in expert mode and they do not use the same TLOD min settings. I suggest you configure them all to be exactly the same settings.

11 hours ago, Reset XPDR said:

I personally object to having performance data in your face while in game as IMO it ruins the immersion

Thank you and I understand...interestingly enough, your reason above is actually why I asked. I was hoping to have the option of displaying a much smaller portion (just TLOD and OLOD) in the upper left corner in place of the much larger dialog box.

Anyway, both of your programs are great and I enjoy using them.

14 minutes ago, Reset XPDR said:

 

I'm am pleased to hear it is working for you now. Re different starting TLODs, one app is in non-expert mode and the other two are in expert mode and they do not use the same TLOD min settings. I suggest you configure them all to be exactly the same settings.

Thanks for explaining.

I inderstand what you mean.
I was wondering why when going back from Expert mode to Non Expert mode the tLOD remained at 50 and is working like a breeze.

 

2 hours ago, Reset XPDR said:

Those log stats are correct for the settings you told me and is consistent with what I said here:

In short, the app is working as intended.

After I unchecked the expert mode, the TLOD will change as the altitude up and down. the FPS target is set to the same limit as the RTSS. Perfectly smooth without stuttering.

Edited March 13, 20242 yr by kcjc073

Re:  Memory Hack...

1 hour ago, Ray Proudfoot said:

Are you aware this is how FSUIPC was created many years ago? It takes a very clever person to disassemble a executable and analyse the contents. The original UIPC was created by Adam Zofran and then Pete Dowson developed his version from the work Adam had done.

He asked Microsoft for help but none was forthcoming. He battled on because with every new version variables were broken so work had to start again. Eventually after many years the Aces team decided to cooperate and Pete's life became a lot easier.

Without that effort flight sim 25+ years ago wouldn't have become what it is today. The development work passed to Pete's son John. These are very clever people whom we should all be very grateful to whatever sim you fly.

Brilliant!  If there was a microphone drop to be had, it would be shattered in pieces on the floor at this very moment. 

Edit: You can be sure that MS / Asobo are looking at this very closely and considering how they can incorporate it in to MSFS2024 in some way.  They are already acutely aware of it as we know by their usual response to these matters.
Also good people, note that the sky colour corrections were also a 'hack' to start with, and are now adapted by Asobo officially.  Sometimes you have to push the boundaries to make progress. 

Edited March 13, 20242 yr by bobcat999

8 minutes ago, kcjc073 said:

After I unchecked the expert mode, the TLOD will change as the altitude up and down. the FPS target is set to the same limit as the RTSS. Perfectly smooth without stuttering.

That's because non-expert mode has less aggressive settings than what you have set in expert mode. Your issue is with the settings you have chosen. This is the third and last time I will tell you this.

3 minutes ago, Reset XPDR said:

That's because non-expert mode has less aggressive settings than what you have set in expert mode. Your issue is with the settings you have chosen. This is the third and last time I will tell you this.

Thanks for the correction. I didn't mean to imply that there was anything wrong with the programme or the logic, in fact I'm very pleased with and respect your contribution. It's just that I was so concerned about the consistency of the RTSS Frame time (not fps )that I neglected to mention that the latest version is optimising the system's capabilities and FPS targets. I found a simple solution after trying to adjust the parameters over and over again throughout the day.

Please forgive me if English is not my native language.

2 hours ago, craigeaglefire said:

Let’s be clear here,

this is a memory ‘hack’,

that is officially frowned upon & rejected by Microsobo,

& completely is outside of Terms of Service…

just checking for authenticity…

If you have nothing better to contribute why bother saying anything?

Trust me there are plenty of people on here that really do appreciate Reset's work. No one is forcing you to use this app and no one wants to hear your constant whining.

If you disagree with this so much delete your AVSIM account and go spend time at the official forum or even better Reddit, that'll be right up your street!!

7 hours ago, Cpt_Piett said:

While I can certainly appreciate your sentiment, I have to respectfully as well as strongly disagree. This thread has provided Reset as well as avid supporters the opportunity to test and re-test various builds for quite some time now. Yes - a thread introducing the app to newcomers is a great idea. But why does this thread has to suffer as a consequence? Where should we continue this discussion?

I can find agreement with both of you.  There is value spread throughout the topic's volumous pages.  No argument.  

 

7 hours ago, Cpt_Piett said:

Fair enough. I’ll still stand by my original comment though. I agree with you - start a new thread introducing the app to new users (who doesn’t care too much about plowing through 53 pages to figure out where to download the latest release build, or where the nice and legible readme can be found). I get this. As I said I do understand your sentiment and agree with it.

BUT - I beg the mods not to close this thread. That’ll be like disabling the expert mode because some users find the settings there baffling. I’m prepared to die defending this hill 😉

This is a great solution.  I am with FalconAF.  Likely because we are both former Air Force (snicker). I am moderately "equipped" to understand all of what has developed here, but moderately is not enough.   I have struggled with chasing too many tails through all of these pages, and have needed to travel away from my sim twice for periods of 5 days each. I have used both apps, and unfortunately based on my RTX 3080 card, I also pursued the FG hack for RTX 3's.  The result in my case turned a relatively smooth MSFS at locked 30fps, into a stuttering mess both at high altitudes and on or near the ground. My fault for chasing too many tails at the same time.  So now I am attempting to revert and then use autoFPS in basic form.  KISS principle to get back to smooth.  And I am not completely there yet. 

A new topic would help greatly, or better yet a userguide that is not so technical.  

Here is where I am at right now. My systems specs are in my message footer.  Smooth with the app not on top.  A bit sluggish when on top. The screen shot taken at VerticalSim's KTPA. Will fly this afternoon. Any suggestions from Reset XPDR or Cpt_Piett are welcome.  Others should apply first (LOL)!

Edited March 13, 20242 yr by fppilot

11 hours ago, Reset XPDR said:

Re acceptability of your settings, it depends not only on your specific hardware but also your expectations, so I can't really make that determination other than that they look reasonable for a VR setup with perhaps an older CPU that struggles with high TLOD.

I literally have the top-of-the-line CPU: 7950X3D. However stuttering was always the largest problem for me, even with Reverb G2, and now Quest 3. Though Quest 3  is much smoother and the only problem I see is cockpit judder when looking side to side, but AutoFPS seems to help a lot here. It seems it needs some headrom to be smooth, even with solid FPS. I could always see great smooth FPS in between the stutters, and TLOD is clearly exacerbating stutters. And taxiing in busy airports was always iffy. So I though I'd set very low TLOD ont he ground (where it doesn't really matter) and put a reasonably good looking but as low as possible top limit, to create some breathing room for smooth flights. Stutterless flights are the top priority for me, and I'm very sensivie to stutters and judders. In VR the images is not as crisp as on a 4K monitor, so visuals still look very nice. Ultra clouds add much more to the visuals - but they do have a large CPU impact. Compared to Ultra, High clouds seem like detailless cotton balls. Anyway, the results are already great, thank you again for the app, it really makes it possible to have a steady and smooth flight. It's a shame we can't have it out of the box, and this would have been so easy to implement in MSFS natively, it's such a simple and effective concept! But I'm sure even if it's implemented natively, there won't be so many options to tune it, they would have to dumb it down.

Edited March 13, 20242 yr by Roman Design