Noel

Thanks I will see if I can get a message to its developer group

IFly MAX 8 is doing this in the Flyby feature and it's the only plane doing this here. Of note, external and drone cam views of the plane in-sim are normal. Pardon the HDR10:

Nvidia DX cache is automatically cleared with every install of the GPU driver. Not sure if using DiskClean to clear out the other generic DX cache matters, but I do it anyway.

Awesome I look forward to this release! I used WT's 787X mod for a long time and enjoyed what it could do but to get a fully developed version will be fabulous!

Mega thanks to rksoftware for this little gem. Since the update the Flyby feature is now mature and it is excellent! Haven't tried any other features in Spotty26 yet but will. I really appreciate the fact I don't need to replace the entire default camera system which to me is elegantly simple to setup new custom camera views with, make minor edits to, and is amply sufficient for numbers of views I need.

Is there much hope for a better program that can actually delivery ultra-smooth animation, like FSLTL's animation. And, I appreciate why FSLTL's is far superior. Right now, besides other issues w/ BATC well known that is a major issue for me. I only have traffic amount set to 3, except for parked at 8, and yet even w/ that modest amount of live moving traffic way too often animation is herky jerky, un-smooth, and is one of two reasons I end up using FSLTL for injection, and BATC only for ATC communication to yours truly. Thanks in advance

Strange but true: BATC's ground traffic management is AS BAD and sometimes worse than in FSLTL's 'blind' operation. Frequently when I use BATC traffic I'll have other planes head right towards me in a Mexican Standoff or other variants of ground traffic conflict.

I generally agree except for one major problem and I don't see any work around but hopefully that is not the case. Strangely to me, I'm not sure why others aren't as bothered by this as I am, but here it is: w/ BATC injection its traffic animation often is, for lack of a better phrase, herky jerky, and I understand the explanation for this versus FSLTL which delivers ultra smooth animation. The other factor for me is that I do use Premium voices in BATC, but only for the controller. If you use BATC traffic injection BATC will use the Premium voices for ALL controllers communicating w/ all traffic, so characters get used up much more quickly than if I use FSLTL's injector in which case BATC will then only use Premium characters for the one controller communicating with me. So typically I end up using FSLTL and Premium characters and despite the lack of actually control of all traffic, the experience ends up generally being better. Sometimes I use BATC's injection at small terminals where the animation quality is likely to be better, and when I do this I use Basic voices.

I've found this to be the case which seems strange at best. In fact, it's as bad and sometimes worse than is FSLTL!

Not sure what the date on this version is but sounds like I should keep using it as long as I can. If n when I'm forced to consider buying the Ultimate Navigraph sub I'll probably do it because using FSLTL is a net plus for me, and I also use BATC for ATC and sometimes use its traffic management but I have a real problem with the poor quality animation that happens too often w/ BATC's traffic, plus when you use its traffic you are forced, if you use Premium voices, to have the system allocate those Premium voices towards all of the other traffic happening even when you restrict to controllers only, so every time an interaction between its traffic and any controller uses characters, whereas when you use FSLTL instead, it's just your own plane and the one controller it interacts with so drastically reduces character use. You do miss the choreography of BATC's injector, but odd as heck it's every bit as bad as is FSLTL for ground traffic conflicts, which don't happen often anyway in FSLTL. You just has to pay attention! Cheers

Nope, just FSLTL. No default RealTime or offline default traffic. All traffic in graphic settings are off. Traffic is OFF in BATC. I rebooted, cleanly updated to the latest NV driver, did KSAN KSFO in the IFly MAX 8, and had lots of ground traffic and air traffic, as configured in FSLTL. I went to open SimBrief and got a pop up from Navigraph where I had to resign in and I thought that may be the end of FSLTL prior and current 'normal' behavior. But...it was totally fine at KSAN as usual. Strange, no explanation!

I haven't done anything different, using the same old FSLTL injector as I've used for years, don't have the Navigraph Ultimate, and yet I'm getting the same parked and active AI traffic I've always had. Why?

I'll be slightly surprised and that because whenever I do a driver install I go thru the ritual of DDU in Safe Mode, clear caches, install cleanly, avoid NV HD Audio, avoid the NV App, and in general it always improves especially if it's been a few months since the last driver install, even when reinstalling the same driver. TBH though that improvement is subtle because smoothness is generally the case.

Actually, moving aircraft as previously. I could be confused because I've done a lot of experimenting lately with default RealTime traffic as well as BATC's herky-jerky traffic, and FSLTL. I'll look again a little later today... A little later...indeed, it's working as it always has, on the old injector. Pardon the HDR10:

Strangely enough I can still use the old FSLTL injector and it's sending AI planes into 2024.

I subscribe to Navigraph only to get AIRAC updates into LNM and various planes. Since this is not the Unlimited subscription will FSLTL still work in my setup?

I did several days ago flying into EBBR which I surmised was server overload and since then totally fine.

Me, zooming in? All I did was hit the Flyby button. You are saying I should zoom out, I'll try it.

I wonder why this happens w/ Flyby. It's the only plane I use doing this, IFly B738M, and yet in regular external default cameras it's fine:

Really nice upgrade now that it can be fully resized--thanks Umberto for following thru. Cheers

And very thankfully he added resizability to the GSX menu it's now been modernized and can be kept as discreet as desired. Many thanks to Umberto for going that extra distance.

I have and live near the Colorado Rockies Front Range. Yes, I can change TLOD on the ground and notice a difference depending on exactly how far away and angle and perhaps also how a particular scene is created, but it's really not that different at all, just discernable in large part when you effect the change in TLOD comparing 100 and 400. But if I were flying into anywhere including mountainous regions, double blinded as to TLOD's setting I'll bet it would be very close to 50% correct guess. And most importantly of all: relative to the performance burden? Just moot, irrelevant, not worth concerning oneself with. Just my honest POV. You and I have nearly identical hardware and I do not get that behavior. I may get some pop in during taxi but since installing a fix for taxiway signs it's improved quite a bit. Maybe it's down to streaming bandwidth or something else but absolutely I do not get what you describe even into the most complex airports. And as I think about it maybe it's down to exactly how we configure the sim to to run. For me it's normally 60FPS-fg via NV DLSS FG, front-edge sync in RTSS w/ passive waiting enabled. Perhaps other configurations force the sim to prioritize aggressive LOD.

I would happily bet on that test outcome. I'm talking about a test where one does not know what TLOD is set at, not a test where the scenario is changed back and forth between 100 and 400 so one can compare. I've done this myself many times in the same flight and I have very sharp details and it's so subtle it's virtually negligible. And again, the processing demand just outpaces the visual change so much it's essentially moot. That is just how I see it maybe others see it differently. I was always struck by this from Day One in 2020 and it persists today in 2024.

I wonder if the SU5 link is coincidental and that what we are seeing is slowly evolving higher demand on servers such that seemingly randomly we will have noticeably poorer performance. If it really relates to SU5 why would we experience one flight fine, the next affected, the next fine. This is what I've experienced recently as well.

Rocky, what behaviors that you find irritating are you referring to w/ regard to 'rather aggressive LOD system...'? You and I have nearly identical hardware and while one can see some 'pop-ins' overall I don't see anything more than that and my brain simply ignores these in large part, hence the 'irritation' piece is largely eliminated. One reality I find remarkable in both 2020 and 2024: changing TLOD makes so little difference between say 100 and 400 it's flat out not worth the performance load. In a double-blinded test I'm certain most would not know whether they were set at 100 or 400. It's just too subtle.