I, finally, released 1.6b

It contains mostly bugfixes and tweaks and some minor changes/additions, including:

- Fixed numerous scripting issues.
- Fixed some (mostly minor) editing issues.
- Improved part bin search.
- Extensive POV-Ray export tweaking, I mostly tried to improve transparency in mixed color parts and the handling of textured parts.
- Duplo and electrical part bin sections.
- Snapping/mirroring info for commonly used parts in the 1701 and 1801 libraries.
- Some new/tweaked templates based upon 1701/1801 parts.


Hopefully this will be the last 1.x version as I want to concentrate on 2.0 exclusively from now on, unless a very severe bug/problem is uncovered.


The Linux version is still compiled on Debian 7.5 as I didn't think it would be very useful to setup 32 and 64 bit 8.1 environments. This is very time consuming, so I prefer to do that only if people having problems with these versions on more recent distro's. Please Let me know if so. I did however fully updated the 7.5 environments.

Enjoy:
http://www.melkert.net/LDCad/download

I decided to spend a few minutes today with ldraw to see how fantastic all the latest stuff is.  Since I tend to use linux these days I started with the linux getting started instructions.  Almost right away I hit a small snag.  The link to make-list didn't work.  Instead I got a 404 error.  But oddly, once I'd navigated there manually from the github project page the link from the ldraw wiki did work.  However that got me thinking.  The complete.zip file contains an ancient Windows mklink.exe executable and a small zip file with the C source code.  Why not also include the make-link bash script inside the complete.zip file?  It's tiny, so space is not an issue, and it would solve the problem with unreliable links on the internet.

Hi there,

Would someone be kind enough to author that Lasso part : 99253.



Is is available on Digital-Bricks.

Thanks a lot.

Could we - in a commune effort - get these:

http://www.ldraw.org/cgi-bin/ptreviewsum...rainwheels

fixed and certified?

Thanks, w.

Hi users and thanks in advance for my newbie question.

I'm new to the group so i hope this is a suitable section to post.

I have created a patterned tile (3068b) using Ldraw Pattern Editor and the provided part template.
Having completed my desired pattern and exported the file as a .dat file, I have then put the .dat file into Bricklinks Stud.io software following this guide.

Quote:Re: Custom Parts
[url=http://forum.bricklink.com/viewtopic.php?p=2238&sid=786117d04d8e474e4f62b00aece95ed4#p2238][/url] Tue Dec 12, 2017 5:50 am
Hi, we currently support custom parts in .dat file format and below is a tip on adding custom parts to your local Stud.io app. 
Please note adding custom parts other than guided below could cause glitches. 

How to add custom parts
1. Go to the Stud.io folder of the installed directory and click ldraw folder (Stud > ldraw)
2. Create a new folder under ldraw and name it as Custom Parts
3. Create another folder under the folder Custom Parts and name it as Parts
4. Add your custom parts under the Parts folder
> A new folder “Custom Parts” will appear under My Folders upon restart of the app
*Please do not make random changes to the existing categories or directory. It could cause unexpected glitches.

Hope this helps and if you have any questions, please do not hesitate to reply 

 
Folder location: 
MAC:
Users > YOUR USERNAME > .local > share > Stud.io > CustomParts
(Note: to see the hidden folders in your user folder(.local), press Shift+Cmd+>.)

Windows: 
find it under \Users\{UserName}\AppData\Local\Stud.io\CustomParts

Hope this would work!!!! 

Hi all,

I cannot get the Mac version of LPub3D to render any bricks or assembly images.
I think I pointed to the LDraw folder, but I guess not?
How to do this?

Hi

since a few days I try to figure out how to create a kind of 'light bar' in pov-ray. I mean a for example a 1x4 plate which seems to emit light from its surface like shown in the pov tutorial with the command looks_like.

I started with a smal example:

I used a transparent brick (LDXColor79) and an area light with 4 light in a row placed exactly on the surface of the transparent brick.
What I do not like in the result is that the brick does not seem to emit light. I would like to have just a plain white surface.

Then I changed the colour of the plate to white:


Here I had to move the area light slightly above the surface in order not to get blocked. But this is still not the look I wanted. Therefore pov-ray has the looks-like command.

If I try to use the looks-like command in the light source definition I have to point to an object name, i.e. the name of the brick. I searched the line in the pov-script where the object is defined...

Quote:// Author: LDraw
object {
        lg_3710
        matrix <0,0,-25,-25,0,0,0,-25,0,0,0,0>
        LDXSeamMatrix(80, 12, 20, 0, 2, 0)
        matrix <1,0,0,0,1,0,0,0,1,0,-32,0>
        #if (version >= 3.1) material #else texture #end { LDXColor15 }
}

Quote:#declare lightbar =    object {
        lg_3710
        matrix <0,0,-25,-25,0,0,0,-25,0,0,0,0>
        LDXSeamMatrix(80, 12, 20, 0, 2, 0)
        matrix <1,0,0,0,1,0,0,0,1,0,-32,0>
        #if (version >= 3.1) material #else texture #end { LDXColor15 }
    }

I'd try to do these myself but my time to work on these things is very limited. Anyway:

87079pr0012 Tile 2 x 4 with Brickheadz Seasonal Calendar print
32606 Friends Accessories Flower with 7 Thick Petals and Pin

Do we have sub-parts of the relevant upper and lower legs? 

I have not seen a hip/legs combo inthe library so far. Am I right to say that those are not yet modeled?

Shall we model them or just realize those parts as "print" on the normal legs?

Hello all,
I have what I hope to be a simple question... I'm using LPub to make instructions for a large 10k piece model.  I'm well aware of the ROTSTEP command, which was critical in ensuring the right perspective at all times.

The problem is that I would like to add a completely blank step showing just the rotation action, so the reader can see the new perspective *before* adding the parts for the next step.  I tried the following seemingly obvious schema, but the extra "step" is being discarded. - I can only assume that LPub has logic to ignore "Step" commands where no parts were added.