May 7, 20224 yr Lovely aircraft, but the KAP140 needs a few tweaks. Armed mode for the altitude is not annunciated, and the when engaged, the AP is seeking 'straight and level', when the real KAP140 engages with a 'pitch and roll hold' basic mode. 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 Commercial Member The emergency crank "bug" has been noted and will be fixed. Please contact oisin at milviz dot com for forum registration information. Please provide proof of purchase if you want support. Also, include the username you wish to have.
May 7, 20224 yr 9 minutes ago, JYW said: Lovely aircraft, but the KAP140 needs a few tweaks. Armed mode for the altitude is not annunciated, and the when engaged, the AP is seeking 'straight and level', when the real KAP140 engages with a 'pitch and roll hold' basic mode. I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. 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 Commercial Member We will check out the above. Thanks. Please contact oisin at milviz dot com for forum registration information. Please provide proof of purchase if you want support. Also, include the username you wish to have.
May 7, 20224 yr 11 minutes ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Thank you for that, good find! 😉 - 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.
May 7, 20224 yr On 5/5/2022 at 5:57 PM, ZoblebV8 said: I found one just clicking around inside the cockpit. Didn't know there were nine. I think that's the number I heard on the stream yesterday. I found eight. Robin
May 7, 20224 yr 58 minutes ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Excellent troubleshooting skills. MSFS
May 7, 20224 yr 1 hour ago, Milviz said: We will check out the above. Thanks. Can you please add the Army or Air Force livery? Thanks! Edited May 7, 20224 yr by DJJose MSFS
May 7, 20224 yr 1 hour ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Just changed it. Great find.
May 7, 20224 yr 2 hours ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Thank you, sir!
May 7, 20224 yr 22 hours ago, Bobsk8 said: Made no sense to me when I first read the negative comments about the KAP 140 AP, since I have used it before and never had a problem. I think some just like to make up issues. Unjustified thinking. It does make sense. When the systems.cfg is set up differently in different planes, of course it will operate differently. Edited May 7, 20224 yr by Sender46
May 7, 20224 yr 4 minutes ago, Sender46 said: Unjustified thinking. It does make sense. When the systems.cfg is set up differently in different planes, of course it will operate differently. Yes , I made some changes in the User.cfg that you posted this morning. I didn't realize that the KAP 140 had a user CFG that could be modified. Edited May 7, 20224 yr by Bobsk8
May 7, 20224 yr 4 hours ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Good find indeed, but after applying the changes, with target altitude set, trimmed in climb, engaging the AP starts up with ROL / VS / 0 fpm. Does it capture current pitch for anyone? Bert
May 7, 20224 yr 4 hours ago, JYW said: I found the cause of the AP issues, in the systems.cfg :- DEFAULT_PITCH_MODE is correctly set to '1' (hold current pitch). However, there's then an errorneous entry of "USE_NO_DEFAULT_PITCH =1", which tells MSFS not to use the above default pitch mode. I deleted the above entry, and the AP engages smoothly and correctly now. Also, DEFAULT_VERTICAL_SPEED is currently set to 700, but should be set to 0, to allow the preselected altitude to be changed, without the aircraft (incorrectly) immediately climbing/descending, without VS mode having been engaged. Thanks for this! Does it need to be saved in read only for it to persist?
Archived
This topic is now archived and is closed to further replies.