March 29, 20215 yr 9 hours ago, DAD said: Did you try the throttle calibration in the EFB? Yes, that solved the issue. Thanks. I was flying into EDDN on VATSIM and got a 360° turn to reduce some altitute. Then I got cleared direct to a waypoint and suddently after I entered the DCT waypoint the flightplan vanished. The only thing I could see was the departing runway from my origin. No data on the CDU, neither on the ND. However, it apparently kept the course of the deleted flightplan. That was weird, I just requested vectors, but that kind of stuff is challening, but sometimes a bit annoying. Especially because the work load is high enough on the approach flying online.
March 29, 20215 yr Amased at the job FBW have done with this, just tried out the autoland feature, and despite a strong cross wind and crabbing in on final it was spot on... this plane just gets better and better.( Experimental version) Edited March 29, 20215 yr by Car147 AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive
March 29, 20215 yr 2 hours ago, daztheman70 said: Update: Tried everything remove all addons from community folder bar the Flybywire updated to the latest version, Calibrated the throttle using the EFB, get to around FL320 climbing at 2-300 Fpm Sometimes it just levels off and wont climb any higher even at Mach 0.78, don't understand the issue I am far from novice been doing this since 1988 lol I just want it to work 😰 Attached some images https://ibb.co/YbcCJZ0https://ibb.co/SJybvQyhttps://ibb.co/6npYMZFhttps://ibb.co/KL3shBjhttps://ibb.co/7N8zKK9https://ibb.co/8jx8nFBhttps://ibb.co/mzJZNYH Thanks daz So you're in open mode. For managed climb your FMA should read CLB ALT and your altitude selector on the MCP should say 36000 ⚫ but since it's just showing 36000 without the dot, I think you might just need to left click the top portion of the selector wheel to get it into automated climb and off of open mode. Being in OP CLB means the aircraft is trying to maintain speed with pitch. I'm not quite sure if it'll actually increase thrust to achieve an altitude or if it will just aim for a speed and that's it. If that doesn't work, which I have a feeling it won't (since you're a veteran with decades of reaching ToC without issue), try the FBW livery and not the new ORBIT / MSFS liveries. I read some talk about how those were bugging the simulation somehow. if neither of those solutions prevail, you'll have to go to their discord channel and post those images into the "help" chat. You'll get help from the devs in under 5 minutes. Edited March 29, 20215 yr by WestAir Take-offs are optional, landings are mandatory.The only time you have too much fuel is when you're on fire. To make a small fortune in aviation you must start with a large fortune.There's nothing less important than the runway behind you and the altitude above you. It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.
March 29, 20215 yr 5 hours ago, daztheman70 said: Update: Tried everything remove all addons from community folder bar the Flybywire updated to the latest version, Calibrated the throttle using the EFB, get to around FL320 climbing at 2-300 Fpm Sometimes it just levels off and wont climb any higher even at Mach 0.78, don't understand the issue I am far from novice been doing this since 1988 lol I just want it to work 😰 Attached some images https://ibb.co/YbcCJZ0https://ibb.co/SJybvQyhttps://ibb.co/6npYMZFhttps://ibb.co/KL3shBjhttps://ibb.co/7N8zKK9https://ibb.co/8jx8nFBhttps://ibb.co/mzJZNYH Thanks daz I did another flight today and even reached FL420, GW was similar to yours and temperatures also not so much different. So I'm curious what is going on. I just updated the experimental version and added more parameters to the FDR (flight data recorder). If you try out the new version and it happens again, you can send me the FDR file if you want. Might help analyzing the issue. You can also press the DFDR button (right of the throttles on the pedastral) to mark a certain point in time. This get's fed into the FDR file as well...
March 30, 20215 yr 19 hours ago, ray hughes said: Is it just me - the very latest update as of 29/3 - the ground role is much better!!! now the A320 doesn't surge ahead - but is much more realistic... 18 hours ago, 737_800 said: Yes, it's beautiful. They even fixed the issue with the increasing taxi speed even while on idle thrust. No it's deccelerating as it shoud be. How it was before was more accurate. I'm sure this will be adjusted in the future.
March 30, 20215 yr 18 hours ago, 737_800 said: No it's deccelerating as it shoud be. It shouldn't be decelerating. That's an issue. It should very slowly accelerate on flat ground.
March 30, 20215 yr 1 hour ago, FlyingInACessna said: It shouldn't be decelerating. That's an issue. It should very slowly accelerate on flat ground. It's normal that I accelerate to 20knots and put the throttle back to idle and the airbus accelerates up to 30,40,50 knots?
March 30, 20215 yr 32 minutes ago, 737_800 said: It's normal that I accelerate to 20knots and put the throttle back to idle and the airbus accelerates up to 30,40,50 knots? Yes, that's the realistic behavior. You have to use the break to taxi within the speed limits. Edited March 30, 20215 yr by crimplene
March 30, 20215 yr 2 hours ago, FlyingInACessna said: It shouldn't be decelerating. That's an issue. It should very slowly accelerate on flat ground. Correct. There's currently an issue where it is decelerating on wet/snowy runways, but we cannot change that ourselves since the SDK doesn't currently allow us to modify any ground friction/handling constants. Edited March 30, 20215 yr by IcemanFBW Please do not contact me via DM for support or help with the A32NX mod. We recommend using our help channel on our Discord.
March 30, 20215 yr 29 minutes ago, IcemanFBW said: Correct. There's currently an issue where it is decelerating on wet/snowy runways, but we cannot change that ourselves since the SDK doesn't currently allow us to modify any ground friction/handling constants. It's decelerating on dry runways in the experimental version with the new engine model. Ground idle in the new engine model will need to be adjusted to account for the too high friction even on a dry runway just like the engine model in the current master was. Edited March 30, 20215 yr by Donstim
March 30, 20215 yr 18 minutes ago, Donstim said: It's decelerating on dry runways in the experimental version with the new engine model. Ground idle in the new engine model will need to be adjusted to account for the too high friction even on a dry runway just like the engine model in the current master was. I can confirm that too. Definitely needs adjusting to a slow acceleration on idle.
March 30, 20215 yr 1 hour ago, Carts85 said: I can confirm that too. Definitely needs adjusting to a slow acceleration on idle. +1 Kind regards, Hans van WIjhe Acer Predator P03-640 2.10 Ghz Intel 12th Gen Core 17-12700F 64GB memory, Noctua NH-U9S Cooler, 1.02 TB SSD HD, 1.02 TB HD, NVidia Geforce RTX 3070 16GB Memory, Windows 11 (x64)
March 30, 20215 yr 14 hours ago, Car147 said: just tried out the autoland feature, and despite a strong cross wind and crabbing in on final it was spot on... t Quick question: I tried an autoland for the first time into Liverpool, ILS Rwy 09. LOC and GS intercept all perfect. Final, flare and touchdown all perfect, as was initial centre line tracking. There was a small headwind component, 4kts I think. Then after the nosewheel touched down, with some reverser going in, the aircraft veered sharply off the runway to the left. As in 90 degrees to the runway. With full right rudder and differential braking, still could not prevent it and ended up ploughing off into the grass on the left side of the runway. Perhaps the AP needs to be disarmed sooner? I am guessing that this should not happen though? Edited March 30, 20215 yr by RaptyrOne GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
March 30, 20215 yr Hi Greg, I'm sure your passengers will forgive you 😉 Yes, disarm the AP before inverting the throttles and you should be fine. - PC Hardware: AMD Ryzen 9 9950X3D // Asus ROG Crosshair X870E HERO // 2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 // ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600 // Corsair 1600W PSU Samsung Odyssey Arc 55" curved 165 Hz monitor. - Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7.
March 30, 20215 yr 1 minute ago, David Roch said: Hi Greg, I'm sure your passengers will forgive you 😉 Yes, disarm the AP before inverting the throttles and you should be fine. Well, the Autoland greased the landing so those passengers that were asleep on landing certainly weren't asleep a few moments later! 🙂 Thanks! GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
Archived
This topic is now archived and is closed to further replies.