SimLego

Members
  • Content Count

    45
  • Joined

  • Last visited

About SimLego

  • Rank
    Level 2 Stud

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hmm, another wierd thing. If I only enter "970x" in the Search box, I can see a lot of 970x* entries, but they disappear if I continue with "970x0", and for example search on "970x021" or any other existing entry renders "Error - No Search Results". Yet the id entered does exist in the database.
  2. I believe in colors.csv, the "is_trans" value of "1039 Modulex Clear" should be set to "t", not "f". 1039,Modulex Clear,FFFFFF,t
  3. I'm not sure I got this right, and I'm pretty sure that if I got it right, this subject must have been brought up already, but... If I got it right, BrickLink lists Hips and (fixed color) Legs assemblies, like 970c09 "Hips and Light Gray Legs" - while Rebrickable lists Legs and (fixed color) Hips, like 970x021 "Legs and Red Hips". From my limited understanding, that makes inventory conversions between BL and Rebr almost impossible, or at least very complicated. Is that correct? Would it be possible to turn this huge ocean ship around and change it so we get the same standard (given I'm correct and it isn't a minor problem easy to workaround after all...)?
  4. Not much I can do with the LEGO logo. I think I oversized the M in most directions; it's looks a little bit too bold, too. But that can be changed later by anyone who likes to torment him-/herself. And yes, Modulex had LEGO logos as well as M
  5. Just a mockup, or a proof of concept. Will this do? What do you think, maybe the M is way too elevated? 1142M.dat studm20.dat
  6. I may study how the LEGO logo is made and then give the M a try. Mayby even see if I can add some more parts to the tiny library.
  7. There is a little yet unofficial LDraw library of Modulex parts, but we didn't distinguish between LEGO on studs and M in it. This means that if you render it in POV-Ray hi-def, There will only be LEGO on the studs if any. Noone has made an LDraw version of a stud with M on it yet, as far as I know. http://www.chris-w-dee.co.uk/Modulex/index.htm I happened to notice that Rebrickable's definition of Modulex Black is very bright. Is there a good reason for that? And yes, here's a new one I made tonight. /Tore brk0205a.dat
  8. SimLego

    Updating LDraw Images

    As long as the file is stored within the virtual Empire of Rebrickable, there is no reason to name it anything else than the Rebrickable part number. Plus ".dat", of course. It depends on how many "humans" will have access to your LDraw files. Any rendering software will not care if you even write a header or not. Basically, the renderer just cares for the five type 1 lines (for one torso, two arms, and two hands.) The original work of my shortcut is actually made by Leonardo Zide, and who knows where he's copied it from, or if he used some Minifig Generator. So you are free to put your name there - or omit that line if it's just going to be used by rendering software. So, for 973pr1244c01, where LDraw has one number for the torso, BrickLink another, and Rebrickable yet a third one, you are free to use any file name you like. But I believe it is most convenient to stick with the Rebrickable number. And the lines of the header are all optional, the only purpose for them is to make it easier for those who have access to the actual LDraw files you create/generate. 0 Torso Mechanic Blue Overalls, Tools in Pocket Print / Medium Blue Arms / Yellow Hands 0 Name: 973pr1244c01.dat 0 // torso 1 16 0 -72 0 1 0 0 0 1 0 0 0 1 973p8z.dat 0 // or use color code 73 directly 0 // arms 1 73 -15.552 -63 0 0.9855 -0.1699 0 0.1699 0.9855 0 0 0 1 3818.dat 1 73 15.552 -63 0 0.9855 0.1699 0 -0.1699 0.9855 0 0 0 1 3819.dat 0 // hands 1 14 -23.552 -46 -10 0.942 0.335 0.0072 -0.2404 0.6906 -0.6821 -0.2336 0.6409 0.7312 3820.dat 1 14 23.552 -46 -10 0.942 -0.335 0.0072 0.2404 0.6906 -0.6821 0.2336 0.6409 0.7312 3820.dat 0
  9. SimLego

    Updating LDraw Images

    Like I said, I have to get the making of those shortcuts automized somehow, and right now I have no programming enviroment installed in any of my computers, so it might take a while for me to even get started on this huge project. But at least it's in my pipline. /SimLego
  10. SimLego

    Updating LDraw Images

    Of course it is OK. I thought about doing that in the first place, but realized it could cause some other problems when viewed directly in an LDraw viewer.
  11. SimLego

    Updating LDraw Images

    I hope this isn't too off-topic, but I found nowhere else to post it. If there is no official LDraw shortcut for a specific assembly, for example 973p47c01 or any torso + arms + hands for that matter, would it be possible to store unofficial shortcuts locally and auto-generate LDraw images for Rebrickable? As I understand it, currently Rebrickable only checks the existence of of an LDraw file at Ldraw-org. (I made this shortcut in Notepad, but there must be some way to make it more automized I hope.) 0 973p47c01 Torso Castle Classic Shield Red/Gray Print / Light Gray Arms / Yellow Hands 0 Name: 973p47c01.dat 0 Author: Tore Eriksson 0 Unofficial LDraw Shortcut 0 // torso 1 4 0 -72 0 1 0 0 0 1 0 0 0 1 973p47.dat 0 // arms 1 7 -15.552 -63 0 0.9855 -0.1699 0 0.1699 0.9855 0 0 0 1 3818.dat 1 7 15.552 -63 0 0.9855 0.1699 0 -0.1699 0.9855 0 0 0 1 3819.dat 0 // hands 1 14 -23.552 -46 -10 0.942 0.335 0.0072 -0.2404 0.6906 -0.6821 -0.2336 0.6409 0.7312 3820.dat 1 14 23.552 -46 -10 0.942 -0.335 0.0072 0.2404 0.6906 -0.6821 0.2336 0.6409 0.7312 3820.dat 0
  12. Currently, I get 404 errors every now and then at Rebrickable. Most of the times when I move parts in bulk.
  13. No, I disagree with both. 'p' is enough for Printed. "pr" or "pt" is just unnecessary and confusing. Three zeroes makes no sence, and don't forget the digit patterns: 3005pr00013, 3005pr00012, 3005pr00021, 3005pr00031... 3005pa through 3005pd (or pe) is perfectly enough to state that it's a 3005 with print and font a through d (or e). So, i suggest: 3005 = base part number p = print/pattern a = Serif Font (most likely Embossed CA(???)) oldest first - if we are able to date them... a = Letter A, ae = Danish AE, ao = Å (A with Ring), a2 = Ä (A Dieresis) And no suffix; it will only be a source of confusion and potential naming conflicts with the special, non-English characters or math signs. As much as I would love to have separate part names for the CA parts, I don't think it's realistic. That would mean *many* new parts, from basic 3001, 3002... 3020... 3024... 3032, 3034... through Classic Windows and I just don't know all. And to be honest, I have a hard time telling the black or the white CA parts from those in ABS. Once I thought it's just to look at the LEGO logo on the studs, but there are several exceptions. My way to deal with the problem is to simply have them on separate lists. And I think the only realistic way to go for now is to keep it that way.
  14. Yes, they attached well in my childhood. But CA ages in maybe 10 years. When they got worse, I recall tearing off small pieces of paper and put them between the parts, helping them to stay. But now we're getting off-topic here. I miss the thin, quite "zoomed in" font. I most wrongly call it "the British font" since I got most of them from the UK. I'm not sure about the rightmost column, but I believe they belong to this variant. Let's see if I'm able to attach a picture here...
  15. Yes, there are a lot of considerations that must be taken before you begin to reorganize! First: Decide how many different series should be counted as unique. I can directly think of four - without even having a look into my own collection, or the LDraw library, or how BrickLink has organized them. Then, decide for a good and consistent part numbering. Then, a good way to describe them, so they are sorted in a reasonable and overviewable way. Handling both math symbols and non-English letters, both in the part numbering and the descriptions. Before all these issues are resolved, noone should be messing around with the official Rebrickable libraries, IMO. PS. Please note that some variants occured in both CA and ABS versions. I separate them in my collection, because I build with ABS parts, but (almost) only collect CA since they generally are warped and virtually impossible to build with. DS.