 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi all,
I've been doing renders for quite some time now, but a new model I'm trying to
convert keeps running into problems. I keep getting the error message "cannot
find file 'ldd-*****.bin' even after trying to append file type extension" (with
the ***** replaced by the Lego part number.)
At first I thought it was limited to the newer parts, but it's even doing it
with older parts. What am I doing wrong?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.06.2018 um 20:59 schrieb Elwood:
> I've been doing renders for quite some time now, but a new model I'm trying to
> convert keeps running into problems. I keep getting the error message "cannot
> find file 'ldd-*****.bin' even after trying to append file type extension" (with
> the ***** replaced by the Lego part number.)
>
> At first I thought it was limited to the newer parts, but it's even doing it
> with older parts. What am I doing wrong?
Please note that your question is very specific to whatever tool you're
using to convert from LDD to POV-Ray; while you may encounter people
here that use LDD with the same tool and might therefore be able to
provide /some/ support for it, you may get better support in a forum
dedicated to the converter tool.
Presuming you're using the "LDD to POV-Ray Converter", the most
important question is whether you are getting the error message for
/every/ part, or just some: For instance, can you render a simple
standard 2x4 brick?
If you get the error message for all parts, my best bet is that the
"Callback File System" used by the converter might not be set up
properly, or that you didn't add `Library_Path="\\.\LDDIncludes"` to
your `povray.ini` file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for the reply. Yes I'm using the LDD to POV-RAY Converter. No it's not
every brick. It seems to be most of the bricks from the LDD update in February
plus random bricks that have been in the LDD library for a long time, such as
the 2x1 brick with 'o' clip.
As I said, the error message says "cannot find file 'ldd-*****.bin' even after
trying to append file type extension" (with the ***** replaced by the Lego part
number).
I've tried reinstalling all programs (Converter, POV for Windows, LDD), but
still no luck.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Not sure where my other reply went. Yes I'm using LDD to POV and as I said it
seems to be most of the parts from the LDD update in Feb, but also random older
pieces.
However, it's now got worse. After another reinstall, I'm getting the message
"cannot find file 'ldd_colors_declarations.bin' even after trying to append file
type extension".
Under that in blue it says "\\.\LDDIncludes\ldd_default_colors.inc" line 20:
Parse Error: Cannot open include file ldd_colors_declarations.bin.
Driving me mad.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 06/22/2018 05:07 AM, Elwood wrote:
> Not sure where my other reply went. Yes I'm using LDD to POV and as I said it
> seems to be most of the parts from the LDD update in Feb, but also random older
> pieces.
>
> However, it's now got worse. After another reinstall, I'm getting the message
> "cannot find file 'ldd_colors_declarations.bin' even after trying to append file
> type extension".
>
> Under that in blue it says "\\.\LDDIncludes\ldd_default_colors.inc" line 20:
> Parse Error: Cannot open include file ldd_colors_declarations.bin.
>
> Driving me mad.
From
http://ldd2povray.lddtools.com/index.php?p=3_2_Running-the-application
Why POV-Ray™ reports "Parse Error: Cannot open include file
ldd_default_colors.inc', even after trying to append file type extension."
This error appears when the Library_Path in POVRAY.ini does not contain
\\.\LDDIncludes, LDD to POV-Ray Converter is not running or POV-Ray is
64bit and LDD to POV-Ray Converter is 32bit.
+++
Oy freakin' vey! It installs a device driver?? That's a pretty obtuse
way to convert from one format to another.
http://ldd2povray.lddtools.com/index.php?p=3_1_Installation
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.06.2018 um 12:34 schrieb dick balaska:
> +++
> Oy freakin' vey! It installs a device driver?? That's a pretty obtuse
> way to convert from one format to another.
> http://ldd2povray.lddtools.com/index.php?p=3_1_Installation
There's a reason behind this:
The LDD software is an original proprietary piece of software by the
LEGO company, and comes with pretty exact definitions of all the LEGO
pieces.
The LEGO company considers the part definitions proprietary information,
and would normally not tolerate any 3rd party to reverse-engineer them
and create a piece of software that would allow the information to be
exported in a different format.
The author of the LDD to POV-Ray Converter seems to have reached a
special agreement with the LEGO company (not sure whether express or
silent) that they tolerate (and maybe even support the creation of) this
particular piece of software. Apparently the LEGO company recognizes
POV-Ray as an established tool to render LEGO models.
However, /the/ major condition for this special agreement seems to be
that the converter must make converted piece definitions available only
to approved pieces of software, which most notably includes official
POV-Ray for Windows v3.7.0, but no unofficial builds, nor even most
development builds.
To meet this condition, the LDD to POV-Ray Converter cannot convert
piece definitions to actual include files for later rendering (because
that would make the data available to arbitrary software). Instead,
corresponding include "files" are provided via a special driver, which
listens to the path `\\.\LDDIncludes\` and produces the necessary files
"onl the fly" from the original LEGO data -- but only to whitelisted
applications. Other applications trying to access that path will get
nothing.
So while at first glance this approach might /seem/ obtuse, it is pretty
much the only way LEGO will allow LDD models to be rendered with POV-Ray.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks. Yeh, I've been reading all of these pages, and it tells me why something
has happened but not how to rectify it. I cannot understand why it now won't
render any of my LDD models - yesterday it was just the one model with the
problems now it's completely knacked.
It now keeps crashing or hanging when I try to use it. Think I'll use
Bluerender.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.06.2018 um 13:30 schrieb clipka:
> So while at first glance this approach might /seem/ obtuse, it is pretty
> much the only way LEGO will allow LDD models to be rendered with POV-Ray.
As a side note, this also means that we need to be careful about adding
export functionality to POV-Ray, because if we're doing it wrong, such a
version of POV-Ray will not be eligible to work with the LDD to POV-Ray
Converter.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.06.2018 um 13:32 schrieb Elwood:
> Thanks. Yeh, I've been reading all of these pages, and it tells me why something
> has happened but not how to rectify it. I cannot understand why it now won't
> render any of my LDD models - yesterday it was just the one model with the
> problems now it's completely knacked.
You'll have to start POV-Ray, from the `Tools` menu choose `Edit master
POVRAY.INI`, and in that file, add the line:
Library_Path="\\.\LDDIncludes"
or
Library_Path="//./LDDIncludes"
(either one should work)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 22.06.2018 um 13:32 schrieb Elwood:
> > Thanks. Yeh, I've been reading all of these pages, and it tells me why something
> > has happened but not how to rectify it. I cannot understand why it now won't
> > render any of my LDD models - yesterday it was just the one model with the
> > problems now it's completely knacked.
>
> You'll have to start POV-Ray, from the `Tools` menu choose `Edit master
> POVRAY.INI`, and in that file, add the line:
>
> Library_Path="\\.\LDDIncludes"
>
> or
>
> Library_Path="//./LDDIncludes"
>
> (either one should work)
Right - now getting an error window saying "Unable to generate necessary
includes. Root element is missing".
If I check the 'don't generate includes' it goes back to the parsing error
"cannot find file 'ldd_colors_declarations.bin'"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
