True. I have checked the manual for the F35. it does not have a key layout to show what key bind to what function. I read the manual and all I can find is CTRL+Z is to enable autopilot. That’s it.
I hope they can remediate their manual to show us what key bind goes to what function.
Managed to takeoff LAX, bug around LA for 20-25 mins, land at Victorville and fuel up, VSTOL out of there and then bug around another 30 mins in the B without any issues. Progress!
EDIT: Next flight CTD within 10 mins ):
Page 46 of manual has info on navigation:
RTE (GPS route) – in this mode, the navigation systems will follow the Flight Simulator flight plan.
NOTE: in the initial release there is no way to alter the flight plan within the aircraft: flight plan must be
created with the game interface o[r] with external tools. It is, however, possible to select a specific flight plan.
NOTE: RTE is the default navigation mode if a flight plan is loaded. Otherwise no nav source will be selected by default
Similar experience for me. My last flight was a CTD and the one before it was fine.
I mostly fly the C in VR and have had only one crash since release. That was when I tried to load Sky4Sim Pad. Other than that, a really incredible flying machine. My pitch trim works too, albeit very slowly. Virpil HOTAS setup. Latest beta update this morning. Departed NAS North Island, flew south and then about an hour low level E along the US/Mexico border. No problems. Man, that’s a big desert out there.
One good thing that came from it was learned how to cold start the plane. There’s got to be something either a file or something that can be updated to make this stop crashing like that
85 mins of flight with the F-35A and no issues so far. Although, good to know the ugly exhaust blob is not related to just the DC Designs jets.
Flew Charlie in VR last night absolutely no issues flew 45 mins.
Two flights, separate but in the same session, in CA, and no issues. They were fairly short flights; combined probably about an hour. I turned off FSRealistic for these, btw.
Now I’m off to do some gliding in the Alps. (Talk about completely different…)
Anyone else having a problem where throttles don’t work?
Even after binding to throttle 1 axis, touching the ground it doesn’t respond to throttle. however, if you enter hover mode and go up into the air in VTOL, it does seem to respond but it’s strange as it flicks around. when moving from VTOL to normal flying, it will be on 100% power until you move the throtttle, where it suddenly goes to 0% thrust. uuper annoying
Thanks to new update, my F35 work like a charm no CTD (touch wood). I’ve enable back all the mods in my Community folder and so far no crash. I’m in my 3 hours of flying in the F35B.
I’m downloading the update. As a Beta user with default path I have a complete reinstall. 115GB. The price to pay for the VR fixes I have been using in Beta for the last month. Fingers crossed the new update helps the CTD as it is unusable having unpredictable crashes every 10mins or 30min if I am really lucky.
I haven’t been able to complete a flight yet with this aircraft since I bought it.
In VTOL thrust is managed automatically , and you have no control over it , read the manual 
It does mention other things towards the back of the manual:
Wing Lights Toggle activates STOVL configuration.
HDG Hold Toggle (when already in STOVL mode) activates true hover mode.
Aileron trim left/right for fine speed control in hover mode (slower/faster. Can go backwards into negative values).
ALT Hold for v-speed hold in hover (not sure you really need this tbh).
Note: Can’t go into hover mode if craft weight is too high (the word HOVER on MFD is red if unavailable).
Need to be <250kts to activate STOVL mode.
Had a great flight for an hour…looks fantastic and flies beautifully but then bang CTD, first one I’ve had in over a year so something is definitely still off with this plane, shame really
Exactly the same here, not had a CTD in a very long time, and was flying this in VR earlier for almost an hour before the crash.
Event View shows this.
Faulting application name: FlightSimulator.exe, version: 1.21.18.0, time stamp: 0x00000000
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
ucrtbase.dll is the C runtime the game is compiled against. Any code running on the plane is TypeScript or WASM, ran via an embedded version of the V8 runtime, and as such mods don’t have direct access to said C runtime. Something between the mods’ code/scripts and the C runtime is screwing this up, not the plane.
I don’t really get what you mean. The mods code and/or scripts is PART of the plane.
Yeah, but none of the APIs of the C runtime are exposed to the plane, neither in TypeScript nor in WASM.
The C runtime contains typical basic functions to deal with memory, strings, files and math. Applications written in C/C++ to run on Windows typically use these, at least when using Visual Studio/C++.
TypeScript is a super-set of JavaScript, that adds a static typing system on top, but eventually gets compiled down to plain JavaScript, which gets then interpreted by V8 with hot paths being compiled down to binary code to speed execution up. At no point in does it have any access to UCRT APIs. It has to use the functionally supplied by the V8 runtime instead.
WASM is a target to compile/port previously native applications/code to, that are/were written in languages like aforementioned C/C++, to allow code reuse and writing more efficient implementations. It doesn’t have any access to UCRT either. While it ships with WASM versions of that, the crashes happen in the native system DLL. If the WASM version would crash, it’d claim the crash location to be within FlightSimulator.exe instead of ucrtbase.dll, because Windows doesn’t have a concept of WASM modules (they’re loaded into memory by the V8 runtime, not the image loader of Windows).
As someone else said, something likely passes a bad pointer to some UCRT function. 0xC0000005 errors are access violations that happen, when you try to read or write memory you haven’t allocated and therefore rights to access. And that’s something outside the code running the planes.
