I downloaded 3.1 and am sorry to have encountered both of these problems (reported elsewhere on this board):
and
Both issues kick me out of TIR, are quite frequent and threaten to ruin one of my favorite applications. Please help.
Specs:
TIR 1 hardware
TIR 3.1 software
P4 2.8GB, ATI Radeon 9800
1GB RAM
Windows XP Pro
LOMAC demo
2 major glitches with 3.1
Re: 2 major glitches with 3.1
I get both errors. The offset motion screen doesn't crash my software though. I also have a P4, 2.6 800mhz FSB, what's your motherboard? For a work around, try reinstalling and not saving a profile to be in enhanced mode at startup.
[ November 05, 2003, 07:26 PM: Message edited by: Snake122 ]
[ November 05, 2003, 07:26 PM: Message edited by: Snake122 ]
Re: 2 major glitches with 3.1
Bahger,
Try this instead of my previous suggestion. I'm assuming you have a hyperthreading P4. For a temporary fix try setting the Affinity to only CPU 0. See if that fixes the problem, seems to so far with mine. Only setting the 3.01 Affinity to a single CPU means all your other programs should still use HT. To set Affinity, run 3.01 and hit ctrl=alt=del, go to the processes tab if it isn't already, right click on the Naturalpont, click on the Set Affinity option and uncheck CPU 1. Let me know if this works for you. It should at the very least fix the wayward tracking screen.
Try this instead of my previous suggestion. I'm assuming you have a hyperthreading P4. For a temporary fix try setting the Affinity to only CPU 0. See if that fixes the problem, seems to so far with mine. Only setting the 3.01 Affinity to a single CPU means all your other programs should still use HT. To set Affinity, run 3.01 and hit ctrl=alt=del, go to the processes tab if it isn't already, right click on the Naturalpont, click on the Set Affinity option and uncheck CPU 1. Let me know if this works for you. It should at the very least fix the wayward tracking screen.
Re: 2 major glitches with 3.1
Snake: Many thanks for the advice. I will reset the Affinity value but before I do, can you just confirm that it will not affect any other application?
The wayward tracking screen is ugly but, on reflection, seems not to affect performance. Do you have any thoughts about the "abnormal program termination" message, which does?
Again, many thanks.
The wayward tracking screen is ugly but, on reflection, seems not to affect performance. Do you have any thoughts about the "abnormal program termination" message, which does?
Again, many thanks.
Re: 2 major glitches with 3.1
The crash smells like a reentrant problem or missing thread lock...but I'v enot done much specific Windows coding on their thread model to be certain...
Re: 2 major glitches with 3.1
quote:Originally posted by Bahger:
Snake: Many thanks for the advice. I will reset the Affinity value but before I do, can you just confirm that it will not affect any other application?
The wayward tracking screen is ugly but, on reflection, seems not to affect performance. Do you have any thoughts about the "abnormal program termination" message, which does?
Again, many thanks.Bagher, so far on my system, it fixed the double tracking screen and seems to fix the runtime crash. Setting the Affinity of naturalpoint.exe will not effect the HT performance of other programs, but the downside is that you will have to do the set affinity dance everytime you start 3.01.
You could also try my original suggestion of not turning on the "Remember mode at Startup" option in the motion page. It seems to fix the crash on wwsensei's system, but not mine after I use it for a while.
Please let me know what works for you so we can narrow do what the real fixes are.
Snake: Many thanks for the advice. I will reset the Affinity value but before I do, can you just confirm that it will not affect any other application?
The wayward tracking screen is ugly but, on reflection, seems not to affect performance. Do you have any thoughts about the "abnormal program termination" message, which does?
Again, many thanks.Bagher, so far on my system, it fixed the double tracking screen and seems to fix the runtime crash. Setting the Affinity of naturalpoint.exe will not effect the HT performance of other programs, but the downside is that you will have to do the set affinity dance everytime you start 3.01.
You could also try my original suggestion of not turning on the "Remember mode at Startup" option in the motion page. It seems to fix the crash on wwsensei's system, but not mine after I use it for a while.
Please let me know what works for you so we can narrow do what the real fixes are.
Re: 2 major glitches with 3.1
I posted this in A. Fokker's thread, but will add it here. I also have HT CPU running with HT on....trying Snake's Affinity setting did correct the problem ( setting it to use CPU 0 ).
I know one of the testers and he has a HT machine, but runs with HT off, and he never experienced this problem. So, as a workaround, looks like we can either set Affinity each time we boot the software, or turn HT off.
Thanks Snake for locating and suggesting this.
I know one of the testers and he has a HT machine, but runs with HT off, and he never experienced this problem. So, as a workaround, looks like we can either set Affinity each time we boot the software, or turn HT off.
Thanks Snake for locating and suggesting this.
Re: 2 major glitches with 3.1
quote:Originally posted by Nealg:
I posted this in A. Fokker's thread, but will add it here. I also have HT CPU running with HT on....trying Snake's Affinity setting did correct the problem ( setting it to use CPU 0 ).
I know one of the testers and he has a HT machine, but runs with HT off, and he never experienced this problem. So, as a workaround, looks like we can either set Affinity each time we boot the software, or turn HT off.
Thanks Snake for locating and suggesting this.No problem, glad I could help!
I posted this in A. Fokker's thread, but will add it here. I also have HT CPU running with HT on....trying Snake's Affinity setting did correct the problem ( setting it to use CPU 0 ).
I know one of the testers and he has a HT machine, but runs with HT off, and he never experienced this problem. So, as a workaround, looks like we can either set Affinity each time we boot the software, or turn HT off.
Thanks Snake for locating and suggesting this.No problem, glad I could help!
Re: 2 major glitches with 3.1
quote:Originally posted by Snake122:
Please let me know what works for you so we can narrow do what the real fixes are.Will do.
The silence from the board mods has been deafening; do you think they are working on a fix? Do they intend to address this or leave it to the users to find a workaround? I'm just curious, as I've found Naturalpoint to be very responsive to their customers in the past. Right now, though, they've got Beta software posing as retail.
[ November 06, 2003, 12:18 PM: Message edited by: Bahger ]
Please let me know what works for you so we can narrow do what the real fixes are.Will do.
The silence from the board mods has been deafening; do you think they are working on a fix? Do they intend to address this or leave it to the users to find a workaround? I'm just curious, as I've found Naturalpoint to be very responsive to their customers in the past. Right now, though, they've got Beta software posing as retail.
[ November 06, 2003, 12:18 PM: Message edited by: Bahger ]
Re: 2 major glitches with 3.1
quote:Originally posted by Bahger:
quote:Originally posted by Snake122:
Please let me know what works for you so we can narrow do what the real fixes are.Will do.
The silence from the board mods has been deafening; do you think they are working on a fix? Do they intend to address this or leave it to the users to find a workaround? I'm just curious, as I've found Naturalpoint to be very responsive to their customers in the past. Right now, though, they've got Beta software posing as retail.I bet they are working on it. They've been pretty busy with the TrackIR2 launch. I'd expect to see a fix sometime soon as lnog as we can pin down exactly what causes and fixes it. That's why everybody who had this problem should please post what fix worked for you. Also be fairly sure of it, I thought a couple of times reinstalling and not selecting the "Remember mode at startup" would fix the C++ runtime crash, but in the long run it actually didn't. But I'm 95% sure that that HT and/or multiple processors are the cause of the C++ runtime crash and the double tracking screen.
quote:Originally posted by Snake122:
Please let me know what works for you so we can narrow do what the real fixes are.Will do.
The silence from the board mods has been deafening; do you think they are working on a fix? Do they intend to address this or leave it to the users to find a workaround? I'm just curious, as I've found Naturalpoint to be very responsive to their customers in the past. Right now, though, they've got Beta software posing as retail.I bet they are working on it. They've been pretty busy with the TrackIR2 launch. I'd expect to see a fix sometime soon as lnog as we can pin down exactly what causes and fixes it. That's why everybody who had this problem should please post what fix worked for you. Also be fairly sure of it, I thought a couple of times reinstalling and not selecting the "Remember mode at startup" would fix the C++ runtime crash, but in the long run it actually didn't. But I'm 95% sure that that HT and/or multiple processors are the cause of the C++ runtime crash and the double tracking screen.