chinjh

I've noticed the ini team have been porting over liveries to the inimanager by batches but it takes time. Meanwhile at flightsim dot to the uploads have been slow but again the a300 has not even been released for 2 weeks so waiting for your favorite paint requires patience i guess. Since the lufthansa freighter is already on the xplane i bet it would be ported over.

The pax variant is a little fussy in a sense after shutting down the engines head to the efb ground equip section and make sure to disarm all the doors before calling in any jetways or stairs. If not the slides will activate. Disarming the doors, each door will show a green icon instead of red if am not mistake.

I pretty much only changed the Empty Weight KG to 80658 and then changing the Max Zero Fuel Weight KG to 138810 i am not sure if this is correct though. As for MTOW likely to be retained as there is no increase for the freighters just more payload. Though ini is likely to upload an update on the simbrief profile tomorrow.

Autobrake button light not illuminating on my end even pressing them after gears down. Heard minimums callout for the first time but its very faint volume.

Their discord mods mention they are expecting a patch earliest this end of the week if no problem arises. Though how many list of bugs they can fix i dont think they can cover all cause its just too short of a timespan.

I've been trying to find a repaint request thread but cant seem to find one but i'll just post it under here. I've noticed for the xplane 12 there's a lot of repaints for the a300-600 but are not listed on the msfs any plans if they would be converted? Also if any repainters are out there are and interested, Im looking for any A300 liveries for the Singapore Airlines, China Airlines and Malaysia Airlines.

Overhead panel make sure the galley button light is not illuminated with white 'SHED' and you're on ground power/apu. Head to efb tablet and click ground equipment the cabin light intensity setting should be there. But note there is a bug right now where looking from the outside the cabin lights does not seem to shine through out of the passengers window.

Both the a310 and a300 dont do well with sim pauses or sim time acceleration. One of the temporary workaround is to disable to autopilot before pausing.

There's the A310 its free on marketplace. Try it out it should be somewhat comparable. Then from there it should give you the impression on the more detailed A300600

Your CPU might be a bottleneck here. I am using the 9th gen i7 and RTX 2070S and 32GB 3666MHZ and frames are not really that high for this plane when compared to other paywares.

Hi there were a bunch of updates to some of the liveries yesterday. However it seems to have broke one specific livery namely the Maskargo TF-ELW one. It now has pink door textures. Also it seems i cant find the previous version of this repaint. Hopefully the team can push an update for this.

Just noticed the transition from flaps 15/20 to 20/40 is too slow. ^ From the above it only took 5 seconds for the flaps to be deployed to 20/40. Where as for the sim it took 34 seconds. Is it the possibility that there is a bit of limitation applied with the flap look and transition speed for msfs? Microsoft Flight Simulator 2023.12.31 - 21.51.34.03.mp4

I got 310KIAS offered but this is with using cost index 0 but at a risk of putting your econ cruise below the green dot speed. Though i am not liking the idea of having to change the cost index for climb, cruise and descent. Best outcome for climb once constrains are off is to use lvl chg.

I had to increase the cost index of 60 or higher to avoid the Econ crz from giving a speed value below the green dot speed.

I noticed the plane has a tendency to dislike cost index lower than 60 especially if heavy as it would put the cruise speed below the green dot. Below cost index 60 the plane would generally like to put the speeds at mach 0.79 or lower. Currently am always using cost index 60-80 and the P.SPD and P.ALT would be alright .

Just wondering if anyone can verify that the green dot speed for cruise level is correct. I am assuming from my point of view that is a bit too high by near 10-15knots indicated though i may be wrong. Hope anyone can check it out.

Just an update. Was tickering around with the performance issue. Upgraded my Ram from 3200mhz 16GB to 3600mhz 32GB and noticed my ram speeds was clocked at 2666mhz. Found out that my BIOS all this while had been underclocking my 3200mhz ram to 2666mhz even with intel XMP set to on. Had to update my BIOS manually, as the UEFI over the wired ethernet kept informing that the bios is already the latest when it was not. Updating the firmware enabled intel XMP to clock the ram speeds correctly. The upgrade to 3600mhz + 32GB seems to give the a310 a significant fps boost. As my previous post at dense airport the fps was 30 for the a310. The ram upgrade seems to push the a310 to 40fps average at dense airport now. Then PMDG and fenix also gained more frames but it was significant as compared to the a310. So anyone out there might want to check the ram speeds over the BIOS to see if intel XMP or AMD DOCP is working as intended.

Believe INI has only went through 1 round of performance optimization so far even though it sounded there was like 2-3 different beta release before public release. Generally this update gave me more fps but its only by about 5fps on ground and 10 fps during cruise while other paywares like PMDG and Fenix are about 10-15fps higher. We will have to wait again for their next beta release to see if any more optimization is rolled out to beta users. Regarding the empty package folder INI has mention on discord that asobo WASM encryption does not require any leftover dll files. Even with RTX2070S i have resorted to flying this aircraft offline without traffic and on 1080p high end settings. Going for 4k ultra with multiplayer turned on is gonna put the fps within the 20s for me. So take note.

Have you tried on an empty community folder and compare all 3.

I have tried starting the a310 with an empty Community folder no gsx no payware airport no other aircrafts yes more fps of 41fps on ground. Switching between standard and enhance a310 and there is no fps difference. Tried the pmdg with the same naked community folder and its nearly 60fps on ground for that aircraft lol and fenix at about 53fps. Populating the community folder with many stuff is just a 5-8fps penalty for PMDG AND FENIX at my end. Other aircrafts with populated community folder would still command higher frame rates by 10-15fps average than the a310.

PC specs? Do not quote rtx 3000 series or more lol. People with less than gen 10 intel i7s and rtx2000s can still get more frames on other payware aircrafts.

Beta Update 1.29.30.0 Some updates for the a310 but fps optimization still not up to standard. Comparison between the a310, fenix a320 and pmdg 737-800 A310 still on the low 30fps with occasional frames dopping to below 30fps. The rest are at 40fps. This is on high settings 1080p. It is also noted the CPU and GPU utilization of the a310 is still very low. Gpu usage never at 70% and the cpu on 30%. The fenix would be at 60% cpu and 70% on the gpu whereas the pmdg would be on 30% cpu but 80% on the gpu. Might explain why the a310 is on the low fps side as resource hardware utilization is still low.

So far everything is up to speculation. But since the fps disparity between other aircraft have been significant. The difference of nearly 10-20fps lower for me than the rest i would say there is definitely poor optimization involve. Plus i feel this aircraft does not run well on 4k. The beta update only brings minor fixes with the wasm encryption fixed but still no dll cache generated. For most users this will still be an issue for mid to high spec pc users to at least maintain consistent 30fps on peak scenery. Ini claims the wasm was not the issue but so far fps is still tanking. It has only been 1 week since release with 1 beta update so far which can be considered quick, so it seem we have to be patient again.

Reporting fps with MSFS Beta Update (1.29.29.0) with the a310. FPS is still on the low end with lowest fps at 18 on my last approach at a big airport while spawning at low end airport is at 38fps, at cruise level it is also at 38fps it seems to be locking the fps at 38 not more on my end not sure why. Though slight improvement has been noted in regards to camera panning. Previously when i pan the camera there is moderate drop in fps, now it is more consistent. Overall still 15fps away from Fenix and 20fps from the PMDG. Package folder still empty with only work folder being present. Technically the beta update has yet to address the WASM compilation issue.

So far nothing. But the ini devs are in the midst of rectifying. Only thing that worries me is how fast asobo would push the update. Here's where one may see it being preferable to have the aircraft installed out of asobo encryption whereby updates can be quicker. But you cannot deny ini was good by handing over the a310 to asobo and enabling it to be free for all simmers. Now we just have to be patient.