11 hours ago, bobcat999 said:

 

Are IniBuilds at least showing signs of looking at it?

At around after update 1.01 inibuild says they can not replicate this issue but now after update 1.0.3 i think they have to move in to investigating what is goeing on with this issue..

More und more A300 user experience this bug and are of course very dissatisfied and frustrated with this problem .

But I think inibuild must and will now devote more time to this matter, hopefully..

The bug is somehow difficult to pin down and there are no clues to pinpoint it, it just comes like that, randomly, somewhere and at some point. For me it doesn't come on every flight, but it definitely comes once on about three flights.

So lets hope inibuild will investigating this issue and find what causes this problem and i think the release of this plane was rushed out to hard ( Christmas time) and hit us with a lot of Bugs.

So some are fixed but this one is a gamebraker issue and makes this Bird unflyable because every flight it happens is a waste of time and who has time at all ?

Don't understand me wrong, i love that plane to fly and have a lot of fun but with this bug it is a no go !!

cheers 😉

Edited January 22, 20242 yr by pmplayer

8 hours ago, Benjamin J said:

I just flew 1.0.3 - don't think I had any of the issues people mentioned, but I had something weird going on with the auto throttle. I had PROF and NAV activated before takeoff, I activate TOGA as usual, and both activate as expected upon liftoff, and all was well until I got to the point of descent. Because I tend to fly with default ATC (yes, yes I do. Not the point of this post) and their clearances don't follow VNAV calculations, I tend to switch to Alt Hold and select a speed manually, so I can then follow their guidance by V/S. Normally I've had no issues with this, but this time when I selected ALT HLD mode, I couldn't get SPD to select manually - upon pushing the SPD knob, it would show a selectable value but illuminate PRE-SET. I don't remember ever seeing this illuminate to be honest... I saw in the change lists that there have been some changes to the logic of this over different versions but I've never seen an issue like this pop up. Since I couldn't select the speed manually, I stayed with the commanded 280kts pretty much all the way down, until I finally deactivated auto throttle altogether and set thrust manually. Another weird thing here is that it somehow managed to stick with the commanded speed even at pretty steep descent rates, without putting the engines into idle. No idea what was going on here. I assume I'm doing something wrong here but I have no idea what it might be. I don't think I did anything different from usual, but it sort of ruined the flight...

I'm not sure if something happened in the update or whether this has something to do with the Brave quadrant I just bought. Perhaps there is some assignment there that I need to deactivate?

Any pointers would be appreciated.

Got the same issue lately, without any change in my controller setup (Warthog throttle). Have to turn AT off and manually land as well. Good practice in a way, but a bit irritating.

6 hours ago, romoni said:

TAT IN ICING RANGE

Eng Ati-ice & Wings -> ON ?

Nah it went down way too fast for that, especially considering that it never displayed any stall characteristics. It looked like it slewed its way down to the ground. Whatever bug this is, triggers something that causes the flight model to behave weirdly from what I can see.

11 hours ago, Benjamin J said:

upon pushing the SPD knob, it would show a selectable value but illuminate PRE-SET.

Make sure you have the Capt. side DH window turned off.  The FO side can stay on if you want...seems like a bug in 1.03....

11 hours ago, Benjamin J said:

upon pushing the SPD knob, it would show a selectable value but illuminate PRE-SET.

If you hover your mouse over the center of the speed knob, you will either see an “up” arrow or a “down” arrow, (depending on what part of the knob the mouse pointer is touching).

I don’t recall which arrow is which, but one of them selects “pre set” mode, and the other enables speed set mode when pressed.

That speed bug is with the DH window open on the captain‘s side. Just close the window / remove the number there and it should work again.

14 hours ago, Benjamin J said:

I just flew 1.0.3 - don't think I had any of the issues people mentioned, but I had something weird going on with the auto throttle. I had PROF and NAV activated before takeoff, I activate TOGA as usual, and both activate as expected upon liftoff, and all was well until I got to the point of descent. Because I tend to fly with default ATC (yes, yes I do. Not the point of this post) and their clearances don't follow VNAV calculations, I tend to switch to Alt Hold and select a speed manually, so I can then follow their guidance by V/S. Normally I've had no issues with this, but this time when I selected ALT HLD mode, I couldn't get SPD to select manually - upon pushing the SPD knob, it would show a selectable value but illuminate PRE-SET. I don't remember ever seeing this illuminate to be honest... I saw in the change lists that there have been some changes to the logic of this over different versions but I've never seen an issue like this pop up. Since I couldn't select the speed manually, I stayed with the commanded 280kts pretty much all the way down, until I finally deactivated auto throttle altogether and set thrust manually. Another weird thing here is that it somehow managed to stick with the commanded speed even at pretty steep descent rates, without putting the engines into idle. No idea what was going on here. I assume I'm doing something wrong here but I have no idea what it might be. I don't think I did anything different from usual, but it sort of ruined the flight...

I'm not sure if something happened in the update or whether this has something to do with the Brave quadrant I just bought. Perhaps there is some assignment there that I need to deactivate?

Any pointers would be appreciated.

Well they fixed a few but we get a few back and new ones...

Hope they will solve those in the NEXT

- VNAV buggy (was far better in 1.02 for me)
- TACT mode
- Rudder sensitivity with auto disconnect tiller function buggy (was fine in 1.0.1) the auto disconnect disabling not saving have to do it manual now (have a dedicate tiller)
- Throttle calibration logic
- ECAM/SGU logic
- Mach/speed switching should occur automatically at 26000 feet
- Missing integral night lightning
- Overhead disarm light emer exit missing
- Small things which are in the RW aircraft just different for example the engine start ecam display and ecam system engine page
- No compatibility with Navigraph for MSFS but using the default MSFS airac

There will be a few more I guess, but those I came across with the freighter version

Major one for some is called "falling out of the skies"

Love this plane and great fun only hope they don't have the trend to go worse with every update...

Edited January 22, 20242 yr by virtualstuff

37 minutes ago, virtualstuff said:

No compatibility with Navigraph for MSFS but using the default MSFS airac

It will use the Navigraph data you put in your community folder

1 minute ago, Tuskin38 said:

It will use the Navigraph data you put in your community folder

Yes but it's not fully compatible and missing stars and sids then compared to the default MSFS airac...

Edited January 22, 20242 yr by virtualstuff

1 hour ago, virtualstuff said:

- VNAV buggy (was far better in 1.02 for me)
- TACT mode
- Rudder sensitivity with auto disconnect tiller function buggy (was fine in 1.0.1) the auto disconnect disabling not saving have to do it manual now (have a dedicate tiller)
- Throttle calibration logic
- ECAM/SGU logic
- Mach/speed switching should occur automatically at 26000 feet
- Missing integral night lightning
- Overhead disarm light emer exit missing
- Small things which are in the RW aircraft just different for example the engine start ecam display and ecam system engine page
- No compatibility with Navigraph for MSFS but using the default MSFS airac

There was barely any change between 1.02 and 1.03 regarding VNAV. Fact is, it depends a lot on the actual STAR and restrictions and other factors: I've had perfect flights and flights where it wasn't even able to hit an a single AT restriction, no matter the patch version.

The mach/speed switching does work, not sure what you mean?

The navdata and the airac is actually from Navigraph (if installed); it's just that the MSFS navdata format is faulty (the format, not the actual navdata). They have to code their own navdata format (like the PMDG or Fenix or anyone else basically), which for some reason they didn't.

The only issue I am having with this AC is I get 80% CTD's when I load the the plane. It happens with various liveries and various airports, can't seem to pin it down. I believe others have the same issue. 

1 hour ago, Fiorentoni said:

There was barely any change between 1.02 and 1.03 regarding VNAV. Fact is, it depends a lot on the actual STAR and restrictions and other factors: I've had perfect flights and flights where it wasn't even able to hit an a single AT restriction, no matter the patch version.

The mach/speed switching does work, not sure what you mean?

The navdata and the airac is actually from Navigraph (if installed); it's just that the MSFS navdata format is faulty (the format, not the actual navdata). They have to code their own navdata format (like the PMDG or Fenix or anyone else basically), which for some reason they didn't.

As for VNAV I don't agree with you on 1.02 and 1.03 despite the facts you mentioned

When using Navigraph you will end up with some discrepancies regarding sids or stars or even runways available in the FMS/FMC due to incompatibility. Nothing wrong with Navigraph but like you said it's how they access the data...
They are now using the default MSFS airac in their logic (I'm using Navigraph for more then 18 years, have a basic understanding now how it works lol)
(Maybe due to all the work they have done already for MSFS, A310 and upcoming A320 then it makes sense)
As for speed/mach pretty simple at 26000 feet the A300-600 switches automatically from speed to mach at least that is airbus telling us 😉 it didn't in V1.03 a few times as before.

Edited January 22, 20242 yr by virtualstuff

8 minutes ago, lehbird said:

The only issue I am having with this AC is I get 80% CTD's when I load the the plane. It happens with various liveries and various airports, can't seem to pin it down. I believe others have the same issue. 

Try to first load a MSFS plane than load the A300 again, from inibuilds forum this should help for this issue, of course only to be seen as a workaround..

cheers 😉

2 minutes ago, pmplayer said:

Try to first load a MSFS plane than load the A300 again, from inibuilds forum this should help for this issue, of course only to be seen as a workaround..

cheers 😉

Thinking I tried that, but could be wrong....will give it another go!! Thanks!! 

2 hours ago, lehbird said:

Thinking I tried that, but could be wrong....will give it another go!! Thanks!! 

As a last resort you could uninstall the bus and delete the following folder AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a300-600

Then reboot after a boot reinstall the bus (this way you force MSFS to recompile the aircraft)

When you do this you have to setup everything new related to the aircraft settings plus custom camera views.

Maybe you tried this already but thought just sharing...