Hello everyone, I am new to the site, so forgive me if I'm posting in the wrong category or something.
Anyways, I'm going straight to the subject. I use the LDraw files to import bricks into Blender and it's a great asset! I use it almost everyday. However, there are pieces missing that I need desperately for a project. I know modeling takes time, so please know I do NOT have a deadline. I have just been looking through the internet inside out for these two parts with no avail, and its really frustrating. I even contacted the Lego Group, but they were unwilling to help, which is understandable. Anyways, before I blabber on, the two parts I need, are part of the Mars Mission sub-space theme. The theme was released in 2007 and in 2008 they came out with a really cool addition; the alien commander. I have attachments of the pieces on this thread. The IDs of the parts are: 62723, and 62724. I have not found them ANYWHERE, including LDD. (Lego Digital Designer). I know you need pics of the bricks in all different directions, so to make it easier, I have done pictures of my own. Just reply to the thread if you are willing to add these bricks. They are complex, but I'm sure one of you can do it!
Not sure where to post this, but I guess here isn't the worst option at least.
Trying to identify a minifig head or torso can be very difficult. I have been thinking of a system of standardized, unique keywords to narrow down the search in a very easy way.
So far, I've just made a pilot test with the 51 first minifig torsos that comes up in my Parts library, and added three new keywords. The point is to be able to filter for example, not only whether there are buttons or not on a torso pattern, but exactly how many. The three "variables" I've been experimenting with so far is:
btn for button count (btn7 for 7 buttons and so on)
pkt for pocket count
and
zpr for zipper count
What would be the most efficient search criteria, could of course be subject of discussions; these three were just the first that came to my mind. But yet, the combination of these three filters looks very promising. Very often, only one torso remains in the search. (But then again, I have only implemented the system on 51 torsos so far...) We could probably add other search criteria, such as base colour[s], belt [clip count], and... you name it, but on the other hand, we can still use the rest of the part descriptions and already existing keywords in our search. So the key is to find the best keywords that has the highest potential for effective filtering. So far, I've found that 'btn' is by far the most efficient variable, but combined with other criteria, the filtering effectiveness increases exponentially.
So, for example, now when I enter "btn7" in LDList (for 7 buttons), I get only one hit: 973p1f. I'm sure there will be more hits if I ever get through all torsos, but then I may enter police or badge in the search, and it will probably be very few hits.
What do you think? A massive amount of work, yes, but IMO extremely beneficial.
Hi guys
I create an unofficial part (4150pb024), and would like to make it available to other users.
Where can I upload him, where he will be tested and published?
Hi!
I'm totally new to LDraw, LDCad, OMR and similars. But I wanted to try to create, upload and share this official model.
Is this the right way to just post it here to get it into the OMR database?
Concerning the inner edge lines on the bushloc primitives, when paired with axleho primitives you end up getting edges where you do not want them. My proposal is to move those edge lines to a new primitive, bushloc5 and also create another primitive bushloc6 where the edge lines math up with the axleho primitives. Is this desirable or should the primitives and the parts that use them be kept the way they are?
