|
|
|
| Our software is compatible, baby. |
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Tachometer and Custom Dashboard Help?
Quote:
I'm pretty sure and Oculus VR has enough resolution to do a full VR dash rather than a simple dual camera display. But the Oculus takes away all the programming fun, since you (IIRC) can set it up as two displays and just run two separate default dashboards set to their respective cameras. Not only that, but you could set up the Oculus hand controllers as joysticks for driving. Although Oculus is so much nicer, I still prefer VIRemote. It's so much more fun. |
|
#2
|
|||
|
|||
|
Re: Tachometer and Custom Dashboard Help?
The easiest way to present a numeric number is to write to DB/String 0 through DB/String 9. Format the number, any way you, like to a string and write to the variables listed above.
If the range works, you can also write to DB/Slider 0 through 3. There are LEDs and buttons too. Beyond that, you can make a custom DB. Controls placed in the Custom tab are still bound by name. The difference between simple and default DB are ... Default --------- 2nd camera - simple supports just one on the left pane Test - allows you to view sensor and motor configuration, values, and experimentally modify many values. Commands - Interactively fire a command for testing Checklist - Display a text file and support checking them off as part of drive team procedure Simple -------- Missing the above features, but the diagram is considerably simpler, therefore a much better template for many to start with. If you identify that binding or other features don't work, please bring it up. Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|