WiiLi.org

rambozo79 · Joined: 15 Mar 2007 Posts: 7

I am trying to use dot1 and dot2 for tracking. In my script, if both dots are visible then it will add the value of each then divide by two in order to get the average, which I use to define directinputx. And that bit works fine.

Aside from using both dots, I also want to be able to use just one dot, in the cases where both are not visible. So basically, I want one dot to be able to pick up where the both left off.

I have been been trying to accomplish this by offsetting the only visible dot by the distance between the dots when they were visible. That should give me the rough distance of where the invisible dot should be, if it was visible. I imagine this to be true because the physical distance between the dots is static, the physical distance between the LEDs in the sensor bar. But It seems that when redefining mouse.directinputx with these values, the cursor still jumps on the screen, as if my virtual dot is nowhere near where the physical dot was.

What am I overlooking? Where am I going wrong?

I don't know if this is reinventing the wheel, but I imagine it to be a better way of IR tracking. It should expand the tracking range beyond tracking off of one dot, and by tracking off of the value between the two dots, it should put the cursor closer to the center of the screen without having to offset your sensor bar from one side of the screen to the other.

Anyway, here is my code.

Dr_Zoidberg · Joined: 29 Dec 2006 Posts: 60

I have been doing this with my IR FPS script. http://www.wiili.org/forum/new-fps-ir-script-using-directinput-t1639.html

Have a look at the first half of the Script where it says Phantom dot.

It is not as easy as I thought it would be.

You haven't included any angle calculation in your script, so you will get a jumpy cursor if you tilt your wiimote.

The distance (reported by the wiimote) between the two dots changes more than it should. Just show the distance variable in the debug line and you will see it changing depending on how far the dots are from the edge of the wiimote sensor.

If only one dot is visible you don't know if the distance between the wiimote and the sensorbar has changed and therefore can't correct the distance between the two dots.

With some fixes it works quite well and I use the extended range for turning in fps games. If glitches happen, they shouldn't matter.

rambozo79 · Joined: 15 Mar 2007 Posts: 7

rambozo79 · Joined: 15 Mar 2007 Posts: 7

Well, I played with your script a bit today. It is very nice. I made some modifications to better suit my needs. I removed the nunchuck functions for flicking it left and right, and replaced it with tilting which works really well for leaning in Armed assault and Rainbow six 3. I am still going to tweak it out a little more for rainbow six 3 yet. There are some more functions I want to map to the buttons, but in all, it is a great script. Thanks man. It accomplishes everything I was trying to do.

Dr_Zoidberg · Joined: 29 Dec 2006 Posts: 60

I didn't include rotation for the nunchuk, because i like to hold the nunchuk without worring about rotations and therefore used flicking. (I haven't updated my script to distinguish between left and right that will be included in the next version.) I have concentrated mainly on the IR part, thats why the rest of the script is rather simple.
I you haven't allready tried it, I recommend changing the values of the speed factors (or even the areas) to adjust the turning rate and range.

rambozo79 · Joined: 15 Mar 2007 Posts: 7