| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 173 online users.
» 1 Member(s) | 169 Guest(s)
Baidu, Bing, Google, N. W. Perry
|
| Latest Threads |
Custom Tiles from 10330 r...
Forum: Part Requests
Last Post: Knud Ahrnell Albrechtsen
2 hours ago
» Replies: 0
» Views: 18
|
Wedge Bricks from 10330 r...
Forum: Part Requests
Last Post: Knud Ahrnell Albrechtsen
2 hours ago
» Replies: 3
» Views: 215
|
27965 Cable flexible 22L ...
Forum: Part Requests
Last Post: Jaco van der Molen
5 hours ago
» Replies: 4
» Views: 4,847
|
Why don't stud grids allo...
Forum: Parts Authoring
Last Post: Willy Tschager
5 hours ago
» Replies: 1
» Views: 51
|
existing parts color vari...
Forum: Parts Authoring
Last Post: Bertrand Lequy
9 hours ago
» Replies: 5
» Views: 496
|
Technic 2023
Forum: Official Models
Last Post: N. W. Perry
Yesterday, 20:14
» Replies: 16
» Views: 27,108
|
Technic 1992
Forum: Official Models
Last Post: Takeshi Takahashi
Yesterday, 18:53
» Replies: 30
» Views: 43,548
|
Minifigure (series 28) - ...
Forum: Part Requests
Last Post: Gerald Lasser
Yesterday, 18:19
» Replies: 2
» Views: 123
|
Technic 2025
Forum: Official Models
Last Post: Paweł Turalski
Yesterday, 17:36
» Replies: 6
» Views: 13,265
|
Friends 2024
Forum: Official Models
Last Post: HowToBrick
2026-01-10, 17:11
» Replies: 5
» Views: 10,158
|
|
|
| Converting CAD to Ldraw format |
|
Posted by: dan - 2014-09-13, 4:16 - Forum: General LDraw.org Discussion
- Replies (1)
|
 |
1st post!
I am researching a project where I will create LEGO versions of a series of existing wooden sculptures (which are 20 feet tall). The sculptures have 3D design files and I was hoping to be able to save a lot of work by converting the 3D files into LDraw compatible formats. The LEGO project will only use rectangular bricks (2x10, 1x4, etc). Is there any existing software that you know of which I could leverage? Can you imagine a better method for producing the brick design/instructions needed for this project?
thanks!
melting man.
|
|
|
| Obscure LDView primitives bug? |
|
Posted by: Stephen - 2014-09-12, 13:20 - Forum: LDraw Editors and Viewers
- No Replies
|
|
Travis,
Not really sure if this is a bug in LDView or not. Thought I'd report it anyway in case it is of interest. I will concede it's arguably a pretty obscure set of circumstances.
With this minimal case MPD (it took me an hour to cut down my 50000+ part model to find the cause):
Code: 0 FILE Untitled.ldr
0 Untitled
0 Name: Untitled.ldr
0
0 FILE Model1.ldr
0 Model1
0 Name: Model1.ldr
0 ROTATION CENTER 0 0 0 1 "Custom"
0 ROTATION CONFIG 0 0
1 4 0 0 0 0 0 1 0 1 0 1 0 0 box.dat
0
0 FILE Model2.ldr
0 Model2
0 Name: Model2.ldr
0 ROTATION CENTER 0 0 0 1 "Custom"
0 ROTATION CONFIG 0 0
1 28 0 0 0 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 40 0 0 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 40 0 40 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 0 0 40 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 -40 0 40 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 -40 0 0 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 -40 0 -40 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 0 0 -40 1 0 0 0 1 0 0 0 1 3068a.dat
1 28 40 0 -40 1 0 0 0 1 0 0 0 1 3068a.dat
0
0
You'll note that I've done something a little unusual perhaps by including a reference to box.dat in one of the models. Note sure if this is "allowed" - but this was done because I wanted to simulate the appearance of edges of baseplates under a model without the render cost of the memory consumed by the studs on real baseplates, and a number of box.dat entries was quicker than using a whole bunch of quads.
Under normal circumstances viewing the above (either model) in LDView works fine.
However, if I then copy 3068a.dat from the LDraw parts directory into the project's own directory (because I intend to later customize it) and view the exact same file above (it now selects 3068a.dat from current directory) the appearance of Model2 is wrong within LDView. The 2x2 tiles still show, but they are completely missing their seams, and the POV export is also missing the calls to LDXSeamMatrix() for these parts.
Model2 fails to show correctly due to the box.dat reference in the unshown Model1. If I hide the box in Model1 (0 MLCAD HIDE), or I rearrange the order of the models so that Model1 comes after Model2 in the MPD, then Model2 once again shows correctly with the seams.
Like I said, pretty obscure circumstances to be using box.dat directly within a model and also using a local copy of another .dat file, so not sure if you'd strictly classify it as a bug since maybe I'm not supposed to be doing this 
|
|
|
|
| Part Length in LPub |
|
Posted by: Johann Eisner - 2014-09-11, 19:33 - Forum: LDraw File Processing and Conversion
- Replies (2)
|
 |
Hello
I am new here in this forum, an so first of all, hello to all.
I already use the search function, but i don´t find a right answer.
Have anyone an idea, how to show the part length from "Technic Flex Hoses" in the BOM of LPub?
The length of axles, beams,... is shown automatically, but not the length of the hoses.
Thanks
Johann
P.S.: Who finds spelling errors may keep them.
|
|
|
|
| Lic - a tool for creating LEGO building instructions |
|
Posted by: Steffen - 2014-09-07, 14:08 - Forum: LDraw File Processing and Conversion
- Replies (32)
|
 |
I just found this tool and wanted to share it with you, quoting from its Google Code page:
Lic is a cross-platform, Python, OpenGL & Qt powered desktop application for creating and editing LEGO instruction books. Lic imports 3D models, organizes them into submodels, pages & steps, and exports the end result as images or PDF.
Highlights:
- A rich, WYSIWYG UI editor, which provides a fully interactive preview window along side a drag & drop-enabled navigation tree, to help organize and layout your book.
- Automatically divide your model into steps. Add a list of parts needed for each step, and auto-layout multiple steps per page for a best fit. Auto-generate a title page and part list pages.
So far, Lic can import any LDraw model, but its dynamic importer makes it easy to add an importer for any 3D file type, and create instructions for that model. A Lego Digital Designer (LDD) importer is coming soon.
When you're done, Lic can export a final instruction book as a series of images or as a high resolution PDF.
http://bugeyedmonkeys.com/lic_info/
https://code.google.com/p/lic/
|
|
|
|
| LDForge |
|
Posted by: Santeri Piippo - 2014-09-07, 1:37 - Forum: Parts Author Tools
- Replies (27)
|
 |
After over 1 year of development, a beta build of LDForge 0.3 is out with massive changes and improvements. Release highlights: - multi-document support
- various optimizations that make LDForge a LOT faster than before
- able to download parts off the PT if desired
- circle tool with ring finder algorithm makes adding rings to parts mostly trivial, can also be used for edge circles and discs
- magic wand tool for easier group selection
- support for logoed studs
- support for direct colors
- auto-subfiler! just select and fire!
- various little new features, improvements and bug fixes
Note that this is beta-quality software and has not yet recieved complete exhaustive testing (i.e. I gotta get that kolhii stick done). This means, don't use in production work lest you risk a crash eating your work! I decided to post this after I managed to finally squish the nasty showstopper bugs. I'm thinking about just making the release 1.0 at this point.
|
|
|
|
| LPUB - how to change assembly scale in a submodel |
|
Posted by: Jetro de Château - 2014-09-06, 20:43 - Forum: LDraw File Processing and Conversion
- Replies (2)
|
|
I'm trying to get to grips with LPUB. Specifically I'm trying to show separate subfiles in an MPD file to show a bigger assembly size than the main (complete) model. So far I have found the metacommand for assembly size is 0 !LPUB ASSEM MODEL_SCALE GLOBAL 1.0000 (=100%), but I have not found a way to make local changes for a single step or for subassemblies.
I have looked for a complete list of metacommands for LPUB, but the best I've come up with is this
https://sites.google.com/site/workingwit...tacommands
and that still looks incomplete - the precise metacommand I found in my LPUB file for assembly size includes the word GLOBAL, which makes me suspect there might be a LOCAL version too. (I've tried "LOCAL" and it didn't work for me)
Can anyone point me in the right direction?
|
|
|
|
|
