iniBuilds A310 first impressions

[JSmith2112 317]

My weather radar display is just blank. Maybe it's because the WASM compilation didn't complete properly?

[JSmith2112 317]

16 minutes ago, virtuali said:

That .DLL is located in the "LocalState" sub folder of the MSFS profile, and it's not supplied with the airplane

Umberto, is this something that can be fixed by the user if they had Fast WASM compilation on?

[james_d 21]

I thankfully seem to have ok frames. Probably similar to Fenix. 
 

However, having some issues with the TCA throttles. Should I have them on throttle 1 & 2 or the 0 to 100% axis? Will give it another go in a bit. 
 

Also a few of the liveries won’t install in inimanager. I’m sure they’ll get round to fixing these few issues. 

[michael8 22]

I dont get what wrong with the fps perfomance on the cpu with this aircraft i get half of fps that get with the fenix a320.  and my cpu cores are all at 50% when with other aircrafts i can see core 1 around  over 80-90%

[KERNEL32 496]

3 minutes ago, michael8 said:

I dont get what wrong with the fps perfomance on the cpu with this aircraft i get half of fps that get with the fenix a320.  and my cpu cores are all at 50% when with other aircrafts i can see core 1 around  over 80-90%

Do you have your gauge display update to the highest setting? Try one setting lower maybe?

[rka 916]

I just checked, Fast WASM Compilation is off on my system. Still I'm getting the issue.

[michael8 22]

1 minute ago, KERNEL32 said:

Do you have your gauge display update to the highest setting? Try one setting lower maybe?

you mean glass cockpit refresh rate? i always use the low one

[MrRoper 27]

Its an issue with the WASM compilation. Plenty of users including me are having the same issue

[pmplayer 9,379]

At the moment i am doeing a flight and up at 38000 feet i get about 40 fps and that is normal for my settings ( i am on 4K ) so OK.

On airports ( depends on how big they are ) i get 19-27 fps and thats also normal for my settings so for me this seems to be OK.

To bad that the pop up from the 2D panel are also ( like PMDG ) not updating from the outside view from the plane..🤔

It's finally time to fix this issue, it's getting on my nerves that it's still happening after such a long time, even though they all ( Asobo ect., ect. ) know it.

 

cheers 😉

 

Edited November 12, 2022 by pmplayer

[Zangoose 1,631]

For those who may not be in the discord and are seeing some performance/FPS issues with the A310: 

 

Quote

We have identified an issue that somehow some users WASM is not compiling and is in DEBUG. This is not intended, and we have sent a message to MS/Asobo. Some people have found some workarounds, but this is still under investigation. Like the PMDG, the A310 is a WASM aircraft, so should take at least some time to load in. If you are loading in <60 seconds something has gone wrong and could explain your poor FPS. This is an ongoing investigation, so we request your patience, and be sure that we will get this resolved for you as soon as we can.

 

[lwt1971 7,342]

I guess those of you who loaded up fast and still getting good FPS are in for a pleasant surprise when this is fixed and proper WASM compilation to non-debug binaries happens :)
 

[Aaron555 52]

3 minutes ago, Zangoose said:

For those who may not be in the discord and are seeing some performance/FPS issues with the A310: 

 

 

What are those workarounds? 

I have extremely bad performance in this plane. Always Main Thread limited @ 25 FPS, even in the air.  

[Zangoose 1,631]

1 minute ago, Aaron555 said:

What are those workarounds? 

I have extremely bad performance in this plane. Always Main Thread limited @ 25 FPS, even in the air.  

You'll be best reading the discord thread on the matter and see what people are trying. I've tried a number of things on my end but hasn't been a success for myself. 

[MDFlier 2,031]

1 hour ago, JSmith2112 said:

Umberto, is this something that can be fixed by the user if they had Fast WASM compilation on?

Delete the a310 in Content Manager and then re-install it. It should recompile next start.

[Gilandred 690]

12 minutes ago, MDFlier said:

Delete the a310 in Content Manager and then re-install it. It should recompile next start.

Tried it, and doesn’t work work.  I have yet to see anyone post their wasm debug screen with a populated dll link path.  I suspect those with acceptable fps don’t have proper files compiled either, and will get even better performance once the issue is resolved.