LDRAW model issues (missing and wrong placed parts)

[Michael Klein]

Hello,

I am back with some tests to render LDRAW-models. I am stucked with the set 8653 Enzo Ferrari I found here:
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=213769

The renderings look correct. Theres a .mpd file to download.

LDView and MLCad are reporting errors.

The problem is that there are missing parts:
X783.DAT
X311.DAT
X310.DAT
X312.DAT
X346.DAT

Some models are also not correctly placed/rotated:
http://clip2net.com/s/3psSxyj

BTW: The model can't be loaded into LDCad 1.4. No idea why.

Thank you very much for your time and help to investigate and fix the issue.

Michael

[Philippe Hurbain]

Ah the old problem of people who don't include unofficial parts in their mpd...

These parts have been renumbered when their real part number became known.
x346 -> 41669
x783 -> 32556
x311 -> 32495
x312 -> 32494
x310 -> 32496

Here is the query to part tracker that allows to find history of a part:
http://www.ldraw.org/cgi-bin/tracker/act...s/x310.dat

And for some reason the ls40 part that was used for this model had a weird origin/orientation, explaining the misplaced issue. I have no idea how to revert properly to the version of ls40 used in this file (except by trial and error)...

Finally, LDCad seems to display nothing because of the spring code included in main model. If you comment out the section between 0 MLCAD SPRING 383 140 0 125 -1 0 0 0 0 1 0 1 0 42 10 20 2 2 2 and 0 MLCAD SKIP_END, the model displays fine.

[Roland Melkert]

Finally, LDCad seems to display nothing because of the spring code included in main model. If you comment out the section between 0 MLCAD SPRING 383 140 0 125 -1 0 0 0 0 1 0 1 0 42 10 20 2 2 2 and 0 MLCAD SKIP_END, the model displays fine.

Yes type 2..5 lines are currently not supported at the model level. It will cause the whole model to be 'degraded' to being a part. Next this part will be prepared for rendering but it having more render data then a set maximum prevents that. If you move the MLCad spring code to a submodel it should load normally. A future version will do that automatically for all MLCad generated blocks.

[Michael Klein]

Great. Thx a lot. I will check this out.

[Michael Heidemann]

This is a task for MPDCenter

The problem of displaying correctly in LDCad still exists, but that is a task for LDCad.

Please see attached file.