|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.06.2018 um 14:36 schrieb Elwood:
> clipka <ano### [at] anonymousorg> 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".
That would be a message from the LDD to POV-Ray Converter. I'm not
familiar enough with the tool to help you out there.
My wild guess would be that the converter can't find the LDD installation.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 06/22/2018 08:36 AM, Elwood wrote:
> clipka <ano### [at] anonymousorg> 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)
The only time I ever use \\ is for Windows pseudo-devices or device drivers.
That's too deep for me to trust //. I've not seen anyone else use // .
(Although it appears to be working because he got past the
ldd_default_colors.inc problem)
>
> Right - now getting an error window saying "Unable to generate necessary
> includes. Root element is missing".
That sounds like an upstream problem. That message is not in POV-Ray.
>
> If I check the 'don't generate includes' it goes back to the parsing error
> "cannot find file 'ldd_colors_declarations.bin'"
Are you mixing 32 bits driver with 64 bit POV-Ray?
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Success!!!
After lots of reading and comparing it was a very simple thing to correct.
On the LDD to POV-RAY Converter, clicking on the 'settings' button brings up a
menu. I clicked on 'Setup paths' and this opens a window with two file path bars
(and a third one that can't be edited).
The second bar says 'Output path for includes:'
Mine said:
"C:\Users\Elwood\AppData\Roaming\LEGO Company\LEGO Digital Designer\LDDInc"
I changed it to say:
"C:\Users\Elwood\AppData\Roaming\LEGO Company\LEGO Digital Designer\LDDIncludes"
Yep - just changed the last word from 'LDDInc' to 'LDDIncludes' and everything
is now working perfectly - in fact it's rendering faster than before.
Hopefully this will help anyone else in the same situation. Still don't know why
it just suddenly happened though.
Thanks to all for their thoughts.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have bad news: LEGO removed the download link to LDD from their
website. So there's no official way for us to even diagnose the problem
you're having.
Mike
On 6/21/2018 2:59 PM, Elwood wrote:
> 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
|
|
| |
| |
|
|
|
|
| |