Just for backup, but also for anybody interested, I'm posting here my current MLCad parts tree setup
which I over some years now found convenient to use.
This is especially useful for me still since MLCad doesn't know of the !CATEGORY keyword yet,
and thus will not show parts in their categories initially.
I'm attaching the MLCad.grp file here to this post (rename it from MLCad.grp.txt to MLCad.grp after download),
so you can directly use it to replace your default one if desired.
I first worked with Ldraw several years ago and I am now in a new computer lab and trying to configure Ldraw for my students. In the past, I downloaded a parts packet for NXT parts and copied it into the Ldraw folder. Ldraw is now installed and I am trying to get teh NXT parts to show up for my students. I copied the nxt files into the parts folders and had Ldraw scan for the parts. I found the NXT sensors - but have not found anything else. Is there something I am missing or is it the NXT parts are just scattered and require some searching.
I would love to simplify the search for my students and remove the parts lists not needed but have no idea which lists my students will not need. We have the 9797 educational sets, the NXT supplement packs and the RCX educational set.
How can I remove the trains and other unwanted lists and is there a way to make finding the nxt parts simpler for my students in their first use of Ldraw?
Posted by: Nazar - 2012-10-05, 19:41 - Forum: Help
- Replies (3)
Hi there,
I'm using a Mac (OSX 10.5.8) and am having some troubles.
Here's what I have done and have working so far:
1) Downloaded BrickSmith - launched it and was able to use BrickSmith to create the model.
2) Downloaded LPub (v4) - launched it but it is saying that it cannot find the parts.lst file. When I load a model, it cannot render that model "LDView Failed" error.
I checked around and it seems like I need to run mklist.exe to generate the parts.lst file, but I can't do that on a Mac (since it's an .exe file). Any other options?
Also.. I can't find some Lego parts in BrickSmith. For example, I can find the NXT brick, but I can't find any of the NXT motors or sensors (but I can find the old RCX style motors / sensors).
When I copied the LSC Summary to the new site I didn't care much about the content. Preparing the LSC summary for 2011/2012 I came across the list at the bottom:
* Updating category list
* Updating the policies for part votes
* Reference parser for LDraw 1.0 spec files
* An XML version of the specs
* Number that has to be used for Sticker
* Define rules for second Author
Would you agree that Reference parser for LDraw 1.0 spec files and Number that has to be used for Sticker can now be deleted?
Once more we are rather late with the nominations/election process...
The LDraw.org Standards Committee (LSC) 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.
To be eligible for LSC membership, per the LSC Charter you must fulfil at least one of the following:
* 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
* Authored a software program that is compliant with either the LDraw 1.0.2 specs or another spec published by the LSC
* Petition for nomination as an LSC candidate approved by 2 current LSC members
* Petition for nomination as an LSC candidate made to the LSC by at least 5 others eligible to be LSC candidates
People can either self-nominate or nominate someone else. When nominating, please reference the person’s eligibility from the list above. For the LSC there is non need that another member of the community seconds the nomination.
Nominations MUST be posted in direct reply to this post to be counted, and must be online by 12:00 PM GMT October 14.
Voting for the elections will begin October 17, and end October 31. The LSC will officially change over on November 15th, giving time to transition newly elected members into the committee.
Only LDraw organization members are permitted to vote in this poll. Since the list of the LDraw organization members vanished into thin air when the old Postnuke CMS went down we will figure out how to handle the election.
Willy Tschager
On behalf of the LDraw.org Steering Committee
I just wanted to drop a quick note here about my favorite HD wallpapers site: http://wallbase.cc
, which hosts a great bunch of just awesome LEGO wallpapers.
Just enter "lego" as search term, and sort the results descending by "favorites".
This way you'll get the most loved pictures first.
Does anyone know if there is a way to export to POV format from LDView using the command line ?
e.g. LDView.exe sample.ldr -exporttopov sample.pov
(or something...)
I've look at the helpfile command reference but don't see it...
Up to now I've always used L3P but I came across a couple of models recently which didn't include all the necessary parts when creating the POV file with L3P whereas LDView created the POV file fine. (Example of part which L3P didn't export was 30552.dat, LDView was fine - which I found a bit odd as I thought both would be using the same parts folders in my LDraw folder ?).
I'm also thinking that LDView is currently supported and being actively developed whereas L3P hasn't been updated for some time, and LDView also tries to download missing parts automatically from LDraw which is a bonus - so would really like to start using LDView instead of L3P I think - but I need the ability to run the export from the command line if at all possible.