Alexair

Just tried to do the same flight to be sure. I got your point now, the Navigraph AIRAC or the A310 (don't know which one is the culprit) is lacking the OSMOS arrival for RWY 10. Thus your decision to build the DME-ARC. There is no STAR for RWY 10 at LGTS in the FMS. Would be good to know from inibuild if it's a navigraph issue or the A310.

Nice video mate, however that has nothing to do with a circle to land. This is a DME-ARC procedure. A circle to land is a totaly different thing. A DME-ARC procedure is a circle of constant radius around a VOR-DME flown in order to get established on a final course to the runway. A circle to land is a manoeuver to land on another runway than the one you flew the approach on. It is a very short/close airport manoeuver. Furthermore, I think you don't need to build this DME-ARC on the A310 FMS (very time consuming to build) as it should be flown by the plane despite the fact that it is represented as a straight line. I did try a couple DME-ARC procedures and while the ND is displaying a straight line from the initial DME-ARC point to the final one, the plane is flying indeed a nice DME-ARC at the correct constant radius. You should give it a try. Just my 2 cents...

Aburek is right, you can tune only ILS frequencies in the ILS tuning box, all other frequencies (ie: VOR) cannot be tuned. It's normal and common on airliners.

That's what I thought... 😅😂

Yes, I agree. On those 2 videos it is obivous that the A/P is little bit lazy correcting the ILS. In the real life airliner I'm flying that can happened (even in CAT 2) when little bit away (12-15 nm DME), the A/P is struggling a bit to maintain LOC centered but that disappeared when around 10-8 nm out, at that point the A/P follow just perfectly the LOC/GS, even with some crosswind. One suggestion though, in the last video you are little bit late configuring and slowing down the plane. in real life the 1000ft RA is the limit to be stabilized and configured for landing (stabilized in LOC/GS and Vapp SPEED ) and in my SOP it trigger the "1000" call by the PNF and the "STABLE" reply by the PF. Of course if not stable it trigger the go-around. In my SOP again (depend airline of course) we have one last trigger at 500ft RA where the PNF call "500, STABLE, TARGET, SINK xxx", mean that by no lower than 500ft the PF should be on LOC, GLIDE and at the targeted Vspeed and the PNF announce the sink rate. I'm not fying the A310 in real life but the principle is more or less the same (just a question of SOP). Just my 2 cents...

Hooray ! New version 2.0.5 is working fine for me. Thanks inibuild team, you're great !! 😁

I might be wrong but I believe the A300-B2/B4, A300-600 and A310 doesn't have such message on MFD or anywhere else. Just the spoilers handle position can tell you if it's armed or not.

Oh ok, I get your point now. I didn't clearly understood the problem initialy. Thought it was during initial LOC interception. Yeah, it make sense now. Unfortunately I didn't get this problem so far, so I can't help you on this one. Give it a try maybe on those airport : KCLT, KFLL, KBOS, LFPO, LFMN, EFRO They are the one that I went and I didn't get your problem. Just to compare if you can get it done correctly on those airport or not. The only advice I can give you now. Inibuild's guys will probably help you out better than me. 😉

As JoshF said, there is a lot of aircraft in real world that cannot capture properly or even capture at all if you intercept LOC within 45° or even 30°. I flew real life on those airplane and still fly on an airliner that cannot capture LOC above 30° and sometimes we have to "cheat" a little bit when some controlers give us more than the aircraft limitations. The A310 is no exception, if you remain within 30° the interception work just fine, maybe sometimes slightly off course when in strong crosswind component but nothing as you are describing.

That doesn't help too much. Can you tried to record a video from the very beginning takeoff roll ? We need to analyse the takeoff much before that point... It look like your spawning. That look strange. Your speed is at 0 (17kt GS).

Hmm, doesn't have this issue. Did you try intercepting the LOC within a maximum of 30° angle ?

Check carefuly the key/axis binding within MSFS/FSUIPC. Also, check breaks axis sensitivity settings, I had a break issue too when I tried to modify sensitivity settings. Reset your toe break axis to default settings and give it a try. The A310 taxi very well with little or no extra power. Especially if light weight it should taxi by itself...

Well, thanks a lot mate ! That solved the problem indeed. Sorry for the trouble, I didn't know that could interfere. I've learned something today... Update seems to be totally applied now. Preparing a flight now to give it a try 😁

I have indeed some textures downloaded from the inimanager as well as outside inimanager (flightsim.to) as well as a cabin light mode from the same website. Didn't think those could interfere. I will remove all those and restart MSFS and have a look right away. Will let you know shortly. Thanks !

Same for me. Still not working...

Thanks, didn't think about this one. Did everything all over again and deleted the folder in packages folder. This time my settings disappeared, however the sound sliders are still there (can slid them but no change in sounds). Would it be possible to have the list of the updated items in order to compare and tell you if anything at all has been updated ? Right now it doesn't look like. Very strange issue...

I gave it a couple of try. Uninstall it (both A310 & A310 enhanced), restarted MSFS, did a fresh install of both and got exactly the same result. Still no update applied. And the strangest thing is that all my settings in the EFB remained the same instead of having to set everything like the first time. Isn't there a file or a config somewhere that might give that result/problem ?

ok will give it a try and will let you know the result. Thanks !

Absolutely. However they look like to be inoperent though.

When I started MSFS yesterday, it run an update including an update for the A310 with description of the A310 update (removing sound sliders, implementing METAR and auto-weather filling in the EFB, and bunch of other things on systems, FMS, etc... (I forgot the details but the list was long). None of those update/bug correction had been applied to my A310 though...

Well, I don't know why I had an update installed yesterday then. Anyway, none of the update description has been applied to my A310.

Hi y'all, Just fired up MSFS and saw that there is an update including a major update of the A310. I was so happy, however it didn't last long. In the sim, the EFB still display version 1.1.6, the one that came couple of weeks ago. And I don't see any change in the sim, for exemple there is still the sound volume sliders, no METAR and the other update, etc. I've checked the folders in content manager and the regular A310 is 1.1.6 and the enhanced is 1.1.7 I've tried both with stock liveries and add-on liveries with the same result. Could you be kind to tell me what's wrong?

Look like they working on it and will provide a new version of inimanager. Let's be patient, just a matter of time now... 😉

Thanks for your reply, OK, I understand. However I think you should consider 2 options: 1) Re-implementing sound sliders in the EFB. OR 2) Decrease the global sounds of the A310 (by around 25-30 % I think). Cheers,

Hi guys, Look like the A310 has been updated in my MSFS (don't have beta). And since then, I cannot longer change sounds parameter within the EFB. Is it normal ? If yes, then I'm disappointed as the A310 sounds (all sounds) are 33% louder than the rest of all aircraft I have. All my sounds are 100% in the sim and I setup my sound at 30% in my Acer monitor. This is giving me a perfect volume for all aircraft except the A310 which I have to put the sound down at least at 20% in my monitor, thus all sounds (environment, FsRealistic, GSX, radio, IVAO, etc..) are way too low. Cheers,