Nice!logicalChimp wrote:Just finished testing the 'stopping' patch - works great
Edit: tested on the home machine (which doesn't have the problems that the works laptop does)
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
Nice!logicalChimp wrote:Just finished testing the 'stopping' patch - works great
Edit: tested on the home machine (which doesn't have the problems that the works laptop does)
Nice you got it working! But... I'm a bit sad that this was the problem because the FreePIE installer should fix this :/logicalChimp wrote:
Edit2: Ignore the IESHIMS.dll bit above - apparently thats an optional import from one of the nested levels of DLLs.
No other dependencies were reported as missing by dependencywalker, so I'm guessing it's gonna be a dll version mismatch instead. I love windows sometimes.
Edit3: GOT IT WORKING! Yay
I had a 'brainwave' - I'd already installed the VCRedist 64bit version from the microsoft site, but I went back and downloaded/installed the vcredist_x86 as well. One reboot later, and FreePIE startedFor whatever reason, despite running Win7 64bit, it seems that the 64bit VCRedist exe doesn't have everything needed to run FreePIE. Just for anyone else that runs into this problem.
If Sony had sold it like this, the reviews probably would have been much better. Are there any downsides to this design?CyberVillain wrote:About the comfort problem you can do the same thing that I did to my T1
Code: Select all
if (enabled and hotkey):
Code: Select all
if (enabled):
Code: Select all
#Use Z to toggle on/off and right mouse to activate head tracking
#(Good for games like Battlefield 3)
def update():
yaw = android.yaw
pitch = android.pitch
deltaYaw = filters.delta(yaw)
deltaPitch = filters.delta(pitch)
if (enabled and hotkey):
mouse.deltaX = deltaYaw*multiply
mouse.deltaY = -deltaPitch*multiply
if starting:
enabled = False
multiply = 40
android.update += update
hotkey = mouse.rightButton
toggle = keyboard.getPressed(Key.Z)
if toggle:
enabled = not enabled
Code: Select all
def update():
yaw = android.yaw
pitch = android.pitch
deltaYaw = filters.delta(yaw)
deltaPitch = filters.delta(pitch)
if enabled:
mouse.deltaX = deltaYaw*multiply
mouse.deltaY = -deltaPitch*multiply
if starting:
enabled = False
multiply = 400
android.update += update
toggle = keyboard.getPressed(Key.Z)
if toggle:
enabled = not enabled
Do you have the Raw data checkbox checked? also try and see if you get any data from the Android plugin. diagnostics.watch(android.yaw)shent1080 wrote:Thanks cyber villain, the file works without any errors, but now the script runs, i start the android apk on my tablet and nothing happens, i feel like i've missed a step or something. can you have a look over this when you get chance.
1. installed freepie on pc
2. installed apk on tablet
3. opened freepie on tablet
4. opened freepie and script on pc
5. set settings on tablet to my ip and port 5555
6. check setting on android plugin and that is port 5555
7. run script
8. tun on tablet app
9. press z to start on pc
10. pressed right mouse on pc.
No errors come up just seems like they are not communicating, when i press z the cursor goes to the top left of the screen and stays there, when i right click the mouse the only thing that happens is a drop down menu appears like normal when you right click the mouse. any ideas?
ok any readings in freepie when doing diagnostics.watch?shent1080 wrote:both the send orientation and raw data checkboxes are ticked, the dropdown is at normal (other choices are fastest, game, and ui), don't know what it does though.
Sometimes the cursor on my screen moves a little (although in the wrong direction) then goes to the top left corner, and sometimes it just goes straight to the top left corner.
sample debug data from tablet
this is how much they vary BY on a flat surface.
Accelerometer 0.19-0.26; 0.06-0.12; 9.98-10.07
gyro keeps refreshing but all figures stay at 0.00
magnometer 4.14-4.54; 9.92-10.25; 36.79-37.02
orientation these are all staying solid, no movement seem top be working ok
Sorry was a bit unclear again,shent1080 wrote:i have the gui version so its just a watch tab, if you look at my screenshot above you'll see it at the bottom, or do you mean a watch script i need to load in or a plugin that i need to enable?
if you do mean the tab, then no there is no activity.
Unclebob wrote:H guys
just down loaded the new version as I have a homebrew hackulus on the go and wanted to add head tracking support.
I have an old Vuzix with head tracking which I thought would cobble into my project.
I can see the plugin VuzixTrackerPlugin.cs on line but it is does not seem to be in the distributable.
Not being a hard coder I am assuming that I have to down load the source and find/buy a compiler if I want to use that plug in?
Any guidance would be gratefully received.
By the way my simple hackulus is based on a Nexus 7 using the Splashtop HD streamer.
Loving your work
Cheers UB
You can use multiple IMU's but that won't give you the capabilities of a Hydra. You can only track direction with multiple IMUs. For example - one sensor on your head and one sensor on your hand/gun for independent hand and head direction. But for true positional tracking (x,y,z) you will actually need to use the Hydra - which is also supported by FreePIE.shent1080 wrote:Just a quick question, can i connect multiple imu's at the same time to freepie and have them work like the hydra for instance? looking into control scenarios for when the rift comes.
No, that 9 DOF nonsense is marketing-speak for "9 sensors". In practice, these 9-sensor packages really only accurately track 3 DOF. And then they can "sense" movement in the x,y,z but not in a useful way for position tracking. Only for stuff like shake detection.shent1080 wrote:But the 9dof imu's like the razerimu will given you positional tracking won't they?
Accel, gyro, magno.
They can each independently track their orientation (yaw, pitch, roll) so for example each sensor will know if its pointing north or at a 45 degree pitch, and you can subtract the two sensors to determine the relative angles between them. But neither sensor will know its position (x,y,z) like whether it's 1 meter off the ground, or whether it just moved 2 inches to the left, or anything related to x,y,z position. You need to use optical (TrackIR, FreeTrack) or the Hydra to track positional data.shent1080 wrote:ok so they can track 1 position relative to another but not full positioning data with full co-ordinates of your true position on earth.
Doesn't work for me just get a juddery mouse in the corner of the screen. Annoying as no obvious solution.shent1080 wrote:Hi, i had similar problems when i was testing with an android device, you need to play around with the .yaw entries as cyber said, where it would say android.yaw, change it to google.yaw if you are just using the nexus now, this will take out the magnometer which is what i think is making your positioning respond in the wrong way, also mess around with checking and unchecking of the raw data etc on your nexus, although, i think cyber has fixed the problems that i was having with this. you can also play around with x=google.yaw etc and change yaw to pitch etc.
Cyber
Just a quick question, can i connect multiple imu's at the same time to freepie and have them work like the hydra for instance? looking into control scenarios for when the rift comes.
Thanks
I would start by holding the tablet so that the screen faces the roof, when faced like this yaw is actually aligned with the magnetic north and thats how the magnometer needs to be positioned for a reliable yaw reading. Is it still only sitting in the cornor? What script are you using? Play around with the multiplier setting in the script. android.yaw uses the magnometer so you wont get good reading out of that fusion when holding the tablet like a HMD.Unclebob wrote:Doesn't work for me just get a juddery mouse in the corner of the screen. Annoying as no obvious solution.shent1080 wrote:Hi, i had similar problems when i was testing with an android device, you need to play around with the .yaw entries as cyber said, where it would say android.yaw, change it to google.yaw if you are just using the nexus now, this will take out the magnometer which is what i think is making your positioning respond in the wrong way, also mess around with checking and unchecking of the raw data etc on your nexus, although, i think cyber has fixed the problems that i was having with this. you can also play around with x=google.yaw etc and change yaw to pitch etc.
Cyber
Just a quick question, can i connect multiple imu's at the same time to freepie and have them work like the hydra for instance? looking into control scenarios for when the rift comes.
Thanks
Thank you anyway
UB