Ok... got my time synced the lazy way, but at least its nist time... and both machines are within a constant second of each other
now either way i look at the data, I am getting all screwy timings... Even blew it away and reinstalled. I am sure that the checkpointing data and the updated time are conflicting, but my question is will this all even out on the next packet? should I just cool it till i get new work? any suggestions?
Originally posted by sachax Ok... got my time synced the lazy way, but at least its nist time... and both machines are within a constant second of each other
now either way i look at the data, I am getting all screwy timings... Even blew it away and reinstalled. I am sure that the checkpointing data and the updated time are conflicting, but my question is will this all even out on the next packet? should I just cool it till i get new work? any suggestions?
are you letting it complete a frame? If you have folding monitor on one PC and reboot the other, folding monitor will keep counting even if the other PC is down or not responding, when the pc without folding monitor completes a frame you will see your time go down gradually. After about five frames or so you should see your real folding time.
This morning all seems normal.. I was looking for a way to check on things remotely on all my networked boxes, so I can pull Folding Monitor through an SSH session now. All seems normal.