Quote:Appendix VI
Programs relying on the parts.lst file rather then the LDRAW_ORG meta-statement use special characters to prevent the parts being included in the list:
- the descriptions of all subparts (i.e. line 4 = '0 !LDRAW_ORG Subpart') must start with '~'
- the description of all obsolete parts, maintained for backwards compatibility must start with '~'
- the descriptions of all aliases (i.e. line 4 = '0 !LDRAW_ORG Part Alias') must start with '='
- the descriptions of all physical colour parts (i.e. line 4 = '0 !LDRAW_ORG Part Physical_Colour') should start with '_'
The use of '~' for part files is at the author's discretion, to hide mouldings that are not released independently. This is one case where merely reading the LDRAW_ORG line is insufficient for tools to know how to treat the file.
Quote:Unofficial parts are allowed to be used, but must be included in the MPD as referenced subfiles. The filename of the unofficial part is subject to the following naming rules:
...show the text line selection in the 3D editor as a selection (if the 3D editor is opened)
...enable Single Vertex Modification (aka SyncEdit) in the Text Editor when you select one vertex in the 3D Editor.
...benefit from a little performance gain (due to some modifications related to logging in the debug mode).
This release includes 10 important bug fixes as well.
The program was tested intensively with "real world" files. Especially, "Undo" and "Redo" should work now fine.
Make sure that you choose the right architecture for your OS and Java Virtual Machine (JVM) (64bit or 32bit).
A short guide how to check if a 64bit JVM is installed on your system is located at the bottom of this message.
Download the zip-Archive
Extract the archive content to the location of your choice
On windows, double-click "run.bat" to start LPE.
On linux/mac, you have to excecute the shell script "run.sh" to start LPE.
Please note that this software is in the beta stage. Although, LPE 0.8.3b was carefully tested and developed, there are already known issues for this release. There is a potential risk of data loss.
Something can go wrong in about 100.000 lines of code.
You can search for updates if you do the following steps:
On windows, double-click "update.bat" to search for updates.
On linux/mac, you have to excecute the shell script "update.sh".
LPE 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 LPE on older machines as well.
System Requirements:
Minimum System Requirements:
Java Runtime Environment (JRE) 1.7
OpenGL 2.1 compatible Graphics Card
Operating System (32/64bit): Windows [XP; Vista; 7 or newer], Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
RAM: 2.5GB
Video-Memory: 512 MB
Free Disk Space: 100 MB
Recommended Requirements:
Operating System (64bit): Windows 7, Mac OS X [>=10.6], Linux [e.g. Ubuntu Linux >=10.4]
CPU: Multicore-Processor with 4 cores (or more)
RAM: >4 GB
Video-Memory: >512 MB
Free Disk Space: 512 MB
--------------------------------------------------------------------------------
How to check your JVM version (32- or 64-bit):
--------------------------------------------------------------------------------
You can try on the command line:
Code:
java -d64 version
If it's not a 64-bit version, you'll get a message that looks like:
Code:
This Java instance does not support a 64-bit JVM. Please install the desired version.
In general, I recommend to install the 64-bit version of the JVM.
edit: I put two releases in one post (0.8.3 and 0.8.3b)
I just "finished" the first step of the "leg rework process"
The corrected hips+legs are attached to this post. The legs do not use subfiles at the moment.
edit: I updated all files on 2015-11-30. edit2: The files are now on the parts tracker! (3815, 3816, 3817)
Here are the test scenarios from Magnus Forsbergs post
0 // The same set-up in real parts makes it clear that the current 3816s01.dat is really wrong.
0 // It is possible to place this mock up on a 3023 in real parts, but not in ldraw-parts
1 44 60 40 0 1 0 0 0 1 0 0 0 1 3023.dat
Next steps:
- Create the subfiles
- Project existing patterns to the new legs (and fix possible pattern errors)
I estimate that it will take 3 to 4 months to transfer all patterns to the new leg.
Following the problem mentionned here and after discussions with Mikeheide about MPDCenter, I think that OMR specifications should be updated to make it clear that unofficial parts MUST be included in OMR conform files.
It is more or less implied by this paragraph of the specification but it should be made much more explicit
Quote:Unofficial parts are allowed to be used. The filename of the unofficial part is subject to the following naming rules:
<Set Number>[-<Optional Qualifier>] - <Unofficial Part Number>.dat
Where:
<Set Number> is the the number printed on the model's container.
<Optional Qualifier> is a sequential number, starting with 1, added if there is more than one set that could be assigned <Set Number>.
<Unofficial Part Number> is the unofficial part number assigned in that very moment.
Example:
33956.dat would be renamed to 3345 - 33956.dat or 3345-1 - 33956.dat.
So this is my first attempt at building in MLCad. I intend to get this to OMR spec if possible. By the way, how do I embed an image in a post instead of just making it an attachment?
Two problems so far:
- How to model the string on the rear winch
- Positioning of the rear facing gun and the round transparent brick as this does not align with the normal Lego geometries
I think I also need to rebuild in line with some of the sub assemblies in the instructions.
I'm new here and taking in an interest as I want to build some models then animate them in Blender.
Anyway - looking at the official models pack I opened the Front End Loader in MLCad and noticed a bug in the model - the pneumatic rams are not correctly located. MLCad gave me a warning dialog as I opened the file to say one or more parts has been upgraded to new versions so not sure if this is the cause.
What is the correct process for reporting this - I'm not yet feeling proficient to tackle fixing the model myself just yet.
![[Image: imgDuke2.png]](https://lh3.googleusercontent.com/-fi18ywwsEUo/VOOuvkpsdzI/AAAAAAAAASw/Ax0RRFkleKA/s64-no/imgDuke2.png)
![[Image: 10240%20-%20UCS%20Red%20Five%20X-wing%20Starfighter.jpg]](http://bricksafe.com/files/papacharly/star-wars/10240%20-%20UCS%20Red%20Five%20X-wing%20Starfighter.jpg)
