forums.naturalpoint.com

<t>Hi Wayne,<br/> <br/> I uninstalled 4.0.21, removed the NaturalPoint directory, and performed a reboot. I then installed 4.0.22, and again rebooted. So far I have not seen the keyboard issues mentioned previously. Maybe there was some type of residual files that was messing things up. <br/> <br/> ...

Hi Wayne,

Haven't had a chance to try them yet (still battling the tail end of pneumonia), but hopefully I can try it out tonight.

Thanks again for your help,
dradecki

<t>Hi Guys,<br/> <br/> Just wanted to let you know of a problem I'm having with the latest Beta software. I installed 4.0.22 because of the added support for Nascar SimRacing. After installing and rebooting my keyboard (my computer is a laptop), my keyboard began acting erratic. Most of the time I h...

I hadn't thought of that, good idea, it looks like it might work for me.

Thanks,
dradecki

<t>Hi All,<br/> <br/> I was wondering if anyone has come across an attachment that would allow the TIR2 to be temporarily mounted on a notebook screen. The manual mentions about placing it on your monitor or laptop but I can't find any such device anywhere out on the net. Any help would be greatly a...

Hi All,

Please tell me that this works also in F1C. I see the setting in the PLR file, butam unable to get it to work for me.

Thanks,
dradecki

<t>According to some of the other websites (or take this as heresay) the development team at ISI has say that all current efforts are to be directed towards the delivery of Nascar 2004. It looks like it will support TrackIR. Unfortunately all their Nascar games have compared weakly to what Papyrus h...

<t>Hi Jim,<br/> <br/> I did look at the spec, and all it states is the value can be in DWORD's (32-bit). It's very open ended and is left to the device driver writer to determine the granularity, which of course equates to whatever the hardware is capable of. If your hardware is capable of up to 15-...

<t>I now believe that the precision is based on the joystick driver being used. The DirectInput entries that are in the Registry (used for calibration, and deadzone) are DWORD's which means they are 32-bit values, which are easily capable of exceeding +/-1000 (many, many times over). This leads me t...

<t>You know that's a good question. But axis value precision is a relative term. It's probably not going to be as exact as say cx/cy values are for mouse cursor movement, but should be more then sufficient for an application like this. For example in the axis experiment I tried with a second joystic...