Subject:
|
Re: LPub Error Message?
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Sun, 12 Dec 2010 15:30:05 GMT
|
Viewed:
|
19489 times
|
| |
|
|
In lugnet.cad, Travis Cobbs wrote:
| |
In lugnet.cad, Dave Schuler wrote:
| |
I can run LDView with general success, but check this out: I noticed after
posting last night is that I get a different error message in LDView. I’m
not sure of the exact phrasing, but it appears to result from part-files not
starting with BFC statements. LDview corrects this by inserting a
NOCERTIFY, but subsequent BFC commands seem to trip this up.
I should note that I’m working with older LDraw parts and a bunch of *ahem*
custom elements, so their header formats may not be fully compatible with
the current versions.
Thanks for looking into this, and thanks for your hard work!
|
The error from LPub appears to indicate and LDView crash. Any errors or
warnings in LDView’s “Errors and Warnings” dialog indicate problems that
LDView detected in the parts that it was given. Having said this, while
LDView does treat files without a 0 BFC command at the top as
non-BFC-certified, this is correct behavior. Here is a direct quote from the
BFC spec:
In order for a file to be processed with back face culling, there must be at
least one 0 BFC meta-statement before the first operational command-line. If
there is no such 0 BFC meta-statement in the file, BFC processing will be
disabled for that file.
Having said this, one might argue that that LDView’s error messages are
confusing, since all BFC commands in the file generate an error saying “BFC
command after NOCERTIFY command.”. However, since the very first such BFC
line generates an error that says “First BFC command isn’t the first action
in file; changing to NOCERTIFY”, LDView is in fact doing exactly what it said
it was doing.
|
Thanks, Travis.
It appears that the problem does indeed arise from an incompatibility between
the accepted part-file format and the format of my custom elements. AFAIK, the
parts used to match the official LDraw format, but that may have been quite
a few iterations ago.
I’ll play around with some of the files to see if I can get them to work; if so,
then I guess I’ve got some BFC statements to add.
One other thing... Presumably LDView expects all sub-parts and primitives to
match the same format too? That is, should they all have a BFC command as the
first action?
|
|
Message has 1 Reply:
 | | Re: LPub Error Message?
|
| (...) Sorry for the delay. Yes, all sub-parts and primitives must have some BFC command prior to the first action in order for BFC processing to be enabled for the sub-part/primitive. (This is typically 0 BFC CERTIFY, incidentally.) --Travis (14 years ago, 16-Dec-10, to lugnet.cad, FTX)
|
Message is in Reply To:
| | Re: LPub Error Message?
|
| (...) The error from LPub appears to indicate and LDView crash. Any errors or warnings in LDView's "Errors and Warnings" dialog indicate problems that LDView detected in the parts that it was given. Having said this, while LDView does treat files (...) (14 years ago, 6-Dec-10, to lugnet.cad, FTX)
|
18 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
