One thing we can all agree on, I hope; MSFS really needs a built-in static benchmark with a good detailed breakdown. Just seeing the amount of effort in having to try and line up a 1:1 benchmark situation is a complete headache and a lot of work goes into creating a clean benchmarking environment. Especially a heavy title like MSFS, a benchmark would be extremely helpful for the userbase.

7 hours ago, Sethos said:

One thing we can all agree on, I hope; MSFS really needs a built-in static benchmark with a good detailed breakdown. Just seeing the amount of effort in having to try and line up a 1:1 benchmark situation is a complete headache and a lot of work goes into creating a clean benchmarking environment. Especially a heavy title like MSFS, a benchmark would be extremely helpful for the userbase.

Hopefully in MSFS2024 they will add this.  Maybe it can be a feature request for dev mode.

It is really non-helpful for people to report they're getting x y or z fps /smoothness when they're using a bunch of add-ons like AI add-ons which are HIGHLY variable in their performance impact.

My comments with 7950x3d and 4090; At heavy scenarios and with fenix, also with ai traffic we are still heavily cpu limited even with 7x3d CPU’s. But it is still playable with frame generation and also a bit stutters. Good luck to all. With msfs 2024 we will get x5 performance, will see:)

Interesting thread, I've just dropped a ton of cash I don't have on a 7800x3D and a 4090.  PC arrives in about a week!

 

On 7/2/2023 at 8:55 AM, GCBraun said:

I believe this is not possible when using my traffic solution (PSXT + Real Traffic). 

It is but you have to limit the % of traffic that can spawn.

In PSXT on the main panel window there is a setting % parked aircraft (live and static), this setting is PER airport but it remembers it once set
At the beginning of that entry it should say "Airport File <icao code>", so if you are sat at EGLL it should have EGLL showing 

 If you set this to 10% it will give you 10% of live traffic (compared to flightradar or flightaware, can't remember which one it uses).  Once you are on your way when you get close to the arrival airport the icao will change, by default the value is something silly high.  Simply change it again and the live traffic will decrease.

If you fly to the same two airports next time PSXT will remember the %, no need to change.  Of course this means you always have to remember to change it for each airport you visit for the first time.  There might be a way of editing files but I've not investigated this.  However this is a great way to use PSXT + Real Traffic with smaller amounts of AI to reduce CPU usage.

This is the extract from the manual, explains it way better than me.

% parked aircraft (live and static)
Value is taken from and stored in the airport file, default 30.
This parameter determines the wanted (and maximum) number of parking positions at the airport that will get a static parked aircraft or a live aircraft. That number is the percentage of the number of parking positions at the airport and is shown in the park airport status line (13.2).

If there are not enough parked live aircraft PSXT will fill up parking positions with static aircraft to reach the wanted percentage.
PSXT will automatically search for the best allocation of static parked aircraft, based on the parking options with day, hour, and real info found in the airport file. (See FAQ #37 too)
In the Log.txt you’ll see a message whether there were sufficient real parking options for the hour of the day.

At every half past the hour necessary changes in parking positions will be re-calculated and they will be made effective in the next 50 minutes unless initial load only is set (8.3).
However, if you change the parking percentage in the UI, the re-calculation takes place immediately and all the necessary changes will be carried out in the next 2 minutes. The new percentage value will be stored in the airport file.

Live aircraft parking stay at the gate for at most a week, unless PSXT detects it pushing back. If PSXT misses the push back it still may detect the aircraft taxing. In the latter case the aircraft will be removed from the gate.

If you fly away from an airport without a destination set the static parked aircraft will stay till you are >= 60 nm away from the airport (“because you maybe want to return”).
If you fly away from an airport with a destination set, the static parked aircraft will be removed if you are >= 5nm from the airport.
If you fly to an airport, with destination set, static aircraft will be parked if the airport is within your lateral range or at 25 nm distance.