All Activity

Unlike during position and waypoint entry, beginning to enter coordinates when in HOLD mode on the INS does NOT cause "insert" to illuminate. Also, after entering coordinates for latitude and pressing insert anyway, the value reverts to the previous position UNTIL longitude is also inserted. Then the position updates. I do not have any evidence of what should happen here, but that feels inconsistent with other modes of operation, and therefore potentially wrong.

I'll test this again. I did a 5.5 hour flight yesterday, and I did a couple of inflight position updates. Landed with a 1.4nm position difference. HOWEVER, that could have been a data entry error on my part. (The "INSERT" light does not light up after entering a latitude in HOLD mode. I don't know if it should or not, but I think someone should double check, since it's the only mode I've seen where it doesn't)

To continue, note the rudder pedal positions and lack of indication on the defective instrument. Hope this helps.

You're welcome. The OP contained a photo. Then 3 posters confirmed the OP defect. This is a very simple defect to confirm. Start on runway, move the yoke and rudder pedals and observe the instrument. Attaching some photos for you: Neutral, full down elevator, full up elevator, and rudder photos to follow in another post due to upload limit sizes.

I'll pass this along to the team, thank you.

Coming back to the INS drift simulation, I just completed a 9-hour flight from Sao Paulo to Lisbon. On purpose I did not perform any position update procedures during the whole flight. After parking on Position 801 in Lisbon, I performed the INS post-flight drift check by entering the parking spot in waypoint 1, activating track change 0 --> 1 and switching the INS Mode to DIS/TIME/ Actual position LPPT Stand 801 coordinates --> Track change 0 to 1. Distance offset for both INS 1 and 2 showing 0.0 nautical miles. As you can see, at least for INS's 1 and 2 the net INS Drift over 9 hours of operation was 0.0 nautical miles. Which clearly indicates the INS Drift is still not there. p.s. Yes, INS Drift was enabled. I also flew with a buddy who flew out of Rio to Lisbon. Same result. No INS Drift.

v1.0.1 of iniBuilds Palm Springs (KPSP) Enhanced for MSFS 2024 has been released. This update addresses a few terraforming issues across taxiways, fixes an issue with gate 4, removed custom wind turbines to prevent duplicate turbines showing and includes a fix for AI pathing bugs. This update can be downloaded via the iniManager. v1.0.1Corrected various terraforming issues across taxiways Gate 4 parking moved slightly to allow for correct jetway operation Removed custom wind turbines Fix for AI pathing issues

1.0.4 update is out on marketplace. You can now walk around. Unfortunately the camera in first person cockpit view is still bouncing and hopping around lol. (Xbox series x)Am i the only one with this issue? But there is a new IDF livery included.. nice. Thanks for the Update.

So, is INI going to be adjusting volumes or nah?

Agree with OP here.

Hi, I'll ask the team about this, thank you.

Added for the team to take a look into again, thank you.

I'll pass this along to the team, thank you

Hi, the manual will be receiving an update to account for the new features were added.

I am glad to read that other simmers are having this rudder and elevator indication problem, as I am. Looking forward to this being fixed in the next update.

More updates will be coming to the manual, thank you :)

Hi, If I went around and asked everyone in a polling fashion if they are having the issue that one user was having whilst also dealing with other work items, I'd be stuck with 1000 one off issues where a good majority of them would be user error unfortunately. The reason I ask for a video is in case the user is either doing something wrong, or it's some other issue entirely, and then if it's not those issues then I already have video that I can pass along to the team showing exactly how this is happening and the reproducibility of it. I'd say that's pretty good judgement if you ask me. Thank you :)

Hello there, I have 1.0.5 and I see a manual 1.1 with change log and change bars. Which is pretty neat.

Hi Genista, I agree that kind of information really should be included in the documentation 👍 I’m using Axis And Ohs, and 1 (>K:AUTOPILOT_OFF) works fine. This should match the same action you get when binding AUTOPILOT OFF in the control settings.

Hi, fix for this will be coming in v.1.0.6. Once that releases, update me in here if you are still having issues, thank you all :)

Hi iniBuilds Team, it would be great if you could provide some documentation for the L:Vars and K:Events you use. Thanks 🙏

I like the idea 👍 Even with thrust levers, it’s hard to get the values right. Virtual flight engineer hands would help a lot.

Concur with the other users this is broken in 1.0.5 and was working before 1.0.5. This is quick and easy to verify and the team should not need a video to confirm the regression. Please use good judgement when asking end users for video evidence of bugs and/or regressions. When something so simple is broke, you don't need video.

No, for AP to follow the GPS on approach, one needs to select RADIO on the INS/RADIO button, AND select VOR not INS as well. Also, as is routine on the GNS530, select GPS or NAV on the GNS, as required for the type of approach. Good idea also to tune all 3 NAV radios to the frequency, if flying an ILS, LOC or VOR approach type.

I'm quite sure you could be able to get the test pattern on the weather RADAR display. Not so anymore in 1.0.5. In all; No test pattern or TEST indication on screen Weather tilt manipulation does not change displayed value of U 3.0 Pressing one mode control button should de-select the previous selection (i.e. Pressing WX while WX+T is pressed, de-presses WX+T) WX+T mode only displays WX on screen. Same as WX mode. (Logical but unverified)