FSR500 not retaining state and always starting as fresh

Sim Update 4 Beta | MSFS 2024 External 3rd Party Products
, , , ,
1

1 tag is required - add them in the tag section next to the title above:

  • One for platform (ms-store, steam, xbox , or xcloud)

  • One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue: FSR500 doesn’t store state and restarts the first fly wizard every flight

FREQUENCY OF ISSUE

Every flight

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Launch MSFS 2024 SU4

  2. Start a flight with the FSR500 aircraft and get the first flight wizard on the tablet; plane starts in a fresh state every time despite activating all the persistence options

  3. Happens when changing livery and when keeping the same livery between flights

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using:

[PC Only] Are you using Developer Mode or have you made any changes to it? No

[PC Only] What GPU (Graphics Card) do you use? 7900XT

[PC Only] What other relevant PC specs can you share? 5800X3D

MEDIA

Please add a screenshot or video of the issue occurring.

2

Moved to Sim Update 4 Beta | MSFS 2024 > External 3rd Party Products since aircraft is a 3rd party one.

3

I can confirm the issue (Beta 1.6.5.0).

4

But what persistance? Fuel? Or failures? Failures should remain un affected.

R.

5

Sounds like this is likely another WASM issue WASM Addons (Just Flight, PMDG, Inibuilds) features broken - #21 by NilPointer3638

6

No is not, our WASM is fine.. I think is something else.. I am asking what symptoms it is.

1 Like
7

On every start of the sim, when entering the aircraft, the music plays and the EFB start page displays the welcome screen. You have to answer a few questions concerning the failure system, or skip it.

2 Likes
8

ok this could be a problem with the saving to the cloud, rather than WASM itself..

R.

1 Like
9

This, and the “timers” on the various components are always reset to zero.

10

They reset to zero as a result of the wizard.. let’s see what the Asobo team investigate with this report.

R.

11

We have replicated this internally, and yes it is something to do with WASM saving to disk.

It affects all my products.

Will spend some days now trying to understand exactly what internal C++ function is now broken so I can report it to Asobo properly.

Best,

Raul

3 Likes
12

UPDATE

I been debugging lines and lines and lines of code.. I think I found the culprit problem with WASM for this under SU4 and I have now raised a proper support ticket with Asobo via their support forums:
https://devsupport.flightsimulator.com/t/severe-wasm-bug-with-su4-unable-to-perform-io-file-functions/16676

We will need to wait to see if my findings are correct, and what actions we can take after, but rest assured I am on the case, wherever happens, we will find a fix guys.

Best,
Raul

UPDATE

Working with Asobo we found now the cause, they have fixed this already on their side and we just need to wait for the fix to go on their next availability window of updates for SU4.

Thanks to everyone for reporting this.

All the best,
Raul

4 Likes
13

I wonder if the last SU4 update fixed it?

14

Yes, try :slight_smile:

15

Ah, shucks, I went back to SU3 for the time being :sweat_smile:

16

Update on this: I reenrolled into SU4 beta.

Flew the FSR500: I had to redo the wizard (I had purged the WASM folder anyway so expected). But then, after ending the flight and loading the plane again, I didn’t have to.

So the issue seems to have been fixed in the current SU4 version.

1 Like
17

I have a small question for the developer, if they happen to see this message. I play via the cloud gaming service GeForce Now, and I’m experiencing the same issue with the SU3. But since it also occurs with other aircraft, I’m confident this is a GFN issue, not a problem with the add-on itself.

I suspect that GFN simply blocks access to the folder where the aircraft state is saved. Before I contact their support team, I’d like to ask the developer: what is the path in question, potentially (Steam version of the game)? Perhaps if I provide GFN with the exact path, it’ll be easier for them to fix the issue. Thanks in advance for your response.

18

It needs access to WASM work folders, required by the SDK, it is all in the msfs SDK documentation.

Best,

Raul

19

Thank you very much!