DIY Head Tracker For A Tenner

has anyone managed to use the edtracker in star citizen yet?
i used this tool to map both
  • v_view_yaw_absolute and v_view_pitch_absolute
  • v_view_aim_yaw and v_view_aim_pitch
to the edtracker's x and y axes and could move my head ingame. problem is, both modes are "accumulate" modes and the sensitivity is way too high (i haven't fiddled with the edtracker code yet ;) )
video of edtracker being used in star citizen (not by me)
 
Awesome you gave me a reason to open that piece of a bugged software again. And that tool is really great, but.... why are you using those commands? I use simply v_view_pitch and v_view_yaw, tried also yours and combined in several ways too but it's always the same, basically the same situation of yours. Too high sensitivity and "absolute" mode. I asked some time ago in the Actionmap megathread info about how to regulate it and Electrocutor (the "guru") told me there was no way via the Actionmaps. If you notice in fact in ED there is a different format (no actionmaps) and here it's possible to set sensitivity and other paraments (like absolute/direct). I'd go ask in that thread or directly the guy who posted the vid on youtube :)

edit: actually I sent him a youtube msg, first time I use that thing
 
Last edited:
I have had that. Usually a reboot and unlug/plug the EDtracker has cured things. Is the axis showing up in the Windows Control Panel settings. Or is the head moving in both axis in the UI. Failing that, you could try saving your custom bindings file and try setting the axis from a keyboard/mouse starting point just to see if the 2 axis are detected before the stick and throttle etc. are bound.
 
Actually, I just removed one of the screw holders and didn't hack the PCB. It seems pretty solid with just one screw.

Yeh, if you're a wimp, you can do that :)

I must admit, it took me a long time to slowly saw though the PCB, so your alternative sounds appealing!
 
I have had that. Usually a reboot and unlug/plug the EDtracker has cured things. Is the axis showing up in the Windows Control Panel settings. Or is the head moving in both axis in the UI. Failing that, you could try saving your custom bindings file and try setting the axis from a keyboard/mouse starting point just to see if the 2 axis are detected before the stick and throttle etc. are bound.

Ah right thanks, I must admit I've not had much time to fiddle with it..
Axis showing in windows control panel? I must have missed the tool to do that... whats that about..? I thought it only showed in ED... or using the cal tool, which I haven't had a chance to use either to my shame, too much real life work :-(
 
Ah right thanks, I must admit I've not had much time to fiddle with it..
Axis showing in windows control panel? I must have missed the tool to do that... whats that about..? I thought it only showed in ED... or using the cal tool, which I haven't had a chance to use either to my shame, too much real life work :-(

It's easiest to look at the UI to see if the head moves in all directions. But in Windows its Control Panel/Devices and Printers right click EDtracker2 that should be showing in devices and Game Controller Settings. Choose EDtracker in the list and then Properties. You should see a representation of the axis. But as I say, it's prob a lot easier to just check in the UI.
 
It's easiest to look at the UI to see if the head moves in all directions. But in Windows its Control Panel/Devices and Printers right click EDtracker2 that should be showing in devices and Game Controller Settings. Choose EDtracker in the list and then Properties. You should see a representation of the axis. But as I say, it's prob a lot easier to just check in the UI.

Ahhhh i was unaware on the control panel properties trick, I'll give that a pop in the first instance then, as the UI looked like a little more effort to set up (I really am silly tight on personal time right now :-( )
Thanks for your help
 
OK, thought I follow advice and run my pre-built device through calibration again just to check it?

So I've downloaded EDTracker2-GUI-64bit and when I run the EDTrackerUtil.exe I just get a dead/frozen/empty window.

Do I need to do something else? I'm following the documentation "Calibrate device drift" on page 9.
 
OK, thought I follow advice and run my pre-built device through calibration again just to check it?

So I've downloaded EDTracker2-GUI-64bit and when I run the EDTrackerUtil.exe I just get a dead/frozen/empty window.

Do I need to do something else? I'm following the documentation "Calibrate device drift" on page 9.

Use the executable in the UI221 folder instead. It's available on the EDTracker website downloads section. I had the same problem with the 64-bit UI. Even with 64-bit Java installed.
 
I would try the 32bit version from the github. Use the UI221 folder version. Ity apparently cures the white screen problem.

Quote from the readme
"32 bit version seems to work better than 64 bit version even on 64 bit systems.

** Do not use this version! **

The UI221 version appears to solve the 'blank white window' issue that's
causes by a bug in the latest version of Processing.
"
 
parts has arrived

So i ordered the kit from hobby components and a daughter board from the edtracker.org.uk site and all parts has arrived

assembly time : 10 minutes do to having to check the pdf for orientation of the parts, and i know how to solder :)

flashed and calibrated and working flawless :D

only problem now is getting my HOTAS but even saitek dont have the x-55 in stock atm.

i really love the work you guys put in to this project and thank you very much :)
 
Ahhhh i was unaware on the control panel properties trick, I'll give that a pop in the first instance then, as the UI looked like a little more effort to set up (I really am silly tight on personal time right now :-( )
Thanks for your help

i only appear to have a z axis, and do not appear to be able to get the cross hair to move forward, is that normal...?
 
Finally got the tracker working and setup in game. A bit confusing at first, but after a few D'oh moments it really works great.

I can say that it has really changed the game for me, for the better it's sooooo good to be able to look around the inside of a station and it's great for dog fighting (I'm still rubbish, but it's great )

Thanks for all of your hard work

Grum.
 
You guys really should design and build a modern wireless HOTAS joystick. You'd be rich and bring joysticks into the 21st century.

The video I saw of Rob's (I think it was Rob?) Augmented Control Panel would be spectacular on a HOTAS setup. Bundle it with the EDtracker and you have a recipe for riches!
 
Can someone explain the calibration process/option? [I was calibrating because my view was seemingly drifting slowly to the right]


What does 3 (reset view/drift tracking) do exactly for example?

Should the process ALWAYS be to calibrate - Run the program. Press 3... wait X minutes press 8?

On one of my earlier tries this was the state of affairs after 10 mins.
image
edtracker1.png
What's interesting is the head is looking to the right, which was the problem I was experiencing in game, with my view seemingly drifting to the right.

On my last session, I came in and press 3 and just left it and after ten minutes had this.
image
edtracker2.png

So does that look OK/normal?

Compared to the manual why are the red and yellow dots miles off?

DMP Yaw means? Good? Bad?

Any advice/tips appreciated.
 
i only appear to have a z axis, and do not appear to be able to get the cross hair to move forward, is that normal...?

Should be movement on all 3 axis corresponding to yaw, pitch and roll. So you should be able to move the x around the white square and see the z-axis move too. Do the UI pick up the tracker ? Next step would be to load the calibration sketch using Arduinio IDE and posting a screenshot of the UI for us to take a look.
 
has anyone managed to use the edtracker in star citizen yet?
i used this tool to map both
  • v_view_yaw_absolute and v_view_pitch_absolute
  • v_view_aim_yaw and v_view_aim_pitch
to the edtracker's x and y axes and could move my head ingame. problem is, both modes are "accumulate" modes and the sensitivity is way too high (i haven't fiddled with the edtracker code yet ;) )
video of edtracker being used in star citizen (not by me)
i managed to get it to work in star citizen arena commander, but it is a little buggy. here's a how-to:
Code:
1) Install vJoy (http://headsoft.com.au/index.php?category=vjoy), make
sure the configuration program is installed too.

2) Download the SC Joystick Mapper
(http://www.burri-web.org/cassini/SCJMapper.html) and the Universal
Joystick Remapper
(http://evilc.com/joomla/articles/9-code/autohotkey/1-ujr-universal-joystick-remapper)

3) Open the vJoy configuration program and add a joystick, 2 axes are
enough.
	Basic Axes: X, Y (only 2 are needed)
	Buttons: 1
	POVs: 0
	Target Device: any
	Action: Configure
Click Apply and wait for the program to finish. Remember the Target
Device number on the right, then close the window.

4a) Run the Universal Joystick Remapper and on the "Axis 1" tab, top
left at "vJoy Stick ID" set the Target Device number from the
configuration program. Depending on how you set up the virtual
joystick, you will have a set of axes that you can set (the same axes
your virtual joystick has, typically X and Y).
4b)In the X Axis line, choose the Physical Stick ID corresponding to
your EDTracker (you can find it by trial-and-error or by going to
windows' Gamecontroller window (if for example the EDTracker is in the
4th position, its Physical Stick ID will be 4)). Choose Physical Axis
1. The Slider in the "State" column will move when the EDTracker is
moved.
4c) Do the same for the Y Axis line, but choose Physical Axis 2. All other 
lines can be left set to "none".
4d)I had a few problems at this step. When the UJR shows error
messages try creating a new virtual joystick in the vJoy Configuration
Program with a Target Device number of 15 or 16. I also found that a
virtual joystick with 0 buttons might not work.
4e) DO NOT CLOSE UJR. UJR must be running when you play or set up the
mappings.

5) Run SC Joystick Mapper. Joystick 1 should be named "vJoy Device".

6) If you use a HOTAS (X-55, Warthog, G940 or X52) or any other
joystick, go to \StarCitizen\CitizenClient\Data\Controls\Mappings and
copy your respective mapping file to, e.g., C:/layout_hotas_x55.xml.
If you use Mouse and Keyboard only, go to step 7.
6a) Open the .xml file you copied with any text editor (windows
editor, Notepad++, ...). In the default Mappings, the Stick is always
js1 and the Throttle Unit (if you have a separate one) is always js2,
but because vJoy is the first entry on the list, you have to change
all "js2" to "js3" and all "js1" to "js2". You can use find and
replace for this. Save the file when you are done.
6b) In SC Joystick Mapper, right click the large, empty text box on
the right and click "open", choose the .xml file you just copied.
Click the "<-- Grab XML" button on the bottom to load the mappings
from the .xml file.
6c) Cycle through the "Joystick 1 - x" tabs to find out which device
has which Joystick number (e.g. 1 - vJoy, 2 - Stick, 3 - Throttle, 4 -
EDTracker)
6d) In my case after adding the virtual joystick the stick did no
longer control the spaceship's jaw, pitch, roll and primary weapon. If
this happens to you, you can fix this by either of these two steps:
6d1) On the left side of the SC Joystick Mapper window, find the
following entries and assign the appropriate joystick movements /
button presses (your Stick's tab must be the active tab):
at "spaceship_movement"
	v_pitch
	v_jaw
	v_roll
	v_newtonian_yaw
	v_newtonian_pitch
at "spaceship_weapons"
	v_attack_group1
If the program does not pick up the correct axis/button, assign it
anyway, this will be solved later.
6d2) Open the .xml file with any text editor and insert the following
lines:
after <actionmap name="spaceship_movement">:
	<action name="v_pitch">
		<rebind device="joystick" input="js#_y" />
	</action>
	<action name="v_yaw">
		<rebind device="joystick" input="js#_rotz" />
	</action>
	<action name="v_roll">
		<rebind device="joystick" input="js#_x" />
	</action>
	<action name="v_newtonian_yaw">
		<rebind device="joystick" input="js#_x" />
	</action>
	<action name="v_newtonian_pitch">
		<rebind device="joystick" input="js#_y" />
	</action>
after <actionmap name="spaceship_weapons">:
	<action name="v_attack1_group1">
			<rebind device="joystick" input="js#_button1" />
exchange the # in the 4 lines for your joystick number.
Save the file and load it into SC Joystick Mapper.

7a) In SC Joystick Mapper, on the left side, under "spaceship_view",
find the entry "v_view_yaw" with the joystick icon next to it. Click
it, select the "Joystick 1" tab on the top and move the EDTracker.
Cmd. should read "v_view_yaw"; Ctrl. should read "js1_x" or "js1_y".
Click assign. Don't worry if the Program picks up the wrong axis, this
will be corrected later.
7c) Do the same for the "v_view_pitch" entry.
7d) Finally, click the "Dump XML -->" button. Right-Click the text box
on the right and choose "save as", save the XML file where it is
easily accessible (e.g. C:/layout_hotas_x55_ed.xml)

8) Open the xml file with any text editor. Find the entries
	<action name="v_view_yaw">
			<rebind device="joystick" input="js1_x" />
		</action>
	<action name="v_view_pitch">
			<rebind device="joystick" input="js1_y" />
and make sure the correct axes are assigned (v_view_yaw = js1_x,
v_view_pitch = js1_y). If you have gone through step 6d1), check
	<action name="v_pitch">
		<rebind device="joystick" input="js2_y" />
	</action>
	<action name="v_yaw">
		<rebind device="joystick" input="js2_rotz" />
	</action>
	<action name="v_roll">
		<rebind device="joystick" input="js2_x" />
	</action>
	<action name="v_newtonian_yaw">
		<rebind device="joystick" input="js2_x" />
	</action>
	<action name="v_newtonian_pitch">
		<rebind device="joystick" input="js2_y" />
	</action>
	<action name="v_attack1_group1">
		<rebind device="joystick" input="js2_button1" />
	</action>
as well. Save the file.

9) Start Star Citizen Arena Commander. Once ingame, open the console
(see the Keyboard layout in options to find the key) and use the
pp_rebindKeys command to load the new keybindings, e.g.:
pp_rebindKeys C:/layout_hotas_x55_ed.xml

10) You can adjust the EDTracker's sensitivity in the Universal
Joystick Remapper tool.

11) I experienced that headtracking would randomly not work after
entering a (drone sim) game. This is a bug of the game, head look can 
be activated by moving the mouse a little.
can also be found here.
 
Last edited:
Back
Top Bottom