All Activity

Which aircraft/operator configuration was used as the reference for the A380 SimBrief profile, particularly the 284,856 kg empty weight and 4,672 kg maximum cargo weight? Is this intended to represent a generic A380-800, a specific weight variant/MSN, or one of the cabin configurations included with the iniBuilds A380? For comparison, a Lufthansa A380 flight with around 420 passengers can result in a substantially higher operational ZFW than the current profile produces. Should users adjust OEW/DOW and cargo capacity for airline-specific configurations?

I'll do some more troubleshooting on my end. Off the top of my head, I'm not entirely sure what's causing the issue, but I'll look into it further. Thanks for your patience!

Gate 235 do not reach A320n FBW front door

Hi, thanks for the reply. I have verified all the items you requested: SimBrief AIRAC: 2609 A340 EFB AIRAC: 2609 R1 FMGC Active Navdata: 03SEP–01OCT (AIRAC 2609) Navigraph login: Active Hoppie login: Configured SayIntentions: Not required for FMGC uplink AOC messages (like the loadsheet) DO arrive correctly, which confirms datalink connectivity. However, the following still fail every time: INIT REQUEST → ERROR DOWNLOADING DATA AOC FLT INIT → fields do not populate AOC RTE UPLINK → no route uplink VERIFY → SEND → does nothing Since AIRAC cycles match and datalink messages are received, this appears to be an FMGC/AOC uplink logic issue rather than a configuration problem. Please advise on next steps. Thanks.

Hi Bert, As a follow-up: RWY 13 REIL: This has been logged and should be fixed in the next update. RWY 23 REIL: REIL will be added and should be included in the next update. RWY 31 PAPI: RWY 31 does indeed have PAPI lights on both sides, which has been confirmed by our reference material. Surrounding imagery: I've mentioned this to the team. However, I believe this may be a limitation with the surrounding ortho imagery provided by the sim. Spot 21: This has been noted and should be fixed in the next update. Dingli Cliffs: I've passed this along to the team for future consideration. Thanks again for taking the time to provide such detailed feedback!

I have the same problem, I debug with Claude Fable, in my ticket 63431 you have good info to find the solution and help the community, thank you.

Like... everything else about the addon seems fine to me. It's just the lack of any ability to use the NAV/COMM 1 without a GPS is what's holding it back...

Thanks for your feedback. I've sent it over to the team for review. Appreciate your patience!

Hi, Could you attempt a fresh install of the scenery again? Thanks!

Hi all, I installed EGCC scenery forXP12, but only the jetbridges seem to be showing up. Log file attched. Help gratefully received. Thanks!Log.txtLog.txt

The L1011 autopilot still needs a lot of refinement. In my last few flights alone I have experienced: The autopilot struggles to hold altitude during a turn, especially when low and slow, where you may lose as much as 1,000 feet in a deep turn. The autopilot struggles to capture VOR radials and localizers, even when the intercept angle is less than 30 degrees. I have set up to intercept localizers at a very modest intercept angle at places with parallel runways like ORD and ATL, and the autopilot consistently turns so late to capture the ILS that you fly through the approach path of the parallel runway and then it curves back around to try and track the intended runway and may even overshoot that turn, too. When a radial or localizer is captured, the autopilot fails to track it and keep the course needle fully centered. This is especially problematic for ILSes. This behavior is especially bad when there is a crosswind. Sometimes even when centered on a radial/localizer per the course needle, you are off course. I flew the ILS 27L into ATL the other night and when tracking the localizer with the needle centered, with no crosswind and no crab angle, looking straight out the window it looked like I was lined up on 27R until I was maybe a mile out. It is not an offset approach, and if it was, it wouldn't be offset into the approach path of a neighboring runway. The autopilot and PMS routinely struggle to connect to each other. Even when the PMS is properly configured -- I have been through the documentation and know what it needs to work -- the autopilot and TM mode of the autothrottle can sometimes take 5-10 minutes after takeoff before they'll recognize each other and go into EPR mode for TM and VNAV mode for the autopilot to climb via the PMS speed plan. As myself and others have been noting on the forum recently, the L1011 still needs -- and deserves! -- significant attention from iniBuilds so that the add-on can live up to the high potential that it has.

Hi, A couple things to go over: Can you confirm your simulator, aircraft and simbrief are all on the same AIRAC cycle? Have you logged into Navigraph/Hoppie/SayIntentions on the EFB? I've attached a few screenshots to verify everything is working on my end. Let me know if any of the steps above helped. Thanks!

Any new developments as to why SimConnect becomes overloaded and the WASM module ceases communicating?

Hello, it's me again! I've managed to reproduce the terrain radar issue. Unfortunatelly I could not upload a video due to the file size limit here, but I've taken a few screenshots of all of the displays. I apologize if the images are a bit bright, I had HDR enabled. I hope it won't be a problem! The steps I did to reproduce the bug: Launched MSFS 2024 Went to Free Flight and selected the A350 I switched liveries from Delta to Lufthansa Started the flight in Cold & Dark then powered up the aircraft When the IRS alignment process was completed and I tried the terrain radar, there was the issue After I restarted the sim and went back to the same airport (JFK), did everything the same way, the terrain radar worked fine. After that I did a few more attempts, tried changing up things, switching liveries before flying or using the same, waiting before powering up the aircraft, changing up the pace of starting things etc, it's been stable ever since. The only difference I've noticed between the attempts is that I got the A/C POSITION INVALID warning message on the MESSAGES LIST page in the FMGS. That message seemed to be a clue, but it came up in two startups, yet the terrain radar has been working regardless ever since the very first attempt. Let me know if there is anything else I can do and if there is any update on your end. Thanks.

Is this with the 1200 version or the 400? Thanks!

Please try the method down below, which another user had success with. Thanks

Hi, Yes, you will be able to pop out the screens and use them with your mouse. We've also created an FAQ covering this topic, which I'll attach for your reference. Thanks!

That is correct! Thanks 😊

Hi, The spawn points in the sim are not dynamic and do not change based on aircraft type. Each gate has a fixed spawn point where the aircraft's nose will spawn, regardless of the aircraft being used. As is standard practice, we select a position that works for the widest range of aircraft types without causing collisions. GSX, on the other hand, can read the aircraft type when properly defined in the profiles and reposition the aircraft to the appropriate stop marker. As a workaround, using the "Reposition Aircraft" feature in GSX should align the aircraft properly. Thanks!

Hi, This is unfortunately a limitation with GSX. We have reached out to the team for further clarification, but have not yet received a response. Thanks for your patience and understanding!

Hi, Thanks for taking the time to share your feedback! I'll pass this along to the team for reference. Thank you again!

The current Trent 900 sound set is pretty decent overall. Here are things you guys can do that WILL make it more accurate. This stuff is really hard to explain properly on text so I'd really appreciate if I could just chat with the sound people in a call somehow. 1. The spool in higher ranges sounds a little too whistle-like. If you can make it sound less like a whistle, the core component of the engine sound will sound better. 2. This is my biggest complaint of the current spool sounds. At ~71% N1, where METOTS caps the second spool, there is no growl. In audio clips and the ones I've been on, there is a growl at that sound point. The howl component of the spool will be a B flat and the growl should be an E flat there. This goes to say in general, the growl part of the engine sound starts too late in the spool. 3.) Additionally, the slats sound pitch is wrong. Currently, you guys have it close to a G natural. The pitch of the slats should be a slightly sharp F Sharp. The sound itself could also be reworked to be louder in certain parts of the sound. Real Recording at 5:56 You can hear the sound F sharp there. Additionally, you can hear how much louder the beginning wind up is. You can hear it loudly in the cockpit too as seen in this video at 6:37. And I have flown on-board the aircraft IRL multiple times so I can confirm the sound. Again, this is hard to explain here. I would REALLY appreciate if I could talk this through on a call somehow. PLEASE seriously consider these changes.

This is after loading into OMDB V2 at gate D1 https://photos.app.goo.gl/hdvAk5EToqxK32689

Okay thanks so much and can’t wait to fly!