I am now flying the B36T. I still shake my head about needing to manually twist the needle after every waypoint on the GPS flight plan, if I'm using TDS GTN750Xi. I just want to check in as it's been a year since the above dialog - is there still no way for the aircraft's HSI to automatically follow the GPS flight plan? Just can't get over someone who would invest in a turbo-prop and the surrouding technology, and not have the equipment to reduce pilot workload, keeping the eyes outside of the aircraft as much as possible. Just wanted to ensure I wasn't missing anything. TDS benefits: includes the IF in the transition list for RNAV's with no feeders (ex: KSMO RNAV 21, PMSS does not show DARTS, TDS (correctly) does. PMSS benefits: allows me to DTK sync to simulate having the equipment that can follow the GPS flight plan.

Thanks, I must have missed that

@Black-Square i investigated a little bit more into the issue in SU5, because i thought maybe it fixed itself because of the new multitasking but unfortunately i still have the same issue. periodic micro stutters coming from the graphics queue. but i found the following: if i increase the "Off Screen Terrain Pre-Caching" value it gets worse, and if i lower it, it disappears. so maybe this give you some hint in a direction? again the problem is: periodic (like every second) microstutters in the TBM850 (and basically other blacksquare aircraft). the graphics queue goes from around 5ms to 15ms every second. which introduces microstutters. ALL other aircraft work fine. PMDG, fenix, taogs hangar, comanche, learjet. it only happens in the blacksquare fleet. sometimes it's worse, sometimes it's less, but the graphics queue is definitely behaving strange in all black square aircraft. it also happens when i have the display refresh rate at a lower setting.

@ploodovic said in Custom Registration confusion: Have you checked, that the EFB option to have the registration visible, is enabled, in the respective versions? Bingo.. that was it! Thanks.

I would appreciate this too.

@pequenyo Historic traffic is something that comes up every so often - and has done since we published our first traffic add-on over a quarter of a century ago. Unfortunately, experience has taught us that the commercial potential is extremely small and so it's not something we'd consider nowadays.

@BAEflyer is this issue solved on fs20 xbox version?

@AlphaEcho Hi Mike, Thanks so much - no wonder I couldn't tfind hem. I must have tried almost every other binding I could think of to do with roll, trim, AP, etc. It was driving me mad. Cheers, Neil.

@MiRexer This issue does not seem to appear with the PMS avionics. Try the KLN90B or the RNAV suite, and you'll get a taste of the problem.

I'd buy a V35 in a heartbeat, but what I'd truly love to see is a Queen Air. I remember there was a freeware model available way back in the FS9 days, since then, nada. A Black Square Queen Air... now you're talking unique and wonderful all in one aircraft It's nice to daydream...

Thanks for the quick response I’ll sort it out over the weekend

thanks very much guys

@jmarkows said in Starting engine doesn't drain battery: Nick is aware of it, see here: https://community.justflight.com/topic/10410/v1.1-electrical-discrepancies-questions I thought we were due a patch this week, I suppose we'll see when that drops if he's applied a fix. Good to know. Missed that completely.

Would like to second the request to enable displaying the FMC screen on external hardware. With the appropriate API and documentation, I would be able to add this feature to MobiFlight. Other MSFS addons make the contents of the FMC screens available either via a local HTTP server or through SimConnect's ClientData feature (SimConnect_RequestClientData and related functions). Could such an API also be provided for the RJ?

I have similar issues in VR. I get no tooltips except on the fire test switches.

Apparently there is an error in the manual, where it says "Also on the HSI compass, two red pointers are available to indicate the bearing to the NAV2 station." (p.28). After tests I realized that HSI's "two red pointers" indicate the bearing to NAV1 (they align perfectly to the direction of RMI's YELLOW needle).