Jump to content

Alexair

Member
  • Posts

    187
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Alexair

  1. Hmm, doesn't have this issue. Did you try intercepting the LOC within a maximum of 30° angle ?
  2. 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...
  3. 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 😁
  4. 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 !
  5. 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...
  6. 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 ?
  7. ok will give it a try and will let you know the result. Thanks !
  8. Absolutely. However they look like to be inoperent though.
  9. 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...
  10. 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.
  11. 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?
  12. Look like they working on it and will provide a new version of inimanager. Let's be patient, just a matter of time now... 😉
  13. 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,
  14. 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,
  15. I have exactly the same issue. Desinstall (including deleting both folders) followed by a clean install didn't solve the problem...
  16. Yep, it's a known bug. They are working on it.
  17. Did uninstall the inimanager and did a clean reinstall. Unfortunately still the same blank screen...
  18. I did try several reboot with no success. Will try the reinstall then. Will let you know. Thanks.
  19. Hi folks, Just got a new problem with inibuild's inimanager. The Pilot Support tab just went blank. Was working perfectly until now. Everything else seems to be working just fine. Any help will be very much appreciated. Here is a screenshot:
  20. Well, everybody is able to start those engines but you. Something telling me that it's not the A310 the problem. Again, verify the starting procedure, this is not an A320 neither a 737. Also, check your joystick/yoke//throttle assignments for mixture, throttle etc. Any binding that might cause this issue. SOme people had various issues because of that. I have Logitech HOTAS X56 and Honeycomb Alpha/Bravo, both are fine with the A310. I have a low end PC and it is starting just fine, either with APU or the ASU.
  21. Did you modify the SENSITIVITY option in MSFS? I tried that and it resulted the same problem. I had to modify the sensitivity again to match the A310 pitch trim data.
  22. I believe they are working on all the lighting.
  23. Alexair

    throttles

    Super! bon vols !😉
×
×
  • Create New...