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.
The problem is, I'm not sure where to go from here. I am a newbie when it comes to parts authoring (and this is cheating at best!), but I really need these parts in LDraw. Frankly, I could really use all of the parts mentioned in my post:
but none, to my knowledge, have been put on the parts tracker. The second pair aren't even in LDD. I know the community is not responsible for part requests, and I completely understand that it is a lot of work, but I still need those pieces, so I have tried to get as far as possible. I think one of the major things that needs to be done is the setting of the part center/rotation center. There may be more work beyond that which I don't even know about. If someone could guide me through the remaining steps, at least to the point where the part is functional, I would be much obliged.
-- I attached the parts if you would like to take a look at them. They are raw geometric data (if I have my vocabulary right) which runs up the file size, compared to official parts.
I was scrolling down this page here (http://www.digital-bricks.de/en/index.ph...ddp&mg=259) and noticed that all of the "Animal No. 5" (T-Rex) parts were available except the head and the tail, both parts simply reading "Not Available." I opened LDD, and found both these parts available in that program. For some reason, each part stand-in at the website had multiple part IDs. Perhaps this is a part of the problem?
I have unfortunately been unsuccessful in using the LDD2LDrawAddOn also downloadable from Digital-Bricks.de, possibly due to the fact that I use a Mac. Is anyone willing to help me figure out how to get access to these two pieces?
When I try to place part 99206
it does not snap to the bottom (2x2) plate but one plate higher (or lower depending on how you look at it) at the "plate 1x2" part of this piece?
This is the case when placing other parts on this part too: they snap to the wrong studs.
Currently I haven't much time to work on LDCad 1.6 but I can't help thinking about the next next version which might be 2.0.
This would also be the perfect moment to go open source.
I consider switching to JAVA or PYTHON but I think both are too slow and JAVA is also a bit messy imho.
So it probably be C++(11) again. If so it will reuse large chunks of the current 1.6 code but in a reworked state.
If I go open source I would also need to select a License (I would like to keep it non commercial only)., this is the thing I'm looking up to the most so if anyone has some pointers on that
Also I'm wondering if there are people who would be interested to help development by taking up e.g. the mac version dependencies etc.
One major improvement planned would be the rendering of the gui (I want to go full OpenGL with this, even for dialogs) and I also want it be multilingual.
An actual usable 2.0 will probably take more then a year to make after actually starting it, so I might do a parallel 1.7
I've looked through all the parts in LDD & Ldraw as well as on the .digital-bricks.de site, and I'm hoping maybe I just missed it? If not, it would be great to have.
I have developing next version of this tool. But I need discuss some topics with Remi Gagne. Did someone know how I can contact with Him.
And I have share work with some OSX user ready to test building process that depended on build.py script.
Is it me, or does LDCad not write a file when I "save as..."
I edited a file, saved it with another name, closed LDCad, restarted it later: no new file?
Admins. This is just a suggestion. Like Part Authors, does it not make sense to add a tag/designation to your community members who are also Application Developers ? It would be better if all contributors identified or even if those whose applications are included in the AIOI. Cheers.
![[Image: 99206.jpg]](https://img.bricklink.com/P/86/99206.jpg)
