These issues need fixes ASAP!

the A300 has become my favourite plane at the moment. Today, I was flying into Nantes Atlantique LFRS, RW21. This RWY has an RNAV approach. During the final phase of this flight, I was turning into Final Approach and I was flying according to the requirements given by Approach Chart. AP was active, I have activated "Land" and "Approach", so that "CAT2" was shown on the PFD.

So, I thought that RNAV would be active - but the plane did not sink below 3000ft (which was the dialed in altitude). This led me to do a manual approach, but since the weather was quite heavy (40 knots wind on the nose, heavy rain), I had to do a go around.

AP and AT were activated again and the plane was climbing to Missed Approach altitude and followed the desired route.

I wanted to do a 2nd attempt, but I was unable to insert LFRS as a destination into the FMC again. Instead, LFPG was shown as the alternate airport. So, I have manually entered the waypoints and constraints of the new STAR until the FAF. When I have reached FAF, I was unable to to make an autoland, because I got the "Discontinuity" message and AP disengaged. I was unable to tell the FMC that I wanted to land at LFRS RWY21. Any attempts to insert LFRS in the "Fight Discontinuity" line failed as well as adding "LFRS" as a new waypoint behind the FAF.

The big question is: What did I do wrong? Any help would be appreciated.  🙂

Ah, I am using Navdata from Navigraph btw...

Best regards,
Holger

Best regards – Fabian

The INI A300-600R is still broken and the developers dont seem to have any intent to fix it.

Half the switches are inverted

The panel text textures flicker in and out

FF gauge is completely broken on the PW variant

Aircraft seems to bank left or right with no reason, forcing the player or autopilot to fight a constant roll, this seems to come and go at random.

Tablet is completely useless and will not take any text input from the xbox ui keyboard.

This is among many other problems users have reported on the forums.

I am not sure how such a product can still be listed and available for sale when its in an almost completely broken state.  At this stage it seems like this aircraft is abandonware.

If anyone is considering purchasing the A300-600R(F) on the marketplace for XBOX I warn you to stay far away for now.

This thread will be the new location for all WASM Crashes relating to the Inibuilds A300-600R for Microsoft Flight Simulator 2020

Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A300.

NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo.

              All WASM Crashes existing in this thread will be removed following the release of a new update.

                    i.e. Any Crashes identified in Inibuilds A300 1.1.6 will be removed from the post following the release of 1.x.x and so forth.

Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - 

Thank you.

take off and climb and I was stuck at 220kts throughout. I had to manually control speed. It wasn’t until I deleted the speed constraints at the end of the flight plan that things returned to normal.

in hope this makes sense. Have I done something wrong or is this a possible glitch?

reading light appears on but turned to zero when starting cold and dark

emergency exit lights on when starting cold and dark

ATC voices now very distorted - see video

On the plus side, RNAV worked perfectly

https://www.xbox.com/play/media/ZkeAvzGxZS

I have been flying the 300 for a little while now and I have come across an issue: when I am setting up for the descent and landing, how do I plan for a potential shortcut during an STAR (just speed/altitude, without erasing the part you expect not to fly)?
The classic example is if you have an RNAV trombone STAR and you want to know at which altitude you have to be at the fix abeam the FAF to be on the profile to cut directly to the FAF - without cancelling the whole arrival - just in case ATC gives you a shortcut.
A practical example is LEBL RULOS2L arrival, planning the shortcut from BL440 direct to SOTIL.

On a Boeing system, you can make changes on the LEGS page without executing them and the FMC will still compute speed/altitude for each point given the new route/adjustment you are inserting.

On a newer Airbus system - which I am not really familiar with - I believe I understand you still would have a similar thing in the temporary flightplan.


How about here on the older A300?

Thank you for your help!

And for Rudder, yes I know A350 is a sensitive airplane, but recently at a typhoon landing roll, with cross wind component ~35knots, the rudder input needed to straighten the plane is just less than 1/5 the travel, that by no means feel reasonable..

I am enjoying this wonderful aircraft but i have a problem.

I did two flights:

- Dubai - Denpasar

- Denpasar - Dubai

Both flights habe fuel factor "P01", but i need to land earlier due to low fuel, what fuel factor is recommended for this airplane?

I heard about this problem on several occasions online, some have it more with the Airbus A330 RR, I didn’t have it at all in August. Since SU4 beta in 9/10 flights. Can I be sure these problems don’t exist in the ‘premium’ A350 / A340?

In MSFS2024

In the inibuilds airbus mcdu… whenever I type in an approach and Runway STAR everything seems ok in the flight plan but one waypoint is waaay off and like 3000nm elsewhere and the arrival onto the runway is jagged. sometimes it says trk79 … what kind of bug is this? it looked new / never encountered it since sim update 4

any updates on this? makes the game unplayable and up until now I didn’t have to think of the Fenix

thanks, warm regards, Claas

I am writing to express my disappointment and concerns regarding the recent release of the iniBuilds A300 for MSFS. As a dedicated user and a supporter of your products, I feel compelled to share my experiences and concerns with the hope that they will be addressed.

To begin, I must express my disappointment with the current state of the iniBuilds A300. Despite my positive experiences with the A310 in MSFS and the A300 in X-Plane, the recent release has left much to be desired. Several issues have surfaced, which were not present in the X-Plane version nor in the A310 for MSFS.

One significant issue I have encountered is the behavior of the tiller after landing. The tiller gets overridden by the smallest rudder input, resulting in the plane taxiing straight ahead. This is particularly frustrating, especially when the tiller option is enabled. Such a critical flaw affects the realism and immersion of the simulation.

Furthermore, on my second flight after the update, all displays and systems froze, leaving me with no option for recovery. This is a major concern, as system stability is paramount for a realistic flight simulation experience.

The (felt) rushed release of the iniBuilds A300 has left me highly unhappy, as I believe it falls short of the quality and standards I have come to expect from your team. I have confidence in your capabilities to rectify these issues, and I sincerely hope that the product will reach the standard I anticipated at the time of release.

However, this experience has also made me hesitant about purchasing the iniBuilds A350 immediately upon release. The apparent oversight of obvious bugs in the A300 has led to a loss of confidence in the thoroughness of the testing process. I implore you to take this feedback seriously and consider implementing improvements to prevent similar issues with future releases.

As of now, the A300 remains grounded for me until these issues are addressed. I believe that, given some time, the product will evolve into the high-quality simulation I initially expected.

I have held iniBuilds in high regard, having positive experiences with both the A310 in MSFS and the A300 in X-Plane. I trust that lessons will be learned from this situation, and I look forward to seeing the iniBuilds A300 and future products in a state that aligns with the high standards you have set in the past.

Thank you for your attention to these matters.

Throughout, I tested using the latest v1.1.6 version in MSFS 2020.

The four scenarios are:
1.  Cruise climb in P.CLB before the Top of Descent (TOD) point
2.  Cruise descent in P.DES before the TOD point
3.  Descent in P.DES at the TOD point
4.  Descent in P.DES after the TOD point

-----

To start the ball rolling, here is the first scenario:

When at cruise in P.ALT and ATC cleared to climb before the TOD point (without a Step Climb point entered in FMS):
    1.  After setting a higher altitude on the Mode Control Panel (MCP), no climb occurs.  This is OK
    2.  IMM CLB prompt appears on Flt Plan LS R1, but serves no purpose as the aircraft won't climb until the Altitude Select knob is pulled anyway.  IMM CLB prompt display without a Step Climb point may be a bug.
    3.  After pulling the Altitude Select knob, the aircraft climbs in P.CLB without selecting IMM CLB and automatically resets the Prog Page cruise alitude to the MCP higher altitude.  This is OK

Note--During climb in the real world aircraft, setting a higher altitude on the MCP automatically erases any lower altitude constraints in the FMS.  This is a "feature" of the aircraft, but many pilots consider it a bug as it is then possible to violate SID altitude restrictions when ATC cleared to climb via the SID.  The sim does not appear to model this "feature".

I set a landing altitude of 6900ft. I was held low during departure and the cabin climbed at about 500fpm to 6900ft. This is exactly right as described in the FCOM.

However, at about 20.000ft during climb, the cabin rapidly depressurized:

This is very unexpected, as according to the FCOM, it should climb to the maximum of the theoretical cabin altitude and the landing elevation and not descend again during climb. It appears that it tried to follow a delta P of 8.1 during climb?

Also, how can it depressurize with all outflow valves completely closed? In that case, I would have expected the cabin altitude to climb.

Descend is also unexpected. Again, it should descend to the higher of the theoretical cabin altitude and the landing elevation. Instead it descended way below the landing elevation at a rate of up to -1500fpm(!):

At some point it climbed again to the selected 6900ft. It does not look like the cabin pressurization controller is implemented correctly.

I don't have your aircraft in my hangar, but for French simulators, it's very useful to have translated documentation.

I found your original document on the net and did the translation work, respecting your layout. I enclose this translation (A300_MSFS_FR.pdf) for you to use as you wish.

PDF documents are not accepted on the contact page. I have sent the file to the following e-mail address: vendors@inibuilds.com and here.

I hope you find it useful and enjoyable.

A300_MSFS_FR-1.pdf

Yesterday a serious problem began to happen in my A300-600, as soon I touched the ground, the throttle levers moved to TO/GA position by itself and stayed there locked being impossible to reduce the speed in the runway, making the airplane accelarate until it goes out of the runway.

I didn't modify anything beteewn a flight to another, no updates, etc, it is simply started to happen sundelly. This problem repeated by the next three flights I made.

Is anyone facing the same problem? If yes, could you please inform the solution?

Thanks in advance for your support, I'm looking forward to reading your comments.

Giuliano Arruda

since the last Update i got a weird problem during taxi operations.

The Plane pulls to the right all the time until I hit TOGA for takeoff then it suddenly is all fine. Same during landing, as soon the nose touches down, the plane pulls to the right.

It is NOT the AXIS and/or Hardware and it only happens in the A306. The pointy thingy on the tiller points to "0".

What i did to fix it:

Unplugged the rudder pedals.

Unplugged all my controls.

Reset the plane state to cold and dark and other states.

Reset and switch on/off Maintenance

Am i missing something?

Sincerely

Pax version runs at 1.5 speed, so a 1 hour flight takes 90 minutes, its almoat like the game speed is running at 50%. Its literslly unplayable.

Landings lights switches are reversed on both freighter and pax version

RAT doesnt deploy, at all, on either

Chronometer doesnt work, on either

ATC sound is non existent, excwpt for a few broken muffled words.

I paid £50 for thos on the marketplace and its getting beyond annoying. 

A320 v2 is the same, 2 hour plus floght and the flight deck screens freeze.

C'mon INIBUILDS, £50 is a lot of monet to sone people.

As you can see, the altitude intercept point (FL070) was drawn on a path resembling the actual curved flight path instead of the straight path on the right. I wonder, if this is actually correct, since the A300 cannot draw a curved flight path.

On a related note, the path on the ND looks surprisingly bendy when performing a direct to...

Yet it only drew fuel from the left outer tank:

I remember back when we had the bug that the APU could not be shut off, I also was unable to crossfeed it from the right tanks. It looks like it is somehow hardcoded.

There was an update for the A306 for FS2020 this week (cw20) . The iniBuilds Manager doesn't show the latest version.
However, upon installing the A306 becomes unusable. The mouse doesn't work, and I see the pilot/co-pilot. The EFB is not clickable, nothing is.

How can I reverse this?

nick