So today I bought EDDK from AEROSOFT. My specs are 5800X3D, RTX 3080TI, 32GB RAM. At 1440p, I get 50-60 fps with FENIX (V2B2). Now when landing on 14L it drops from 30 to 15 but also 10 fps. Absolutely unflyable. I’m upset that I spent money on such garbage… Can Asobo or Aerosoft solve this problem??
3 Likes
Just had exactly the same issue! I nearly crashed on VATSIM the frame rate was so bad! Will avoid this airport in the future.
2 Likes
I believe City Update1 is the thing that causes the trouble.
Hope Asobo can fix/optimise it.
2 Likes
tried EDDK tonight, couldn’t get the plane straight out of the airport since FS2020 rendered at 5-9fps… seems like there is no fix in sight since there’s non in the beta as well.
1 Like
RTX 4070TI with 5800x3d and 3200mhz 32Gb ram and getting 7fps just now on flight from EGSS to EDDK. This is a horrible scenery.
3 Likes
Still suffering those issues with CityUpdate 1. Without CU1, EDDK (aerosoft) is ok in terms of performance (not great in the Fenix, but still playable).
2 Likes
same here… lost all hope for city update 1 area… compared to the new cu6 or wu6 german sceneries its an absolute mess. performance-wise and visually…
2 Likes
Just came to post exactly the same. Totally unfit for purpose and a region I won’t be in a hurry to revisit.
FWIW, I did manage 35fps+ on take off from EDDK when lowering TLOD and OLOD from 150 to 60 temporarily until out of the area.
Confirm massive frame drop on EDDK
Just done a flight from LOWS to EDDK (Asobo) in the Cessna 414 on Xbox Series X and had black screens on final and lots off stuttering and low fps on Su15 Beta.
Can confirm huge FPS Drop at EDDK, as well as EDDL with many Stutters!
Seems to be a poor optimized Area…
SU 15 Beta
using EDDK from Aerosoft this area is giving me a huge fps drop, but only 1 looking or flying in 1 direction from the airport. Makes the area unusable. my specs 7950x3d and 7900xtx. This is the only problem area , even KEWR is giving me steady 60 fps .
Yesterday I was flying VATSIM from LTFM to EDDL. It went all smooth until nearing EDDL. Stutterfest. From what the Task Manager showed, it was due to CPU, not GPU, overload. I tried closing any other application (VATprism, Litte Navmap, …) but I usually run FlightSimulator and VPilot with a slightly elevated process priority, so the improvement was almost nil. On the RNAV 23 Transition it was barely acceptable, on short final the autopilot could not cope with the lag and I had to disconnect and terminate my flight.
I did some experiments afterwards. I deleted both EDDK and EDDL sceneries and set up a new flight. No VATSIM, no VPilot, no additional software running. Same stuttering. Revelation: The culprit can not be the EDDK scenery itself.
I deleted and disabled the rolling cache. Result: No more stutters. I re-installed EDDL and EDDK. No stutters on a full VFR flight between the two airports.
I will now do another test with (a clean, freshly created) Rolling Cache re-enabled to see how it goes.
No stuttering on a flight between EDDK and EDDL with a freshly created rolling cache of 32 GB.
Result: The EDDK/EDDL area seems to trigger a problem with the rolling cache in some circumstances.
■■■■■■, yesterday I should have made a backup of the bad “rollingcache.ccc” to send it to Asobo to investigate.
Hi @Godot9217,
It is a good idea to delete & recreate the rolling cache whenever there is a world or city update. Otherwise, data in the cache can “conflict” or “compete” with the new WU or CU data, causing stutters or other anomalies. Some folks also delete & recreate the rolling cache on a regular schedule (e.g. weekly or monthly) to avoid potential problems. See:
Still an issue. When loading into EBBR with Justsim scenery, I get 60 fps. Loading into EDDK only 35 fps. Rolling cache is OFF, so that cant be the issue.
OK, maybe some ideas in this topic might help?:
No, I just checked. With all city updates ON, and Asobo/Inibuilds EDDK scenery, the FPS are normal. Turning Asobo/Inibuilds EDDK ON, the FPS almost halves.
So the issue is in the EDDK Asobo/Inibuilds scenery, which is a well know complaint.
Any update on fixing this nonsense?