| |
I found two more things that are styming my progress
1. LPub quits on error if a part has a color other than 16 for the
X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
and colors other than 16 aren't technically illegal either, just not very
common.
2. The checkbox under the L3P tab for Exclude Non-POV code doesn't seem to
apply to all LPub generated POV files. I have some primitives in my P
folder custom modified to sub in POV code. For some reason POV stops on
error if I don't exclude the non POV code but LPub doesn't seem to always
use this option when the checkbox for it is checked
On more thing I just thought of,
Can a feature be added to LPub to mabybe add colored dots or diamonds to the
images with flexible stuff to denote which flexible tube is what length.
I'll see if I can come up with an example image if you need one.
-Orion
|
|
| |
In lugnet.cad.dev, Orion Pobursky writes:
> On more thing I just thought of,
>
> Can a feature be added to LPub to mabybe add colored dots or diamonds to the
> images with flexible stuff to denote which flexible tube is what length.
> I'll see if I can come up with an example image if you need one.
>
> -Orion
Some more on this,
This idea doesn't have to confine to just color coded dots, it could also
encompass lengths for pneumatic hoses as well. Maybe an added parameter to
the PLIST BEGIN SUB meta command or an extension to LSynth.
-Orion
|
|
| |
In lugnet.cad.dev, Orion Pobursky writes:
> I found two more things that are styming my progress
>
> 1. LPub quits on error if a part has a color other than 16 for the
> X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
> and colors other than 16 aren't technically illegal either, just not very
> common.
Example please.
>
> 2. The checkbox under the L3P tab for Exclude Non-POV code doesn't seem to
> apply to all LPub generated POV files. I have some primitives in my P
> folder custom modified to sub in POV code. For some reason POV stops on
> error if I don't exclude the non POV code but LPub doesn't seem to always
> use this option when the checkbox for it is checked
Quite possibly. I'll run through all calls to L3P and see what I can come up
with.
>
> On more thing I just thought of,
>
> Can a feature be added to LPub to mabybe add colored dots or diamonds to the
> images with flexible stuff to denote which flexible tube is what length.
> I'll see if I can come up with an example image if you need one.
This is a good idea. Jennifer Clark first suggested this for pneumatic hoses.
My first throught is to have a special end cap part for these things that we
can set the color for, but it gets tricky. You can't use the entire flex-axle
end piece with a special end cap, because the flex axle has a specific color,
and the end cap a different color. LDraw file format only allows for one color
parameter per part usage. So we could provide a fixed list of end caps with
hard coded colors, or possibly post-process the POV file to replace the end cap
color after conversion to POV.
Obviously the first one seems easier to me.
Kevin
>
> -Orion
|
|
| |
In lugnet.cad.dev, Kevin L. Clague writes:
> In lugnet.cad.dev, Orion Pobursky writes:
> > I found two more things that are styming my progress
> >
> > 1. LPub quits on error if a part has a color other than 16 for the
> > X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
> > and colors other than 16 aren't technically illegal either, just not very
> > common.
>
> Example please.
Try this:
1 0 0 0 0 1 0 0 0 1 0 0 0 1 stud.dat
1 0 0 0 0 1 0 0 0 1 0 0 0 1 4-4edge.dat
A little further investigation reveals that LPub quits on error no matter
what the color of the edge. The exact error I'm getting is:
'L3P failed for file lupbtest.dat part 4-4edge.da color 0. Cannot continue'
-Orion
|
|
| |
In lugnet.cad.dev, Orion Pobursky writes:
> In lugnet.cad.dev, Kevin L. Clague writes:
> > In lugnet.cad.dev, Orion Pobursky writes:
> > > I found two more things that are styming my progress
> > >
> > > 1. LPub quits on error if a part has a color other than 16 for the
> > > X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
> > > and colors other than 16 aren't technically illegal either, just not very
> > > common.
> >
> > Example please.
>
> Try this:
>
> 1 0 0 0 0 1 0 0 0 1 0 0 0 1 stud.dat
> 1 0 0 0 0 1 0 0 0 1 0 0 0 1 4-4edge.dat
>
> A little further investigation reveals that LPub quits on error no matter
> what the color of the edge. The exact error I'm getting is:
>
> 'L3P failed for file lupbtest.dat part 4-4edge.da color 0. Cannot continue'
Please try to run lpubtest.dat through L3P manually. I do not have a way to
continue if L3P finds an error in the file.
You may need to talk to Lars about this one.
Kevin
>
> -Orion
|
|
| |
In lugnet.cad.dev, Kevin L. Clague writes:
> In lugnet.cad.dev, Orion Pobursky writes:
> > In lugnet.cad.dev, Kevin L. Clague writes:
> > > In lugnet.cad.dev, Orion Pobursky writes:
> > > > I found two more things that are styming my progress
> > > >
> > > > 1. LPub quits on error if a part has a color other than 16 for the
> > > > X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
> > > > and colors other than 16 aren't technically illegal either, just not very
> > > > common.
> > >
> > > Example please.
> >
> > Try this:
> >
> > 1 0 0 0 0 1 0 0 0 1 0 0 0 1 stud.dat
> > 1 0 0 0 0 1 0 0 0 1 0 0 0 1 4-4edge.dat
> >
> > A little further investigation reveals that LPub quits on error no matter
> > what the color of the edge. The exact error I'm getting is:
> >
> > 'L3P failed for file lupbtest.dat part 4-4edge.da color 0. Cannot continue'
>
> Please try to run lpubtest.dat through L3P manually. I do not have a way to
> continue if L3P finds an error in the file.
>
> You may need to talk to Lars about this one.
>
> Kevin
>
> >
> > -Orion
I did that already just to make sure and got no error.
Here's some more info I've found troubleshooting
This error seems to occur when LPub thinks the X-Xedge.dat primitive are
parts for the Construction Images and BOM. In other words LPub runs a file
through L3P in which the only element is the X-Xedge.dat primitive. This
will result in an empty POV file and therefore an error.
-Orion
|
|
| |
In lugnet.cad.dev, Orion Pobursky writes:
> In lugnet.cad.dev, Kevin L. Clague writes:
> > In lugnet.cad.dev, Orion Pobursky writes:
> > > In lugnet.cad.dev, Kevin L. Clague writes:
> > > > In lugnet.cad.dev, Orion Pobursky writes:
> > > > > I found two more things that are styming my progress
> > > > >
> > > > > 1. LPub quits on error if a part has a color other than 16 for the
> > > > > X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render • edges
> > > > > and colors other than 16 aren't technically illegal either, just not very
> > > > > common.
> > > >
> > > > Example please.
> > >
> > > Try this:
> > >
> > > 1 0 0 0 0 1 0 0 0 1 0 0 0 1 stud.dat
> > > 1 0 0 0 0 1 0 0 0 1 0 0 0 1 4-4edge.dat
> > >
> > > A little further investigation reveals that LPub quits on error no matter
> > > what the color of the edge. The exact error I'm getting is:
> > >
> > > 'L3P failed for file lupbtest.dat part 4-4edge.da color 0. Cannot continue'
> >
> > Please try to run lpubtest.dat through L3P manually. I do not have a way to
> > continue if L3P finds an error in the file.
> >
> > You may need to talk to Lars about this one.
> >
> > Kevin
> >
> > >
> > > -Orion
>
> I did that already just to make sure and got no error.
>
> Here's some more info I've found troubleshooting
>
> This error seems to occur when LPub thinks the X-Xedge.dat primitive are
> parts for the Construction Images and BOM. In other words LPub runs a file
> through L3P in which the only element is the X-Xedge.dat primitive. This
> will result in an empty POV file and therefore an error.
Ah, this is different than what you first described.
LPub tries to ignore primitives when making PLIs and BOMs. I wonder why it
missed these.
I can recommend a work around:
PLIST BEGIN IGN
PLIST END
Kevin
>
> -Orion
|
|
| |
"Kevin L. Clague" <kevin_clague@yahoo.com> skrev i meddelandet
news:HDpArM.n2J@lugnet.com...
> In lugnet.cad.dev, Orion Pobursky writes:
> >
> > On more thing I just thought of,
> >
> > Can a feature be added to LPub to mabybe add colored dots or diamonds to • the
> > images with flexible stuff to denote which flexible tube is what length.
Why not have an invisible LDRAW part with color, just like the LIGHT.DAT?
--
Anders Isaksson, Sweden
BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm
Gallery: http://user.tninet.se/~hbh828t/gallery/index.htm
|
|
| |
In lugnet.cad.dev, Orion Pobursky writes:
> I found two more things that are styming my progress
>
> 1. LPub quits on error if a part has a color other than 16 for the
> X-Xedge.dat primitive. This shouldn't matter since L3P doesn't render edges
> and colors other than 16 aren't technically illegal either, just not very
> common.
Fixed.
>
> 2. The checkbox under the L3P tab for Exclude Non-POV code doesn't seem to
> apply to all LPub generated POV files. I have some primitives in my P
> folder custom modified to sub in POV code. For some reason POV stops on
> error if I don't exclude the non POV code but LPub doesn't seem to always
> use this option when the checkbox for it is checked
Found it in part list image rendering, thanks. Fixed it.
>
> On more thing I just thought of,
>
> Can a feature be added to LPub to mabybe add colored dots or diamonds to the
> images with flexible stuff to denote which flexible tube is what length.
> I'll see if I can come up with an example image if you need one.
I think that in the case of LSynth I can make this happen, but otherwise I
think this is going to have to be left as "an exercise for the student".
>
> -Orion
Kevin
|
|
|
