You can reach an open and free chatroom for LDPartEditor here

http://bloochat.com/ldpartedit

to contact me and maybe other users of LDPartEditor.

Hi all,

As suggested in the Eurobricks forum thread I decided to share my personnal LGEO library.

Last Version:

   - LGEO Library - Darats  - 2019/07/03
   - LGEO.xml - Darats  - 2019/07/03


My library is a bit different from the original LGEO one:
I have usually 2 files per part :

   - lg_xxxx.inc (LGEO file containing Patterns and Studs)
   - xxxx.inc (High quality STL file converted into PovRay format)

While waiting for a better solution, you will need to add :
#declare L3LDrawToLgeo = transform { matrix <0,-LG_BRICK_WIDTH/20,0, 0,0,-LG_BRICK_HEIGHT/24, -LG_BRICK_WIDTH/20,0,0, 0,0,4*LG_BRICK_HEIGHT/24> }
#declare L3LgeoToLDraw = transform { matrix <0,0,-20/LG_BRICK_WIDTH, -20/LG_BRICK_WIDTH,0,0, 0,-24/LG_BRICK_HEIGHT,0, 0,0,0> }
at the end of your lg_defs.inc file (just above the very last "}") or use my own lg_defs.inc provided in the package (but it might conflict with Owen's one on some parts).


You may want to put the lg_xxxx.inc files in your usual LGEO directory and the xxxx.inc files in another folder (don't forget to declare it in PovRay or it will not find the requested files)
There is a high probability that some Parts already exist in the Official LGEO library or other users-made ones. Be aware of it if you overwrite some file.

You need to put LGEO.xml in your Ldview install directory (be aware that you will overwrite your own file that might have parts that mine doesn't have).
Be carful: this xml file might give errors until I fully release all the parts that are in it (should be a matter of a few weeks).

When colors are needed (for Patterns for instance) it uses Ldview exported material format (LDXColorx).
My package doesn't contains lg_color.inc, but it must be accessible by PovRay.


I'm sharing all my xxxx.inc files, but as I'm currently cleaning the lg_xxxx.inc files, I will make regular release of them (so during that time, there will be xxxx.inc files without lg_xxxx.inc files (so not usable) but I will do my best to release everything fast).

The unpacked archive will be more than 1.5 Gb because of the high quality STL files, don't be feared of that, but make sure that you have enough hard drive space for it.


Do not hesitate to test it, ask questions and give me feedback here, it works on my system but I don't know if it will in others.

I've been using LDraw for a good number of years, but I've never done much with stickers before. The one time I did use one it came out backwards and I just assumed something was wrong with that sticker so I flipped it over.

Now I'm working on something which will likely use a lot of stickers and the first sticker I placed (not the one I used previously) exhibited the same problem, so I added about 20 more and they all behave the same way.

To be clear: I place the sticker against (or a fraction in front of) a brick. Both MLCad and LDView correctly show the front face of the sticker. But a POV-Ray render shows the empty back face of the sticker. If I flip the sticker 180deg then POV-Ray now renders it correctly, but I'm now only seeing the back face in MLCad and LDView.

Is this just a bug in LDView's .pov export? or is there an incorrect setting buried in a file somewhere that is affecting these? I can live with flipping them, but it would be nice to be able to see them properly in MLCad/LDView as well as POV-Ray without having to write a script to auto-flip them all for POV-Ray.

Part Request:
Tile, Round 2 x 2 with Red Fan Pattern
http://www.bricklink.com/catalogItem.asp?P=4150px20
http://www.peeron.com/inv/parts/4150px20
http://bricker.info/parts/4150px20/

Can't find any higher resolution image than the enlarged one at bricklink.

Also, on the subject of round tiles:
98138pd11.dat "Tile Round 1 x 1 with Pink Doughnut Pattern"
... should be named "Tile 1 x 1 Round with..." for consistency - e.g. MLCad sorting.

I've just got very sad news from Australia:

Robyn Jessiman Wrote:I have to inform you and the ldraw community, that James's father died on 17th February this year. He had been sick for 25 years, really, and had struggled through 7 Heart attacks and lots of problems with diabetes and kidney problems, and succumbed finally to a further heart attack. One thing I am content about is that he did not have to go into care; I was always able to look after him. Heaven's Computer and now Accounting work will be well looked after.

Could you please spread this information around, please.

Kind regards

Robyn Jessiman

This meta would be followed by a short string (max length to be defined, 6 chars is probably OK) containing the length of the element (or any other string that would help distinguish a part from another). That string would be displayed next to the part image in BOMs and in editors parts bin. Counting holes or studs in tiny thumbnails of a part is tedious at best, distinguishing a 9L axle from a 10L one is next to impossible...
Possible extension:
0 !BOM V string
where V would be a "verbose level", the editor or BOM generator would only display text below some user defined level. It would be the responsability of part author to set this level at a sensible value, 1 beeing "most useful to be displayed", 2 "useful", 3 "if you insist you may display this"...

Hello,

as I wrote a few times before, that I am very motivated to fix the last "unknown" bugs in the code of LDPatternCreator (LPC).

The main problem is, that I am not able to reproduce some of the critical errors.

Here is a list of issues which require in my opinion more investigation:

1. From time to time, LPC "forget" the information of primitives. The geometry is still there (triangles, etc.), but the primitives are gone.
   
2. Sometimes, the information of the background image offset and scale is missing.
   

The Steering Committee [1] has selected the following volunteers for the 2015/2016 Standards Board (in alphabetical order):

Chris Dee (seat reserved as current LDraw Library Administrator)
Roland Melkert
Ben Supnik

The SteerCo has opted for the lowest required number of people to streamline the upcoming processes as much as possible. Their accounts have already been upgraded for the LSB forum.

More information on the LSB can be found in the LSB charter.

[1] Try not to confuse the LDraw.org Steering Committee (SteerCo) with the LDraw.org Standards Board (LSB). The Steering Committee sets the course for the LDraw Organization while the Standards Board deals with the LDraw File Format.

Congratulations to the new and a huge thank you to the outgoing members!

Willy Tschager
On behalf of the LDraw.org Steering Committee

For Example.
I have 42026: Black Champion Racer. And I have build bigger version with larger wheels and so on.
What I need to know is
:: how much and what part is necessary
:: availability of the used parts

Tell me, What you think about this opportunity. And propose how handle it.

Hello to all

I'm using LeoCAD 0.82.0 (latest) on Linux Ubuntu 14.04 (install using this)
I'm using LDraw 2014-02 library without "parts.lst" file.
All work fine.

Now I try to add "LS02.dat" & "LS100.dat" parts to generate input to LSynth.
As soon as I add the .dat files, on next LeoCAD start, I see these parts LeoCAD part browser.
But parts are invisible i.e. without any graphic displayed.
Can a person explain me my wrong way?