My LODs are nowhere near that! I keep them both at 75, simply to avoid any issues in resource-hungry areas. The difference isn’t that noticeable when you’re busy flying.
I’m not an airliner type, so, for me, an LOD of 75 is absolutely noticeable.
My laptop runs on High-End defaults and the 100 LOD that defaults to is very clearly a reduction from my desktop’s higher settings.
400 down to 200 is subtly different and 400 is, potentially, unnecessary. It’s worth my re-testing at 200.
Interestingly, after that flight and later in the day after a fresh boot of the sim, I reloaded the C310 parked at KHND and the performance was markedly better. There was still some stuttering when I panned the camera directly at downtown LV, but the camera pan was smooth otherwise and FPS felt much higher.
It’s been an ongoing “thing” that end-of-flight performance with this sim is problematic. I wonder if that is partly to blame here, too.
I suppose it depends whether you want smooth flying or enhanced visuals. I don’t like having my LODs set so low but I’ve found 75 seems to be the best balance between aesthetics and very good performance in even the most demanding areas (NYC with the ‘big three’ installed, for instance). I tried TLOD400 / OLOD200 briefly and it’s fine for the most part — even with some highly-detailed scenery (I was still getting 50fps at NZA’s NZTG) — however the thought of constantly fiddling with the LOD sliders isn’t appealing.
The alternatives are adjusting the LOD in settings for each flight, or that mod that shall forever remain nameless here.
We’ve gotten a bit down the rabbit hole, but I’ve had the 400/200 set since I built the PC a year ago April.
For the most part, I’ve been fine with it this way and this landing performance at KHND was a complete anomaly.
I’m apt to think it is just this scenery and/or combination of scenery that is the root of the issue.
Maybe it was the intense magnetic storm on the sun that caused it…
https://www.sfgate.com/local/article/northern-lights-san-francisco-bay-area-aurora-19452572.php
Out of curiosity, I stuck both LOD sliders on 150 earlier and departed KLAS in the E175 (the most resource-hungry plane I have). While it was slightly less smooth than having the LODs at 75, it was still very good, even with the entire city in the frame.
Again, I have nothing else in the area. Strange.
1 Like
Thanks for checking that out for me.
I’ll do some experimenting and testing with various combinations to see what might be causing the issue for me.
I wonder how these add-ons are going to play with the upcoming City Update 8: Las Vegas.
Wondering that myself. I’m confident that FT will address any issues, though. Eventually.
These two USA CUs have the potential to mess with Samscene’s USA Modern Cities packs, too. Again, another dev who will almost certainly be willing to accommodate them.
I was thinking the exact same thing when I heard about this in the dev stream
I have a hard time believing a City Update’s version of Las Vegas will improve on FlyTampa’s. I also didn’t hear any reference in the Dev Stream to doing a better stock KLAS as part of it, but I guess we’ll see. Personally, I expect I’ll “buy” the City Update for the sake of completeness but leave it uninstalled unless it’s at least comparable but with substantially better performance. But I doubt it will be.
The CU will add better photogrammetry. So once FlyTampa addresses whatever issues arise, the two combined should give you a nice experience
1 Like
Except that the City Update is also modeling the Strip, which is more than just photogrammetry. Overlapping models never works well and almost always requires picking which of two packages for any given airport or scenery to be installed and which to remove.
1 Like
Perhaps we’ll be able to delete a file or two from the CU package to isolate the strip or KLAS from the photogrammetry upgrade of the CU?
I don’t think that’s how it works as the data is streamed. If FT already uses an exclusion zone, then it should work fine with the CU, depending on your load order.
Perhaps it’s my wording (rereading my writing).
Aren’t custom airports and scenery objects (in this case KLAS and the strip) not streamed, but the photogrammetry is?
What I meant was we could remove a MS custom KLAS and strip, but keep the photogrammetry. That would allow for the 3rd party KLAS and strip to work with the MS photogrammetry, no?
Or am I still clueless about how this works?!
if anything like the chicago pack and the 40th edition update, they will conflict. A couple months later will get an update. it will look good from the air but on landing like at meigs field it will look like a building site.
Xbox flyer
Drzewecki Design made an initial stance to not update their scenery to be compatible because the order was able to be updated for PC. Months later either they or Microsoft made an update to the order on XBox which fixed it so that it wasn’t competing.
This happened with Madrid and Barcelona for LVFR and was fixed after a few weeks. So I expect this to be the same since it’s happened many times before and usually gets updated by the Developer to fix it.
FlyTampa KLAS & City 2.1.0 is now available on ORBX with support for CU8.
2 Likes
FlyTampa Las Vegas has been updated to 2.1
1 Like
Now just gotta wait for it to trickle into marketplace
1 Like