YS0430
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by YS0430
-
-
4 hours ago, Marcaggi said:
Could you be more precise I don't understand the first part of your message
In the ini manager you can select your community folder location, I put the link of the FS2024 folder into the FS2020 location and install the 2020 version into the 2024 sim, it then worked in the sim but not the 2024.
Now after this step I did my second reinstall of the FS2024 (plus all my most used scenery, fenix and FBW) and... bam! the 2024 version loaded!!! first compliation is like 3minutes and finally it worked.
-
Just to update:
Out of distress I tried to map the same community folder of the FS2024 into the ini manager FS2020 folder, and try once loading the A350 (2020 ver) and bam, that version worked... although no cabin or co pilot...
-
6 hours ago, Farlis said:
There are no refunds for digital products. Some companies offer them regardless, Inibuilds does not.
And on top of that a refund policy for a faulty products only applies if a product is really faulty. In this case it is not, it is the system of the end user that is faulty because it is not compiling the software as it should.
Update from the official direct support, they can't figure it out why this happens and is asking asobo, and they agree that it is very strange that thei default A320Neo V2 runs perfectly (first load 15sec), and the A350 just cannot load. will wait and see.
-
1
-
-
2 hours ago, Farlis said:
The steps he described in this thread clearly point that this is not a matter of where he puts the aircraft. Something in the sim, I suspect a setting in the Developer Mode, is preventing the compilation of the WASM data that is necessary to run this aircraft.
If his initial load after installation is done after 30 seconds than something went wrong. It should take at least 15 minutes the first time.
I didn't alter anything in dev mode and that's the weird part, fun fact is that the asobo inibuild coporation A320 neo just worked, and first load also <30sec.
-
35 minutes ago, pete_auau said:
have you tried starting from the gate and not the rwy maybe it doesnt like being started at the rwy
I try starting at the gate first, but since it cannot start any battery and external walk around I am able to find the GPU connection cover, open-> and GPU appears, shift+C into the cockpit the ext power button is lit up but nothing else work, contacted support and they told me to try start at runway to force WASM compilation and thus I tried and have the situation as in the video.
-
8 hours ago, Xenon341 said:
You can contact direct support through the ini manager, considering your problem it could be better.
Trying to do so and they are silent since I sent the sample video, hopefully they are investigating.
-
here is a sample video starting when I choose the airport to start (LXGB) and shows what it happens, you can see the initial load just took like 15 sec. the WASM folder have no files, only a works folder inside the A350 folder afterwards
-
20 minutes ago, foliainfx said:
The first load after an update/install will be WASM compiling, this will take quite a lot of time compared to other loads. While this compiles you can switch to other tabs just fine. The time varies, it's 10-15 minutes roughly on average.
If so I really think I've wasted $80 at the meantime and have no way to solve it, tried a few dozen times and the problem is that the first load after any re-installation the WASM compile time (assume it's the time where pressing start flight and the circle spins on the big map) is 100% within 30 sec and then nothing is complied, all sidestick, throttle just don't respond and no screen/battery not working at all.... tried the -900, -1000, fresh install, nothing really make it work..
-
Just out of curiousity, for the "first load could take up to 20min", does that mean even if I load to the "ready to fly" tab appears (which never exceed 30 sec in my case...) I cannot press the ready to fly button and need to say, in a spawn on runway situation wait till the engine blades turn??? also can I switch to another window to let it complie the WASM in background (e.g. watch some youtube) or need to wait the sim to load 20min at least before doing something?
-
Tried another night and even delete the whole community folder and only leaving in the ini A350 and still, nothing worked... same quick load on to runway but it just stuck with no buttons working, ironically I can use the other in game ini A320, fenix A320, FBW A380 all fine
-
1 hour ago, haza2 said:
Hello, did you follow this to clear your WASM folder?
Yes, tried at least half a dozen times... it just don't work
-
This is one of the trial, started on kai tak runway and nothing pops up
-
7 hours ago, Xenon341 said:
Yeah the WASM compilation failed.
Try deleting the a350 folder inside the WASM folder and reload a flight.It should take a few minutes to compile and let you fly.
Tried a dozen times, tried the cathay (official inimanager livery) -1000 varient with duplicated control for the stick and throttle for Fenix A320 and start flight, dead plane, external walk around points mostly usable, internal knobs can turn and button have visual clicks, clicking the GPU port externally lights up the ext power light but batteries button have no response
removed the WASM A350 folder, restart on runway in default LXGB, it loaded for <1min, get into the "Start flight" button, nothing worked, only sound, engine not spooling, cockpit door cannot open, only flaps lever and parking brake moves with the TM TCA quadrant, sidestick, rudder etc. stays still
Tried a few more times with the default ini builds livery, the -900 varient and even wait with that nothing works state for 30min and still nothing happens. So frustrated for a $81 product, paid the cash, hope for some calibration and good to go, and nothing works.....
Tried loading the default in game (I am using MS store) ini A310 and A330, A321, all worked flawlessly, just this A350 don't work at all
-
edit: I looked through discussions about WASM issues, and when I go into the WASM folder, I find that although my load time is quick even on first load in free flight, the WASM folder only generated an empty works sub folder, and nothing else inside the WASM\inibuilds-aircraft-a350 folder... any idea?
-
Hi there I've just purchased the A350, using 1.0.12, I can select the aircraft, can load into airport, walk around removed the engine cover, pitot tube cover and open the GPU door, but somehow I just cannot start the battery and no system have any response so I could try to load into the first calibration, anyone have idea????
-
Same issue here, I just bought the A350 and in FS2024 I just can't get the power on to do my initial config...
-
Hi there, have been flying on the Fenix A320 prior to the gorgeous A310, while the flight model and lack of FBW tech feels great , one drawback is that the weight and loading seems unable to be synced from simbrief and then have some refueling/ boarding time for immersion, could this be done or will be done in near future?
fs2024 ai ATC gone haywire on approach?
in Systems
Posted
Anyone have the issue? whenever I am on approach phase the co-pilot will keep request for destination change to the airport and mess up all ATC messages, it feels really strange, but if I disable the AI ATC, when I am off I will need to do Esc->enable AI ATC and then turn it back off during final, worse still in FS2024 it seems that the assistant tab isnt available on the toolbar?