All Activity

I have noticed several bugs and issues while using the KwikFlight Striker: Cockpit behavior: Opening the cockpit automatically switches to walking mode, which breaks immersion. In real life, the cockpit door starts open at startup and closes only when the engines are started, but in this aircraft, it is already closed on boarding and cannot be opened. Flight model: When pitching up sharply and lowering the collective, the nose should descend smoothly, but the movement is jerky. Critical bug: Loading the aircraft more than once consecutively in a single game session always crashes the game. This does not occur with other aircraft and seems specific to this add-on. Despite these issues, the add-on is excellent. I hope these bugs can be fixed.

Since the recent update, there are occasions where the external lights on the A350 do not appear. This does not happen consistently, but it has been noticed several times during flight.

Your silence is even more disappointing than the bug itselft... 🙄

Gonna jump on this as well. Same issues as above. On takeoff roll my aircraft basically just steers out of control and flips over.. I don't have any double assignments either.

By the way,I know that FENIX's model aircraft has an engine icing simulation feature, requiring a certain thrust to be maintained for a period of time after starting in a cold environment until the ENG VIB drops. I've tried this many times with FENIX. But on the 330 RR, I don't know how to do it.

Test condition: DigitalDesign ULLI -7 ℃ with or without GSX deicing From Cold and Dar to APU bleed start engine A330-300 RR all 5 test no work A330-300 GE all 3 test work A330-200R all 2 test no work After I change temperatur to +0℃, all RR engine work I didn't know the RR engine was so sensitive to temperature. The icing assist is ONLY VISUAL.

I'll pass this on to the scenery team. Thanks for the insight

Sorry....my fault. I was looking for it in 'My Products'. Which automatically goes to the 'Installed' Status instead of 'Not Installed'. Didn't know it even had that silly extra area. So it didn't show. Got it now thanks.

Good Day Kwikflight Team, First let me just start with a compliment on the 3d modeling, she looks beautiful! In control bindings, Throttle and Condition levers, are coded to the collective. This should never be the case. Only one thing should be coded to collective, and that is collective. I am fortunate to have physical hardware with dual throttles and a full collective hardware kit. I would like to assign my controls properly. Any physical control including an xbox controller can have any axis assigned to collective on our end, it should not be hard coded to have all power levers assigned in duplicate on the developer side. Please fix this ASAP. Best regards, Woog

Have you tried logging out and back into the IniManager.

Good start. Just bought the Kwikflight Striker. got the emails, confirmed the payment....There's no sign of it in iniManager. How long until it appears?

Hi Steve, thank you for the reply. I can confirm the issue is resolved for me.

I'll be honest, I don't know. I have never taken the time to actually look inside. I'm also someone that feels like interiors aren't a priority unless it's something your see from the cockpit. I love good looking scenery but interior for me isn't priority.

Hello , i came here to say this is also happening on the PS5 , the stutters make flying the plane a miserable experience so hopefully it will fixed. thanks.

Yep, all working now after latest SimApp update.

Hello everyone! The A350 1.2.1 update is really disappointing; it's impossible to even fly for an hour without WASM. I'd like to know how to revert to the previous update. On the other hand, the A340 is fantastic and very realistic. Thank you so much for this exceptional aircraft! 😉👌🏼

Hello it is very strange with your iniManager. That is not the first time, I got into trouble with installed sceneries: Sometimes, the installation is still not recognized, although the add-on was deleted and install again. This morning, six updates performed, but still none of the add-ons are recognized as installed. Nevertheless, many thanks for assistance, but the two suggestions were not successfully to resolve my issue. To your question: I am aware of the problems with linked add-ons, therefore I am using two specific folders for the add-ons from iniBuilds (one for MSFS2020 and one for MSFS2024). With some expections (see 1.) that functions properly until the last update of the iniManager. This update caused the strange behavior described in my post before. I will execute a complete new installation (the second one). However, based on my experience over the last few years, I can say that your iniManager does not work perfectly. Sometimes it is unreliable. Regards

I noticed the same Problem. Yesterday I updated the SimAppPro to Version 1.16.88 and proceeded with Firmware- Updates for MCDU-Cpt (v1.04), MCDU-Co (v1.04) and btw.ECAM (v1.01). After loading MSFS2024 and iniBuilds A340-300 respectively restart SimAppPro all was working fine, that means : FCU, EFIS 2x, MCDU (2x), ECAM and AGP.

I seem to have fixed this issue by deleting ALL the bindings for MIXTURE. I was getting one or both engines failing every flight at T/D.

Any help? Here is a picture of what we're talking about.

I've experienced a PFD and system freeze as well. On my way from Cape Town to Frankfurt. Checked the console and it was not a WASM crash. I was lucky to have noticed it in time and loaded my save to recover.

Hello. Today I updated my 340 from markeplace like always and again, all my previously saved costum panel states were missing. This happens after almost every update. Please fix it!

Yep I thought maybe it was some intended simulation of slight changes to passenger numbers. But it’s always fewer passengers, never more, and the ZFW is always still exactly the same as Simbrief. So it has to be a bug.

Further, have managed to identify the issue with help from BATC's team. Red boxes are the issue, green box is fine. You'll see the holding point nodes for 08R are correct in the middle, but are listed for 08L for the top and bottom one in the screenshot. Changing those holding point notes leading onto 08R to specify 08R, not 08L, should resolve the issues.