All Activity

You have to output it to a folder that is allowed to write in, for example I put mine in documents/logs The text file goes into LocalState [SimConnect] level=verbose console=1 RedirectConsole=0 OutputDebugString=1 file=C:\Users\(your user name)\Documents\Logs\SimConnect%u.log file_next_index=1

Setting up STAR for a flight to EIDW when the screens went orange. V.1.0.8 Aircraft: A300 Freighter PW Simulator: FS2024 Version: SU5, iniManager Navdata Method: Navigraph Specs: 9800 X3D, 5090, 64 GB RAM WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) WASM: Error -239 / ffffff11 [fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set. WASM: Impossible to get user aircraft [flowmodule.wasm] [FL][ERROR] Failed to get CAMERA STATE from SimVars: -1 WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/A300-600/attachments/inibuilds/Function_Interior_Freighter/panel/inibuilds-A300.wasm is now dirty EDDPEIDW_PDF_1778906271.3ea2187c.pdf

It does seem to be an issue that popped with sim update 5.

Hi, I am having a problem with my A350. Whenever I load a save after a WASM crash, the aircraft starts oscillating in roll while on autopilot, and in manual flight I need to keep the joystick tilted to maintain straight flight. I am not sure whether this is a bug or some kind of system logic, but it always happens after a WASM crash and after loading the autosave. During the last crash (2-hour long-haul flight using AutoSimRate), the displays froze and the aircraft started turning in circles to the right. After loading the save, the aircraft began oscillating in bank on autopilot, and in manual flight it constantly banked to the right. The left and right fuel tanks are balanced. I also tested with ChasePlane disabled. On the control surface display, there is a constant deflection shown on one wingtip control surface. It is possible that I am missing something, but this behavior only appears after a WASM crash and save reload.

Rejected again, because there's no screenshot. I give up...

Since 1.06, it seems, manual waypoint entry triggers the aircraft to immediately sequence to the next waypoint EVEN when the waypoint being edited is NOT the current OR the next waypoint. The issue does not occur in manual mode, but I don't think it should happen in auto mode either, unless the waypoint being edited is part of the current leg.

I've noticed during radio navaid tracking, that it is still not holding a proper WCA. The aircraft will slowly drift downwind over time.

After departure in TOGA mode, selected VNAV and INS modes on the FD. FD began vertical guidance, but the lateral FD kept jumping around. Once the AP is engaged, the lateral guidance became correct.

Same issue here. It happened yesterday and today, so it appears that whatever was "fixed" in the update, broke the APU start. Prior to the latest release, I never had any issues starting the APU.

If one of the INS units does not have a track initialised, it will not show wind data when that mode is selected. It should, since the only data required to compute this is the aircraft heading vs the sensed track.

I went through the PMS setup process whilst using the new progressive aircraft loading system. I noticed that as soon as I entered the fuel and gross weight, those numbers began increasing in real time. This suggests that rather than using fuel flow data to subtract from the initial total entered during setup, this page is actually directly connected to the GW and fuel on board values. (This is also true of the EFDARS thumbwheels, which adjust for every change in weight). This cannot be accurate, since if the aircraft were able to sense FOB and GW on its own, there would be no need to enter these values into the PMS (as it is on more modern aircraft) I suspect it's supposed to only have access to fuel flow values and subtract from the totalizer. However, I could be wrong....

Something is still going on. It's a bit hard to determine what the mechanism is. I just did a Seattle to Boston flight. Nearly 6 hours in the air. During the flight, I updated INS postions 1 & 2 as I passed over VORs. I did NOT update INS 3 during the entire flight. However, upon arrival, INS 3 showed less than a mile of drift, whilst INS 1 & 2 showed 0.4nm and 3.1nm of drift respectively. (You can see this in screenshot 1) In screenshots 2 &3, you can see the sensed position and actual position of INS 3. Although the position is NOT identical to the real position, it does not seem quite right that it drifted so little. It still seems like it's getting a bit of a correction from some operation during flight.

It's something we've starting seeing recently and as of current has no effect on the operation of the aircraft or systems, thank you :)

I'll ask the team about this

Don't know why but the MCDUs are on when you spawn in, and the aircraft is in a Cold and Dark state on these "Verify" screens. When do you do power the aircraft the MCDUs go to its normal status page, but when you depower the aircraft, it stays on and on the same page, but its frozen.

Ultimately yes, In your case for the A350 having your Twist Axis binded for Rudder, and then enabling "Rudder Controls Tiller" would allow use of Rudder and Tiller with the single axis you have. Remember you can also make profiles by aircraft and adjust them as such.

I'll pass this along to the team, as for seeing your own pilot model, I want to say that's a setting in Graphics. I'll have to check Tristar and verify that pilots aren't missing because I've seen the avatar in other aircraft.

Hi all, What do we need to do in order to have the crew displayed in the cockpit. I've been flying this model exclusively for the last week (loving every moment of it) but haven't found a way to get anybody showing up. From the external view it looks like a ghost plane... As a suggestion - how about adding a flight engineer avatar to the 3rd seat. Doesn't have to be animated, and in a perfect world they'd be selectable as on/off so those who like doing the FE role don't have to worry about it getting in the way... ? Just a thought. Bunkie

After this last update the following KVAR works for setting the heading selector on the Autopilot. K:HEADING_BUG_SET

Yeah, ini has gone for a headphones approach which I didn't realise now (so understandable that my topic a while back was locked, I complain a tad bit much about this) but they've used youtube gpws callouts (insert aircraft here) as reference which isn't entirely accurate, all the vids I've seen have the incorrect tonality Here's a video where it does appear the audio is hooked up to the audio panel in the aircraft which means ATC audio and RA callouts: Etihad A350-1000 landing at super busy New York JFK Airport Airbus A350 - Full Approach and Landing in Boston (ENG subtitles) ^That is a bit more clearer audio, I hear a difference They did correct the voice with the a340 and the quality was superb, although the last time I requested it unfortunately it turned into youtube low quality audio.. if there's anyway to implement it like the a340 would be great.

I noticed this in a flight I did yesterday, I will pass it along to the team, are you able to get a video of it happening (if not I will get one later), thank you :)

Can you please make this livery based off the etihad 787 Man City livery . It will make you millions 😀

About 10 days ago the A350 started causing MSFS 2020 to crash out before getting to the launch stage - MSFS just shuts down when I try to use the aircraft? Never had a problem with it before (though it does take an age to load) and every other aircraft I regularly use still launches and flies perfectly (PMDG aircraft, TFDI MD-11 etc), it's just the A350 causing the crash. Any suggestions or anyone else having this problem? It started (or seemed to start) after update v1.2.5? Thanks.

The A300 is still using sim default, even if you have navigraph base installed, ever since the sim move to LIDO NAVDATA in FS24 and as such it won't be updated until the new runways are updated into the sim navdata

This has been logged for the team, thank you.