All Activity

When flying in VR, the map display screen is partially blocked by the reverser handles of the throttle levers while in flight. There is a spacer on the top of the map display. Could this spacer be put to the bottom of the map allowing the map to move up in the pedestal. Thanks

I haven't installed any light mods.

am reporting a specific issue regarding the Pilot-side instrumentation and Autopilot 1 behavior while using the INS for navigation. Even though all three INS units are fully and correctly aligned, I am experiencing a freeze on the left-side HSI. While the bearing needle on the HSI still rotates to point toward the waypoint, the distance (DME) readout remains completely frozen and does not count down. TConsequently, when AP1 is engaged in INS mode, the aircraft fails to track the route and begins to fly in circles. The strange part is that the Co-Pilot's side (right) works perfectly fine. If I switch the flight to AP2, the aircraft immediately captures the track and flies the route as intended. On the right HSI, all data (distance and time) is updated correctly in real-time. This issue seems restricted to the left-side HSI and its connection to AP1. I now had this two times.

The information provided applies to navigation in general. The key difference is that the Delco Carousel IV-A (CIVA) can perform these calculations automatically, while the LTN-72 requires the crew to calculate positions manually using navigational charts. These updates are usually planned in advance during flight planning. In practice, they’re often done during a VOR-to-VOR segment, where radio navigation is used temporarily while updating the INS. Full flight navigation via random fixes only was very uncommon at the time, so there would typically be a suitable cruise segment to carry this out. Overflying a radio navaid with known coordinates would be the most straight-forward way. Alternatively it would be the procedures detailed in the manual with the help of navigational charts. These days you could use something like SkyVector or LittleNavMap for guidance. There is no OVFLY function as far as I'm aware but I'll ask the developer regarding that too. The way to go about it is manual flight, or reverting to radio navigation / heading hold temporarily during a VORDME-to-VORDME segment ideally. I believe it is the former. You are telling the INS what the *actual* coordinates were for the position which you told it to hold, thereby correcting the drift/error that was present in the system. However, I will confirm with the developer as well. Thanks!

I just transferred my A340 and A350 to the inimanager and now they won’t load in. I can see the plane from the loading screen but it won’t enter into it

Do you mean if you're spawning airborne somewhere in the sky (instead of on the runway or on a gate?). Could be an issue with the panel state its trying to load in that instance, we'll have a look. I would recommend disabling all 3 crash detection from Settings > Assistances. They usually cause conflict with 3rd party addon systems. Thanks!

The FAQ reads: To start a descend, the operator should follow the next procedure: Select the desired altitude on the glareshield panel On the PMS go to the CRUISE page and update the ALT value to this new altitude and press insert Press VNAV mode and check ATS and TM are engaged too And at the bottom of the FAQ, an Important Notes for Descent: To initiate a correctly computed descent profile, you must keep the cruise ALT value unchanged (the value entered on the CLB or CRZ page). The PMS calculates the required descent altitude difference (and therefore the TOD/BOD distances and required VS) based exclusively on the difference between cruise ALT and BOD ALT. If you manually change the ALT value to match the BOD ALT (or set both to the same altitude), the system will detect zero altitude difference. As a result: Descent distance becomes 0 The required descent VS becomes invalid The TOD and BOD predictions will be incorrect or show as zero Recommendation: Leave the cruise ALT exactly as it was set during climb/cruise planning. Only enter or modify the BOD ALT when you want to start the descent profile. The cruise ALT must remain the original reference altitude for the calculation to work correctly. Has anyone made sense of this yet with respect to changing ALT on the CRUISE page? Thanks!

This occurs temporarily right after a new batch of waypoints has been imported. While the INS is navigating from waypoint 9 to waypoint 1, the map seems to simultaneously display the OLD waypoint 9 AND the NEW waypoint 9 and draw a line between them. Thankfully, it does NOT affect how the aircraft flies the route.

Ok, definitely sounds like a bug, then.

Thank you for that information. However, there are some aspects of it that I find confusing. A few follow-up questions about the nuances of the update procedure: 1. All the info about the DME/DME fix and intersection fix accuracy are relevant for systems like the CIVA, which can compute position corrections based on it, but it sounds like the LTN-72 can't do that. Also, the pilot can't manually derive lat/long coordinates from a DME/DME fix either, without a lot of math. So it seems like directly overflying a radio navaid with known coordinates is the only way to do this update procedure. Am I right? If so, that leads to the next question: 2. The aircraft is moving at multiple miles per minute, and tends to sequence to the next waypoint slightly before arriving at any particular one. How do you indicate to the INS that it should overfly the fix rather than cutting the corner, so that you fly precisely over the coordinates you intend to update? (Manual mode? or is their an OVFLY function?) 3. Does pressing the "hold" key, as indicated in the procedure, cause any newly entered position apply a correction to a) where the INS thought it WAS at the moment you pressed the "hold" key or b) does that entered position become where the INS thinks it is RIGHT NOW? I'm hoping it's the first option. Otherwise, any delay in typing the corrected position in would cause miles of error given the aircraft's speed.

What about the cabin pack currently available in the iniBuilds installer v2.5.3?

all 3 of mine shutdown as soon as i move my throttles forward. tried messing with the calibration menu but it doesn't seem to help. every restart of engine, same thing. if i leave the thrust lever a little above idle, it continues to run. but as soon as i bring it back to idle, they shut down.

Several functions of the PMS are missing, including the CLIMB SELECT, CRUISE SELECT, HOLDING SELECT, DESCENT SELECT, STEP DATA and DES BOD OPT pages.

Hi @LNOSS Could you share the PDF OFP of the affected route so we can try to repro on our end? Thanks!

1. The LTN-72 is not capable of triple-mixing IRL, so not simulated by design. The AP on this equipment configuration can be driven by INS-1 or INS-3 only. At the moment, only INS-1 drives the autopilot in the simulator. Team is investigating feasibility of coupling INS-3 in a future update. 2. Remote functionality is planned for a future update. 3. INS-Drift is simulated, and is a user-configurable option via the PFB Aircraft Settings (Note: Further refinement of drift-rate is in progress). As MD82 mentioned above, there is no automatic position updating on the LTN-72 (manual excerpt attached). The manual position-updating procedure is explained starting Page 105 in the manual which can be obtained here.

Thanks, forwarded to the team for further investigation.

Thanks, logged.

For the upcoming v1.0.1 update, we’ve made adjustments to the tint. Once the update is available on the Marketplace (expected around next week), we’d really appreciate it if you could try it out and let us know how it fairs. Correct, the simulator doesn’t factor that in when determining interior brightness. The noticeable contrast between the interior and exterior is mainly due to how the sim currently handles eye adaptation, which is still a balancing limitation. The main workaround would be to brighten the cockpit textures, but that introduces much greater inaccuracies in the overall colors, so it’s a difficult trade-off. Thanks!

I have a flight sim setup with separate controls for the rudder and nosewheel steering tiller, and in the L1011, I've noticed that the nosewheel steering turns much too far with rudder pedal input. If the L1011 is anything like other simulated airliners I've experienced, in setups like mine, rudder input should cause the nosewheel to turn a maximum of roughly 10 degrees in either direction, and the nosewheel steering sensitivity should dampen to zero (or nearly so) at higher speeds to make it easier to control during takeoff and landing. Instead, it turns through almost its full range of motion when the aircraft is moving at slow speeds, and doesn't sufficiently dampen when accelerating for takeoff or decelerating during landing, making it quite difficult to keep the aircraft on the centerline. I'm not sure whether fixing this issue would require a change in the plane's code somewhere, or the addition of a "separate rudder from tiller" toggle in the PFB, or both, but it needs to be fixed before I fly the L1011 any more, as it makes it frustrating to control during takeoff and landing. Real shame, because I like it so far otherwise. If this somehow turns out to be a setup issue or skill issue on my part, I do apologize, but I've all but ruled out that possibility because I have no such problems with any other airliner.

I am unable to enter fuel quantities higher than 159 900 LBS in the PMS even though the maximum fuel quantity is around 213 600 LBS. Entering anything higher than 159 900 LBS (1599 in the PMS) gives an ERROR. I have the units set to imperial in the PFP.

Thanks for your reports. For the upcoming v1.0.1 update, we’ve made several adjustments to textures aimed at improving overall FPS. Once the update is available on the Marketplace (expected around next week), we’d really appreciate it if you could try it out and let us know how it performs on your end.

PFB performance calculator is good but seemingly does not factor in the runway and therefore the weather. Can this be added, presumably it formed part of the real world calculation?

The PMS seems to give a climb EPR that is much higher than the maximum climb EPR from the table on the FEs desk. In this example I am at FL260, with a TAT of 3 degrees. According to the maximum climb chart this should give me an EPR of around .640, however the PMS gives me a climb EPR of .716.

Hi @GACSavannah Check that your simulator paths are set correctly in iniManager. Click your name at the top left, choose 'Sim Paths' from the menu. Use the 'Scan' button to set a path automatically or click the 'Folder' button to pick your community folder manually. Then, restart iniManager and try again. Alternatively, you can also grab third-party liveries from external sites like Flightsim.to for example. Thanks!

Thank you for your suggestion. We are currently exploring the possibility of integrating your OFP flight plan for preview within the Enroute page of the PFB.