With regards to some systems (like the TRP and YD) not being functional following a change of aircraft state on the EFB, this possibly could be misunderstood for the FGC test. If the aircraft's power supply is changed when switching states (such as Cold and Dark > Turnaround) an FGC Test will be triggered once the power is restored. Off the top of my head, the FGC Test takes 45 seconds to complete after power has been applied to the aircraft and during that time, a few systems such as the TRP and YD will not be functional. Once the FGC Test is complete, an FGC PASS message will appear at the top right corner of the PFD.

However, we have also found a situation where the FGC Test logic can get confused if a state change is triggered prior to the test being completed. We will be implementing some changes in the next update to the RJ Professional to try and mitigate this.

Mark - Just Flight

Resetting the aircraft position in the FMS isn't currently supported in the sim. It's something we would like to implement in the future, but at the moment the IRS just basis it's calculations on the initial position entered at the start of the first flight.

Mark - Just Flight

Any route inputted into the RTE page can be saved locally on your PC by selecting the SAVE FPL option on the INIT/REF INDEX page. Once saved, that flight plan can be recalled on future flights either by using the CO ROUTE field via the FLIGHT PLANS option on the INIT/REF INDEX page.

Mark - Just Flight

@flightstrike

Hi. No ... as auto-throttle was on and autoland, I'd reduced them 'physically' to idle.

But heh, it was my first autoland so I need to read the manual a bit more.

And I use a 3rd Party Cardiff EGFF so I know elevation and ILS angles can be 'problematic'.

Prolly a good idea to test it on a stock airport.

@Black-Square If you insist. 😉

image.png

I refuse to believe that the King Air will be ignored.. I'm betting the King Air will be a new aircraft from the ground up by Black Square.

@hughesj2 Interesting tip, I will surely try it, THX!

Will try again today…

As stated in the FAQ linked above, those are performance tips, not mandatory settings. The settings chosen are completely up to the discretion of the user based on their personal experience and preferences.

Unfortunately, just as a low-spec PC will struggle to run MSFS at Ultra Graphics settings, with high-fidelity third-party aircraft and high-quality third-party airport scenery, Xbox consoles will also struggle (particularly the Series S with its extremely limited VRAM).

As Xbox users don't have access to the Graphics settings that PC users do, there is a very limited number of ways that performance can be adjusted. The tips listed in that FAQ are some ways that Xbox users can improve their performance if required, based on our experience when testing products.

Mark - Just Flight

Okay good, then that was just an isolated glitch.

@Mark Regarding this:
"I think the OP is assuming TO REDU is the same as TO FLEX, when it is not in this case."

The FCOM says:
The "REDU values are just particular FLEX values".

The mode TO REDU on the TRP carries out the calculation I posted multiple FCOM references to.
When you push the TO REDU button, it will set a default T FLEX, this temperature is called T REDU.
You can actually calculate the values in the N1 REDU table using the method I provided. The reason for this is simply that N1 REDU is the same as N1 FLEX, it's just been decided that a particular T FLEX will be called T REDU.

If your TRP implementation isn't carrying out the calculation I provided from the FCOM, then it's not doing what the real aircraft does.

How can I be so sure about this?
I did the calculation using real data from 3 videos and my calculations matched the N1 set by the TRP for the particular temperature setting in the videos and pressure altitude (±0.1% N1 precision is acceptable).
If I was wrong about all of this, then the calculations should return non-matching values.

When I do the exact same scenarios in the JF RJ, the values output by the TRP doesn't match at all.

Funnily enough, I think there was a request on some just flight video comments to use the presenter's voice as pilot monitoring voice.

Personally I was surprised when I heard it in one of the trailer and that did put a smile on my face. I like the current voices as it is.

We had this issue early on with the 146.

CPU use was spiking.
... ( As it is here. You can almost predict it... levelling off after climb, turning via Lnav control... very noticeable.)

It was sorted after a while... maybe 2 patches (?)... so hopefully this will be too.

Tldr; go back and see what caused this with the 146 😁

I was hoping being able to use SimBrief's Takeoff Performance calculation, however it always returns SEL TEMP = NONE.

I assume this relates to missing performance data in the aircraft profile. Is this something JustFlight could collaborate on with Navigraph?

@jmarkows Somewhere, someone from Just Flight mentioned that all the 3d objects in the analog 146 uses alot of system resources in VR and that the flat panel glass of the RJ would give them more headroom.

Sure thing. If you search for...

SimVar.SetSimVarValue("L:var_RNAV_WAYPOINT_NUMBER", "number", this.displayChannel);

and add this, immediately below...

SimVar.SetSimVarValue("L:var_RNAV_ACTIVE_WAYPOINT", "number", this.useChannel);

That should do the trick too! Always happy to help.

@NickD27 Thanks for your input. I thought it seemed like I had to push the yoke forward a significant amount to have any result.

We'll see what the dev team can find when they look into it.

The v2.3 (0.2.3) has just been released for our customers and should fix the EFB issues. That will be available on other stores, including the MSFS Marketplace, sometime in the next few days.

Ok I need to lift it, thanks! Sorry read to fast

@smashingjonor Thanks for these, this should be a good starting point.