vincentrouleau

Actually, I still have the problem, I turned it off and the monitor never goes blank/lock/sleep

I also received my Tobii last week. Somehow, my old TrackIR was giving me bad 'spikes' of wrong direction even without sunlight. I didn't even know that the Tobii was a Windows Hello device, nice! I noticed that with Tobii Experience running, my PC would not go in sleep. I solved it now as I use it with opentrack and disabled the Tobii Service. That was the Tobii experience is not running, and my PC goes to sleep. I couldn't find discussion about this issue anywhere. As anybody had this problem?

As for me, did 3 flights just today on su4. testing the new fsfo a300 module. I have the premium a300. Like all my other plane, steady 90 FG frames. With locked 45 fps native in msfs2024.

Doesn't happen to me, except if I am very close to the right windows, the label take like 100ms to show, but never the seats like you. Have you tried installing the longitude instead of streaming?

I had this https://flightsim.to/file/93075/hues-zcore left over after removing the other repaints. Also inibuilds own cabin pack have the same problem. Guess they havent uodated it themselves.

Update: Never mind. the zHueCore texture was causing it. Its ok once removed I have no cockpit in SU4. I deleted rollingcache, nvidia shaders, uninstalled/re-installed. Same behavior for default/no cabin. No Cockpit

I am doing tours on staralliance.org now. Especially since beyondatc now has 24hours historical, i can take advantage is the actual flight departure times that aplv2 did not have. It added i bit more realism for me. So full historical in flytheline isn't for me.

I've tested, It is ok to set it to "Microsoft Flight Simulator 2024". It does not 'need' to be global.

I ve got scenery bleedthrough. There is a bug report on flightsimulator.com. I reverted back https://forums.flightsimulator.com/t/bleed-through-of-aerial-imagery-with-certain-ground-textures-at-custom-airports/700299/1

The operation manual contains the text version of their YT tutorial https://downloads.justflight.com/products/JFF003765/RJ_Professional_MSFS_Operations_Manual.pdf

FYI, I did more testing. I just realized that I in "FPS Caps" mode, I had left the Target FPS to 40, assuming that the target was FPS before LSFGx3. But no, I had to set it to 120 to match my 40 caps x3 . So now, it doesn't inflate the TLOD that I was 'asking it ' to do. With a Target FPS 120 is is ok. This is testing on ground. I will do some actual flying in "Fps caps" mode this weekend and report back. Somewhat related question: How do you lock your frames? I've lock it inside MSFS2024 since the Nvidia app causnig the "6% Loading Language" problem. Do you guys have a workaroung?

No, its not caching. Using hotkeys,successively switching between from say overhead view to EFB view i find I get to much stuttering. That i why i hate motion blur in any game. That is the first feature I turn off in any game. Whereas at say TLOD 75, i cant see any difference with any higher TLOD. And even in drone view spotting planes. I tend the maximize stutter free panning. But as I say, I am super happy with “Fps sensitivity” mode.

Because, even thought my FPS is high and GPU Mem is within limits, there is still stuttering on view change in the cabin during plane setup. So I still prefer for the TLOD to be low on ground. I'm fine with keep using "FPS Sensitive"

I must admit that I am getting overwhelmed by all the configuration. I too am also starting to use 40 Locked FPS + LSFG x3 for a solid 120 fps, which I can achieve everywhere now. But I still use "Fps sensitivity" as someway in "FPS Caps" something the TLOD on the ground goes up to 300. I don't really understand the behavior. So I guess I would be a candidate for "FPS Caps" but still using "FPS sensitivity"

I’ve switch for my last 2 flights. I now run at 40 fps cap, LSFG x3 , DLSS Quality, Beyond Atc, AutoFps and I get a solid 120 FPS now every where I tried ( inibuild egll, klax ,…), turned off freesync. VRAM usage much lower then with native FG and GPU usage equivalent. Can t wait for DLSS 4.0 drivers/ patches to get rid of ghosting now.