richboy2307

Thanks issue is logged for further review. I was able to reproduce. The same axis assigned via FSUIPC or Mobiflight doesn't exhibit such behavior for me which is puzzling. Logically if the axis input was being blocked/intercepted by the aircraft code then it should not work via any external tool 😅 Anyways, for the time being assign via the sim directly to work around the issue.

Above 60 kts, tiller and nosewheel operation inhibited, which is most likely what you're experiencing. Any rudder axis input above 60 kts will only move the rudder. Tiller (Nosewheel Steering) Axis will not be operational. In v1.0.7 there is an Flight Model update coming to give more effectiveness to rudder alone but the rest appears to be by design and not a result of any hydraulics. Please verify against the 60kts threshold for what you're experiencing.

Hey @zbrainlezz That is odd, I do have both and I'll check as well. I've been using mine bound via FSUIPC7 at the moment so I do know it can be controlled externally, but will see if can reproduce the above issue via SPAD specifically. Based on video alone seems like while Bravo is active, its sending commands but once it stops giving commands, another device thats still at idle is then taking over perhaps? Can you confirm there isn't another connected device that is being read by the sim (or SPAD) also sending thrust commands, thereby creating a conflict with each other? Thanks!

Are you referencing the EPR target set on the glareshield in TM Mode specifically? If so, observe on the PMS when you're seeing this behaviour, and you'll note whats happening when it "drops again" is its shifting from MAX CL (CL1) to NORM CL EPR (CL2) values as the target. The way its modelled now is it will try to use calculated CL2 table values for your weight, temperature and altitude ranges. If outside the tabled parameters, it will instead use the calculated CL1 values for your current weight, temperature and altitude. It will transition back to CL2 if within tabled parameters at the next update point. Using this image example from above again, the calculated CL2 and CL1 values at the moment are .573 and .630 respectively. It will command only either of those (+- 0.001 EPR) in TM mode. Yes, the IRL counterpart behaves the same way automatically modulating between the CL modes - except - there is more specificity in the logic for conditions that must be met before the switch happens. That additional conditional specificity as well as manual mode selection is not currently simulated. We have it on our wishlist for systems we'd love to add depth to given the development time, but it is beyond the initial scope set for the product. What is simulated is the essence of how the actual unit works - i.e that it references current conditions against MAX CLB EPR (CL1) and NORM CLB EPR (CL2) performance tables for -500 stored within the PMS database AND automatically modulates commanded EPR between CL1 and CL2 based on periodic data-comparison to obtain the nominal climb rate. Yes according to the team what we have currently is set based on the -500 performance data available to us. For all parameters such as EPR, N1, Fuel Flow etc. For the sluggish climb rate you are expecting - try manually controlling your throttles exactly per the NORM CL values shown on the PMS at various stages and see if you still have the issue. If so, please advise with screenshots or video reference of exactly what you're seeing in sim vs roughly what you'd expect at the various stages so we can investigate further. Yes you don't have -500 specific data but if you make an estimation of the expected result based on your -100 data, we can run a comparison against the data we have and verify if the sim is exhibiting that or not to determine any adjustments required. We also appreciate your reporting, and are not trying to be dismissive of it but random image comparisons such as that provided are also not conclusive in establishing tangible data for resolution/adjustment without also equally full knowledge of all the parameters such weight or atmospheric conditions as you mentioned.

Hi @Joshua Green The team is not able to reproduce this currently. 20260519-2130-32.7561892.mp4 | Could you please provide additional details as follows What waypoints you had loaded in at the time exactly - FROM/TO Your approximate position What was the new waypoint entered and in what WPT POS? A video or screenshots showing the process so we can try to repro exactly. Thanks!

Noted. For now, you can use independent axis for modulation of rev thrust within IDLE REV and MAX REV ranges after reverser engagement - they all toggle together from IDLE to IDLE REV and back. In normal A-B flying, there are rarely situations that require engaging individual thrust reversers. Additionally, failure or abnormal situation simulations are not the primary focus of this product line hence why it was not a high priority during development. You can actuate them in unison using the listed HOLD or TOGGLE commands below as of 1.0.6: Depending on what you're doing you may need to adjust the trigger between BUTTON PRESSED, RELEASED or HELD accordingly. I use the Bravo myself and have it set to TOGGLE reverse thrust on one of the bottom detent buttons (26) on the throttle levers. This allows me to control the reverse thrust amount for each engine using independent throttle axes after having toggled it once. While they will toggle together, you can still apply asymmetric reverse thrust within IDLE REV to MAX REV range once you have independent axes assigned. The reversers are toggled back to forward IDLE thrust using the same button. I could also set it to HOLD reverse thrust when held (bottom option), that way once I push it down into the detent, it engages max rev as long as the button remains active/held.

Yes ensure the MASTER RADIO ESSENTIAL and NO.2 are engaged. We have also identified some other specific scenarios which may cause it to stop working in SU5 due to JS conflicts - expect a fix in v1.0.7. Appreciate your patience meanwhile. Thanks!

The community identified a potential conflict with Twotter Revived mod that was preventing ENG 2 startup. If you use the mod, ensure you updated it to the latest version.

This one is kind of by design as a sim-ism for both stability and performance reasons. The entire INS computations/detection logic is inhibited unless user does a TK CHG 0 (P.POS) to another waypoint to initiate it.

@here Mod Conflict Can you please try with an empty community folder? Its possible there is some other mod installed that is now causing a conflict. There was already one identified by the community (Twotter Revived) that was preventing ENG 2 startup. That mod itself has received an update which will prevent the conflict with Tristar (or any other addon), but its possible there are other mods influencing core sim functions even when their respective add-on is not loaded. So a conflict needs to be ruled out. You need not uninstall any addons, simply rename your existing Community folder (e.g. _Community) and the sim will create a new empty one in its place on next start. Once you're done testing, delete the empty one and rename the old one to restore your addons. Assistance Settings Verify that all assistances are disabled. They have a tendency to reset after sim-updates even if you had previously disabled them. These ones are known to conflict with logic Automixture AI Auto-Trim Auto-Rudder Disable Crash Damage (ticked = disabled) Disable Aircraft Stress Damage (ticked = disabled) Disable Engine Stress Damage (ticked = disabled) Unlimited Fuel No Repro On our end we're not able to reproduce these issues starting the APU from C&D. Neither using the auto-flight engineer nor manually. See video attached on a streamed copy of 1.0.6. 1.0.6 - Starting from C&D manually - Standard 2026-05-18 23-42-12.mp4 1.0.6 - Starting from C&D via PFB FE Autocomplete - Cabin w/ Lounge 2026-05-18 23-49-46.mp4

Thanks we'll investigate

Thanks will pass it on to the team for further investigation. Appreciate the references.

Hi Acceleration is planned for update 1.0.7.

Can I suggest setting it to TOGGLE THROTTLE REVERSE THRUST instead for this function? If its a button you intend to use while its held, set it to toggle both ON PRESS and ON RELEASE.

@Joshua Green If you can, at the end of the flight look up these variables in dev mode - Tools > Behaviours > Variables tab > uncheck "Only show variables..." > search for "drift" : Include your OFP as well, for devs to investigate further. Thanks!

Hi As Bunkie mentioned above, the HSI DIS/TIME Readouts are only driven by the INS Computers. They cannot display data from any other sources such as your GPS or NAV1/2 DME. To use GPS Navigation, you have to Import or manually enter your route into the GPS Ensure CDI is set to GPS instead of VLOC Set the RADIO/INS switch to RADIO Set FD to ON and use VOR mode for guidance On your HSI it will also read "GPS" to show you the source driving the HSI needle I've done a number of flights already swapping between VOR, INS and GPS modes frequently across the same flight from C&D and haven't yet come across your issue. Maybe a video from Cold & Dark till when you notice the issue can help assess if there is some bug or any kind of missed step during setup? You can upload to Youtube/GDrive and share link here in case file size is too large.

Thanks logged.

Hey thanks logged for further investigation.

Hi @JaredGPW Please try v1.0.6 and see if the issue persists? We have reworked how HOLD THROTTLE REVERSE THRUST and TOGGLE REVERSE THRUST keybinds function and hopefully that resolves your issue? Thanks!

Thanks we'll investigate. Its more likely SU5 as it changed emissive properties of materials again.

Yes as of v1.0.6 you can now. The FAQ item has been updated to reflect this:

Now you can via RMT Entry Function. For more info see this: https://forum.inibuilds.com/topic/36719-how-to-ins-remote-entry-function/

Should be fixed in 1.0.6 but please check and let us know. The issue was already identified before it was reported here :)

As of v1.0.5 Update, you can now remotely enter waypoints across all three INS units manually or via Simbrief Import from the Paper Flight Bag (PFB) - OFP Page. Remote Entry Function (RMT)Due to the complexity of the original autofill procedure and common user difficulties when operating the INS, this feature has been simplified to provide a more intuitive user experience while preserving the intent of the real system. The process generally works as follows: Set the desired units to RMT mode (at least 2 required for this operation). Enter waypoints manually or import them from Simbrief into the transmitting (TX) unit using the standard procedures. Each time a latitude or longitude is inserted (by pressing INSERT) or when an Simbrief import is completed, the TX unit will automatically transfer the data to all receiving (RX) units. Remote Manual Entry (v1.0.5+)Procedure Set INS 1, 2 and 3 MSU to STBY , ALIGN or NAV on the overhead panel Set INS 1, 2 or 3 Mode to RMT (at least 2 units required for this function) Set the Display Selector Switch to WPT on the Transmitting (TX) unit Set WPT Selector Switch to any number from 1-9 on the TX unit Enter Waypoint Coordinates on the TX unit The entered waypoint LAT and LON will update automatically on your TX unit and any other Receiving (RX) unit set to RMT as you press INSERT. Note: The waypoint will be entered into the same WPT number as selected on the main unit (i.e. if you populate WPT 3 on TX Unit, any other RX Unit will also populate its WPT 3 position) Set INS 1, 2 and 3 Mode to AUTO or MAN for navigation. Example In the example video we have remotely entered N3701.0 W00758.0 into WPT 3 from INS 2 (TX) to INS 1+3 (RX) at the same time via RMT function. 2026-05-12 04-52-20.mp4 Remote SB Import (v1.0.6+)Procedure Set INS 1, 2 and 3 MSU to STBY , ALIGN or NAV on the overhead panel Set INS 1, 2 or 3 Mode to RMT (at least 2 units required for this function) Use Captain's PFB to import to INS 1 (or First Officer's PFB to import to INS 2) The waypoints will be imported to INS 1 (or INS 2) and the other INS units set to RMT. The auto-batch logic (if more than 9 waypoints on SB import), will apply to the main and any other RMT unit as well. Set INS 1, 2 and 3 Mode to AUTO or MAN for navigation. Example In the example video below we have remotely imported from the FO PFB to INS 2 (TX) and INS 1+3 (RX) at the same time via RMT function. 2026-05-12 04-13-23.mp4