1 hour ago, Noel said:

Good for you, but that does not answer the question, at all.  I fly all over the world from large terminals and this one consistently causes stuttering especially during pushbacks, so my tact is to avoid starting FSLTL until I'm about to taxi.

My point is that on a system that's considerably less powerful than yours, I don't see the performance drop you describe, so it seems likely your issue is something other than FlightBeam's scenery.  If it's unique to KDEN, maybe there's a problematic regional AI model or traffic file that shows up there and not other places.

So it may not directly answer your question, but it certainly addresses your problem.

Has Asobo fixed the elevation issues with the taxiways on the default DEN?  I have FB's and I don't have framerate issues unless there's a lot of AI traffic as others have said.  My problem with FB's version is that, IRL, DEN is rather quite hilly which you get in the default, but FB's is flat as a pancake.

I just flew out of FB DEN in a PMDG 739.  No issues at all.  

5 hours ago, Dave_YVR said:

Might be worthy to try with reduced settings. Those FSLTL 2 Lod models running 4k textures can be tough on the system.

Well, that's just it what I'm looking at is context.   KDEN really is isolated from complex terrain and scenery within a significant radius.  And I'm comparing with other major terminals I'm in and so forth.  I've never had a completely stutter-free pushback out of B45 in PMDG or FBW whereas it's very common elsewhere sometimes in places that are really demanding.  So it makes me think the airport is just poorly optimized, relatively speaking.

As far as FSLDL very familiar with it and use very modest loads with it, and that is why at KDEN I will not start it until commencing taxi.  One key difference that I did not mention is despite my hardware I don't use DLSS Frame Generation, so use native rendering only which puts my frame rate at 40 at FB KDEN, which again is lower than it would need to be in so much more demanding environs in my experience.   Perhaps if I did FG I could sit at 30/60 and experience smoother animation there, but I won't so that's out.

4 hours ago, cappy42 said:

Has Asobo fixed the elevation issues with the taxiways on the default DEN?  I have FB's and I don't have framerate issues unless there's a lot of AI traffic as others have said.  My problem with FB's version is that, IRL, DEN is rather quite hilly which you get in the default, but FB's is flat as a pancake.

I don't think I would have added FB's KDEN if the elevation problems were ever addressed and lord knows I tried at least 2x with zendesks.  I think I'll uninstall FB and check it out.

5 hours ago, Bob Scott said:

My point is that on a system that's considerably less powerful than yours, I don't see the performance drop you describe, so it seems likely your issue is something other than FlightBeam's scenery.  If it's unique to KDEN, maybe there's a problematic regional AI model or traffic file that shows up there and not other places.

So it may not directly answer your question, but it certainly addresses your problem.

Sure, thanks.  It's unique for what KDEN is--as you well know it's surrounded by very low demand terrain in large part.  So yes, in my context it's atypically poor.  Not terrible, it just is worse than I would have expected with that setting.   Do you use Frame Generation?  I don't, and that may be part of your perspective.

Flightbeam all the way!! Not even a comparison, have to laugh about this thread!!!.

Denver is one of my main airports I frequent.  X-Codrs from ORBX is the best right now.  Flightbeam is wayyyy outdated, it's missing half of the gates. Denver has expanded greatly since this old FB P3D port over.  FB is supposedly working on a V2 for Denver - maybe after SFO, so maybe it is next in line but don't expect it soon. 

There are some things wrong with X-Codrs mainly stylistic and minor variances but as I understand it they are working to perfect it based on community feedback.  The airport is fully functional and all the gates are there. Term A extension on the west side for United, Terminal B extensions and correct commuter area, Terminal C extensions on both sides, most current layout are all in the scenery.  AI gates are assigned. AI traffic works with in the limitations of MSFS.   I use it a lot and I have been pretty happy with it.

I  would never recommend a Feel There product they are always incomplete in some major way.  Also, let's not use FT as a abbreviation.  Someone might confuse it for a high end developer called Fly Tampa. 

X-Codrs Denver v 1.1:

Edited September 5, 20241 yr by aniiran
add pic with performance

Yeah, that's odd if its the FB version. I just had a flight around there a few days ago on a larger jet and it was no different from other large but kind-of-remote airports. A little outdated, not too heavy on traffic, lower photogammetry area. Hmmm. While others have brought up a lot of good ideas have you thought of any conflicts around the area?

GSX, ground clutter? GSX profile?

Any surrounding airports or scenery around the area?

Just bouncing ideas off, that's all.

9 hours ago, cappy42 said:

Has Asobo fixed the elevation issues with the taxiways on the default DEN?  I have FB's and I don't have framerate issues unless there's a lot of AI traffic as others have said.  My problem with FB's version is that, IRL, DEN is rather quite hilly which you get in the default, but FB's is flat as a pancak

They fixed the elevation issues and there is a lot of relief/depth in it but all the heinous slopes are gone now.   Ultra smooth test just now.   I'll probably stick with it for now it's good enough for my needs and I'd rather have more FSLTL and less animated passengers inside terminals and other performance-sapping effects.  Speaking about performance how is X-Codrs?

8 hours ago, Sonosusto said:

Yeah, that's odd if its the FB version. I just had a flight around there a few days ago on a larger jet and it was no different from other large but kind-of-remote airports.

I can fly around FB KDEN just fine it's mainly just pushback and early taxi for me that always stutters and that is despite 2 different OS', and complete reinstalls of MSFS over the years.

X-Codr did a good job with the airport's mesh. 

I switched out the FB version for x-codr a couple of months ago and am quite pleased with the results. The FB rendition really quite old and looks like a port from P3D.  x-codr did a very nice job with the terrain and the terminals and just released a significant update to address some of the issues people have raised. 

FB does great work but they seem to struggle to keep their sceneries current.

On 9/5/2024 at 1:43 PM, Cognita said:

I switched out the FB version for x-codr a couple of months ago and am quite pleased with the results. The FB rendition really quite old and looks like a port from P3D.  x-codr did a very nice job with the terrain and the terminals and just released a significant update to address some of the issues people have raised. 

FB does great work but they seem to struggle to keep their sceneries current.

How's "performance", frame rate, micro stutters, etc vis a vis FB?

55 minutes ago, Noel said:

How's "performance", frame rate, micro stutters, etc vis a vis FB?

FB is an expert on optimization and I never experienced stutters with their KDEN, having had it since it was released. I have only flown into x-codr's version once and out once and I had no performance issues, approach, landing and taxiing were smooth, but I was not watching framerates. My system is a little older now, a 10700K and a 3070, just as reference.