I should clarify this comment, LOL
All I meant to say was the SCRIPT was working in FreePIE to get the data from the TrackIR software - It was progress lol but I still do not have TrackIR in game.
Still fiddling!
Moderator: JeremyaFr
Well, if you post a guide, I think it would actually help *me* figure out what I'm missing -- and it will help others get this working while I'm working on the next release
Ok, I'll post exactly the steps to get tIR working, and my cockpitlook.cfg is default - no changes.blue_max wrote: ↑Fri May 31, 2019 6:42 amWell, if you post a guide, I think it would actually help *me* figure out what I'm missing -- and it will help others get this working while I'm working on the next release
Also, I've been looking at the code and I don't see why the Hook is forcing you guys to use openvr_api.dll. Can you check what cockpitlook.cfg says? It should have "tracker_type = FreePIE".
Code: Select all
def update():
freePieIO[0].yaw = trackIR.yaw
freePieIO[0].pitch = trackIR.pitch
diagnostics.watch(freePieIO[0].yaw)
diagnostics.watch(freePieIO[0].pitch)
if starting:
trackIR.update += update
Excellent! I can scratch "make video" off my todo list lol!ual002 wrote: ↑Fri May 31, 2019 3:44 pmhttps://www.youtube.com/embed/DH7FdI5OWX4
Here is a test video of it
My pleasure, but it's really just a listed version of this thread and your instructions. Plus a couple tips from ual002!
Definately requires -1 for trackIR. I checked the TIR software to see if I had enabled inverted pitch but I could not find any such setting.* pitch_multiplier = 1 works for me when reading data directly from FreePIE; but I'll take note of this if I manage to get native support for TrackIR.
Can't wait to see the future developement of this hook!!!* I think I understand now why the hook is trying to load openvr_api.dll. As I said previously, this is my fault. I'll fix this.
My final guide will have these removed, it's nice to see the values changing during setup* The lines that begin with "diagnostics" are not really needed. After you get the script working, you may remove them or comment them out.
Getting the trackclip won't help you, you could do the same by sticking reflective tape on a cap or something heh. You would also need an infrared camera, or make your own, plus I really doubt the TIR software/drivers would work without native hardware, but I could be wrong about that.I've been looking at how FreePIE supports TrackIR and it looks like I still need to guess what's the right protocol here -- and it doesn't help that I'm working blind. Checking in Natural Point's page, it looks like there's a track clip for less than $10. If I buy this, will I be able to get all the features of TrackIR?
This might be possible without breaking the UI code (?), at least partially; but we need a texture that serves as a marker/reference point and a place in the 3D cockpit where said texture is attached.
So does that mean we won't be needing openvr_api.dll?blue_max wrote: ↑Fri May 31, 2019 6:43 pmThanks for posting this guide, ffaaway!
* pitch_multiplier = 1 works for me when reading data directly from FreePIE; but I'll take note of this if I manage to get native support for TrackIR.
* I think I understand now why the hook is trying to load openvr_api.dll. As I said previously, this is my fault. I'll fix this.
* The lines that begin with "diagnostics" are not really needed. After you get the script working, you may remove them or comment them out.
I've been looking at how FreePIE supports TrackIR and it looks like I still need to guess what's the right protocol here -- and it doesn't help that I'm working blind. Checking in Natural Point's page, it looks like there's a track clip for less than $10. If I buy this, will I be able to get all the features of TrackIR?
@ual002: Beautiful video! Just watching that makes me want to hack-in support for 6dof. Maybe in the near future...