Jayberlin
-
Posts
5 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Jayberlin
-
-
Hi all,
after a weekend of analysis and checking everything possible in regrads to FS2024, aircraft (especially inibuilds A350 (actual v1.0.12), but also x-check with other aircrafts) and addons, I found out the following. When deactivating XMP 1 as well as all overclocking features in the BIOS of my system, I could complete (up to now) at least one long haul flight (WSSS to FYWH) of approx 11 flight hours. It seems as if FS2024 do not like any overclocking and speed up option. However, the CTD did not occur on this flight and I will test that with other flights during the next days. Due to the fact that the CTD also occur with other aircraft (inibuilds A330 GE/RR or FBW A380X), I assume I have to live with the fact, that FS2024 do not like that overclocking option of my system and that at least the CTD are not an issue of the inibuilds A350 (for the time being).
Hopefully the display freeze has the same cause, but I am not sure. At least at the last flights I monitored the FS2024 dev mode console and had no relevant WASM or inibuild warnings/failures.
So I will keep switch off all overclocking features, even if I lose some FPS for the moment. Maybe the ASOBO team and/or inibuild find a solution in due time.
I will now start to enable my other features, such as Simracing Studio SRS software and the MiniCockpit plug-in for MiniFCU and MiniEFIS, to check if they have any effects in terms of CTD/display freeze.
Brgds,
Jayberlin
-
Hello everyone,
too early to celebrate: last night and this morning I tried a longrange service (planned WSSS to FYWH, about 11:30 flighthours), but after 2h at first flight frozen displays (no error messages neither in Windows nor in the Fs2024 dev mode console) and after approx 35 minutes of the second flight a CTD with Windows error message (0xc00000050).So the aircraft is still unflyable. 😞
Inibuild Support told me that they have contacted Asobo for their consultation.
Brgds,
Jayberlin
-
1
-
-
Hello everyone,
last weekend I made an BIOS update to my ASUS z690-F Gaming mainboard (to version 4301, which came out end of May) and since I did that update the freeze of displays is gone (for now). For the time being - I made just a short flight of about 2 hours - my problem of freezing displays is gone.
Before that BIOS update (coming from version 4101) I was not event able to use XMP1 with my G.Skill Z5 DDR5-6000 RAM; memtest86 and also the Intel XTU stresstest fails (especially with the AVX-tests). I found on an Intel website regarding failed AVX-tests, that it may help to set in the advanced BIOS settings -> AI tweaker -> SVID Behavior to "Intel fail safe".
I also avoid to use the weather radar in A350, as I read that in another post in this A350 forum.
However, I am not able to say wich action mentioned above solves my problem, but I hope the CTD/freeze-problems of the A350 are solved.
Next I will try a longhaul flight and keep you informed if A350 flys stable now.
Brgds,
Jayberlin
-
Hello everyone,
I have the same problem with frozen display units: Since A350 version 1.0.10 this behaviour starts for me and I am not able to complete a longer flight with the A350 in FS2024. After approx. 1,5-2 hours flight time all displays are frozen (aircraft is still flying and sound and cockpit cameras are working). I am able to manupulate some switches and knobs, however there is no reaction on the respective display/functionality.
I am on FS2024 SU2 (version 1.4.20), Windows 11, 64-bit, 24H2, and an intel i9-12900K gaming PC with 64 GB DDR5-6000 RAM and an AMD Radeon RX7900 XTX graphics card.
I have had serveral emails with the inibuilds support, but nothing of their advices worked so far for me (reinstallation, clearing the WASM folder, etc). For the time beeing the A350 is unflyable in my FS2024. However, other planes such as the FlyByWire A380X or the Headwind A339X works fine, so that I assume, that it is a problem of the A350.
I try to reproduce if it is a WASM crash by reading out the failures and errormessages in the console of the FS2024 developer mode, but it seems, that I have to wait 1-2 hours until the next crash occurs. I will keep you informed.
PLEASE iniBuilds-Team: help me / us with this "freezing displays error" - your A350 is such a nice and advanced airplane !!!
Brgds from Berlin, Germany,
Jayberlin
-
1
-
Cockpit Instrumentation Froze
in Systems
Posted
Hi all,
unfortunately the display freeze is back: monday evening I tried a flight from Windhuk to Cairo (about 8 hours ETE) and after approx. 2 hours in flight - display freeze. But I have also some news: I tried to investigate in terms of switching off systematicly my tools (such as AI OC, XMP 1, SRS, FSLTL, different airplanes, MiniCockpit DLS,...) I use with my system, and found out, that I have for the time being, no freezes, when I completely switch off my miniCockpit equipment! Does somebody else made the same experience ? Maybe the miniCockpit DLS (I use miniEFIS/-FCU and DLS with firmware 20241117 and DLS version 2.3.9) causes these freezes in combination with the inibuilds A350?
However I will investigate further, but since update to inibuilds A350 v1.0.10 this display freeze starts (after some hours flight) and it seems, that one possible cause could be some interaction with the minicockpit stuff - who knows...
I will investigate further and keep you informed. Here my preferred MS FS 2024 equipment:
The freezes occured approx. after 2h flight duration, but there are no error messages such as CTD-Windows messages, or other. There is no error nor warning in the FS2024 dev mode console. The only way to escape out of the freeze is to force FS2024 to shut down.
Brgds,
Jayberlin