richboy2307

The GNS530 getting stuck on initialisation is a sim bug as far as we can tell. It's all WT code and we're not doing much our side with it besides giving it power (without which the display wouldn't turn on at all). If you do get stuck in this situation, you can as Jake suggested, try to recycle power (Trip the APU GEN or disconnect EXT Power) as that usually resets it. Alternatively you can try to restart your flight though that is rarely necessary. This issue is reported on other aircraft using WT GNS as well and we're hopeful it will be resolved eventually.

Hey Randomised from doors open to doors close on the ground Random 10-15 mins after seat belt sign turned on above FL200 Randomised on ground after doors open again for arrival

Thanks, there were many different cabin configurations for the L1011, but the version we’ve modelled is based on the best references available to us. At this time, we don’t have plans to add additional cabin layouts, and we believe the existing variants already offer a good range of options to capture the feel of this era of aviation.

We're not seeing this our end. Try the following maybe? If you locally installed the addon via My Library, try deleting and revert to streamed version? Check under "My Library" if these liveries show up and are not "disabled"? Delete your Content.xml file and restart the sim after to let it build fresh. NOTE: This will reset any addons you may have previously disabled manually via My Library. Keep a backup of the original file and re-disable the addons after if needed.

Is a livery-side issue. Already reported elsewhere, the relevant livery artists will work on it when possible. Expect livery updates via iniManager or Marketplace Livery packs for this. Thanks!

Try spawning on runway, then use whatever keybind is bound to TOGGLE AUTOPILOT MASTER? For me its Z on my keyboard and another key on the Win Cntrl URSA Minor joystick and both work. If that doesn't work, for testing purposes try creating a new controller General Controls and Airplane Controls profile that is blank with only TOGGLE AUTOPILOT MASTER bound. This will help rule out some keybind conflict. 2026-05-01 13-32-52.mp4

The AP1 can be toggled between CMD and OFF using the "TOGGLE AUTOPILOT MASTER" keybind. The Autopilot disconnect (on yoke) can be used via the "AUTOPILOT OFF" keybind. The only one not mapped is AUTOPILOT ON as forcing it on via key event was causing other logic issues with CWS in certain cases. As for the 000 EPR issue, as mentioned above team is investigating the correct behaviour and working on it for a future update. Thanks!

Try this recommended procedure If starting fuel quantity is less than 63,000 lbs: Feed tank-to-engine throughout flight. If starting fuel quantity is between 63,000 lbs and 116,000 lbs: Crossfeed all engines from tank 2 until fuel levels in all tanks are equal. Leave one tank pump operating in tank 1 and tank 3 while crossfeeding from tank 2. Monitor tank quantities to ensure that lateral balance remains within limits. Feed tank-to-engine for remainder of flight, especially when fuel remaining fuel quantity is less than 63,000 lbs. If starting fuel quantity is 116,000 lbs or greater: Crossfeed all engines from tanks 1 and 3 until total fuel remaining is 116,000 lbs. Crossfeed from tank 2 until tanks 1, 2, and 3 are equal. Leave one tank pump operating in tank 1 and tank 3 while crossfeeding from tank 2. Monitor tank quantities to ensure that lateral balance remains within limits. Feed tank-to-engine for remainder of flight, especially when fuel remaining fuel quantity is less than 63,000 lbs.

Thannk suggestion is noted but just for reference you can "right click" or "middle click" on the dial to auto-set current GW value.

There is no default profile, though we do have an "official" one available in the FAQ section: https://forum.inibuilds.com/forum/744-faqs/ You just delete any 3rd party profile you installed and replace it with this one. Restart COUATL after if sim was running at the time.

Repaints (those obtained via iniManager) should not affect this as there are no files included that would affect systems logic. We can't say the same for all community-made liveries however. Changes have been made in v1.0.3, so please let us know if this is still the case now?

This should be resolved as of 1.0.3 update, please let us know if not. This is by design currently per reference documentation used, so it will sequence the next filled waypoint in AUTO sequencing. The only condition to this is that you have 3 or more waypoints in the INS in total.

Hi, Thanks for your patience. Please see response from our dev team: We will update the manual accordingly, but if you notice any discrepancies even after following the above, please let us know. Thanks!

Thanks, with 1.0.3 we have made changes to the AP controller, but only added this to "VNAV" for now. We are working to implement the same logic into IAS/MACH modes as well for future update. If you have any additional feedback meanwhile, specifically to how AP behaves with TM/VNAV , please let us know. Yes, see the post attached below. We're investigating the following:

I have split your topic as its a separate issue to the one you had replied to. Thanks we want to investigate this further. Was your AFCS ALT window indicating the mode as "ALT CAP" still when you changed the target? Or was this after it had already changed to ALT? How were you changing the altitude target? click and drag or mouse wheel? Thanks!

While it is correct that TM mode requires FD+AP, we'll have another look at what it should do when conditions are not met (i.e. just disengage TM instead of commanding EPR 000/IDLE thrust). The other thing to note is that both PMS are independent, so need their data entered separately. PMS1 data is only used by AP1 channel.

Hi There is a potential fix in v1.0.4 coming that may address the issue of the spoilers not appearing visually post landing. Please verify and let us know after. Thanks!

Hmm. Can't say I'm seeing this on my end. Could you please record a video starting from C&D till after pushback when you notice the offset? This will allow us to observe and possibly recreate the issue better. You can upload the video to youtube or Gdrive and share the link here. Just ensure its public / "anyone with link" can access. Thanks

We believe this may be related to an issue some users encountered, where the electrical generator would briefly reset during flight. This momentary interruption appeared to have a knock-on effect on avionics (GPS/INS/PMS) and other electrical systems. A workaround for this electrical issue has been implemented in version 1.0.4. Please let us know if you still experience it after that update. Can you please make all your links public? Currently there is no permission to access. Hmm, can't repro this. It is correctly illuminating with AVAIL only when GPU is connected via the PFB. Tested both with/without GSX (just to see if it was perhaps forcing it avail).

HI Did you import the waypoints from your OFP/Simbrief at any point? Or were they all always only manually entered? If auto-import was used, there is logic that wipes the INS in order to import the next batch of waypoints, but this shouldn't trigger from fully manual entry normally. Could you please provide some screenshots showing your active modes + AFCS + configuration (flaps/gear) at the time? The team is working to fine-tune autopilot ALT HOLD behaviour particularly during configuration changes (Flaps or Gear) but if you can provide specific examples we can ensure those are specifically checked too. Again, it would be more helpful if you can provide specific examples of scenarios where it didn't work as you expected? This would include steps taken before intercept, and particularly data such as heading, speeds, altitude, weights etc. Specifically with regards to ILS, you should not intercept at angles greater than 45 degree, preferably try less than 30 degrees to avoid massive overshoots or it failing to follow at all. Thanks!

Yes, you entered it correctly, and the current SAT was +40c on the ground. The limitation is that the PMS only knows "current" SAT, not predicted SAT at FL360. Hence its running the OPT calculation with a +40c Temperature, which is way too high at the cruise levels and hence nets in "888" or invalid result. As mentioned above, the PMS references available do not indicate any PMS capabilities to predict SAT at different flight levels, or calculate any ISA deviation on its own. All the logic shows it using "current" temp probe sensor data directly, hence making it unserviceable if temp probes are INOP or malfunctioning even. The SAT entered during pre-flight setup is used only for Takeoff EPR advisory on the ground.

Should be fixed as of EGGP v1.0.4 Update.

Hi As of 1.0.3, the PMS behaviour was changed to show "888" when it cannot calculate any valid result. It is also actively using the current SAT value to determine OPT. As such, it will update in flight, particularly when current SAT updates to sensible values where a valid result can be achieved. SAT of +40c at those weights won't net any valid results, hence the 888. Team is still investigating whether you can force a prediction on the ground, references we have are unclear but the behaviour currently is reflecting best the "known" reference logic.

Hi, This is intentional. At night (from dusk to dawn in the sim), the PFB brightness is controlled by the Utility Light. There is switch at the center that toggles it on/off, while the outer knob adjusts the intensity. This was added based on user requests to make the PFB behave more like a reflective surface at night. To achieve that effect, its brightness is linked to the Utility Light. Because the PFB is still technically a screen, it reacts to lighting conditions and may dim under direct light (like a flashlight), which is how the sim handles displays. Linking it to the Utility Light is the best workaround to this sim limitation to create the intended effect. 2026-04-24 13-15-38.mp4

Thanks team is working on pressurisation system/controller related issues.