B350 GNS530 hardware issue
-
Because I fly only with the B350 I bought the FlightSimBuilder GNS530 wich is plug and play in MSFS!
Compare to other aircrafts available in MSFS with GNS530 or 430, the BS B350 has 1 issue, nevertheless not very important, I can leave with it...
So every buttons on the FlighSimBuilder GNS530 works as it should, except the PROC button! For other aircrafts it works but not for the B350... So I have to click on the PROC button on the sim to get the Procedure page to be displayed... not a big deal but...By the way, an other point not linked to the FlightSimBuilder GNS530, the Flight plan loaded in the sim is not loaded in the GNS530. this feature is not activated I guess.
Not vey matter but for long flight with a lot of waypoints it is quite a lot of time which could be avoided.
If you could have a look on it, it would be very appreciated!!
Thanks
Pascal -
@lancealotg you are right I could have put a better image ;-)
-
@anderson Thank you for this information, I will give it a try and let you know :handshake:
-
@anderson
Well I tried but I do not know how to program the PROC button in order to Send AS530_PROC_Push-Event
All other buttons works as it should
Thanks to give me a clue how to do it
Pascal -
@anderson Thanks Anderson. this is understood.
I use Axis and OH for such configuration but here the issue is on the PROC button on the FlightSimBuilder hardware which is not recognized as such in the BSQ B350.
Axis and OH does not recognized the button so I can not program it...
Then I will ask to FlightSimBuilder support if there is something I can do
The BSQ B350 is so good !
Pascal -
This is odd since all of these functions are set in the RealSimGear configuration. I assume your 530 works with other aircraft no problem?
This is a bit of a long shot but might be worth trying. I was getting some really weird behavior with my RSG 530 and the King Air - effectively double button presses that did weird things like add duplicate waypoints to my flightplans and caused other interface issues. Even if you don't have the second GNS displayed in the cockpit (e.g. the picture you posted) the second unit is still 'live' which was what was causing my issues.
So what I did was comment out the second GPS in the panel.cfg. You can find it in ...Packages\Community\bksq-aircraft-analogkingair\SimObjects\Airplanes\bksq-aircraft-analogkingair\panel
Find the VCockpit03 section in the cfg file and put two '/' in front of gauge line so it looks like this:[VCockpit03] size_mm = 320,234 pixel_size = 320,234 texture = $Gns530Screen_2 //htmlgauge00=NavSystems/GPS/AS530/AS530.html?Index=2, 0, 0, 320,234
This completely solved my GNS issues, it might work for you, keeping in mind that you won't have access to the second GNS screen in the cockpit and you will probably have to redo the fix after any updates.