| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
LDraw.org 2025-11 Parts U...
Forum: LDraw.org Announcements
Last Post: Orion Pobursky
Today, 0:00
» Replies: 0
» Views: 90
|
LDraw.org 2025-10 Parts U...
Forum: LDraw.org Announcements
Last Post: Jake Cowledge
Yesterday, 16:11
» Replies: 3
» Views: 988
|
40775 - Mini Knight's Cas...
Forum: Official Models
Last Post: Magnus Forsberg
Yesterday, 14:40
» Replies: 0
» Views: 187
|
LEGO Icons 2025
Forum: Official Models
Last Post: N. W. Perry
Yesterday, 13:34
» Replies: 3
» Views: 4,091
|
Here are the new raw part...
Forum: Part Requests
Last Post: Orion Pobursky
2025-11-28, 22:09
» Replies: 2
» Views: 217
|
Part request 68502 please
Forum: Part Requests
Last Post: Peter Grass
2025-11-27, 15:52
» Replies: 2
» Views: 222
|
Gap in offical part (stic...
Forum: Parts Authoring
Last Post: Gabriel Läufer
2025-11-25, 20:41
» Replies: 2
» Views: 406
|
Technic 2025
Forum: Official Models
Last Post: Philippe Hurbain
2025-11-25, 8:20
» Replies: 4
» Views: 11,110
|
Parts Request- Marvel 202...
Forum: Part Requests
Last Post: James Simpson
2025-11-25, 2:41
» Replies: 5
» Views: 827
|
Slope Brick 31 width 3 an...
Forum: Parts Authoring
Last Post: Orion Pobursky
2025-11-25, 2:22
» Replies: 1
» Views: 284
|
|
|
| How to author parts myself |
|
Posted by: Neil - 2015-03-21, 13:39 - Forum: Part Requests
- Replies (2)
|
 |
Greetings all,
Could anyone provide me with guidance as to how I can author parts myself? The parts I need are not in LDD, I don't have LDraw experience, and I don't have a 3D scanner.
Thank you,
LegoSW
|
|
|
| Whislist for the MLCad minifig generator |
|
Posted by: Willy Tschager - 2015-03-18, 12:50 - Forum: LDraw Editors and Viewers
- No Replies
|
 |
Hi,
as you might know I have added parts to the MLCad.ini file that drives the MLCad minifig generator in MLCad, LeoCAD or Bricksmith, which do not come with a "Minifig" statement such as 75° slopes or bars. I'd like to add some more of those, so please forward your wishes which parts you wanna see in the generator.
w.
|
|
|
| [MLCad 3.40] MLCad.ini vs. MLCad.grp vs. MLCAD.CFG |
|
Posted by: Steffen - 2015-03-17, 22:13 - Forum: LDraw Editors and Viewers
- Replies (11)
|
 |
This question is about MLCad 3.40.
I know that MLCad settings are stored in 2 files mainly, which sit in its program folder:
- MLCad.ini - contains its main application settings, including folders to look in for parts, settings for its built-in LSYNTH support, settings for the Minifig generator etc.
- MLCad.grp - contains the configuration of its parts tree which allows to group parts together into groups by their name
However, MLCad creates a binary file named MLCAD.cfg in my LDRAW folder additionally
when I run it. It re-creates the file when I delete it.
Does anyone know what this file contains, what its purpose is?
|
|
|
| Design in CAD and then order to your door |
|
Posted by: Matt Aitken - 2015-03-17, 19:58 - Forum: All Other Programs.
- No Replies
|
 |
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]
|
|
|
| Using JSON as HL library export |
|
Posted by: Roland Melkert - 2015-03-15, 23:14 - Forum: Official File Specifications/Standards
- Replies (6)
|
 |
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.
|
|
|
|