forums.naturalpoint.com

Hey all,

I posted this awhile ago in the WWIIOL section. After being re-assured that it was probably not my TrackIR3 I started looking at all other things - I began to write it off as maybe bad memory, CPU over-heating. All sorts of different checkes...I even went out and purchased a new gfx board :0 - It's OK, I justified a 6800GT. I recently started using FS2004 - and guess what...It locked up...

Suddently my friend asks..."Hey do you think your TrackIR might be causing the problem?" - So here I am again and I've noticed a few other posts regarding intermittant locks that people think might be related to the TrackIR in IL2 as well. So before I go and buy an AMD64 - has there been any new headway to help users figure this stuff out??

Thanks

P-

piercer,

Can you be a little more specific about when your system locks up? There can be many reasons for a system lock up, so it may not be TrackIR's fault, but if it was then it�s my job to find out what it was.
Does this happen at a certain time, or when you change between Absolute and Relative modes, do you have your TrackIR software on the desktop or minimized.
Do you have listed in your Event Viewer which may provide an answer, normally Windows will save an error message.

I am sure there is a simple explanation to this.

Wayne -

I just noticed another thread a few down about people having something with motion mode - though this isn't what's happening with me, I also have an Asus board with 4 usb ports on the back. So here are my system specs:

Asus - A7V8X
1 GB DDR 2700
AMD XP 3000+
BFG 6800 GT
Nostromo N52 Keypad
Saitek EVO Stick

P-

Wayne - Thanks for the quick response. First let me say that I think the TrackIR3 is a great product, from the outside you give a very polished, customer oriented business - which I think is needed by most companies in this day and age - now back to my problem

First - Why might I think it's the TrackIR? My system has been running without any hiccups for the past 12 months. This particular problem crept up within a day of installing the 3.12 drivers (initial installation). The only caveat here is that I also upgraded XP (I'm running SP1 again now as Sp2 I found to many problems with - but still have the lock problem). Also, the lock ups haven't happened in any of my non-trackir based programs: Farcry, COD, Word, Excel, Firefox, ...

I'll also say that I work in the software industry, not that this means 'I know' or anything, but suffice to say the lock-ups are intermittant - I actually haven't been able to nail down a pattern except that the lock-ups are happening in games that use TrackIR, which I do know is a real Pain in the XXX to debug, because of the lack of use-case information.

What's a typical lock-up look like: I'm playing my game (with or without using the TrackIR at the moment) and suddenly the frame freezes, I can still hear the audio for about 5-10 more seconds. Then suddenly the audio goes into a continuous loop and I'm stuck. Once in a great while I can actually wait a minute and it will un-lock, but 99% of the time it sits their indeffinately.

Their are 3 things I have noticed.

1) If I'm playing WWIIOL and I switch (alt-tab) to the TrackIR desktop screen a few times and play with it, there is a much higher % chance of it locking. I have the desktop control always up.

2) Once in awhile when I reboot the machine TrackIR gives me an error saying it could not find the hardware and doesn't load properly.

3) I don't notice in my events log an exact correlation to lock-up time and error messages, but looking through the log I have gotten the following a few times:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 11/27/2004
Time: 5:19:36 PM
User: N/A
Computer: DAVE-9NYL0PFJNH
Description:
Faulting application naturalpoint.exe, version 3.1.1.0, faulting module cameradll.dll, version 0.0.0.0, fault address 0x00011d43.

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 63 61 6d 65 72 61 64 camerad
0038: 6c 6c 2e 64 6c 6c 20 30 ll.dll 0
0040: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0048: 74 20 6f 66 66 73 65 74 t offset
0050: 20 30 30 30 31 31 64 34 00011d4
0058: 33 0d 0a 3..

So, I'll go see if I can make it lock-up again and recheck the logs to see if their is a new entry. It did lock-up yesterday, but the timestamp on this entry is about 2 hours different than when it locked up, so this may be the error from not detecting the hardware that I got yesterday.

P-