Hi, I’m Matt and I’m a big fan of LDraw and, of course, LEGO. I've been building LEGO in all forms since I could talk – I actually was playing LEGO before I could talk… I’d love to tell you about a related product I’m building that I think you might be interested in.

Form is an app you use to invent amazing things and order them to your door. Using a combination of simple parts (beams, axles, joints, gears) and intelligent parts (processors, batteries, motors, sensors) you can create sophisticated toys, robots or machines. In fact, you can design almost anything you can think of. Or you can browse what other people have made and build their creations instead.

First, design your invention and then hit order. Once your creation arrives, follow the step-by-step instructions to put it together. Whatever you’ve designed – whether it's the ultimate remote control car, quadcopter or roller coaster – you can control it and view all the live sensor data using our app.

If you love your invention you can share it with the community. All shared designs are free to build, you just need the required parts. If another builder doesn’t have all the parts to build your invention, then they can order any extras they need. Each time someone orders parts to build your invention, you are rewarded with money, or credits for more parts.

We’re building a user base of those who are interested in the product and are keen to help us develop it further. We’re making steps everyday and will be sharing our progress with those who join our newsletter – including early previews of all the parts. I’d love to get your input and for you to be amongst the first to find out more.

Sign up here http://www.buildwithform.com

Thanks,
Matt
[email protected]

Hi,
It would be great to have the following new parts from Speed Champions sets available for LDraw/MLCad/LeoCAD/etc..
Here's their description;
Front 4X3X2/3 W. Bow » http://brickset.com/parts/design-11291
Windscreen 4X5X1 1/3 W/Stu » http://brickset.com/parts/design-18972
Windscreen 4X6X1 1/3 W/Studs » http://brickset.com/parts/design-18973
Brick W/Arch 2X4X2 1/3 » http://brickset.com/parts/design-18974
Brick 2X4X1 1/3 W/Ø4.85 Cutout » http://brickset.com/parts/design-18975
Rim Ø18X12 W Cross \U0026 Stud » http://brickset.com/parts/design-18976
Tyre Low Ø24X12 » http://brickset.com/parts/design-18977
Hub Cab Ø15 No.1 » http://brickset.com/parts/design-18978
Hub Cab Ø15 No.2 » http://brickset.com/parts/design-18979
1/2 Circle Plate 2X6 » http://brickset.com/parts/design-18980
Thanks for reading!
Cheers! :-)

Hi Everybody,

I am a new guy here and looking for a part which is very simple.
The brick size is 1x1 in round tube with stud(diagram in pink) but height is as the orange square brick show.

Can any one local this part for me ? Or help to creatr it.

Truly thanks for help.
Andrew

Attached Files

Thumbnail(s)
   

I've been playing with a simple JSON export in LDCad 1.5 alpha to see if its worth the effort in regards to the introducing a second HL library topic.

It resulted in this extremely light weight welGL renderer. This is far from a full featured LDraw renderer but it demonstrates the ease of doing so when using a new HL LDraw library format.

The JSON structure is readable in the test's javascript source. For now the format only includes polygons (excluding textures).

The test also raised some questions we need to awnser if we ever want to setup some official JSON LDraw format, My main concerns / discussion points I would like to throw into the group are:

How to split the geometry data

In the example I basically dumped the LDCad OpenGL vertex data into a single array (made out of continues pos/nor pairs). Alternative could be to first list all unique positions, normals and tex coords individually and also setup separate index arrays for them per mesh. The enduser software can then construct any kind of buffer they need. Optionally ignoring normals and / or texture coordinates etc.

Webgl (one of the main end users of the format) has no QUAD support, should we therefore drop quads in the fileformat to?

For now I converted the quad indices to triangle indices while keeping them separated. That way you can transform them back when needed.

How to handle non BFC parts
Non bfc parts are handled with dual lighting inside LDCad so these export tests will cause problems for non bfc parts. So how do we handle non bfc parts in the JSON files? Ether by duplicating all data or by setting some flag so the enduser handles it with a different shader or by drawing everything twice (CW and CCW) or something.

This is the official call for volunteers on the LDraw.org Standards Board (LSB).

The LSB is responsible for maintaining semi-regular internal discussions on pending file format issues, the overall progress of the LDraw file format and new or proposed developments made by different LDraw-based software authors. They adopt new official standards by voting on them, and publish documentation on LDraw.org following such a decision. The LSC has documented and will document past, current and future LDraw File Formats.

With revision 1.5 of the LSC Charter the number of seats is restricted to 4 since one seat is reserved for a current LDraw Library Administrator.

Most urging issues are:

• LDraw File Format 2.0 (Discussions here and here)
  
• Standard for a connection database (Discussion here)
  
• Define TEXMAP resolution and naming conventions (Discussion here)
  

• Authored at least two LDraw parts subsequently released in an Official LDraw.org Parts Update
  
• Served as a reviewer on the Parts Tracker through at least 2 official parts updates, and posted at least 5 reviews in at least two updates since their initial participation
  
• Released a still available software program that is compliant with either the LDraw 1.0.0 spec or another spec published by the LSB
  
• Petition for nomination as an LSB candidate approved by 2 current LSB members
  
• Petition for nomination as an LSB candidate made to the LSB by at least 5 others eligible to be LSB candidates
  

Hi forum,

I'm going to design several custom Lego compatible parts.
First I'll create 3D model and then print it on my 3D printer.
I'm familiar with SketchUp, but it seems is not very suitable for Lego parts.

Is it possible to use LDraw for that?

Could you please recommend other CAD software suitable for me?

Thank you very much.

Hello,

On the off chance that someone else finds this interesting, I would like to introduce the OpenSDraw builder. This builder is a little different in that it provides a domain specific language for creating MOCs instead of a GUI interface. The language is built on Python, but the language itself is a prefix language like Scheme or Lisp. The project includes a customized editting mode for emacs. The project also includes a GUI part finder, but I'm sure better ones exist. You will probably need to some Python skills to get it to work for you.

The project is here:
https://github.com/HazenBabcock/opensdraw

The documentation and some examples are here:
http://hazenbabcock.github.io/opensdraw/

This project was inspired by OpenSCAD, a solid 3D CAD modeler, thus the name.

Best,
-Hazen

Now you can download new version of LEGO Instruction Book Creator at https://code.google.com/p/licreator/

Please, share you comments here. In next version one wish per person will be graded**. I you put more that one I selected only one - randomly. This list will be closed at May 20, 2015 at 20:20

** maximally 10 in total. If I can do it.

Changes related to previous 0.8.501 version Wrote::: Set minimum size of width and height of application
:: Assistant now display properly
:: Fixed group of miscellaneous bugs
:: Key TAB can now work in loop
:: Added ability to re-opening current Instruction book
:: Disable real-time preview for speed-up and avoid crash situation
:: Added the ability to positioning the preview of sub-model from then menu
:: LicColor class can now use colors from LDConfig.ldr file
:: Remember now latest import location
:: Re-organize configuration file
:: Added switch options to monitoring L3P ,POV-Ray activities
:: Added option to restore data source of imported model
:: Added delimitation of the notification area for tool-tip and other
:: Added information about value of current zoom
:: Handling AttributeError exception for:
:: - getPartBoundingBox
:: - callGLDisplayList
:: - renderFinalImageWithPov
:: - updatePersistentIndices
:: Rewritten LicPovrayWrapper class
:: Provided information about license and author
:: Support of custom colors of user /0x, opaque; 0x02, opaque; 0x03, 50% Alpha/
:: Support of invisible color /0x07, 10% Alpha/
:: NOTICE: POV-Ray calls work only on instruction without submodels

Hello to all,
I will upload the Space police II models that I made .
You can use it freely, I give it 'Free ONLY for NON-Commercial Use' .
At the time are referred as "Unofficial model" but only because they were not verified by other people.
In case of errors or problems reported me. Thanks.

Here are some notes for possible improvements.

They collected all the models of the Space police II series.

There are 7 box-sets that I organized in 1 mpd for each one.
The set 3015 is not present, it is the same of 1916.

If there are moving parts (hooks, trailers, tippers, ...) I created more ldr files for a single object in order to simplify a possible next animation.
In order not to complicate the archive, however, the wheels have been incorporated into the one file ldr of the vehicle.
In the mpd file of a box-set, each vehicle has its own independent structure (ldr file).

The basic idea is to assign names to the following :
xxxx [x ] - [ yyy ] - [ z ] - [ u]
xxxx [ x ] is the code box ( four or five digits)
yyyyyy is the option code for the second box , if the vehicle is a combination
z is the progressive optional for different independent models inside the box
u is a letter optional for the parts that make up the model , and that can move between them.

As for the choice of colors, I tried to respect those provided by Lego, but it is possible that some have escaped me.

I did not use stickers: I do not like in real life and I prefer not to use them even in the virtual world.
I did not realize the minifiugres in the box-sets.

Ldr files were introduced in the steps for building: do not reflect the official ones of the instruction manual.
The models are built bottom-up.

The vehicles are all oriented with the longitudinal axis x and muzzle in a positive direction.

Now stop write, it's time to load the models!
I hope you enjoy them as I liked building them!

I apologize, I'm trying to get LDraw running for my son to create his own Lego instruction manuals. We went through installation with the AIOI, selecting the option to have a desktop icon, and got the message that installation was completed successfully. Yet, there's no desktop icon, and when I search for "LDraw" I get no results. We're running Windows 8. The LDraw folder is in my Program Files (x86) folder, and contains folders: "LDView, LPub, LMCad, Tutorials, Web Links. Does LDraw not run on Windows 8?

Thanks!