 | | Re: LPub woes
|
|
(...) Thanks for the heads-up. I'll correct that in the next LDView release. I haven't edited the model in so long that I never noticed that some of the parts had moved. I suppose I should also add moved-to detection to LDView, and have LDView show (...) (19 years ago, 15-Dec-05, to lugnet.cad)
|
| |
| | RE: LPub woes - more info
|
|
Just the model file that comes with LDView 3.0 No spaces in any of the paths, and also no directories longer than 8 characters (so also no ~'s in the dosified paths) -----Original Message----- From: news-gateway@lugnet.com (...) (19 years ago, 15-Dec-05, to lugnet.cad)
|
| |
| | Re: LPub woes - more info
|
|
(...) What is m6459.ldr? Just a model file, or something special? Do you have file paths with blanks in them? If so, this is a problem. Not all the tools that LPub uses supports this. Kev (19 years ago, 15-Dec-05, to lugnet.cad)
|
| |
| | Re: LPub woes - more info
|
|
Uninstalled LDView and LPub2 (neither of which actually do a complete un-install as they leave registry keys, sub-directories, start menu items, etc lying around) Removed all traces of them. Install LDView 3.0 (13th Dec 2005 build) Set LDraw (...) (19 years ago, 15-Dec-05, to lugnet.cad)
|
| |
| | RE: LPub woes
|
|
Hi Travis, Unfortunately you're right in that it doesn't fix the LPub problems. One minor point, you may want to update the m6459.ldr file as some of the parts have been ~moved (and LPub can't cope with those as it looks in parts.lst for its (...) (19 years ago, 15-Dec-05, to lugnet.cad)
|
