Dreadnought1906 Posted December 13 Posted December 13 Flightplan is loaded, IRS aligned, It's been about 20 minutes. I restarted the sim and got the same result. 1
Andreas Ochs Posted December 14 Posted December 14 OK.... nice it is mentioned in the known issues.... but.... when will this be solved?
xe_operator Posted December 14 Posted December 14 A known issue of this magnitude should have delayed the release of this update.
frank_m Posted Monday at 07:42 PM Posted Monday at 07:42 PM Since it does not happen very often, there is an easy workaround and the reason behind it is a simulator issue, it is really no showstopper. 1
Dreadnought1906 Posted Wednesday at 07:44 PM Author Posted Wednesday at 07:44 PM You seem to think that we should psychically know what the workaround is, and the cause. I have considered the A350 unflyable until the next update, but if there is a workaround fix, please enlighten us.
Transair Posted Wednesday at 10:26 PM Posted Wednesday at 10:26 PM On 12/16/2025 at 6:42 AM, frank_m said: Since it does not happen very often, there is an easy workaround and the reason behind it is a simulator issue, it is really no showstopper. Frank, having had very few WASM crashes to date, I just had three in a row. All on the ground during the set-up process. I found the AIRAC had re-set to a previous one interestingly. i cleared WASM, Updated Nav, and re-callibrated the throttles (forgot to do that between crashes), and now all fixed and running. I thought it very odd to have WASMs as I have not had them for a long time. It's a very stable platform and I've been enjoying it right through the updates.
frank_m Posted Thursday at 07:24 PM Posted Thursday at 07:24 PM 20 hours ago, Transair said: Frank, having had very few WASM crashes to date, I just had three in a row. The issue described in this thread is no WASM crash.
Transair Posted Thursday at 10:45 PM Posted Thursday at 10:45 PM oh...what's the issue with it then, as that's the pic I got. I assumed it was WASM
frank_m Posted Friday at 08:31 AM Posted Friday at 08:31 AM It is a texture loading problem. By the way, there is a workaround in 1.2.0, so it works for the time being.
Transair Posted yesterday at 12:01 AM Posted yesterday at 12:01 AM (edited) 15 hours ago, frank_m said: It is a texture loading problem. By the way, there is a workaround in 1.2.0, so it works for the time being. good to know..thks..and I have flown it in 1.2 without issue. Edited yesterday at 12:02 AM by Transair
Farlis Posted 5 hours ago Posted 5 hours ago On 12/17/2025 at 8:44 PM, Dreadnought1906 said: You seem to think that we should psychically know what the workaround is, and the cause. I have considered the A350 unflyable until the next update, but if there is a workaround fix, please enlighten us. Maybe using the forum search function would have given you the results? Anyway, the workaround is to wait a bit longer before entering the aircraft after you initially spawn in walk around mode. Let the load settle first. So waiting 10-15 seconds before pressinc crlt-c and spawing into the flightdeck should help.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now