April 27, 20224 yr Turning on FD on the ground, pushing VS, and the VS wheel does not do anything. Altitude alerter armed or not. Setting and adjusting PIT works, and after taking off in ROL/PIT mode, first time pushing VS results in -2000 fpm. Turning off VS and turning it back on, VS then captures current vertical speed. After some use in the autopilot, VS mode seems to work OK. Bert
April 27, 20224 yr 2 hours ago, Bert Pieke said: Turning on FD on the ground, pushing VS, and the VS wheel does not do anything. Altitude alerter armed or not. Hmmm... strange. Just tried that with the C414 ver 1.7 and the TDS panel, and can't replicate that problem. Al
April 27, 20224 yr Author 29 minutes ago, ark said: Hmmm... strange. Just tried that with the C414 ver 1.7 and the TDS panel, and can't replicate that problem. Al Hi Al, strange indeed.. right now I cannot replicate it either... Next time this occurs (if it does), I'll pay attention to the specific situation. Right now, I can load it up, or switch from another aircraft, and all is well.. Beta 1.7. is definitely the best one yet! 🙂 Bert
April 27, 20224 yr Author However.. if I sit on the ground adjusting the VS wheel, I go from 0 fpm to 100 / 200 / 300 / 400 as seen in this screenshot, and the next click on the VS wheel is... -500 fpm.. The exact sequence matters (maybe this will help with troubleshooting..) PIT/ROL mode, VS, HDG.. and the VS adjustment is OK PIT/ROL mode, HDG (which forces VS) and the VS adjustment skips from 400 to -500 fpm The altitude alerter also needs to be armed (ALTS) If I continue to roll the VS wheel, it again skips after it reaches 400.. and again and again. Edited April 27, 20224 yr by Bert Pieke Bert
April 27, 20224 yr 38 minutes ago, Bert Pieke said: However.. if I sit on the ground adjusting the VS wheel, I go from 0 fpm to 100 / 200 / 300 / 400 as seen in this screenshot, and the next click on the VS wheel is... -500 fpm.. The exact sequence matters (maybe this will help with troubleshooting..) PIT/ROL mode, VS, HDG.. and the VS adjustment is OK PIT/ROL mode, HDG (which forces VS) and the VS adjustment skips from 400 to -500 fpm The altitude alerter also needs to be armed (ALTS) Hi Bert, I've tried the sequence you posted and some others, and reloaded the plane a few times, but still can't reproduce the problem. Maybe some others can chime in with what they are seeing on this. Al
April 27, 20224 yr Author Just now, ark said: Maybe some others can chime in with what they are seeing on this. I have asked my buddies to try this.. hopefully someone can figure out what is going on. Does the autopilot (incorrectly) assess that I am above target altitude and want me to descend? Bert
April 27, 20224 yr 2 minutes ago, Bert Pieke said: I have asked my buddies to try this.. hopefully someone can figure out what is going on. Does the autopilot (incorrectly) assess that I am above target altitude and want me to descend? I don't think so. I've been testing at an altitude of approx 6100ft (KCOS) with alerter settings above and below that. Al
April 27, 20224 yr Author Just now, ark said: I don't think so. I've been testing at an altitude of approx 6100ft (KCOS) with alerter settings above and below that. Al I'll try at another airport... My test was at CYCD. You might try that as a test.. I am still getting this, in spite of restarts etc. Bert
April 27, 20224 yr 43 minutes ago, Bert Pieke said: I'll try at another airport... My test was at CYCD. You might try that as a test.. I am still getting this, in spite of restarts etc. OK, finally got some "results". It seems if you go to a sea level airport (CYCD, KSFO, KJFK) strange things happens, like I can't adjust the VS with the wheel after turning on the FD and then HDG. But if I go back to KCOS, or another airport not close to sea level ( ie, greater than 300 hundred feet above sea level) it all works. So I'm thinking the issue has to do with the initial value of an altitude related Avar. Al Edited April 27, 20224 yr by ark
April 27, 20224 yr Author Just now, ark said: So I'm thing the issue has to do with the initial value of an altitude related Avar. Yup.. confusing.. the VS skip point moves with the baro altitude setting. Edited April 27, 20224 yr by Bert Pieke Bert
April 28, 20224 yr Replicated at A Coruna [LECO] (336ft MSL). Exact cockpit sequence, with altitude alerter set at 2,000ft, armed, AP Roll/Pit, HDG (activates VS), then roll vertical speed. Sequence is 100, 200, 300, 400, -500, -400, -300, -200,-100, 000, 100, 200, 300, 400, -500 ... (Several other variations on this order do not seem to produce the strange result.) --Mike MacKuen
April 28, 20224 yr 3 hours ago, MM said: Replicated at A Coruna [LECO] (336ft MSL). Exact cockpit sequence, with altitude alerter set at 2,000ft, armed, AP Roll/Pit, HDG (activates VS), then roll vertical speed. Sequence is 100, 200, 300, 400, -500, -400, -300, -200,-100, 000, 100, 200, 300, 400, -500 ... (Several other variations on this order do not seem to produce the strange result.) A fix for this bug is being tested, and should be ready for the next C414 update. Al
May 7, 20224 yr @Bert Pieke Both APs in this (otherwise beautiful) bird are a real mess, don't you find? The Navomatic has no physical way of engaging APPR mode - the "button" is just an annunciator and (like most modes in this a/c) APPR is not bound to the default MSFS key commands. Have you managed to engage APPR in the Navomatic version? If so, what's your trick? Also, as you mention, there are many gremlins with VS and IAS selection, and with just mode selection in general. I don't know why FSW just have not binded all AP commands to their respective MSFS key assignments / offsets, as every other MSFS aircraft developer has. A shame to see that FSW have abandoned this forum section in favour of "Discord only" support (see the bug reporting thread). Not much good for those of us that do not use (and will not use) the monstrousity that is Discord. 😊 Uninstalled this plane now - have never come across anything with such a mess of an AP(s). Don't hold up much hope that this will be addressed as I originally reported it to FSW on release; months later, the plane is at v1.08 and the AP issues are exactly the same. [/whine] Edited May 7, 20224 yr by JYW Bill 😎FS2024 • Currently in 'GA mode' : A2A Comanche 2024 & Aerostar • Black Square C208, Bonanzas, Barons, TBM850, Dukes • COWS DA40 & DA42 • FSW Legacy, C24R Sierra & C414 • Echo Falco F8L • FFX HJET, Visionjet and P180 2024 • Got Friends A32 Vixxen • FSReborn Sirius TL3000, Sting S4 and Piper M500 • Flyboy Rans S6S • Skyward DA50RG • SWS Zenith CH701, RV-8, RV-10, RV-14, PC12 • Milviz C310R • Air Foil Labs Bristell B23 TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro9800X3D • RTX 3080 • 64GB DDR5-6000NPPL licence holder in the UK
May 7, 20224 yr Author 1 hour ago, JYW said: Don't hold up much hope that this will be addressed The AP is still in beta... suggest you be patient (like the rest of us) and fly the C310 in the meantime.. Edited May 7, 20224 yr by Bert Pieke Bert
Archived
This topic is now archived and is closed to further replies.