I have zero issues with VNAV. I love this plane. Especially the flight dynamics

The "Falling out of the sky" problem which affects many A300 users..

 

cheers 😉

Is the TRP broken in this update? I don’t seem to be getting the thrust reducing to CLB at the thr red altitude. 
 

i will say however that taxying this is really nice now. It has a solid inertia and goes where you steer it in a nice linear way. 

Edited January 21, 20242 yr by bennyboy75

1 minute ago, bennyboy75 said:

Is the TRP broken in this update? I don’t seem to be getting the thrust reducing to CLB at the thr red altitude. 

Are you taking off in Profile mode?  That's the only time it will automatically engage. I don't use Profile for takeoffs so not sure if something changed on this latest version.

2 minutes ago, Flic1 said:

Are you taking off in Profile mode?  That's the only time it will automatically engage. I don't use Profile for takeoffs so not sure if something changed on this latest version.

Ah that might be it. I didn’t know it only worked automatically in PROF. There’s lot of subtle little differences with this bird and the newer Buses. 
 

Apparently you need to revert to a basic mode rather than PROF when not in NAV as the VNAV gets very confused. Of course in the A320 in HDG it won’t let you use managed DES or CLB at all, something they intentionally locked out in the later aircraft. 

Edited January 21, 20242 yr by bennyboy75

1 hour ago, pmplayer said:

The "Falling out of the sky" problem which affects many A300 users..

cheers 😉

I genuinely felt sorry for the 'bus at the end.  What a sad noise!     

I don't think the flight model can go so badly wrong like that, so there is something deeply wrong happening with the data in the sim at that point. 
I am wondering if it is a simconnect or other similar type issue.  Basically something that is injecting data into the sim.  I have never seen it with any other aircraft in the sim though.
Are IniBuilds at least showing signs of looking at it?

I counted -86000 fpm right before impact, that’ll ruin your day!  I wonder what the terminal velocity of a flat falling A300 would be, I’m guessing that dropping is outside the realm of real physics.

Luckily I haven’t experienced this yet.  Hopefully they can fix it soon.

Edited January 21, 20242 yr by regis9

1 hour ago, regis9 said:

I counted -86000 fpm right before impact, that’ll ruin your day!  I wonder what the terminal velocity of a flat falling A300 would be, I’m guessing that dropping is outside the realm of real physics.

Luckily I haven’t experienced this yet.  Hopefully they can fix it soon.

Let's hope for those users they find a fix, didn't experienced it myself...

Wow!  I'm not having any problems like that! (the video above) with probably about 30-40 hours on the airplane.  If that happened to me, my next flight would be with an empty Community folder (other than the A300-600).

I just did a KMIA-->MTPP and it went fine.  ILS-Z Rwy 10 and boy was it smoggy in Port-au-Prince.

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.

6 minutes 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.

I don't know if it's related or not, but this evening on my descent into MTPP the airplane was a little fast (holding 180 KIAS rather than dropping speed to my Vapp).   And similarly, when I switched to ALT HLD I didn't get a manual SPD selection.  I'm not a great master of the A300/310 overall, so I could be doing something wrong, but it seems like I typically, with the A300 or A310, at that point in the descent -- would be able to start manually selecting my speed down.  So anyway, I ended up disconnecting the autothrottle and going in manually.  I find, depending on weight, around 60% N1 is in the ballpark for a final approach.  I always disconnect A/T anyway, it's just that tonight I did it a little sooner than I might normally do it.

12 minutes ago, Benjamin J said:

Ihether 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.

I use a HC Bravo as well but have had probably about a dozen flawless or nearly flawless flights with the A300 + HC Bravo.

Some people did report a bug when one of the knobs (not sure if it was the lft knob, or the right knob) were assigned to IAS knob on the autopilot, but, I thought that bug was addressed with 1.0.3.  I do not have either knob assigned to anything so it was never an issue for me, but apparently for those who did have it assigned it cause them some problems.

10 hours ago, pmplayer said:

The "Falling out of the sky" problem which affects many A300 users..

 

cheers 😉

TAT IN ICING RANGE

Eng Ati-ice & Wings -> ON ?

10 hours ago, bobcat999 said:

I genuinely felt sorry for the 'bus at the end.  What a sad noise!     

I don't think the flight model can go so badly wrong like that, so there is something deeply wrong happening with the data in the sim at that point. 
I am wondering if it is a simconnect or other similar type issue.  Basically something that is injecting data into the sim.  I have never seen it with any other aircraft in the sim though.
Are IniBuilds at least showing signs of looking at it?

It‘s a WASM crash. WASM crashes and the systems go out, easy as that.

2 minutes ago, Fiorentoni said:

It‘s a WASM crash. WASM crashes and the systems go out, easy as that.

Could be possible they already have some WASM fixes but could be still happen..

cheers 😉