Yep. If you're doing it on protoboard you can always put the button somewhere else if you want - it's only on the custom PCB that the button point is covered.
If you need another piece of protoboard I've got loads of the blasted things here so I can happily pop one in the post for you if you need![]()
Hi Brumster,
In the event that FD adds FPS to ED, do you have a plan to add translation to EDTracker?
EDIT:
I was just reading that the 9250 has an accelerometer. How come it isn't used for translation?
So when following a guide, I cut first, and measured after. Turns out I have the MPU with the NCS and FSYNC spots, and am now stuck with a protoboard that's 12x7. So now the MPU doesn't fit, and I have no idea what to connect those extra bits to even if it did. Would someone please tell me if I now need to order another protoboard, or if by some magic there's a workaround, and possibly refer me to a guide that includes my version of the MPU? I haven't soldered anything yet.
Thanks.
Cheers!
Edit:
Ok so I found the page on the website describing what to do in the event of a 10-pin. Basically I just need to put it together sans button to get the extra space I need, and do not have to do anything with the extra connections correct?
Sure, but then the costs ramp up massively. We need to develop a camera, plastic mouldings and construction/assembly of all the parts, plus the software development costs. I bet we wouldn't be far off TrackIR money at that stage.Well, that blows. Ok then, throw an IR emitter on the module and three IR sensors on the monitor (or wherever it will fit) and calculate translation from the varying differences received from the sensor.
No. It has an integral lipo; battery life isn't a problem. It's wireless certification and some antenna tuning; all time and money, that's all!And is power consumption what is holding up the wireless version? I don't mind mounting a battery pack on my headset.
Unfortunately, Opentrack doesn't allow you to specify two trackers. :-\
I had the brilliant idea of using the camera for translation and EDTracker for rotation, but alas, there is no option. I tried it on FacetrackNoir, but it only recognized the EDTracker input.
I think you just answered your own question: ED only supports 2 axis for head tracking so 3D movement is pretty much impossible.Hi Brumster,
I have an idea so fantastic and ludicrous that you might want to slap me twice and call me Shirley. But hear me out.
When you rotate your head around a point your eyes actually move through an arc and undergo a tiny bit of translation. In this, merely rotating your head can generate parallax and artificially simulate 3d. Would it be possible, or even worth it, to calculate this translation in EDTracker and inject it into the (x,y,z) axes to simulate parallax? Or is this idea so ludicrous it should be laid out in plaid?
And speaking of which, why doesn't ED have configurable axis for rotation (sans yaw and pitch) and translation?
LOLHi Brumster,
I have an idea so fantastic and ludicrous that you might want to slap me twice and call me Shirley. But hear me out.
When your real head and eyes are doing it, there's nothing artificial or simulatedWhen you rotate your head around a point your eyes actually move through an arc and undergo a tiny bit of translation. In this, merely rotating your head can generate parallax and artificially simulate 3d.
Is it possible? Well, technically, yes although everyone's eyes and head sizes are different. Is it worth it though? I would say no.Would it be possible, or even worth it, to calculate this translation in EDTracker and inject it into the (x,y,z) axes to simulate parallax? Or is this idea so ludicrous it should be laid out in plaid?
That you'd have to ask FrontierAnd speaking of which, why doesn't ED have configurable axis for rotation (sans yaw and pitch) and translation?
I think you just answered your own question: ED only supports 2 axis for head tracking so 3D movement is pretty much impossible.