@Black-Square

Thanks Mark... I'll give it another go... Rob

This was helpful! Thank you!

Your best bet would be to contacts Just Flight support. They should be able to help with this kind of thing. https://community.justflight.com/topic/2/product-support

Brilliant, thanks for the update. Regards, Neil.

@Frafty said in Things that (in my opinion) should be changed: Creating your own schedules defeats the purpose of the program...to fly the line, i.e. the schedule you're given. I may have misspoken. What I meant to say is that I would like the option to create bespoke routes (not schedules) based on older airlines that are no longer in operation. Since the program already supports real routes from current airlines, it seems logical - and really no different from what the program already does - to also provide the flexibility to fly defunct airlines with their actual routes rather than (or in addition to) random ones.

fixed in SU3

This happens so much with so many different things (not just imported BSQ aircraft for what it's worth) in 2024 I just leave collision off. The common denominator for me was "various 3rd party scenery": in my case most often it would happen turning off of runway 35 at twy A at Tacoma Narrows (TIW). I have the Orbx scenery for it and there is just some seam or misalignment in various parts of the field that cause this, whatever it is is invisible to me. I've also seen it at Anacortes taking off south, multiple planes, same thing: you crashed! I also have a 3rd party scenery there, too. I thought I was doing something wrong til I disabled collision and magically everything is fine. No random bumps in the physics, just smooth sailing. If I had to guess, that may be your issue: if you haven't, try another field with just the basic 2024 scenery and maybe as flat a runway as you can find. Failing that, disable collision, though I can understand not wanting to.

Thanks. I am enjoying the RJ. My reasoning to get both was that I am not planning on getting a full glass cockpit airliners. I used to have the PDMG 737-800 in FSX, but used to only take it on short trips. The RJ is a good mix for short flights with some level of automation. I know that I will enjoy the 146 even more.

I primarily tune in frequencies through the CDU. I notice that it is impossible to input a comms frequency in the recall field. Not sure if there is perhaps a logic in that, so the RTU and CDU don't "fight" over that field, but if that is the case, I wonder why the yellow arrow still appears - seemingly indicating that the LSK can be used to input the frequency in that field.

This has been fixed in the upcoming next release and as mentioned in another post, I am working on real time integration as well. So far it's looking promising.

Thanks for the feedback Rolo. I'm currently looking in to Fly the Line giving you complete freedom with regards to date and time. Touchdown zone was always there to help you focus on not just greasing it but making sure you hit the touchdown zone and get a decent sink rate. This can be challenging but there's meant to be a challenge element to it. I get your point about all the dependencies. It's a fine line between realism, challenge and fun. This can be quite hard to balance. Maybe as we go forwards there will be ways to to adjust this to suit each user.

I want my MTV. If your back hurts when you get up in the morning, you will understand this

Had to do a big of digging, but here should be a mostly complete list of the triggers needed for each stage: https://community.justflight.com/post/15635

@MarkS said in If you're doing a world tour.....: I'm on leg 25 of this massive world tour, available on flightsim.to. It did not include a stop on Reunion, but flew right past it so I added it, as well as a stop in Antarctica. [image: fa09f856-73ae-43a3-bdac-9d3c37af2e14.png] https://flightsim.to/file/93601/around-the-world-flight-plan All these places and still skipped Hawaii...

Oohh...system.cfg... voltage curves... so that's how that works. I was looking all over .xml files trying to find some reference to 26 So maybe when the simvar gets the voltage number, it's starting from the left of the curve and finding the 0:26 entry first and setting capacity to 0? And there's some (undocumented?) behavior in MSFS that says "0 remaining capacity is automatically 0 volts," even if the voltage curve says 0 should be 26? But if that's the case... Yep, tested it and Recharge Batteries disables external power too! (I should note I've only been trying it in FS2024)