nenzaa1122

Thank you for your patience, and I apologize for the late reply. To conclude, the issue has been resolved. It appears that some data within MSFS 2024 itself had become corrupted, and the Strike add-on was triggering a crash when accessing that data. Reinstalling MSFS 2024 resolved the problem. Most likely, the corrupted data was created at some point, and that information was saved as part of the Strike’s cache. This add-on is not related to the cause of the crash. I sincerely apologize for the inconvenience and truly appreciate your time and support throughout this matter.

Regarding issue #3, I checked the Event Viewer and found the following error message. Faulting application name: FlightSimulator2024.exe Version: 1.6.34.0 Time stamp: 0x00000000 Faulting module name: FlightSimulator2024.exe Version: 1.6.34.0 Time stamp: 0x00000000 Exception code: 0xC0000005 Fault offset: 0x000000000453a195 Faulting process ID: 0x4BD0 Faulting application start time: 0x1DC9B0DAE3B1CB5 Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.6.34.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.6.34.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Report ID: ed12f20b-7549-4619-b47e-d39a0056f17a Faulting package full name: Microsoft.Limitless_1.6.34.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App This log was generated at the time Striker crashed. I tested it approximately five times, and the same message appeared each time. As mentioned previously, this issue does not occur with any other aircraft. Therefore, I suspect that this aircraft may be causing some kind of memory-related issue or unintended memory behavior. I hope this information is helpful.

Thank you very much for your reply. Regarding the canopy operation, I understand that this is a design choice made by the developer to accommodate many users, and I accept it. As for point ②, it seems that my original report was slightly inaccurate. After conducting more detailed testing, I found that the issue occurs when increasing pitch and simultaneously moving the cyclic to either the left or right. For reference, I have attached a video demonstrating the behavior. 無題のビデオ ‐ Clipchampで作成 (5).mp4 Due to the file size limit, the video is very short and the quality has been reduced. As I am still not very familiar with this website, I would appreciate it if you could let me know whether there is a way to attach a longer and higher-quality video, should one be necessary. Regarding point ③, I rebuilt my MSFS 2024 Community folder and tested with only the Striker installed. However, the issue persists: if I load the aircraft more than once within the same game session, the simulator crashes every time. This does not occur with any other aircraft. My system specifications are: GPU: RTX 3070 CPU: Ryzen 5 5600X RAM: 32GB Once again, thank you for your time and support. The Striker is a truly excellent addon, and I am very impressed with it. I sincerely hope these issues can be resolved.

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.