Sabretooth78 56 Posted May 13, 2020 Share Posted May 13, 2020 Since installing the latest full build (1.3.1.0) of the A320, I've noticed that the outer COM dials won't "turn over", i.e. when standby is set to 136.xx, dialing up on the outer dial will not cause the number to cycle over to 118; likewise I can't cycle down to 136 from 118. The minor dial will roll over, i.e. 124.95 -> 125.00 -> 125.05 but again won't cycle past 136.xx or 118.xx. I also seem to be seeing the 8.33 spacing, i.e. x.000 -> x.005 -> x.010, etc.; which I didn't see before this last update. I did a quick search and didn't see that anybody else has reported this behavior. Is it possible there is something I've done that could be causing this? Link to comment Share on other sites More sharing options...
Sabretooth78 56 Posted May 14, 2020 Author Share Posted May 14, 2020 In an attempt to root out a possible issue on my end, I reinstalled the buses (A318-21 and 330; with Windows virus protection turned off), repaired all the C++ libraries and ran the Netfx repair tool. The issue still persists identical to as I reported it above. Link to comment Share on other sites More sharing options...
Deputy Sheriffs masterhawk 799 Posted May 14, 2020 Deputy Sheriffs Share Posted May 14, 2020 We added 8.33 in preparation for v5. And the dial logic was corrected to real world functionality. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted May 18, 2020 Aerosoft Share Posted May 18, 2020 Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.