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)

Since we have Simbrief calculations and an Excel tool, I really hope you reconsider this. The speeds are often close, but not always the same. It is annoying having to ignore the callouts in the latter case. I think it would make sense that it uses the speeds entered by the pilot.

Same here. I used the Simbrief calculations for HKJK. It showed I barely use half the runway with flex 50. Turns out, more than 4000 meters of runway is not enough for the RJ85. Even in the air, it would not gain altitude at flex 50, I had to switch to climb power early. Sure, HKJK is hot and high, but I would expect that to factored into the calculations. Either the data from Simbrief is seriously off, or the JF simulation does not produce enough thrust at high derates.

I checked again and ran the trig for different altitudes and was completely unable to paint the ground in MAP or WX mode regardless of the tilt. This seems like a shortcoming, I have on occasion at night with heavy rain tilted the radar down so the bottom of the beam catches ground at the edge of the display range. This helps identify a lower detection plane for the radar. For instance is I set the radar to paint the ground at 100 nm and the aircraft is ~30000ft AGL then at 50nm the bottom of the beam is 15000ft etc. Every tilt from -1 to -12 resulted in a dark screen for trying to get any sort of ground return

Thats bad, because several other planes, who works well with the RealityXP GTN out of the box also with the TDN GTN. Their ist the Thranda Beaver, the Thranda PC-6 Turbo Porter, the Rotosim EC135 (Freeware) I'm sorry, but if i use the TDN use in an outside Window all funcition of the TDN works like the RealityXP. The only thing is, that i cannot Activate it on the Tablet. THIS cannot be such a big Problem. I buyed the PA-28R Turbo Arrow III/IV vor X-Plane 11 and vor X-Plane 12, because this are verry fine planes.

@Buzz you may well be right. Given that the majority of the time the aircraft is loaded in the sim, it will be in a running state, that approach won't make much of a meaningful difference vs a failure timer that only runs when engines are running. Nick said there's a reason for real inspections being "based on calendar months", which I took to mean that all the elapsed time between flights would be considered for failure generation when you next load the Duke in the sim, but I may have read too much into it. I suppose one way to test might be to set my computer clock to 1995 (furthest back Win10 will go), reinitialise the Duke by deleting any saved/state files, then load it in the present day and see if any failures had appeared. But I'll just wait and see if Nick clarifies first. If your idea is right, then maybe my idea can go on the wishlist instead - perhaps as a toggle option

A go around is a not that uncommon and should be recognized by FTL... and not be penalized. It would be enough to add a button with "go around" to tell FTL that I did go around.

Grinning and rubbing hands together in the corner