Very sweet, but a possible bug/instability
Very sweet, but a possible bug/instability
Got my first ever TrackIR (TIR3pro) yesterday.
Took it for a spin today in LO-MAC.
I must say (like everyone else) WOAH! I can't believe I've managed to do without it all this time.
A very nice product there, Naturalpoint.
I'm still getting used to it. One of my problems is that I tend to turn my head a little bit to the right if I'm turning right etc which pans the view. I guess its a normal reflex.
I've been fiddling around with the software, to get to know it and I stumbled upon this (sorry if it has been reported earlier).
I don't know if its a bug or some instability on my computer (which just got pre-loaded a couple of hours ago).
If I switch between enhanced-mode and mouse-mode without turning off the TIR, the software crash and close (illegal op).
If I switch off the TIR and then switch from mouse to enhanced or vice versa, then turn the TIR back on everything is fine.
No biggie though.
System:
P-IV 3GHz, Asus P4C800, 4x512MB Kingston 2.5CL 400MHz, GF6800GT w/61.77, WinXP w/SP2, TIR sw 3.12, latest Asus USB-drivers.
Took it for a spin today in LO-MAC.
I must say (like everyone else) WOAH! I can't believe I've managed to do without it all this time.
A very nice product there, Naturalpoint.
I'm still getting used to it. One of my problems is that I tend to turn my head a little bit to the right if I'm turning right etc which pans the view. I guess its a normal reflex.
I've been fiddling around with the software, to get to know it and I stumbled upon this (sorry if it has been reported earlier).
I don't know if its a bug or some instability on my computer (which just got pre-loaded a couple of hours ago).
If I switch between enhanced-mode and mouse-mode without turning off the TIR, the software crash and close (illegal op).
If I switch off the TIR and then switch from mouse to enhanced or vice versa, then turn the TIR back on everything is fine.
No biggie though.
System:
P-IV 3GHz, Asus P4C800, 4x512MB Kingston 2.5CL 400MHz, GF6800GT w/61.77, WinXP w/SP2, TIR sw 3.12, latest Asus USB-drivers.
Re: Very sweet, but a possible bug/instability
Forgot to add the error-log from the eventlog.
code:Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 27.08.2004
Time: 19:44:49
User: N/A
Computer: SHADS
Description:
Faulting application naturalpoint.exe, version 3.1.1.0, faulting module naturalpoint.exe, version 3.1.1.0, fault address 0x0000ac82.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 61 74 ure nat
0018: 75 72 61 6c 70 6f 69 6e uralpoin
0020: 74 2e 65 78 65 20 33 2e t.exe 3.
0028: 31 2e 31 2e 30 20 69 6e 1.1.0 in
0030: 20 6e 61 74 75 72 61 6c natural
0038: 70 6f 69 6e 74 2e 65 78 point.ex
0040: 65 20 33 2e 31 2e 31 2e e 3.1.1.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 61 63 38 32 0d 0a ac82.. [/code]
code:Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 27.08.2004
Time: 19:44:49
User: N/A
Computer: SHADS
Description:
Faulting application naturalpoint.exe, version 3.1.1.0, faulting module naturalpoint.exe, version 3.1.1.0, fault address 0x0000ac82.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 61 74 ure nat
0018: 75 72 61 6c 70 6f 69 6e uralpoin
0020: 74 2e 65 78 65 20 33 2e t.exe 3.
0028: 31 2e 31 2e 30 20 69 6e 1.1.0 in
0030: 20 6e 61 74 75 72 61 6c natural
0038: 70 6f 69 6e 74 2e 65 78 point.ex
0040: 65 20 33 2e 31 2e 31 2e e 3.1.1.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 61 63 38 32 0d 0a ac82.. [/code]
Re: Very sweet, but a possible bug/instability
Shadow,
I will have a look at this. I have switched between Absolute and Relative mode without this happening. Are you running your unit through an unpowered hub?
I will have a look at this. I have switched between Absolute and Relative mode without this happening. Are you running your unit through an unpowered hub?
Re: Very sweet, but a possible bug/instability
quote:Originally posted by Wayne:
Shadow,
I will have a look at this. I have switched between Absolute and Relative mode without this happening. Are you running your unit through an unpowered hub?No, it's connected directly to one of the 4 ports on the back of the motherboard (ASUS P4C800).
Also running latest USB-drivers from Asus.
Shadow,
I will have a look at this. I have switched between Absolute and Relative mode without this happening. Are you running your unit through an unpowered hub?No, it's connected directly to one of the 4 ports on the back of the motherboard (ASUS P4C800).
Also running latest USB-drivers from Asus.
Re: Very sweet, but a possible bug/instability
This sounds like the same issue I just emailed you about Wayne.
Looking at Shadows system specs, we are very similiar. Perhaps an issue with the ASUS USB as mine also has the 4 USB ports back panel (I'll try it in another slot when I get the chance).
My specs:
P4-2.8c 800FSB HT
ASUS P4P800
Kingston 1 gig (2x512 matching) RAM
ATI 9800 Pro (4.8)
WinXP w/SP1
Looking at Shadows system specs, we are very similiar. Perhaps an issue with the ASUS USB as mine also has the 4 USB ports back panel (I'll try it in another slot when I get the chance).
My specs:
P4-2.8c 800FSB HT
ASUS P4P800
Kingston 1 gig (2x512 matching) RAM
ATI 9800 Pro (4.8)
WinXP w/SP1
Re: Very sweet, but a possible bug/instability
Update:
Same thing happends if I press the hotkey for Precision and motionmode (F7 and F8).
Also tried remapping them to something else and still same issue.
Tried setting USP to full-speed too in BIOS. Makes no difference.
[ September 16, 2004, 11:48 AM: Message edited by: Shadow ]
Same thing happends if I press the hotkey for Precision and motionmode (F7 and F8).
Also tried remapping them to something else and still same issue.
Tried setting USP to full-speed too in BIOS. Makes no difference.
[ September 16, 2004, 11:48 AM: Message edited by: Shadow ]
Re: Very sweet, but a possible bug/instability
Just an update (if you're interested).
I no longer have this crashing issue.
I had a unstable CPU that I recently RMA'ed to Intel. Now I'm running the same computer but with an older CPU (P-IV 1.8) in and it works fine toggling relative/enhanced mode etc without turning it off first.
Will report back on the behaviour when the replacement CPU arrives (P-IV 3).
I no longer have this crashing issue.
I had a unstable CPU that I recently RMA'ed to Intel. Now I'm running the same computer but with an older CPU (P-IV 1.8) in and it works fine toggling relative/enhanced mode etc without turning it off first.
Will report back on the behaviour when the replacement CPU arrives (P-IV 3).
Re: Very sweet, but a possible bug/instability
Shadow,
Thanks for the update, thats very interesting. Please let me know how you get on with the different CPU.
Thanks for the update, thats very interesting. Please let me know how you get on with the different CPU.
Re: Very sweet, but a possible bug/instability
I experienced same problems. And, I reported it to Wayne. I think he is working on it.
The problems I reported is like below.
Shadow Please let me know the detailed fix by replacing CPU.
1) When I press F8 (Motion mode change) several times at the �Motion� screen. It causes an error like below.
*** But this error only happens when I loaded any profile. Before loading a profile, the error does not occur. ***
AppName: naturalpoint.exe
AppVer: 3.1.1.0
ModName: naturalpoint.exe
ModVer: 3.1.1.0
Offset: 0000ac82
2) Autoload function with 'Lock-On:Modern Air Combat' does not work. (but, with GTR, works well.)
3) I turned off the Hotkeys for �Motion Mode� and saved it to my own profile. But, when I reopen the profile, �Motion Mode� option is �On� again (rechecked). So, I can not save the state of �Motion Mode�.
[ November 18, 2004, 05:21 PM: Message edited by: Seyoung ]
The problems I reported is like below.
Shadow Please let me know the detailed fix by replacing CPU.
1) When I press F8 (Motion mode change) several times at the �Motion� screen. It causes an error like below.
*** But this error only happens when I loaded any profile. Before loading a profile, the error does not occur. ***
AppName: naturalpoint.exe
AppVer: 3.1.1.0
ModName: naturalpoint.exe
ModVer: 3.1.1.0
Offset: 0000ac82
2) Autoload function with 'Lock-On:Modern Air Combat' does not work. (but, with GTR, works well.)
3) I turned off the Hotkeys for �Motion Mode� and saved it to my own profile. But, when I reopen the profile, �Motion Mode� option is �On� again (rechecked). So, I can not save the state of �Motion Mode�.
[ November 18, 2004, 05:21 PM: Message edited by: Seyoung ]
Re: Very sweet, but a possible bug/instability
Finally got a replacement CPU (PIV 3).
I had one error when I toggled from Enhanced to mouse-mode. But I only got the error once. I must have toggled the modes atleast 20 times. Only the first time did it fail.
code:Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 24.11.2004
Time: 21:20:41
User: N/A
Computer: SHADS
Description:
Faulting application naturalpoint.exe, version 3.1.1.0, faulting module naturalpoint.exe, version 3.1.1.0, fault address 0x0000ac82.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 61 74 ure nat
0018: 75 72 61 6c 70 6f 69 6e uralpoin
0020: 74 2e 65 78 65 20 33 2e t.exe 3.
0028: 31 2e 31 2e 30 20 69 6e 1.1.0 in
0030: 20 6e 61 74 75 72 61 6c natural
0038: 70 6f 69 6e 74 2e 65 78 point.ex
0040: 65 20 33 2e 31 2e 31 2e e 3.1.1.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 61 63 38 32 0d 0a ac82.. [/code]
I had one error when I toggled from Enhanced to mouse-mode. But I only got the error once. I must have toggled the modes atleast 20 times. Only the first time did it fail.
code:Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 24.11.2004
Time: 21:20:41
User: N/A
Computer: SHADS
Description:
Faulting application naturalpoint.exe, version 3.1.1.0, faulting module naturalpoint.exe, version 3.1.1.0, fault address 0x0000ac82.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 61 74 ure nat
0018: 75 72 61 6c 70 6f 69 6e uralpoin
0020: 74 2e 65 78 65 20 33 2e t.exe 3.
0028: 31 2e 31 2e 30 20 69 6e 1.1.0 in
0030: 20 6e 61 74 75 72 61 6c natural
0038: 70 6f 69 6e 74 2e 65 78 point.ex
0040: 65 20 33 2e 31 2e 31 2e e 3.1.1.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 61 63 38 32 0d 0a ac82.. [/code]