LDraw.org Discussion Forums

Full Version: MLCad.ini 2018-01 update now available
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi folks,

I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2018-01. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.

Download the file from my website: http://www.holly-wood.it/mlcad/mlcad_ini-en.html

Bye, w.
(2018-02-06, 0:46)Willy Tschager Wrote: [ -> ]Hi folks,

I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2018-01. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.

Download the file from my website: http://www.holly-wood.it/mlcad/mlcad_ini-en.html

Bye, w.

Thanks!
thank you very much!

for a future release, could you add the missing line

Code:
31 - ELECTRIC_CABLE                       = SYNTH BEGIN ELECTRIC_CABLE 375

in the [LSYNTH] section, please?

That will enable MLCad to create electric cables.

This could/should be done already now, independently from:

The current element for that cable inside lsynth.mpd is already existing, but wrong/broken:
the cables get generated too thick.
Its section needs to be corrected to

Code:
0 FILE ELECTRIC_CABLE.ldr
0 ELECTRIC_CABLE SYNTHESIS DEFINITION
0 Name: ELECTRIC_CABLE.ldr
0 Author: Steffen [Steffen]
0 Unofficial Model
0 SYNTH BEGIN DEFINE ELECTRIC_CABLE HOSE STRETCH 9 35 0
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
0 SYNTH END

I'm seeking contact to Kevin to get this corrected in LSYNTH.
Could you maybe also update your
http://www.holly-wood.it/files/lsynth/LS...pd_3-1.zip
with this?

A usage example file is attached to this post
(2018-02-24, 22:06)Steffen Wrote: [ -> ]thank you very much!

for a future release, could you add the missing line

Code:
31 - ELECTRIC_CABLE                       = SYNTH BEGIN ELECTRIC_CABLE 375

in the [LSYNTH] section, please?

That will enable MLCad to create electric cables.

This could/should be done already now, independently from:

The current element for that cable inside lsynth.mpd is already existing, but wrong/broken:
the cables get generated too thick.
Its section needs to be corrected to

Code:
0 FILE ELECTRIC_CABLE.ldr
0 ELECTRIC_CABLE SYNTHESIS DEFINITION
0 Name: ELECTRIC_CABLE.ldr
0 Author: Steffen [Steffen]
0 Unofficial Model
0 SYNTH BEGIN DEFINE ELECTRIC_CABLE HOSE STRETCH 9 35 0
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
1 0 0 0 0 0 0 -1 0 1 0 1 0 0 993.dat
0 SYNTH END

I'm seeking contact to Kevin to get this corrected in LSYNTH.
Could you maybe also update your
http://www.holly-wood.it/files/lsynth/LS...pd_3-1.zip
with this?

Ok. I'll look into it. Please note that LSynth 3.1 is the work of Don Heyse.

w.
oh, I did not know this. when running the tool, it still output Kevin Clague's mail address as contact... :/
Code:
LSynth version 3.1 by Kevin Clague, kevin_clague@yahoo.com

Don, are you reading this? I've sent you a PM referring to the post above.

I edited the post above to attach an electric cable test example.
It's been a while since I did the work on lsynth 3.1, and it looks like the sourceforge site has fallen into disrepair in the meantime. 

So I'll see if I can manage to move it to github and incorporate the change.  Any tips on how to migrate a sourceforge project to github and retain the source history would be appreciated.  My github web skills are currently limited to a single picture embedded in the readme markdown, although that may actually suffice for lsynth.
I can easily help you with this if needed.

If your current repo on SourceForge is an SVN,
then you can easily open it using SmartGit and push it to github (history-preserving) as GIT repo.

If you need any assistance let me know via PM!

Actually, I like your idea to move to github a lot
because there people much more easily can suggest corrections to you via pull request.

As said - I'd be happy to help, I work with this all day.
I got the source code migrated from sourceforge CVS to github https://github.com/deeice/lsynth and updated the lsynth.mpd file.
Now I need to make a new installer with the mpd fix and a github web page to host the downloads.  But I'll probably take a nap first...
(2018-02-25, 13:46)Don Heyse Wrote: [ -> ]It's been a while since I did the work on lsynth 3.1, and it looks like the sourceforge site has fallen into disrepair in the meantime. 

So I'll see if I can manage to move it to github and incorporate the change.  Any tips on how to migrate a sourceforge project to github and retain the source history would be appreciated.  My github web skills are currently limited to a single picture embedded in the readme markdown, although that may actually suffice for lsynth.

I just did this for LDDP. As long as the code is in an SVN respository then all you need is the url and you can use Github import tool.
cool! thank you very much!
Pages: 1 2