thetford569

One cool thing I immediately noticed that has been fixed in SU5 is that there are now red blinking obstruction lights. The floating yellow lights over wind turbines had also been fixed and replaced with red blinking obstruction lights. Other obstructions had red solid lights depending on height which I believe was all done to specifications as in real life. So much better for night flying! I only saw this at one place in the US so I have not checked other areas but this was a welcome and undocumented change since I had reported the floating yellow lights multiple sim updates before.

I lost frames when I tested in VR as well yesterday and could see no perceivable difference in smoothness with SM on or off. I see in other posts that he is getting the fps display on the 2d monitor. I don't believe this is reflective of the fps in VR which was also one of the reasons it was noted that this didn't work in VR in the past. I really don't think it actually works in VR as if it did and caused this kind of performance increase it would be all over the internet. I have an i9 11900k and a RTX4090 and have gotten my best performance lately with the new DLSS 4.5 and Preset M on Performance mode. I also have my resolution in Pimax play turned down to 90%. That is giving me about 40fps and very smooth flight even in complex aircraft unless I am around a high detail large airport + photogrammetry area. Unfortunately for me I am not seeing a benefit and will likely turn HAGS back off as I am now experiencing some judder in the headset after turning it on to test SM. However I don't know yet if it's HAGS or the updated Pimax Play software causing that issue.

I tried turning on smooth motion in VR on my Pimax Crystal light and saw no difference in perceived smoothness either way. FPS was also the same (which I would expect because these are perceived doubled frames so I would assume the fps counter is not going to be higher. Anyway I see no difference just as I have in the past in VR. I don’t know if I am doing something wrong but as before it does not seem to actually work in VR. All I did was turn on HAGS and the activated smooth motion for MSFS2024 in the NVIDIA app.

It is hard to understand but it also may not be that simple or they probably would have done it. And since all of the Photogrammetry fixes that 3rd parties do are for small areas and have to be done by hand I can see why they haven't tackled it. Not saying it's great but maybe the AI isn't that good? How does it differentiate between a tree blob and other blobs? It would be awesome if it worked but I think this is a limitation of the way it works in the sim.

Maybe it’s a design decision because the leafy trees (even the colored ones) are hiding the photogrammetry blob trees. If you use trees where the leaves are falling off then you’re not hiding the blobs anymore and it looks like crud. Maybe they decided to keep hiding them as the fall colors fade and leaves are supposed to drop.

Tested this out myself today with the Pimax Crystal Light. I saw no performance improvement or any noticeable changes when turning motion smoothing on in VR. The VR mirror on my PC was noticeably smoother however. I tried a recording in OBS however the recording looked the same as in my headset which makes sense because I remember that I am using an OBS plugin that captures the OpenXR view and is not just a mirror capture. I can see where this might be useful if you’re capturing your mirror or you want it to be smooth for someone watching your screen. However it does nothing for you in your VR headset to make the experience better. I’ve also rolled back to NVIDIA Driver version 577.00 because I started getting graphics card errors (no crashes though) with the 580 drivers and my 4090. This continued with the latest 580 driver today when I updated to try this motion smoothing out.

Everything I am reading says this does not work to increase VR performance and I can’t find the text you originally posted anywhere else where it says: NVIDIA Smooth Motion is a driver-based feature that generates interpolated frames to improve visual smoothness, especially in VR, All I have been able to find is a YouTube video where he shows that it helps performance in the VR mirror for recording. Everything else I have read says it’s not supposed to work in VR?

Calvin, While it’s way better the issue is still not resolved. Had 2 other flights now with the same jittering issue but a lot less frequent. Also noticed if I placed my fingers over the top cameras it would quit. May go back to tape if this continues as it seemed to not happen at all with the tape over the cameras.

2024 - SU3 Beta latest version

So far after multiple flights it appears to have been resolved with the latest Pimax Play for me. I no longer have the tape on my headset and have not experienced the juddering at all.

I’m also using latest SU3 Beta with 2024 so I’m not sure I’m the best to compare with.

Well in 2 flights last night I didn’t have the issue and didn’t change anything with my tape on the headset and still on latest Pimax Play. I did experiment with various graphics settings and TAA vs DLSS and Textures between High and Medium. With my 4090 in TAA and textures High I got bad performance and the pop up asking me to lower settings. On this build I’ve settled on DLSS Quality and Textures at High (VRAM was only about 3% different between the 2. This was tested in San Diego a known hard performance area and the Miltech MH-60. I was getting around 30fps in VR. Flying outside of town away from the details I could get 38-40fps and at no time experienced the jitter in the headset. This was all MSFS2024. I am not using 2020.

Hmmm, ok. I was still getting the same issues in the headset last night with the tape on but maybe with the updated dll file I need to try it with tape off. I will do a deep dive this weekend checking performance with the new SU3 and do some experimenting. If I need to I will contact support.

Did the new .dll file come with the latest 1.41 update? If so I saw no improvement with the tape off the Crystal Light so I put the tape back on. That being said I also tried the new SU3 beta update tonight which improves performance in heavy areas and I could see it for sure with reduced sim stuttering especially when looking around. I had fps of 36-40 in San Diego which is way better. However even with the tape on I started suffering from the jittering again with fps still 36-40. If the new DLL file does not come with 1.41 then I will contact support.

Hmmmm….it stopped working for me on 1.5.23 (SU3 Beta) and won’t connect. I am also on the latest app version.

Glad we could help each other out! I love OpenKneeboard and my Wacom tablet to write stuff and view pdf checklists!

@Reset XPDR Would it be possible to change the name of Auto FPS in the main window when it opens to not include the version number and to stay the same for each release? I use OpenKneeboard for VR and I have a tab that I keep a window capture of AutoFPS in so that I can see what it's doing while I am in VR. Since the name changes with every release OpenKneeboard doesn't recognize the window each time a new version comes out and I have to set up the window capture again for all the profiles of every aircraft I fly. Just a quality of life improvement I would like that would be helpful. Maybe the version number can just go on the main UI screen instead of in the window name.

You could technically program in the lat/longs for the approach waypoints and do a GPS approach flying everything manually without autopilot. And alot of military aircraft I believe do just that. It's just not available to load into the systems in alot of cases. The F-18 has no ILS for example (US Navy ones) even though they do have a carrier ILS at the aircraft carrier. It only works there at the boat and doesn't pick up civilian ILS. The F-18E/F Super Hornet versions just picked up within the last few years the ability to load RNAV approaches for airfields. The F-18 C/D did not have this but I do think that some of the remaining Marine C++ models have actually gotten that in their avionics now too.

Don’t have it yet myself cause I’m on SU3 so I will wait for fixes. But, I don’t believe it loads approaches cause the real one doesn’t. This is a combat helicopter so the systems aren’t designed as civilian helos would be. That being said I don’t know if the Coast Guard MH-60Ts can do this with their CAAS avionics but the Miltech MH-60T shares the cockpit with the R/S versions and is an external model only. They did not model CAAS avionics but may in the future if they decide to do a UH-60.

Yes it’s in PC settings but not VR.

They forgot to include the new fauna, passive aircraft, and vehicle traffic options in VR. I made a report at the their forums about it. And, I say forgot because as usual it's VR so they forgot! Got Xbox taken care of though!

I am on the latest release from July 17th and yes I had updated the firmware with that release as well. I didn’t reach out to support because I thought it was a sim issue. I haven’t used the headset in anything else in awhile so I didn’t think it was a Pimax problem. This is also the first I’m hearing about another .dll

I am making this post in the hope that it helps someone else as it did me…. I have an i9 11900k, RTX4090, and 64GB of RAM. I could not for the life of me figure out why I was having 40-45fps in all these builds but having severe stutters/jittering. Sometimes it would do this randomly or during the whole flight. I came across this thread today and this was the exact issue I’ve been having for so long in this sim. I thought it was MSFS2024 performance issues but I put 2 pieces of painters tape on the top cameras of my Crystal Light and had the smoothest flight ever this evening in SU3 Beta. Turns out this was a tracking issue with the headset all along. https://forums.flightsimulator.com/t/jittery-unstable-vr-experience/728950 Hopefully this helps someone else with the same issue. I chose to go the painters tape route instead of roll back Pimax Play versions and it worked fine.

I love the Longitude in 2024 and flew it all the time. Maybe I’ll fly it again but I’ve been waiting for a C750 since my FSX/P3D days as it was always my favorite. The C750 is just as “deep” in my opinion with a lot more to manage as a pilot. The C700 is also very deep but you really don’t have to manage as much. The automated systems do alot of the work. Sure you can see them working on the different pages but there’s just not much you have to do. I prefer to be a little more involved with my flying to the C750 is a better mix for me. Both are great aircraft. I also want to say that I am very impressed with what FlightFX delivered. There’s hardly many bugs and the ones that are there have somewhat easy workarounds for now. Love this jet!

Nope I’m not kidding but I think you read my message wrong. The LOD curve was changed for SU3 to make things visible from a further distance. Which really means the system is now allowing more vertices (faces/triangles) to be drawn further away than the original curve. This came with a slight performance penalty in 2D. The new curve allowing more LOD is enabled by default so 2D players are getting it automatically without having to do anything. Presumably after collecting telemetry the last several builds they have now decided in the latest build to turn the new curve off for VR mode. This means VR users do not get the increase in LOD. They said it was because it reduced performance in VR too much. Personally I have not seen enough yet to determine if I lost performance between the 2 curves. I have a 4090 card. Others are saying they didn’t have a loss in performance either and are mad that they have made this choice. So really it’s the 98% of the market is going to get the increased LOD and the 2% is not. So if you’re not a VR user then I guess you don’t need to be so upset.