| |
In lugnet.cad, Orion Pobursky wrote:
| |
In lugnet.announce, Travis Cobbs wrote:
| |
- Curve smoothing in POV-Ray exports.
|
This feature alone is awesome (and way better than mesh enhancer). Thanks
for the hard work.
|
You’re welcome. For many people, this will be the premier feature of LDView
4.1. I intended to include it in LDView 4.0, but decided it was better to get
the release out instead of delaying it just for that. It was not an easy
feature to implement.
| |
-Orion
P.S. Any plans to build in support for 3rd party POV part libraries (i.e.
LGEO, Anton, etc...)?
|
LGEO support is already there (via the LGEO.xml file in the installer). In the
POV Export options dialog, check the “Use XML mapping file” option. Then,
either leave the path field blank (to default to LGEO.xml in LDView’s install
directory) or browse to LGEO.xml yourself. Some people have customized their
LGEO.xml (and hopefully saved under a different filename, since I think the
installer will overwrite LGEO.xml) to use Anton parts in certain places.
However, that requires a POV-coded wrapper for each part, since Anton’s parts
are specified in POV files as a function call, where LGEO parts aren’t, and
LDView currently only supports the LGEO way of doing things.
--Travis
|
|
| |
In lugnet.cad, Travis Cobbs wrote:
| |
In lugnet.cad, Orion Pobursky wrote:
| |
In lugnet.announce, Travis Cobbs wrote:
| |
- Curve smoothing in POV-Ray exports.
|
This feature alone is awesome (and way better than mesh enhancer). Thanks
for the hard work.
|
You’re welcome. For many people, this will be the premier feature of LDView
4.1. I intended to include it in LDView 4.0, but decided it was better to
get the release out instead of delaying it just for that. It was not an easy
feature to implement.
| |
-Orion
P.S. Any plans to build in support for 3rd party POV part libraries (i.e.
LGEO, Anton, etc...)?
|
LGEO support is already there (via the LGEO.xml file in the installer). In
the POV Export options dialog, check the “Use XML mapping file” option.
Then, either leave the path field blank (to default to LGEO.xml in LDView’s
install directory) or browse to LGEO.xml yourself. Some people have
customized their LGEO.xml (and hopefully saved under a different filename,
since I think the installer will overwrite LGEO.xml) to use Anton parts in
certain places. However, that requires a POV-coded wrapper for each part,
since Anton’s parts are specified in POV files as a function call, where LGEO
parts aren’t, and LDView currently only supports the LGEO way of doing
things.
--Travis
|
Oh dear... I hope I did this.
I should add for Orion that it’s quite trivial to add parts in whatever library
you choose, especially if you make use of header files to do a lot of the mass
declares etc. It really is a fantastic conversion system and I’ve not looked at
l3p since using Travis’ earliest alphas of the conversion.
Tim
|
|
| |
In lugnet.cad, Travis Cobbs wrote:
| |
LGEO support is already there (via the LGEO.xml file in the installer).
|
As a note for OSX users, the LGEO.xml file is built into the .app package.
-Orion
|
|
| |
In lugnet.cad, Orion Pobursky wrote:
| |
In lugnet.cad, Travis Cobbs wrote:
| |
LGEO support is already there (via the LGEO.xml file in the installer).
|
As a note for OSX users, the LGEO.xml file is built into the .app package.
|
Thanks for pointing that out. For the default case (not creating a custom xml
file, and not filling in the path field), this made the most sense on the Mac.
For the advanced case, I’m hopeful that advanced users will know how to dig into
an app wrapper.
--Travis
|
|
|
