JRHorse

Hello, I used 1.0.4 on a livestream last night flying into Dallas Fort Worth runway 36L. I had issues while attempting to have the autopilot capture the ILS. I intercepted the localizer using LOC at a 30 degree angle, which Autopilot seemed to do rather aggressively. Then when I changed over from LOC to ILS it stopped attempting to track the localizer all together and completely missed capturing the glideslope, even though LOC and GS were showing on the AFCS annunciator. Thankfully I was able to disconnect and manually land the plane. i was navigating with the GPS, and can confirm it was set to VLOC and that NAV 1 was set to the correct ILS frequency and course.

I wish to suggest that on AFE APU start, the AFE turns on the bleed air after APU startup. Perhaps also set the bleed and pack switches to provide air conditioning to the cabin, as well as set APU gen field, breakers and bus ties. Currently from what I have seen, this AFE function merely turns on the APU. Unless I’m missing something, following solely the AFE through to engine start results in zero pneumatic pressure for the start unless additional manual setup is done to ensure the isolation valves and pack switches are set.

Hi, I want to post again (in the correct topic this time 😅) the issues I'm having with the GNS 530. I thought this had been fixed as I mentioned in a previous post, but this is continuing to be an issue for me. In a few instances, the GNS 530 is not working upon loading the plane. Confirming that there is electrical power as well as the radio master switches turned on, I cannot get past the database screen (OK/Enter to advance). Reloading the plane is hit or miss as far as getting the unit to properly load. Then, as I'm continuing on with my first flight in INS+GPS mode (the INS driving the autopilot), I saw the GNS 530 reboot on its own. No flight plan data loaded is lost, so far.

Disregard, looks like it came up on a subsequent load.

My apologies, this should have been posted in "systems" subsection.

I know I should be brushing up on how INS works but... Upon loading the Tristar, the GNS 530 is not functioning for me. The enter button (and all buttons for that matter) do not work on the first screen after loading (database screen). This applies to both GPS and INS+GPS modes. I also let the INS computers align, and even after that the GPS doesn't work.

Hi, I noticed the provided SimBrief profile for the F27 has a maximum of 22 passengers, whereas the seating capacity of the plane is listed as 44 passengers. I am doing a short flight from KSAT to KDFW and I attempted to edit the profile on my own to increase the maximum number of passengers; at 44 passengers it is giving me a maximum landing weight warning.

Hi, since I have not come across this from my searches... is there a specific Simbrief profile available for the A340 VIP variant? Or is this a question that need to be addressed with the navigraph folks? Thanks so much!

Hi and thanks so much for your reply and video. I do need to make a correction, the navdata method for this was the in-sim nav, instead of navigraph. Today I tried another flight from KJFK to KLAS, and there were no WASM crashes. Everything was pretty much as expected. Before this attempt I cleared the WASM folder, and after loading into the sim I changed to Navigraph and updated the data before switching on the electrical power.

Reporting a WASM crash on the iniBuilds A340 when inputting the arrival into the FMS. Steps to reproduce -Load plane at gate, power on, turn on APU -Load flight plan in tablet then via FMS -Enter Departure and Arrival procedure While putting in the arrival procedure, select the runway, approach, arrival and arrival transition. WASM crash occurred when I clicked on "NO VIAS" in the ILS approach for runway 27C at KORD. Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Version: 1.0.7 Inimanager Navdata Method: Navigraph Specs: AMD Ryzen 7 7800X3D, 64 GB Ram, RTX 4070 Ti SUPER 16GB The Autosave file was not available in the folder indicated in the post about making WASM reports. I am enclosing all other screenshots and the flight plan. Not a good way to start off my first flight in the A340, but I hope this information helps. Thanks, Jose KJFKKORD_PDF_1768609824.pdf

Hi, thought this would be the best place to ask this question… I saw via email update that the iniBuilds A340 aircraft will soon be available to download on iniManager. Will it be possible to transfer A340 marketplace orders to iniManager using the transfer request at that time?

After unloading Inibuilds KLAX and taking a spin down runway 24R a few times in the "vanilla" KLAX, to me there are no noticeable bumps on the runway.

After unloading Inibuilds KLAX for further testing, this appears to be an issue with the game itself as it's happening with multiple airports (both default and 3rd party), so please close this discussion and I'll report this as a bug to Microsoft.

Wanted to add here that I experienced a problem landing at KLAX tonight, using the TFDI MD-11 and version 1.3.0 of KLAX. I've seen some posts reporting bad bumps on 24L. My landing was on 24R, and on the landing roll my plane hit a bump on the runway and tipped over to the left. I loaded a couple of random aircraft and slewed to 24R (see previous post about spawning on runways) for some practice runs, and I definitely ran into some pretty noticeable ground bumps. If needed I'd be happy to try and record what's coming up for me on my end.

Hello, I'm using the latest version of KLAX, version 1.3.0, using MSFS 1.38.2.0 (which released on the date of this post). When I am attempting to spawn a plane on any runway, no matter which runway I select, the plane will always load on Runway 25R.