December 16, 20205 yr 2 hours ago, DAD said: Correct this is also what I see. Atc provides arrival information too late with STAR beginning behind you and forcing AP to turn around. I got used to DCT on the FMS to the next WP, too ps: downloaded the actual cfbw version today and it behaved like the current stable mod 0.4.2, ie after I engaged AP after takeoff the neo went into a right downwards curve. Went back to the previous cfbw mod (approx. 3-4 days old) and same departure went flawless, catching flight plan and track perfectly. @AGuther as I saw that you made some changes today on the cfbw mod Hmm, strange indeed. I mean I mainly keep the FBW branch up to date with the master...the last days it did not make real changes that could do that. Is this behavior reproducible with that newer version? The problem is that I do not really fly with the usual A32NX...I’m constantly working on some stuff, today I worked on the LOC law...
December 16, 20205 yr 8 hours ago, AGuther said: Is this behavior reproducible with that newer version? hmmm, may be one of those MSFS mysteries as I installed the last cfbw downloaded Dec 11 and everything is now ok, just heading towards NZCH and landed safely Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr is the link on the first page up to date automatically with the latest version ?
December 16, 20205 yr @dyl55 earlier in the thread @AGuther mentioned it does. Looking at the GitHub, it was updated 2 hours ago again! Martin Martin Parr Retired professional yacht skipper for vessels up to 46m System: Omen 40L GT13-0054na Gaming PC; Windows 11 Home 64-bit OS; Intel Core i9-10900K CPU @ 3.7GHz; RAM 32GB; Samsung S34J55x Monitor 3440x1440 @75 Hz Resolution; NVIDIA GeForce RTX 4080 Ti. MSFS P/D; TM Pendular Rudder Pedals, TM Warthog Hortas Throttle/Joystick Combo.
December 16, 20205 yr 1 hour ago, DAD said: Is this behavior reproducible with that newer version? Yes, it is. At random, however, sometimes all goes well, other times the plane goes berserk near the first right/left turn in an APP. Workaround is to make that turn to the right/left in heading mode. A DIR to shows this same behavior, sometimes all goes well, other times it fails. 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)
December 16, 20205 yr 1 hour ago, hvw said: Yes, it is. At random, however, sometimes all goes well, other times the plane goes berserk near the first right/left turn in an APP. Workaround is to make that turn to the right/left in heading mode. A DIR to shows this same behavior, sometimes all goes well, other times it fails. wish me luck then, trying yesterdays's cfbw now from Malpensa to AS's Cologn-Bonn Update: perfect takeoff and flight following... so far so good. wiper don't work though 🙂 Edited December 16, 20205 yr by DAD Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr 13 minutes ago, DAD said: wish me luck then, trying yesterdays's cfbw now from Malpensa to AS's Cologn-Bonn Update: perfect takeoff and flight following... so far so good. wiper don't work though 🙂 Phil, I did a lot of approaches to EDDK. The last few days rwy 14L was the prevailing one for landings. Out of the 5 APPs I did only 2 were without any problem, the other three had the reported problem after WYP. The workaround I found that works is, as soon as I passed WYP I switch to heading mode, fly passed the next waypoint and then engage managed mode again. Doing so, all goes well. I don't think FBW is to blame for this undocumented feature, rather ASOBO is with their repair of a more or less well-behaving A/P turning it into a Russian roulette one 🙂 . 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)
December 16, 20205 yr Hey, I've just tried an approach at KPHX with the custom version and as soon as I click the approach button, the plane do not follow the GS and start to descent till ground way before the runway, do anyone know why ?
December 16, 20205 yr 18 minutes ago, dyl55 said: Hey, I've just tried an approach at KPHX with the custom version and as soon as I click the approach button, the plane do not follow the GS and start to descent till ground way before the runway, do anyone know why ? Did you double check that the ILS was tuned in and wa active at all? Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr 22 minutes ago, hvw said: I don't think FBW is to blame for this undocumented feature, rather ASOBO is with their repair of a more or less well-behaving A/P turning it into a Russian roulette one Yep guess Asobo is the culprit here as STARs are added too late when giving ATC approach clearance, I am in 99% of all cases already ahead of the first WP of the STAR, causing the neo turn turn back to start the STAR from the beginning. As you mentioned, enable HDG can help. I myself got used to add and activate the approach in FMS and then veeeery quickly use the DIR TO function to skip the first STAR WPs (which are behind me already by then), still causing the neo to steer away but if you are fast.... 😉 Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr 58 minutes ago, hvw said: The last few days rwy 14L was the prevailing one for landings Same here. And again adding the approach added WPs behind me, quickly chose DIR to DEPOK and all good 🙂 EDIT unfortunately a CTD on short final 😞 Edited December 16, 20205 yr by DAD Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr 33 minutes ago, DAD said: Did you double check that the ILS was tuned in and wa active at all? I did, ILS is correct in RAD/NAV, I can also see it in the bottom left corner of the main screen, it takes the LOC correctly but apparently not the G/S, gonna give it another try
December 16, 20205 yr 6 minutes ago, dyl55 said: I did, ILS is correct in RAD/NAV, I can also see it in the bottom left corner of the main screen, it takes the LOC correctly but apparently not the G/S, gonna give it another try Well, wide field then. If you are not necessarily familiar with flying ILS approaches you may want to make sure to capture the glide path from below the signal to properly capture the approach. If that is not your issue then only other hint is that I did hear (but haven’t seen it myself) that some (default) airports do have issues with displaced ILS signals (and I do not mean those airports with a displaced threshold/approach path like LOWI) Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
December 16, 20205 yr 55 minutes ago, DAD said: Same here. And again adding the approach added WPs behind me, quickly chose DIR to DEPOK and all good 🙂 EDIT unfortunately a CTD on short final 😞 If not for bad luck we wouldn't have any luck at all 🙂 . I said this before but it still chases me, I would go back to P3D if not for the challenge to see if I can get the FBW320 to do a "normal" STAR/APP/Landing without me interfering. So far no cigar. Guess I should stay away from casino's as well, I might get stuck to the tables there 🙂 Sorry to hear about your CTD. Did you report it to the wonderful Asobo folks? 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)
December 16, 20205 yr 2 hours ago, hvw said: Sorry to hear about your CTD. Did you report it to the wonderful Asobo folks? same flight again. same approach. same CTD again on short final... see no need to report it to MS, rather AS. Anyway, let's get back to topic again, my issues shall not bother you all Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
Archived
This topic is now archived and is closed to further replies.