Lovely Calibration Errors

[Ghost_Train]

I just spent 30 minutes wanding and got the best results every.
Then as I was about to click calculate....literally 1 second before...hand on the mouse...finger ready to click...

CALIBRATION ERROR

All I did was change the setting "Refine" to "Full"

All wanding data lost.

Please make an update where and error like this does not cause Arena to forget all the collected wanding data. Such a frustrating waist of time when that happens.

[NaturalPoint - Mike]

What version of software were you running at the time?

[Ghost_Train]

1.8.1
I have run into the same problem in past versions as well.
The whole wanding process seems very sensitive.
There have been many times where I'm still on the floor wanding, nearly done and then I see that dreadful red box appear around the wanding data area. I have yet to discover a cause. It happens less then it used to. Maybe something in the updates helped.

[Ghost_Train]

And of coures, the good ol Error that happens for no good reason.
Never fails to ruin my morning when I come in to work early to mocap and spend the whole time just trying to get a good calibration without an error.
Maybe it has trouble if the computer's processor is too slow. Then it gets too much info at some random point and decided to lock up with an error.

[NaturalPoint - Mike]

What are the specs of the system?

[Ghost_Train]

Manufacturer: HP-Pavilion
OS: Windows 7 Ultimate 64-bit (6.1 build 7601)
Model: AW018AV-ABA e9210t
Processor: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz (4 CPUs), ~2.5GNz
Memory: 8192MB RAM
Page file: 1982MB used, 14397MB available
DirectX 11
Graphic Card: NVIDA GeForce 8400GS

[NaturalPoint - Mike]

Hmm, with 24 cameras that might be a bit much for the Core2 quad. What does the CPU usage look like in the task manager during calibration? Perhaps you may want to evaluate your computer's performance during the calibration with perfmon running in the background? I'd recommend the following monitors to start:

Processor:
%processor time (You can do this per core, too, to see if one core is pegged)
interrupts/sec

Memory:
Page reads/sec
Page writes/sec

Physical Disk
%disk time

Compare them to the system running arena pre-calibration, see if anything appears to be getting excessively high