JRHorse

Confirmed here before my away time starts, thanks DroneSim. I'm not sure how this got ticked for me (maybe because I'm still getting my feet wet in FS2024 compared to FS2020). Inibuilds team, since I've heard nothing of this until now, and there's no mention about piloting assistance in the A350 manual from what I can see, could I please suggest you add this to your manual or FAQs in the future. Some may not realize this to be a standard operating procedure, as it is for other aircraft out there. Thank you for your consideration 🙂

I meant to add as well, there are no issues with my joystick inputs when testing them through windows and my thrustmaster control panel.

To follow up on this, with auto tiller disconnect DISABLED I tried to take off again. There was some drift on the runway as I got up to higher speed, but I was able to stabilize down the centerline and get into the air. However, upon touchdown and rollout the plane immediately veered off to the right again and I could not straighten the plane out on the runway. An unfortunate ending to what was otherwise a nice flight. I'll be following for any updates, but will be away from my PC for a few weeks.

I have a Thrustmaster T Flight Hotas One which uses the Z axis of the joystick to control the tiller (Rudder control tiller set to yes) With Auto Tiller Disconnect enabled, when I start my takeoff roll and try to steer the airplane on the runway, the plane suddenly turns hard right. It keeps wanting to turn right, and I am unable to straighten the plane out any further. Turning off Auto Tiller Disconnect seems to keep the aircraft on the runway for me. The manual says that Auto Tiller Disconnect is meant to disconnect the tiller input above 70% N1 for smoother control, so this behavior doesn't seem right, at least for me.

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.

Hi, yes that's correct.

Hello again! I have been experimenting with a few things with the graphics in my sim, as well as the textures on the A300. I wanted to report that when the "Optimised Texture Resolution Pack" is installed for me through iniManager, GSX will not work as I get an error that the "simbrief aircraft doesn't match MSFS aircraft." There's also an error in the corner that says: "Simbrief Error Simbrief Aircraft A306 Doesn't Match MSFS Aircraft W_Flyer" I've attached a screenshot. When the texture resolution pack is removed, GSX works as expected. If I understand correctly GSX usually pulls one's aircraft.cfg file, and since the texture resolution pack installs a second folder in the community folder, I'm wondering if this is where things are getting tripped up. While not running the pack appears to be the simplest solution, I hope you'll consider in a future update a way for it to work with the pack installed, unless there is a workaround that one can suggest. Many thanks! Jose

Hello, just wanted to say what an amazing plane! Really had fun with a cargo flight tonight! I had some issues with the EFB tonight and I don't seem to be finding any topics on this here. I'm on 1.0.1 of the airplane (the most recent iteration) in the cargo version, and when attempting to load simbrief values the plane's fuel listed on the IFB (and on the plane) appears to be in kilograms, even though I set my plane up for pounds. The airplane's fuel values on the overhead appeared to be listing kilogram readouts as well. Now I'm not sure at that moment whether or not the correct fuel amount in pounds was loaded; entering the fuel manually in the IFB initially yielded the same problem, but after several attempts to fuel it finally loaded (and indicated on the overhead) the correct amount in pounds. For me just one small blemish to what is otherwise a wonderful plane. I hope to take it for another spin when I can.

I did a A310 flight from KDEN to KDFW with a pretty straightforward route. After reading your comment and doing my homework, looking at some very interesting cockpit videos on YouTube, and reviewing a fascinating document I came across on google about the A310 autoflight system, the method I took to using the autopilot was as follows: -Climb in Profile -Cruise in ALT.HLD -Descent starting in VS using descent calculators, then eventually changing to LVL/CH before configuring for approach and landing The V/S Dev showed I was way below the descent path, but at least I hit all of the altitude restrictions properly this time. 😅 One thing I noticed on the descent was that I could not set a pre-set speed in knots in the speed display, and was wondering if this was a bug. Pre-set speed worked fine before departure (setting my V2 and then using Pre-set to select 250 knots). On descent, when the plane was descending in VS and Mach and I attempted to pre-set a speed of 290 knots (so it could capture 290 knots on the descent per the STAR), the Pre-Set button did not light up and the display read 000 knots, spooling the engines down at that point. Clicking the black button to the left of that display returned me to mach, and the engines were revving up again. I ended up just leaving it in Mach speed until 290 knots was indicated, then selected the black button to change Mach to Knots. Many thanks for your insight and feedback!

Thanks, I experimented with V/S and Level change on my return trip to Denver. Seems I have some homework to do on these descents; some descent restrictions were met while others were missed. While following the vertical deviation at times, I noticed it fluctuated from waypoint to waypoint. I'm guessing this is normal behavior?

I just completed a flight from ORD to DEN in the A310 and tried the TACT speed intervention, setting the 280 knot speed as called for in the star. Unfortunately, this did not stick (it went back to ECON speed after passing a waypoint). Changing this a few times resulted in the aircraft flying too high off of the descent path and not respecting altitude restrictions on the approach. The PROG screen also got stuck on ECON CLB, which is a first for me; not sure if it resulted from what happened here.

Good day, I've returned to flying the A310 in the sim and just had one question, as I can't seem to find an answer to it. I have not run into this scenario yet, but is there any way to modify the descent profile of the A310 ahead of time to change its speed (like can be done on, say, A320 or 737NG), or is that done strictly from the FPLN pages in the case of the A310? The scenario I may run into is on STARs to certain airports that have the speed instruction to maintain mach number until 280 knots (or whatever the chart says) then maintain the speed in knots until slowed by the STAR. So I am wondering if, say, I could set a descent speed of "mach number / knots number." Thanks for any assistance, Jose