[Crashes when using MCDU]

And...once again. same page, same information, crash.

For goodness sake, if you're going to call an aircraft premium, make sure it works right before releasing it and charging money for it.

I've now wasted an hour of my night dealing with this. Thanks.

[Crashes when using MCDU]

This was the second time tonight while I was entering information on the MCDU that the plane froze up and the game crashed on me. This time it was while entering information on the Progress page. 

I hope the team is aware of stuff like this going on and has a fix planned, because it's really annoying to spend all that time preparing for nothing. 😠

[Grass on approach path]

There is some grass coming up through the concrete at 01L.

[Jetways not connecting properly]

At gate 76 the jetway did not connect to our aircraft properly. FBW A32NX

[NZDN: doubled-up vehicle models]

The two vehicles parked in front of the fire station have doubled-up models, i.e., there are second, duplicate models placed on top of the first ones.

[Engine sounds with covers on]

With the engine covers on, you can still hear the engines spinning, as if they are open to the wind. 

[Hoppi]

That's up to Microsoft. 

[Snow coverage issues and animals in the airport]

Default LOWI confirmed disabled, too.

[Snow coverage issues and animals in the airport]

[Snow coverage issues and animals in the airport]

There are a lot of issues with snow coverage along the perimeter roads and along the approach path, plus I spotted a buffalo wandering the ground as well. 🙂 

[Rudder trim reset button sound]

8 hours ago, Eddie said:

Hi,

Thank you for the report. Are you seeing this issue across all variants? I tried to reproduce and there is a sound made each time; see video:

Hi, I've only tested it with the GE freighter. It seems to be an issue only when the rudder trim is zeroed out (or perhaps it's just really faint). 

[A350 Inibuilds]

When it's done. 

[Freeze MCDU again again again !]

On 1/12/2025 at 10:21 PM, Kevin B said:

indeed no response. you'd think they didn't care, especially no updates since the release..

Take your complaints to MS. They are the ones responsible for updating these aircraft, not iniBuilds. 

[Rudder trim reset button sound]

It appears the rudder trim reset button has no sound right now. 

[QNH mismatch when using historical weather]

To add: this also seems to extend to the takeoff performance page too. 

[QNH mismatch when using historical weather]

Tonight I flew a flight where I set the clock back about 12 hours. After importing my flight plan I checked the A300's EFB (not the MSFS one), and the QNH was given as 30.00. However, when I requested a weather report at the same time from the IDC, it said the altimeter was 30.13 (the actual value in the real world at the time of the flight). So,it looks like the A300 EFB is reading the historical QNH but the IDC (and BATC for that matter) is showing the current QNH. 

[A300-600 FS2024]

Been noted weeks ago by inii that they can't do anything with a fix from Microsoft. 

[Autopilot switch sound missing]

When using the default "autopilot on" command, the associated switch doesn't make a sound. However, it will make a clicking sound if one uses the mouse cursor to turn it on.

[ILS 23L at KIND issue]

I had an issue tonight where, even though I was tuned into ILS 23L at KIND, the glideslope and localizer never showed up on my PFD, and so I had to make a visual landing approach. I triple-checked I had it tuned correctly, which I did. 

The scenery is the one from DDT.

[LVARs for exterior light switches]

9 hours ago, richboy2307 said:

The Behaviours menu is a bit different in terms of layout in FS2024, with alot more options but it generally works in the same way. 

• Enable Developer Mode in settings and then open the behaviours menu from the [DEVMODE] toolbar.
• Highlight the interaction you want to inspect by hovering your mouse over it and then press 'L Ctrl' +'G' on your keyboard.
• On the [INSPECTOR] Tab, you can usually fin the affected variables under Animations or Mouserect dropdowns.
• Then go to [VARIABLES] Tab, type in the name of LVAR and use your mouse to conduct the interaction to monitor the changes in values.
• Note: The sim does not allow all LVARs to be defined by the user, but this way you can find the affected LVARs for each interaction to see the ones you can manipulate.

 

Thanks!

Appreciate the help again, thank you. 🙂 I did ultimately find what I needed last night by enabling the behavior debug mode and hovering my mouse cursor over the switch I wanted LVARs for. 

[LVARs for exterior light switches]

On 1/3/2025 at 11:33 AM, richboy2307 said:

There is an LVAR list posted here for FS2020, I believe the same should apply for FS2024 as well:

Alternatively, you can use the method mentioned further up in the post to access the Behaviours Dev menu and see switch-associated LVARs yourself live in the sim.

Thanks!

I tried that in 2024 but I couldn't get it to work right. Did anything change with dev mode or am I just missing a step?

[Capt ET Run/Stop LVARs]

Perfect, thanks!

[LVARs for exterior light switches]

1 hour ago, richboy2307 said:

I believe it is INI_TILLER_DISC with values of 0 / 1  for pulled out/pressed in respectively.

Thanks, yes, that did it.

[Hand microphone and FCOM binder]

In the A310, there are hand mics on each side of the cockpit, as well as some sort of thick binder that's probably an FCOM in the middle of the pedestal. In the A300 cockpit those items are missing. Would be nice to have them there.

[Capt ET Run/Stop LVARs]

I am having some trouble getting the RUN and STOP buttons to work correctly in AAO for the captain's clock. The code, per the mobiflght page is this:

3 (>L:INIDR_CHRONO_GMT_STATUS)

4 (>L:INIDR_CHRONO_GMT_STATUS)

But neither of those work. In AAO, I have them set up like this, but neither respond:
 

3 (>L:INIDR_CHRONO_GMT_STATUS, Number)

4 (>L:INIDR_CHRONO_GMT_STATUS, Number)