chinjh

Nothing much we can do but wait for ini to pass the fix to asobo and for asobo to push the update.

Those with low frame rates are advised to trim down the graphic settings and to temporary use 1080p plus dlss and fly at less dense airport. I get 38fps at low dense airport and running high end settings. But the moment i start out at very big airports it dips to 18-22fps and i have to start lowering my settings. Far cry from fenix which gave me 42fps at very heavy airports and even more frames with pmdg both on higher graphic settings. Am not sure how fast can asobo issue out an update for marketplace aircraft. I own the indiafoxtecho t-45c from marketplace and that aircraft update was always nearly weeks behind the non marketplace version. It was also the same sentiment for the marketplace aerosoft twin otter and crj. It was one of the reason for me to avoid buying payware aircrafts directly from marketplace. Just hope ini and asobo can expedite the update far quicker than the others and not make us wait for more than 7 days for something this critical.

WASM configuration on first start can take 10min or more on SSD hard drive may take even longer on standard HDD. If you want to check if the WASM has been configured. Launch MSFS at go to options>general settings>developers and enable developer mode. Then select the A310 and spawn at any airport of your preference. Once loaded at the developer mode toolbar on top of the window, select options and locate "display WASM debug window". Open it and locate the ini a310. If it is loaded which for most of us it did not, the dll path should have a folder path specified. For example the image below the a310 did not have dll path and the other wasm module i select for e.g GSX it had proper dll path located. Checks on Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300 only shows the work folder and nothing else. If the A310 had been configured correctly it should have a bunch of dll cache files inside of nearly 50-200mb in size.