mryan75

I did a video for another purpose today so I had LOD mod and FG mod both off, just stock 2k in DLSS-DLAA, and the ground tile popping in the sim was the worst I’ve ever experienced. I usually don’t even notice it, today it was literally like laying out a sidewalk in front of me as I walked, each step forward more tiles popping in front of me. Never experienced this before. I was flying in the Caribbean so maybe it’s filtering in the updated ground imagery coming tomorrow?

Well you’re talking to someone who got banned over there. And I suppose we all tend to favor our own narratives, but what I got banned for was doing the job the mods weren’t doing. There were so many clickbait thread titles it was absurd (“I can’t believe this happened!!!”, “WHAT CAUSES THIS?!”, etc.) and the mods never did anything. It’s against their terms of service, so I started flagging the threads. They were non-plussed as the kids would say. Then when people would be sniping at each other or in particular, ganging up on another user, I’d call people out. “Knock it off guys, this is not a place for personal attacks,” etc. Well that was apparently the last straw, as that got me banned. “You’re creating more work for the moderators” was the reason given. Well, maybe if they did their jobs to begin with… But you have to understand people with small minds and authority, it’s always like this (and I am NOT an anti-authoritarian type). I check over there for any news of interest on a regular basis and I see so many things I could help people with, but nope. Oh well.

If you’re not limiting framerates or limiting them with VSync only, that’s probably going to be your issue. I had the exact same thing happen to me on a few flights, same timing and everything, until I set a hard maximum frame rate in NVCP. Also keep in mind that you can use something external like Riva tuner (which I’ve never used and can’t comment on), but that causes other problems for some people. And a lightbulb just went off - another thing that can cause these crashes is using an external program like Riva tuner of MSI Afterburner to check framerates. I wouldn’t run any of those external framerate counters either.

Yep. And sometimes with higher refresh rates like yours you have to limit it at something like 120, but try 144 first.

Use Nvidia Control Panel to limit your frame rate to your monitor refresh rate. That is what solved the problem for me.

I personally think FS2024 is going to be completely different in terms of resource use and what the CPU-GPU performance balance is going to be.

No ghosting (I don't even really know what that is), no artefacts, nada here with a 3080ti. Smooth as can be at 60 FPS. Menus and things like Navigraph charts flicker and so on, but that's no big deal.

Be interested to hear how you fellas’ experience is with native vs the mod.

Yeah that’s what you’re looking for with FG really.

I do. This is one of those weird settings: the standard advice is Vsync on in the Program Settings tab in NVCP and off in the sim, but some people have had success with it on in both NVCP and the sim. Which of course doesn't make sense, but that happens sometimes.

Glad you got it working! There are some different ways to try and refine the image, but it's definitely a game-changer.

I have it set to my monitor refresh rate (60) in NVCP and it is as smooth as any metaphor you can name.

Why I would be happy to help. This video shows you how to do it. Always glad to help a fellow flight simmer!

I honestly give up on trying to figure this airplane out. Just flew the ILS 09Z into TBPB, it captured localizer and glideslope (albeit about 0.4 NM early on the GS capture), followed it down, went below the GS even though it was captured, never did anything to correct, and would have easily put me down about 2 miles short of the runway.

In this particular case it brought to the threshold of the physical runway, in other words the start of the displaced threshold. I remember because I had to add power and fly the length of the displaced threshold at 20 feet AGL before plopping it down on the runway. Prior to the update I know that at several airports (TJSJ being one) where it would take you roughly halfway down the runway. So they did change something, I’m just not sure what.

The only thing I can say for sure is that in literally every other aircraft, the distances on whichever nav equipment you’re using match the distances on the charts. In the ATR they’re off literally every single time. I just can’t figure out why and where the distances in the ATR are coming from. It’s always the distance from the last fix before the runway fix to the runway fix (if there is one of course). It’s off every single time on any approach of any kind. It’s bizarre. It seemingly flies ILS approaches just fine now, whereas prior to the update it did not. But following the guidance on RNAV approaches is all over the place. Sometimes it brings you down short of the runway, sometimes halfway down the runway.

I find this comment more than a bit snide. We were talking a GPS approach before, where whether the ATR had DME or not was completely irrelevant. I more than once edited a reply to you in order to reign in how tiresome the DME bit had gotten. Apparently you weren't finished. I, however, am. Blocked. Goodbye.

Actually they are spaced well enough apart that I think they’re fine, although with the step max they’re probably not needed.

Whether it would follow the glide path (it did) and if the distances on the approach would be correct (they were not).

Flew the ILS10 at TTPP. It doesn’t hold glideslope on RNAV approaches, the vertical guidance is all over the place. So I wanted to see if it could fly an ILS.

That would also explain why the glideslope jumps up or down when you hit approach waypoints - if you're high or low as you reach a waypoint, it will affect the distance. I really like this theory. Time to test!

That is actually a pretty darn good theory! I've tried so many different ways of figuring this out, there have been a few that would have made sense in theory but didn't pan out. I think this one has a good chance of being correct. How weird would that be?

It flew the ILS just fine.

Yep, I've come to the same conclusion. Whatever it is always happens between the final waypoint before the RW waypoint (if there is one) and the RW waypoint itself. I'm literally astounded nobody has brought this up in the official forums yet.

Currently flying a route that will end in an ILS approach, we'll see how that goes. @martinboehme you've had some really valuable input here, thank you. I will check some of the waypoints on my route against the chart. Edit: Well, from SHARK to TRI on both the Jepp chart and in Little Navmap is 11.2 NM, in the ATR's FMC its 11. From TRI to RW10 on the chart and LNM is 4.2 NM, in the ATR it's 5.0 NM. All the distances between the other waypoints in the flightplan are correct. So in reality from SHARK to RW10 it's 15.4 NM, in the ATR it's showing 16. The question is why. It would be great if someone could post this in the official forums, I got thrown out. 😲