F-18 vapor, trails, and visual fx massive fps drop

Bug Reporting Hub Aircraft & Systems
, , ,
21

Top Gun expansion out and still no joy. Whilst this bug exists there is no point flying the F/A 18 (or the other affected aircraft obviously). Very disappointed.

22

Yeah, not fixed by Top Gun expansion for me as well. Sad

23

What else is common to everyone?

Seems you all have the same series cpu.
*Edit- not just 5 series then. @SebTajtaj

Any body running AMD cpu/gpu and having this issue or is it just the AMD cpu with Nvidia gpu ?

24

Iā€™m have a super old amd cpu, a 8500fx.

25

Well, the most common thread is that weā€™re all on AMD and Nvidia albeit different generations. What kind of motherboards are we on? Running ASUS here.

26

Asrock.

Same, I have AMD CPU and Nvidia GPU. Issue persists even after updating the game with the Maverick update.

27

Iā€™m on a Ryzen 5 5600X and 3060ti and have the same problems.
F-18 and any of the 3rd party planes which have added the same effects are basically un-flyable for me

28

So it looks like weā€™re all on AMD and Nvidia, has to be something with the sim not meshing well then.

29

Just kicking rocks for ideasā€¦
resizable BAR / smart access memory SAM = on or off ?

30

Resizeable bar is on.

5900X on Asus TUF Gaming X-570-Plus - latest BIOS/chipset
Igame 3080 - latest Nvidia driver
32GB 3600 RAM

31

I do not utilize the BAR on my 3070, nor the smart access memory

32

Is there a way to disable the effects. ItĀ“s really a shame that I canĀ“t enjoy the F18 and the new challenges because of this.

33

Only thing Iā€™ve been able to do is go into the aircraft CFG file and delete the lines of code that reference that. Really wish Asobo could have included a setting to turn it on and offā€¦

34

I had this issue on my Ryzen laptop after I was experimenting with Windows HPET boot policy settings. I put everything back to default and that fixed it (seemingly, I am unsure that was the true cause).

For anyone with this problem, open an admin command prompt and execute the following to inspect your Windows boot loader settings: (note: it doesnā€™t actually change anything)

bcdedit /enum {current}

Here is mine after I deleted the custom HPET settings (those dealing with ticks timers and clocks):

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {guid}
displaymessageoverride  StartupRepair
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {guid}
nx                      OptOut
bootmenupolicy          Standard
35

HPET was the culprit! Disabling it in cmd prompt completely fixed it

36

i try this but dont work :pensive:
Edit: disable HPET in cmd works!!!

37

To be clear I didnā€™t disable HPET. I just deleted any overriding boot loader values. What is the output of your bcdedit /enum {current} command?

Edit - Glad it helped. Too bad I didnā€™t get any credit for the solution. Oh well, thatā€™s life.

38

There are a few articles available for hpet.

This one is fairly new and explains it nicely.

Happy Flyinā€™

39

Windows Boot Loader

identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {383de80b-39c0-11eb-9d00-b89912d5fa4f}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {383de809-39c0-11eb-9d00-b89912d5fa4f}
nx OptIn
bootmenupolicy Standard

I used the command:

bcdedit /deletevalue useplatformclock

and it seems to have solved it.

40

Ok. Seems turning HPET off works for me. Huge thanks HethrMasn and ccrbc!

Notes:

  1. Disabling HPET in device manager did not work.
  2. Using these two commands in admin comand prompt worked:

bcdedit /deletevalue useplatformclock
bcdedit /set disabledynamictick yes

On the basis that I do not really want HPET off as there may be unknown consequences elsewhere I assume Asobo will fix this. Meanwhile I guess I will run a bat file before and after running MSFS turning off and on these settings - albeit restarting the PC will be a pain in the proverbial.

FYI to reverse the two commands above use these:
bcdedit /set useplatformclock true
bcdedit /set disabledynamictick no

Asobo please fix. I have 1,319 games installed and I only need this fix for your flight sim.