All Activity

Hello, I have encountered a weird navdata problem when flying A320 v2 to Cork (EICK) I was flying inibuilds/Asobo A320neo v2 and the ILS frequency in the FMS for runway 26 was 109.5, whereas it should be 109.9 I believe. In any case it did not work. As this happened immediatley after the navdata update, I first reported the issue to Navigraph, as I thought something was wrong with it. Their support investigated the issue, and came out with the following: Problem seems to be specific for A320neo v2, or at least on some other aircraft it does not occur, Problem only occurs if the handcraftdd EICK is on - if it is off, the ILS works, Problem occurs also on default navdata. They also noticed a strange behaviour of the FMGC, where the ILS frequencies are not displayed. Not sure if this is a scenery or aicraft issue. For details see: https://forum.navigraph.com/t/ils-freq-eick-26/22727/2

WASM Crash Report When the crash occurred, I was switching my approach into VHHH from RW25C to 07L on the flight plan page of the MFD. The exact moment I clicked the transition point "LIMES", the WASM crash occurred. Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: RJAAVHHH_PDF_1771894529.a10404a1.pdf WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 Specs: Ryzen 9 5900X, MSI RTX 4080, 64Gb DDR4 3600Mhz Autosave File: 1771907873.bin

If you've also got the message that says: vhf1 reception not selected Then right click the VHF1 knob to pull it then turn it up to receive ATC audio

When the plane touches the ground, the chicks and GPU appears… it disappears a few seconds later. Chocks and GPU off in the EFB doesn’t affect the landing at all, but I don’t think that was supposed to happen 😅

You can see here that the VNAV path calculation still needs work. The aircraft is predicting that it will not meet the AT 4000 constraint at CAMEL. However, the calculated descent path is just too shallow. The aircraft is only descending at 500 fpm and having to add thrust to maintain speed. Why not calculate a steeper path that can be done as an IDLE descent and therefore also meet the constraint at CAMEL? This is just one example of what is not an isolated incident. Of course there are plenty of other errors with VNAV and the aircraft's altitude and speed predictions which I have reported elsewhere and am looking forward to seeing some progress on.

Hi, attached some tail screenshots and a cockpit one. I apologize but a video was too big to be attached. I tried. Anyway, you can see the jagged edges visible only at night with logo light on. There are artifacts also above the cockpit with the torchlight on. I have to correct myself since on the A300 there is some minor problem of the same nature on the tail and the cockpit too. The A340 is perfect, no issues at all. I run MSFS24 in 4k with TAA and ULTRA settings, full screen. These kind of artifacts happen on the edges of the 3d model when under direct lighting, for example when using the torchlight in cockpit, and in AMD RX9000 video cards. New drivers helped to solve the issue on others planes but is still present on the A350 (and A300). Hope this help and thanks for your support. Cpt Dart

IT's ok. I solved my own problem. For those who are trying to do something similar with a Streamdeck+ or a 7-segment display. When you preselect a speed whilst in managed mode, the displayed value is L:INI_PRESELECT_DIAL not L:INI_AIRSPEED_DIAL. You can then monitor "L:FCU_SPD_TIMER" which will be a non-zero value all the time the preselect value is displayed before it defaults back to ---. Don't precisely know how inibuilds have done it themselves but this works for me.

Any news on this topic? Still the same liveries. All the included "freeware" in MSFS24 from inibuilds are a little bit forgoten.

Haha all good, happens to the best of us sometimes when there is so many different things to click on. Glad you were able to resolve it!

@IniJamir @IniSteve Just making sure you guys saw this...found another one missing last night, looks to be the same barrier type texture. Confirmed by multiple console users at this point, let me know if you need any other info, thanks as always! --Nick

So, sorry I didn't get to you before I got to me. I figured out that as usual, I'm an idiot. I had unfortunately disabled in FS24 this scenery (in addition to the world update scenery All working now, and it looks beautiful!!

thanks! very much appreciated!

I will pass this along to the team. Thank you

I'll ask the team about this

Good morning. Loaded up at DFW today to do a flight and I noticed a weird anomaly with the AI taxi routes. The ai would taxi south on K, enter the E ramp at spot 47, then take the ramp around to spot 52 before turning onto B for the bridge. IRL at DFW we head south on K and turn onto B avoiding the ramp area. IDK if that’s an FSLTL thing but I figured I would bring it to your attention.

Did you clear the scenery index in between uninstall and reinstall of the scenery Microsoft Store/Xbox App: C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes Steam: C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes Delete all files inside the SceneryIndexes folder

Hi, Can you post a video demonstrating the issue, I have a 5700XT (I know right) and as a result I can't 1:1 the issue that could be occurring here, thank you.

I’m one of the ones who have waited patiently for 2024 to finally resolve all the issues at release and I’m proud to say I’ve finally migrated over and I’m loving it . So many improvements and it finally works . As a treat I downloaded the A350 and absolutely loving it . Credit to inibuilds as this is the first plane I have purchased from them and they’ve done a superb job with this . Kudos to them .

Hi, Unfortunately if it still does not function following those steps I can refer to you to contacting direct support as their team has a better handle on these sort of unique situations. Thank you for understanding and sorry for the inconvenience https://inibuilds.com/pages/contact

Hi, This is definitely quite the unique aircraft, I'll pass it along to the team

Hi, I'll pass this along to the team

Hi, Thanks for the suggestions, I'll pass it along to the team.

Sounds good, glad I could help. 🙂

v2.5.2 of the iniManager has been released. This is a small update to address an install error for some executable products. This update will be downloaded automatically when you launch the app or you can manually download it here. v2.5.2 - Fixed install error for executable products where the path had a space in it.

Bug 1: Glass in cockpit doesn't show rain drops at all. Screen grab below. Unless I've turned off a setting somewhere. It shows on other aircraft. Bug 2: When first going to the MFD Map (Say at an airport) It shows a really zoomed in view of the map. Showing taxi lanes, buildings etc. Also the Zoom amount on the left says 4. But if you then go to Zoom the map in and out, the closest you can get is 2 then 4 then 8 etc...you can never get it back to the close in View you started with. 2 zoom is still far out. Questions; Just wondered if some odd things are how they should be, like: 1: To fly in a straight line I need a constant boot full of Right rudder. Otherwise the heli flies at a constant left pointing angle. A little to get started I imagined but not this much constantly. Is this how it should be? This isn't needed with the Hunter or other heli's as much. 2: This one I need to check more. ( I might have pressed something like reArming inbetween) But the dotted line showing the route to the target sometimes disappears after taking out the first target. I just get the circle highlighted but no line. Is this normal? 3: Collective seems to have all it's sensitivity at the very top 80 percent and up. I feel it needs to have this area kick in around 60. 4: I absolutely love the sounds on the Helicopter, great job! Also I can hear the missions being loaded but when getting close to a Target, if they're saying anything like " Target five miles out" or anything else like the one in the Hunter does, I can't hear it. Is it there? Or is it very quite and drowned out by the engines? Thanks