[Emergency slides are deployed after each deboarding]

11 hours ago, Crabby said:

Doors are not being disarmed before opening them.  Hit the disarm all doors button.  

Disarm function only works when recognition light is switched off. I think the devs need to allow the the disarm door button to work once parking brake is set instead. Cause i have some sceneries where the moment u dock in the jetways starts connecting automatically without even requesting.

[Logo lights missing]

Not sure for the A300 but for the A320 and up to the A380. Once you retracted the landing gear on take off the logo lights will be turned off automatically.

On descent even turning it on by the switches the tail logo lights would only be turned on if you selected flaps config 2 onwards even config 1 wont trigger it.

[Systems and displays freezing]

6 hours ago, pmplayer said:

And on the last yards to the runway the LOC pointer move away to the right and the plane try to follow this pointer and steers away, you have to shut down fast the AP and do a hand fly landing, hopefully they look at this problem..

cheers 😉

I just tried this out Hong Kong (Chek Lap Kok) Intl. Airport (VHHH) NavData for Three-runway System

It sort of fix most of the issues with missing runways of 07L and 25R and waypoints. But note some of the Loc pointers are still heavily missplaced and you would have to manually plot them or delete them to avoid jamming the fmc. I noticed my FMC jammed cause it was drawing up a lot of incoherent lnav directions whenever selecting any arrivals of 07R and 25L.

[Systems and displays freezing]

VHHH still a no go. Selecting STAR arrivals will jam the FMC. Odd thing only 07R, 25L are available.

[Nose down look]

8 hours ago, jstnj said:

Any more recent acknowledgements of this?

I won't say "this is an easy fix" because I don't know what other effects this has on things like the flight model...but if its working in the 310 I'd think a similar "fix" can be done for the 300 🙏

I did 2 long sectors and 1 very short 1 so far no issues apart from the annoying very minor bouncing compression on the nose gear when decelerating from 3knots to 0 knots with brake pedal applied.

I am getting a bit frustrated cause this was logged for 3 months without any patch issued to address it and i ended up having to eyeball a self DIY fix on the contact points.

[Nose down look]

Some further checks with adjusting the nose gear contact points.

1) Abrupt deceleration causes wonky bouncing.

2)low speed around 3knots to 0 knots causes the same wonky bounce.

Currently adjusted the points to minimize the disturbances but it is still around
 

Quote

point.0 = 1, 46.700022, 0, -15.574176, 2000, 0, 1.68, 65, 0.96, 1.151, 0.86, 22, 22, 0, 0, 0, 2

Seems to be the only go to while we wait for the devs to push a proper update.

[Nose down look]

Looks okay now. Still not nose down enough but its a compromise.

[Nose down look]

Okay looks like i've found a little niche area without compromising too much. Also just did 2 circuits does not seem to have any CTD causing stuff. 

What to do
Locate the flight_model.cfg file at
Community\inibuilds-aircraft-a300-600\SimObjects\Airplanes
Inside this directory there are 4 variants of the A300-600 each needing some changes to their respective cfg.

• Open flight_model.cfg as notepad for each aircraft
• Ammend the line under [CONTACT POINTS] Replace the following below.
  point.0 = 1, 46.700022, 0, -15.574176, 2000, 0, 1.68, 65, 1.0, 1.15, 0.85, 22, 22, 0, 0, 0, 2
• Save what you have edited.

Note it may still look off visually but at least the nosegear does not seem to sink so far into the ground now.

[Nose down look]

Some interesting stuff. Played around the flight_model.cfg namely [CONTACT_POINTS] under

point.0 = 1, 46.700022, 0, -15.574176, 2000, 0, 1.68, 65, 0.328, 2, 0.33, 22, 22, 0, 0, 0, 2

The 2 figures that has highlighted bold seems to effect the nosegear relative to the ground but unfortunately not for dampening nor compression. A high value used "1.23" and "1.25" than the bold default values results in lower nose gear which by right makes the nose down look there but this results in the nose gear sinking further into the ground. A lower level results in the nose gear gradually rising above the ground to a point it floats.

Overall there just does not seem to be any compression with whatever weights added that effects the nosegear compression no matter what contact points have been amended. The default modeling of the nosegear itself appears to be tall in default.

Another fishy area that i am suspecting is under
static_pitch =-0.2

[Nose down look]

9 hours ago, cu206wrc said:

On the ini A310 it is correct !

Tried to take a look at the data values especially for contact points from the A310 but it being an official msfs aircraft means the flight_model.cfg file is encrypted by Asobo!

[Sound Mixing]

Still barely hear the alttiude callout during approach tried various different volume mix to no avail.

[Version 1.1.1.: Rudder (tiller) steering not working anymore]

When u make rudder inputs does the Nose wheel tiller circled here turn as well?

[Version 1.1.1.: Rudder (tiller) steering not working anymore]

I believe they've incorporated some part of the ground physics with the latest update. Confirm you only do 90 degree turns at under 9knots and not more? cause it is recommended not to do sharp turns at higher speeds.

[A300/310 very very slow throttle response: throttle spooling up very slow]

Those old widebodies tend to take quite a long time spool up the engines thats a real fact. And it still somewhat the same for current modern widebodies.

[Nose down look]

11 hours ago, Tripdog87 said:

It makes me wonder if it’s a contact point thing like in the fs9/p3d days? I definitely see what you are saying.

On
Community\inibuilds-aircraft-a300-600\SimObjects\Airplanes\inibuilds-aircraft-a306r
and
\Community\inibuilds-aircraft-a300-600\SimObjects\Airplanes\inibuilds-aircraft-a306f

Both having a a file called flight_model.cfg inside there's a field called contact points i believe this is where certain parameters if adjusted correctly can effect certain parts of the plane visually. But note i do not know which points needs adjusting or even if correctly adjusting the correct points would effect. Cause currently the default nose gear itself has some modeling issue.

MSFS SDK WHEELS AND CONTACT POINTS

MSFS SDK flight_model.cfg - [CONTACT POINTS]

[Nose down look]

1 hour ago, Tripdog87 said:

This one is tough while I do see what you folks mean in some of these photos where you can say, "yeah there is definitely a nose down" but some of these photos I have uploaded like the UPS and DHL it looks as though the fuselage is flush. I am torn...

If i am not mistaken when the plane is on acceleration and deceleration at higher speeds the tendency for the nose gear to lift(floating look but wheels is still on the ground with lack of compression on the gear) is always around. The A330 is also somewhat affected by that. It is also present on the 738.
 

 

For now i am hoping the devs could at least take a look at the nose gear modeling cause there is definitely something over there that is affecting the default stance of the aircraft on the ground. I am not sure if tinkering with the flight_model.cfg's contact point would visually bluff viewers with it as i dun really know how to edit this part. Unless some other people in the forum are more willing to play around with it.

[Nose down look]

9 hours ago, cu206wrc said:

https://www.jetphotos.com/photo/227143

 

found a good Picture 

Thanks thats a really good closeup photo from a spotter. Did a small comparison yes there is something that needs to be changed on the nose gear.

[Nose down look]

I know this problem has been reported in a few closed threads before Nose up to high and on discord. But the A300 currently has this issue where it does not have the iconic nose down compression look like the A330 has.

Currently i have tried moving the weights to the nose which causes bad CG but has resulted in not much compresson to the nose gear itself. So i guess this is much tied to a modelling. issue. Also this bug is not present on the xplane release of this product.

Is there any timeline or promise or a small hint that this will be addressed in the future?  This is probably the only remaining visual gripe left with this aircraft at the moment.

[Cant use reverse thrust keyboard bind]

Latest update has fixed the issue mods can close this thread now.

[Cant use reverse thrust keyboard bind]

What i've noticed unplugging the logitech control and using the keyboard input with f1, f2, f3, f4 does nothing to the engine throttle. Seems only the side stick throttle slider is the one having inputs to the throttle but i cant use reverse thrust as this slider has no proper physical detent for it.

Tested PMDG and FENIX both have their reverse thrust working on f2 commands with all relevant throttle related keyboard commands.

[Door slide behavior with many sceneries]

It seems to be gsx related especially once you've prompted the gate you wanna park at in advance. Some sceneries especially with some of the payware i own will have the jetway start docking in whenever i come to a complete stop at the gate without giving me time to shutdown the engines and headover to the EFB for disarm all the doors.

 

 

[Cant use reverse thrust keyboard bind]

Ever since the Dune update or v1.0.7 the keyboard command on f2 for "TOGGLE THROTTLE REVERSE THRUST" does not work while the alternative of "HOLD THROTTLE REVERSE THRUST" on the other hand is not proper as it goes all in on max reverse and the button has to be hold consistently. Any workaround for this? Currently only using a simple logitech sidestick with reverse on axis turned off on the EFB.

[V.103 Callout sounds]

9 hours ago, Nico - Gumby said:

Minimum callout is definitely there, can you confirm that it is not present?

I got the minimums callout but that is after muting so many other audio parameters from the efb. The altitude callout volume can be heard even though its low but the the minimums callout volume is on a level that i often thought its not there or not working when actually the volume level is so low that it is difficult to hear it.

[No Safe TO Calculation]

6 hours ago, donkeys said:

I noticed if the winds are greater than 12 knots or so I cannot get a TO calculation on the EFB. Surely the A300 can handle more than a 12 knot crosswind. 

Some of the airlines i've seen would not authorise a take off if the crosswind is above 20knots and for direct tailwind component it cannot be more than 10knots. No limit for direct headwind though.

But overall all of this it should not affect efb computation for the vspeeds and TORA especially if the runway is greater than 3000meters.

[Door slide behavior with many sceneries]

I know the standard op is to ensure the engines are off, parking brakes set, beacon light off before disarming all doors. But I've encountered issues where the moment i taxied to the gate and have my manual brakes still tapped in for the plane to stop, some sceneries with their jetway would start attaching itself to my L1 door before i could even do the shutdown sequence which resulted in the emergency slides deploying.

Perhaps its better to allow an option to temporary disable the door arming behavior for some of us via the efb. Also one additional suggestion to have a single button *disarm all doors* instead of having to go through one door at a time on the EFB.