LDraw.org Discussion Forums

When I use part 6141 (plate 1x1 round) LDCad crashes on my machine @ home (old laptop with low specs).
This is an alias ("~moved to" or "=moved to") parts. Isn't that strange too?
Using 4073.dat everything runs fine.

I know there must be more parts that cause crashes.

4073 is actually the moved to part. It's moved to 6141. 
Both work fine in my LDcad (both 1.5 and 1.6) though. I've never had a certain part crash LDcad

(2016-05-31, 18:16)Jaco van der Molen Wrote: [ -> ]When I use part 6141 (plate 1x1 round) LDCad crashes on my machine @ home (old laptop with low specs).
This is an alias ("~moved to" or "=moved to") parts. Isn't that strange too?
Using 4073.dat everything runs fine.

I know there must be more parts that cause crashes.

Is this in the last 1.5 version, as it reminds me of the bug


I fixed in 1.5 beta 1a

Right. I work with the normal 1.5 version, not beta.
And, loading LDCad the round 1x1 plate is not currently visible in the partbin, only in the model.
The strange thing is that when loading a model all these blue and green + signs are visible while rendering the model.
Only where the round 1x1 plate is going to be, it looks very different. Seems no + signs but blue dots or something. I'll try to make a screenshot before the crash to illustrate this later today.
And the crash does not happen with the same model on my PC at work.

(2016-05-31, 18:22)Merlijn Wissink Wrote: [ -> ]4073 is actually the moved to part. It's moved to 6141. 

Ah, right. My mistake :-)

(2016-06-01, 5:46)Jaco van der Molen Wrote: [ -> ]And, loading LDCad the round 1x1 plate is not currently visible in the partbin, only in the model.
The strange thing is that when loading a model all these blue and green + signs are visible while rendering the model.
Only where the round 1x1 plate is going to be, it looks very different. Seems no + signs but blue dots or something. I'll try to make a screenshot before the crash to illustrate this later today.
And the crash does not happen with the same model on my PC at work.

Blue crosses are files being loaded/parsed.

Green crosses are files (waiting to) being prepped for rendering.

Yellow crosses are files of which the render prep failed, maybe the gpu is out of memory or something, The logfile might give some more insight.

Red crosses are missing files.

Here is what it looks like where the 1x1 round plates should be using 6141:

[attachment=2328]

A few parts render complete then crash.

(2016-06-02, 17:53)Jaco van der Molen Wrote: [ -> ]A few parts render complete then crash.

Could you send me the logfile(s) as it should indicate which part/file it was working on during the crash.

(2016-06-02, 19:22)Roland Melkert Wrote: [ -> ]Could you send me the logfile(s) as it should indicate which part/file it was working on during the crash.

OK, I'll clear the logs and start a fresh one.

Sorry Roland, didn't have time yet to reproduce the crash and send the logs. Will do this a.s.a.p.

LDCad keeps crashing here (old laptop). Now in a model without 6141.
Though 6141 is mentioned in the log?
Here is that log, Roland. Perhaps you can take a look?

(2016-06-28, 17:53)Jaco van der Molen Wrote: [ -> ]LDCad keeps crashing here (old laptop). Now in a model without 6141.
Though 6141 is mentioned in the log?
Here is that log, Roland. Perhaps you can take a look?

I'm afraid the log isn't very helpful. Are you sure you are using the latest ldraw library? If not which version are you using.

Also the used model might shed some light on it (mail it directly if you don't want to share it).

I'll take a closer look in a couple of days.

OK, I am pretty sure I have the latest update, but might reinstall.
I'll mail you the model.

(2016-06-28, 19:36)Jaco van der Molen Wrote: [ -> ]OK, I am pretty sure I have the latest update, but might reinstall.
I'll mail you the model.

I think you are using the 1402 library as I got 1.5 to crash looking for 6143 in the part bin when using the 1402 complete.zip as main lib

It seems the above mentioned alias in part bin bug isn't fixed after all. I'll reopen it.

edit: upgrading to the 1502 lib should fix the issue too.

OK, thanks for finding out. As said, I am unsure I had the latest update.
I have 4 machines I work with LDraw on, so I probably thought I updated them all, but forgot my old laptop.
I'll install and let you know if it solves the problem.