Skip to content

[Bug] <title>Steam Gauge VOR#2 disengaged from SIM - FSB Version 1.32.0 #1

Description

@fdorrin

What happened?

This discussion is limited to testing just completed in xplane12 with the Cessna 172 SP; Baron 58; and the King Air C90.
Native Piston Single + Pop-Out G1000 MFD on the C172SP

  • Test was performed out of KTOL (Toledo Ohio Airport) using ILS Z 25. I takeoff from RWY25 and fly to HARBS intersection to begin the approach. The number 2 NAV/COM was set to the CRL VOR on frequency 115.70.
  • Changing SIM VOR#2 OBS does not change the FSB VOR #2 OBS
  • The FSB Range Knob is not configured to change the FSB VOR #2 OBS so there is no way to set a new OBS Course without doing it on the SIM itself.
  • I tested the TO/FROM flag and found it working by intercepting the radial 252 degrees that it was stuck on, then flying over the CRL VOR until the flap flipped accurately. Both the CDI and the TO/FROM flag work, but there is no way to change the OBS course you want.

Native High Performance Piston Single + Pop-Out G1000 MFD on the C172SP

  • test results show that this steam gauge display has the same issues with VOR #2
  • I did not test the TO/FROM flag in this configuration

Native High Performance Piston Single + Pop-Out G1000 MFD on the Baron 58

  • the OBS in the SIM does change the OBS on the FSB
  • The FSB Range Knob does not control the course on the #2 VOR as it should

Native High Performance Piston Single + Pop-Out G1000 MFD on the King Air C90

  • Altitude know does set the Altitude Selector on the SIM
  • The FSB Range Knob does not control the course on the #2 VOR as it should
  • VOR #2 doesn't appear to be connected at all with the SIM VOR #2

Steps To Reproduce

  1. Start the HUB with version 1.32.0
  2. Use only XPLANE12
  3. HUB Native Piston Single + Pop-Out G1000 MFD
  4. SELECT C172SP
  5. Begin a flight at KTOL on RWY 25
  6. Sit right there on the runway and set 115.7 frequency on the Garmin 430 NAV
  7. Use the FSB knob on the #2 VOR and you will see that it doesn't do anything.
  8. Try to change the OBS on #2 VOR on the FSB - you cannot.
  9. On the SIM directly, change the OBS on the #2 VOR and verify that it does not change the #2 VOR on the FSB. They are not linked.
  10. QUIT XPLANE12
  11. RESTART XPLANE12 HUB Native High Performance Piston Single + Pop-Out G1000 MFD r
  12. Repeat steps 1-9 and you'll see the same results.
  13. From within XPLANE12, change to the Baron 58.
  14. Observe that changing the SIM VOR#2 OBS does drive the FSB VOR#2
  15. Observe that the Range knob does not control the OBS on the VOR#2 FSB
  16. From within XPLANE12, change to the King Air C90
  17. Observe that the SIM VOR#2 is not connected to the FSB VOR#2 in any way

Expected result?

The expected result is made clear in my comments, so I'll use this for general comments that may be helpful. Expected results should be obvious. I expect the very basic instruments to work. The tests I've performed should have been done by your team long ago and part of a standard testing protocol.

I suggest getting specific models fully functional so that when people buy your panels as I have, you'll be able to suggest they use those as your team works on whatever other fixes are required.

You have a great idea here and it will help me train a few pilots - both private level and instrument. When it works, it is realistic and awesome as a training and recurrency tool.

I very much appreciate the fact that your team is working on this and making progress. Please don't slow down on meeting the promises of the sales team by bring the #2 VOR to life for the C172SP, Baron 58, and King Air C90 in XPLANE12. I'm happy to keep testing as new versions roll out.

Actual result?

You are improving but not there yet.

Which product is affected?

Steam gauge panel

Version

Latest Stable

What simulator are you seeing the problem with?

X-Plane 12

Aircraft / Addon

C172SP, Baron 58, King Air C90 (defaults in XPLANE12)

Upload log file (log.txt)

No response

Upload screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions