!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About aerostar

  • Rank
    Ramp Agent
  1. After looking at it more ... if when the A320 radios are set to a Vatsim frequency by the Flightbag Radio input panel or by clicking on the controllers freq from the 'Controller list' as shown - Then if I go back to the Aircraft radio and the frequencies are out of step from ---.-00 ---.-25 ---.-50 ---.-75 then you could sort the code in the radio to step back into line with those steps at the next click of the rotary inner knob. That would probably solve the problem. e.g. - If aircraft radio reads 126.820 and I turn the inner rotary knob to 126.925 then it would come back into sync and displays that and not 126.920 as is happening now.
  2. I had the misfortune, while on the ' Vatsim new Codec stress test Event ' recently when I was calling the controller on the wrong channel, he was very busy and there were a lot of pilots on frequency. It was embarrassing. I had entered the last controller's handoff COM frequency into the Aivlasoft numeric input panel as shown... but the last digit was changed to a '0' instead of a '5' For example - 119.875 was changed to 119.870 in the aircraft radio. I think you have to make the frequency steps in 8.33 Khz spacing. I believe 8.33 Khz spacing is now adopted by the industry and Vatsim uses this channel spacing, mimicking real world. It was hard to understand what had happened at first then to try and resync the aircraft radio. Are there any plans regarding this ? PS- Maybe it's when the calculations are rounding up... maybe if you calculate to 4 decimal places and only display the 3 decimal places . Just had a thought... if the freq now has an extra 2 decimal places (8.33 Khz) then a full freq could look like 119.87533 Mhz maybe, therefore you should calculate to 5 decimal places or 6 ? EDIT:- Simconnect shows capability for 6 decimal places...
  3. Thanks guys... Shift L ... works a treat, I'm a happy bunny.
  4. I really like the work you guys are putting into the Bus ... you have fixed so much that it is a joy to fly now. There is one area that is still in need of a little attention though, on my system anyway, and that is the VC cockpit being a bit too dark especially the overhead panel, even with all lights at max. The pic I have posted doesn't show this as I had the monitor and sim brightness settings up higher than normal (when switched to daytime was way way too bright). The main problem is the FMC's themselves when popped up the buttons are totally NOT identifiable.... as can be seen in the pic they cannot be seen. This makes it impossible to fly at night.... please help as I'm getting more of an interest to fly at night. Thanks
  • Create New...