Did this happen?

No problem, thanks so much for the follow up and your help. Much appreciated.

Thanks Neo. So the activities are also partially a gambling. Good to know.

Hey - so if you were late, that would eat in to your turnaround time for the next sector so if you were 10 mins late and your next turnaround is 20 mins, it will be cut to 10 mins. You can depart before the end of your turnaround time if you want to by the way. You dont have to wait until the counter gets to 00:00. I hope that makes sense. You have 15 mins +/- grace to be on time so even if you landed 10 mins late, you're still good.

There aren't any plans in place at the moment to revisit the engine spool times in the RJ. From the data we have and the input from the pilots on our testing team, the fast engine spool is accurate to the real aircraft. As you say, they are smaller engines, so there isn't as much mass to rotate as there would be in larger engines. Mark - Just Flight

Great to hear, thanks

Aha, that makes sense since I was tinkering with the air bleed switches to do the air + cross-bleed start. Thanks!

Thanks, Mark, much appreciated. I definitely was on external power pretty quickly after the flight started, so I'll assume it's the second behavior you describe. I'll report here if I notice this happening again post 0.1.4. Fantastic plane, always at the top of my list!

Thank you Mark. That’s much appreciated.

I'm encountering the same issue when using the LOCK interaction mode. When I hover over the VS click spot and scroll the mouse wheel, it zooms the view in or out instead of adjusting the VS setting. Switching to the LEGACY interaction system does resolve the problem. However, since I use LOCK by default, it's not very convenient to constantly switch to LEGACY just for the Arrow. It would be great if this inconvenience could be addressed somehow. Everything else is fantastic - an outstanding product, thank you for it.

I spent yesterday looking at this to try and recreate it and I wasn't able to reproduce it. I tried with MS2020, 2024 and the latest Beta via Steam. However, I have made some changes. This will prevent the message coming up about the time change being detected. This is in the build I have sent to Just Flight for Early Access. I'm hoping once customers get there hands on that it will either solve this issue or help steer us in the right direction. One question - does anyone have any add-ons running that may or could have the potential to manipulate time? Flight recording, replays anything like that? My installs are fairly bare bones with limited add-ons running. X-Plane seems to be fine and so is FSX.

Hey Mark - a couple of options here. You could drop support a line with your details and I'll get in touch and fix it for you. Another option is we're aiming to get the early access build out, possibly later today, which should fix the issue, and stop it from happening again. It's no trouble at all.

Great, thanks

I get this error constantly- almost every flight, even when Im at the correct airport it tells me incorrect airport and cant get a dispatch...I have to go into the FSUIPC interface and disconnect/reconnect and it seems to fix the issue.

Which lights are you speaking of? You can see descriptions of all interior lighting in the "Lighting Controls" section of the manual.

@Bentree Thanks, I will try that.