Mikealpha

Yes, I have. It's all in there as it's supposed to be Mike

Yup, I do. Thanks for the heads-up., much appreciated. I have seen your thread in the Navigraph forum and will follow it. Mike

I wonder if we will ever see night lighting like in the attached EDDF photo. I haven't seen anything like that in any scenery, not even close. Just meant as something to consider for future sceneries . Please no more dull airport lighting 🙂 Mike

it was mentioned here already, not sure if it's a 5 character limit problem.

I tried the fix by Guenter and it is still not working, jetways do not move. P3Dv5 and 2.0.0.3 is installed. Sode.log has this ... [14:47:41.563] INFO SODE.FSLOOP : - SimObject 'aerosoft_LSGG_SODE_Jetways:Gate B44' [LSGG_Jetway_Type004]. ID: 62 [14:47:41.609] INFO SODE.FSLOOP : + SimObject 'aerosoft_LSGG_SODE_Jetways:Gate B44' [LSGG_Jetway_Type004_Static_B44]. ID: 63 [14:47:43.745] WARN SODE.FSLOOP : [JETWAY CONTROL SYSTEM] No 'jetway.cfg' found. Unable to move Jetway... Any ideas ?

I made a side-by side comparison on my Desktop and Laptop of the CRJ in P3Dv5 and MSFS, a flight exactly parallel. While LNAV in P3Dv5 is not perfect either, in the latest CRJ version it is definitely better than in MSFS now. The main reason might be the turn radius, it is much tighter now in MSFS than in P3D. I remember that incorrect turn radius was always an issue in FSX, then carried over to P3D. So I'm wondering, has the CRJ LNAV being carried over from the P3D version straight into MSFS ? Looks like the now correct turn radius leads to the wrong turn anticipation now (see the screen

Well, Number 23 here. For me it looks like turn anticipation comes way too early, then the inevitable lateral offset needs correction. Which is done too aggressive with 30deg bank S-turns. Setting it to 1/2BANK helps a bit, but then the correction often takes way too long, sometimes up to the next waypoint. That's not a new problem though, it plagues the CRJ since the first P3D version and got only marginally corrected. Mike

oh, Ok, thanks for the information. Then just making textures available here would be certainly a much appreciated compromise ! Mike

Oh, that's surprising, but I was already wondering why no MSFS scenery contains any configurator. So if you change textures in the Community folder, MSFS does not consider it at the next start ? Mike

who knows when this will happen that far north :). What about putting this in a configurator, so the user can decide himself ? Mike

Oh, OK ! I'm new to MSFS 2020, didn't know that. I'll turn the airport vehicles off then, to see them on active taxiways is too much of an immersion killer. Thanks, Oliver, and sorry to bother you with that. Mike

To my surprise, I found some vehicles standing on Taxiway S, and even met a bus approaching me after turning S7 - S. Could you remove these please. Mike

As the title says , transitions need more than just 5 characters. In this case to distinguish between e.g. GIPOL28/RILAX28 and GIPOL34/RILAX34 If you click on any of them, it selects both, so you get e.g. <SEL>RILAX twice, which is wrong as well. Mike

In 1.0.2.0 there are still gates where SODE VDGS is incorrect, B5 is an example. The STOP indication comes already very far out from the final position, looks like the distance is incorrectly set.

I could not reproduce it today, now I got indication for all I checked. Sorry, don't know what went wrong yesterday. So that leaves only Gate C8 with wrong indication (STOP already too far from final position)