I don't want anyone to get me wrong here. I am an absolute fan of this software and it's concept but there are a few frustrations on the part to Nirvana.
I have finally got LazyTurn working on my desktop 'puter but I just cannot get a dxf file to open.
I am presented with Error Found, LazyTurn Art Code: O, Attempt Recovery.
And clicking yes has no effect, while clicking no asks me to send a message to MS and then shuts down LazyTurn.
I cannot find any reference to Art Code: 0 anywhere.
Some help please.
Is there going to be a standalone install for LazyTurn sometime?

Can you post the dxf file so i can have a look at it?
Eventualy LazyTrun will be standalone but until then follow the installation info given in the manual.

RICH

Hi Rich,
I think I've followed everything in the manual but it's difficult breaking old habits
Here is the dxf that I have tried most recently. I have also tried a few others but always end up with the same error.
Ross

Ross,
See appendix "B" in the manual, 3.6 Do not draw more than the top part / upper half of the profile....

See attached modified dxf.

RICH

Same result Rich. I had also tried your test file SECT_5_HCIR.dxf and still get the error message.
LazyTurn Art Code: 0
I should have pointed out, in my earlier post, that clicking Yes, for the Attempt Recovery option, just recycles the error message.

Those files should work...

May be an installation problem, so let me check something out and i will get back

RICH

Hi Rich,
I've included the error text file that is generated when LazyTurn is terminated.
Ross

watch for an answer from ART here:
http://www.machsupport.com/forum/index.php/topic,5767.msg103803.html#msg103803

RICH

Thanks for all your efforts Rich.
Ross

Hi Ross:

 In general an "ArtCode" is simply an indication to me where in the porogram an error occured. A 0 doesnt mean much. Its a divide by zero, question is where..

  Did you delete your lazyturn.xml as a test? If it still occurs after that Id recommend updating your video drivers as its usually an OpenGL error in a video driver that can cause that, ( or at least thats when Ive seen it occur..).

 
Art