I was asked to describe the workflow I use to convert my LDraw models to Studio (with unofficial parts not in Studio) in order to render them. Here it is...
Choose a folder in "Directory for Extracted Files". Note that MPDWizard is an old tool, and doesn't play well with complex folder trees! I use a simple folder in the root of my hard disk, eg. "C:\newparts"
Press Extract button. All the subfiles contained in the mpd are now extracted.
Now go to Studio custom parts location. On Windows it's located here:
C:\Users\<your user name>\AppData\Local\Stud.io\CustomParts. If there is no CustomParts folder in Stud.io folder, create it.
in CustomParts folder, create a "parts" subfolder and a "p" subfolder.
Copy all parts files (eg. 80271.dat or u9560.dat) from C:\newparts to (...)CustomParts\parts
Copy "S" subfolder from C:\newparts to (...)CustomParts\parts (thus creating a "s" subfolder in CustomParts\parts)
Copy all primitive parts (eg. 3-16con14.dat) from C:\newparts to (...)CustomParts\p
Copy "8" and "48" subfolders from C:\newparts to (...)CustomParts\p (thus creating a "8" and a "48" subfolder in CustomParts\p). Note that "8" and "48" folders may be absent if there's no hires or lores primitives.
Launch Studio and open Custom Parts palette. You should see all the new parts there.
You can now import your original model.
...hopefully that's all. But there may be more to do manually, because some Studio parts are incompatible
Hi! Here I share one of my Lego Technic (in LDD), in this case Lego Technic 8458 - Street Sensation (Web Extra). Also, I post the MPD file in case someone want it.
Hope you like the car.
The file is far to be MPD compliant and have several flaws.
Edit: Change the pic and updated the file. Don´t know if it´s OMR compliant.
Question was raised initially by Javier Orquiera: https://forums.ldraw.org/thread-26076-po...l#pid45017
The OMR specification don't seem to address official instructions of models made from multiple sets, while this situation does occur quite frequently:
- extension sets (eg. education sets such as Spike Prime 45678 + expansion set 45680, but also retail sets such as 9747 Robotics Invention System + 3800 Ultimate Builders Set)
- Some simple sets that can be used in combination to create bigger models - this is common with the pull-back motor sets.
What should we do to accomodate this ? We could use set1 + set2 as <Set Number>, but what about <Set Name>? What are the implications on OMR website?
This is my first time posting on these forums and my first time using Lua, but maybe this will be useful or fun to someone else.
My 3 year-old and I build almost exclusively in DUPLO.
Our collection is about 2,500 parts.
He enjoys building anything big: towers, bridges, castles, etc.
I enjoy trying to make our creations aesthetically pleasing. So far, that just means using parts in a color gradient (e.g. rainbow).
I also use Rebrickable.com to maintain my part inventory.
LDraw and LDCad have been wonderful resources for making us both happy. By coloring my designs in LDCad, I can have a plan when I begin a build with my sometimes impatient building partner.
These attachments are my attempt at using Lua to let me build in LDCad without worrying about color, and then recolor the entire model with a click from the parts we actually own.
Originally, I wrote this to assign color to the parts in order by their y value. But then I actually read Roland's very helpful LDCad documentation at http://www.melkert.net/LDCad/docs/scriptAPI where I saw the getComp method, and realized I could parameterize this function to easily sort along different axes (e.g., XYZ, ZYX, etc.)
If anyone has ANY thoughts or suggestions, please share, as I am clearly new at this.
Next, I plan on working on scripts to build walls using the parts in my inventory.
I have a number of extra search directories set in my preferences, but LDView does not appear to be searching them so all those parts are missing. I know the directories are valid because if I set one of them as the main ldraw library, its parts (and only its parts) will appear just fine. Have I forgotten to tick a simple box somewhere, or is something amiss?
Posted by: vitor campos - 2022-02-25, 4:36 - Forum: Help
- No Replies
Hello o/
I'm new to the forum so first of all thanks for the effort around it. I really appreciate all of your time and effort.
I am running LeoCAD on a armhf machine (Ubuntu focal) and have even suceeded compiling it myself through git.
However, when I try to run it, it is plain white. I cannot see a brick on the project. Nor even the "mesh" is visible. Has anyone experienced something similar?
This is what my screen look like:
And this is my terminal info about the package and its dependencies!
A new Contributor's agreement has been agreed upon by the SteerCo. The text is as follows:
Quote:By submitting work ("the Work") to The LDraw Organization ("LDraw.org"), the submitter ("the Author"), agrees to release the Work under the Creative Commons Attribution License 4.0 International License ("CC BY 4.0").
If you are reading this, you have, at a minimum, Parts Tracker submit privileges. While it is not required, I ask that all of you email [email protected] with the following:
"I accept the LDraw.org Contributor's Agreement dated 23-Feb-2022 with regards to all past and future contributions I make to LDraw.org".
There is some documentation and coding to do so the expected implementation of the CC BY 4.0 license will be the May or July update. I will not be suspending accounts or anything like that to enforce agreement (although expect an email nag from me if I don't hear from you) as the CC BY 2.0 is fine for us but it has some legal baggage that we want to avoid hence the revision.
Thank you and thank you for making the LDraw library what it is.
A new Contributor's agreement has been agreed upon by the SteerCo. The text is as follows:
Quote:By submitting work ("the Work") to The LDraw Organization ("LDraw.org"), the submitter ("the Author"), agrees to release the Work under the Creative Commons Attribution License 4.0 International License ("CC BY 4.0").
If you are reading this, you have, at a minimum, Parts Tracker submit privileges. While it is not required, I ask that all of you email [email protected] with the following:
"I accept the LDraw.org Contributor's Agreement dated 23-Feb-2022 with regards to all past and future contributions I make to LDraw.org".
There is some documentation and coding to do so the expected implementation of the CC BY 4.0 license will be the May or July update. I will not be suspending accounts or anything like that to enforce agreement (although expect an email nag from me if I don't hear from you) as the CC BY 2.0 is fine for us but it has some legal baggage that we want to avoid hence the revision.
Thank you and thank you for making the LDraw library what it is.
this version comes with new installers and does not need a Java installation anymore.
It also improves the compatibility with Mac OS X and Linux.
Please uninstall the previous LDPartEditor version, before installing version 1.8.54.
LDPE uses now a very modern technology stack (self-contained Java 17).
...use installers of LDPartEditor for Windows, Linux and Mac OS X (without the need to install Java)
...see more digits (at least 4 decimal places) on the protractor and the distance meter.
The following critical issues were fixed:
"Set X/Y/Z (for Selection)" loaded always the vertex from the clipboard if there was one vertex stored in it.
Outdated UI libraries for Mac OS X were updated.
The program was tested intensively with "real world" files.
However, it is still a beta version and something can go wrong in about 140.000 lines of code.
Installation on Windows:
Download and extract LDPartEditor_win32_x64.zip
Run LDPartEditor-1.8.54.msi
Start LDPartEditor from the start menu
Installation on Linux:
Download and extract LDPartEditor_linux_x64.zip
Install ldparteditor_1.8.54-1_amd64.deb
Start LDPartEditor from the menu or via launcher
Installation on Mac OS X:
Download and extract LDPartEditor_mac_x64.zip
Mount LDPartEditor-1.8.54.dmg
Drag LDPartEditor.app to the Applications folder
Copy ldparteditor.sh to your home folder
4a. Open a Terminal.app and run ./ldparteditor.sh
4b. Or open a Terminal.app and run /Applications/LDPartEditor.app/Contents/MacOS/LDPartEditor
Please note that this software is in the beta stage. Although, this version was tested, there are already known issues for this release. There is a potential risk of data loss.
I listen carefully to your requests and possible complaints. Please leave me a message, with your thoughts and wishes to further improve the software.
LDPE is a 3D CAD application: The overall system requirements are higher. While I recommend to use a powerful 64-bit multicore system, it could be possible, to run LDPE on older machines as well.
System Requirements:
Minimum System Requirements:
OpenGL 2.1 compatible Graphics Card
Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
RAM: 4GB
Video-Memory: 1 GB
Free Disk Space: 100 MB
Recommended Requirements:
Operating System (64bit): Windows 7,8,10, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
OpenGL 3.3 compatible Graphics Card
CPU: Multicore-Processor with 4 cores (or more)
RAM: >4 GB
Video-Memory: >1 GB
Free Disk Space: 512 MB
For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
I'm going to become much more of a stickler about HISTORY lines. If you have a submit on a part and you are not the author there must be at least 1 HISTORY line with your username. This is a CC BY 2.0 requirement that we must abide by. Submissions that fail to meet this criteria will be header edited or held until the submitter contacts a Header Admin for an edit.
)
![[Image: 592331995_Capturadetela_2021-09-17_01-10...3f1893.png]](https://forum.armbian.com/uploads/monthly_2021_09/592331995_Capturadetela_2021-09-17_01-10-32.thumb.png.77e1f9dddb160350dd1c3f6fd63f1893.png)
![[Image: 573839915_Capturadetela_2021-09-17_01-11...f35c24.png]](https://forum.armbian.com/uploads/monthly_2021_09/573839915_Capturadetela_2021-09-17_01-11-09.png.07b76173ffe2b673667af3254bf35c24.png)
