All Activity

No, I'll try this and get back to you.

That is the most nonsense comment I have ever read here in forum, even frank couldn't reach that level, so congratulations! You don't have to read all the topics, if you are tired, be proactive and look somewhere else, no one is expecting anything from you.

I only use Vatsim, GSX and airports that I take off and land, what are the suspicious add-ons? I don't think these addons will cause any problems as they are widely common. And also, since this is the forum of the iniBuilds, I don't think there is anything wrong to report the problems here. Otherwise why would you have a special section for it, right? I am not sure what made you chuckle but really sick of the people like above who jumps between the topics and acts like forum moderator. We are having unique problems and we will report them to let you know and hope for the solution.

Just ignore that character, waste of time.

Hi Steve, hope this one helps. It is from a slight lean forward in the seat.

Thanks @richboy2307, ill reproduce the same steps over the weekend and report back. Appreciate the help on this!

Hi Steve, Pimax Crystal Super. It's not all of them, but it is the majority of the alphabet keys. I'll see If I can get some through the lens pics now.

With the evidence I have, I do agree that the initial cause is outside addons, but I don't see how the TCAS warning staying on after those addons are closed could still be from the addons. Like I stated before, I'm no dev. So if I am wrong, I'd be interested in learning how the addon is causing the TCAS warning to be persistant. Could you point me to another forum thread if it's already been explained?

I obviously did look at the forums. That's how I ended up here. So sorry I didn't dig deap enough to satisy your expectations. You too have a bad tendency of being rude to other users on here. Not a good look, especially when the other people are trying to fix a problem or help the devs with more info regarding a problem. Hope your day gets better too.

Providing bug information for the devs is always helpful, regardless of whether or not it's a known issue. What's not helpful is someone constantly being rude and belittling others on a forum for trying to solve problems. You have a bad habbit of doing that. Hope your day gets better.

@Roders Thank you for your time and for sharing your concerns. I understand your frustration, we genuinely do our best to address WASM crash issues because our goal is to provide a smooth experience. That said, these crashes can be difficult to reproduce, if at all, so every bit of information you provide is incredibly helpful! Thanks for the additional information; it was very helpful. Still no WASM crash, but I did notice the unusual ND line drawing/flickering behaviour, which could be another clue. Perhaps the WASM crash happens eventually whilst the PFD/ND system was re-drawing paths from memory. Thanks, noted with regards to DISCON as well. In the meantime, try performing all the actions through the F-PLN page instead (see video below)? Seems to work better in this instance (though there is no DISCON between AMIKI and CI14 initially still). If you encounter the WASM crash again, please let us know. We'll keep working with this in the meanwhile. Thanks! 2026-01-16 07-01-45.mp4

Here you go. Names self explanatory I hope. EDIT most shots to large for here. Same outcome. Attempt TO Perf in LBS, FAIL. TO Perf in KG, Sucess. Easily reproduced SB Flightplan attached. Edit II reduced some screenshots hope these are helpful -A SB Flightplan KPDXKOMA.txt

There have been significant changes to the model since this was first posted. To that end, very few uses are reporting degraded performance. Are you running 3rd party traffic addons or weather injection with these flights? If so, try repeating one with these off to see if the results are the same.

it should be on the product page.

What headset are you using. A few labels do LOD out but there entire MCDU obscuring isn't something we've seen

Hi @richboy2307, Appreciate the help! Sorry about my rubbish attitude there, flightsim can be frustrating. I didnt have the nerve to try reproduce the error when I restarted the flight. Will spawn the aircraft in over the weekend when I have some time and try make the same inputs. For context I didnt modify the flightplan until descent - I had ILS 14 NEGRA 2A arrival preloaded before departing Mumbai and left eh FLPN overnight with auto S/C etc. The crash happened as soon as I tried to enter a waypoint after AMIKI. I selected the waypoint from the FPLN page in the MCDU and then entered TRA into the 'Next Waypoint' field, it then prompted me to chose between two TRA waypoints. I selected the correct one and then pressed insert, which is when the crash happened. I noticed the PFD and ND froze for a couple of seconds and the range selector knob didnt work before finally the screens went orange. I also noticed when using PLAN mode and cycling through the FPLN that after entering ILS 14 NEGRA 2A the MCDU drew a path straight from AMIKI to CI14 for runway 14, which was confusing as surely it should insert a discontinuity. There are AMIKI transitions for RWY 14 but they involve a series of turns and ZHxxx waypoints (you also have to go into VIAS to select it). I usually enter TRA manually as I noticed this is what most ZRH controllers give me whenever I fly in. Perhaps the lack of a 'discontinuity' confused the aircrafts VNAV calc when entering TRA as an intermediary waypoint. What I was expecting was AMIKI - TRA - [DISC] - CI14 but I think the aircraft was trying to solve for AMIKI - TRA - CI14. Unsure, ill see if I can reproduce. Best, Roderick.

Unfortunately, a CTD can come from anything. Have you tried to isolate just the aircraft without any other addons/3rd party-plugins to see if the sim still crashes?

No, because it was the cockpit setup on the ground and the save didn't have time to complete. I'll try saving before entering the point. I need to try the latest update, and most importantly, I'm going to remove it from that thing... marketplace! Never again should a product be released on anything other than that awful place, to put it politely!

Unfortunately there remain some difficult to deal with LOD issues in the A340 post update when using VR. Of these the most frustrating is that 90% of the MCDU buttons are missing labels unless you move your head right up to the unit (which is mostly impractical). Any idea if these are on the fix radar? Many thanks.

Hi. We are taking a look and trying to determine what if anything has changed as we haven't made an update to LAX in a while.

The above made me chuckle. As for the erroneous TCAS error we have taken a deep look and suspect it's an external issue (we've seen reports of it happening in other addons. Despite that, we continue to check when we see reports and investigate when it's consistent.

Hi @Roders Sorry to hear about the WASM crash, and thank you for reporting it. The team will be investigating further. Although I haven't been able to reproduce this crash myself, I did notice some discrepancies with the VNAV calculations after applying the changes you mentioned, which might provide a clue. To help us better to reproduce the WASM crash, Are you experiencing a consistent WASM crash when performing this action (based on the attached autosave)? Did you make any modifications to the flight plan prior to this autosave? Thanks!

Ownership notwithstanding, this is likely a nav database issue. Did you replace the base data with NG via their hub? Can you share the routing so we can take a look and see if there is a formatting issue causing the 320 to parse it incorrectly?

Do you have an autosave you can share?

For this kind of thing you should reach out directly to the Web assembly devs (W3C) as they can deep dive you into how wasm works and what causes exceptions. On our end there is rarely one unique cause for crashes. Some of the code we use is written in C++ and xml among others. Best of luck to you in your thesis!