All Activity

This stream auto-updates     

  1. Yesterday
  2. Found the following which has an extensive discussion about the three versions in case anyone is curious. https://www.eurobricks.com/forum/index.php?/forums/topic/89612-lego-set-box-differences-by-region/&do=findComment&comment=1771521
  3. Thank you. Looking at those notes, it appears the inventories will vary slightly for the 2006 version (10152-3) once we add stickers to the database (I'll submit CRs for those shortly) due to the name change from Maersk Sealand to Maersk Line. The only distinction between the -1 and -2 versions appears to be in packaging (they use the same stickers) so I'll suggest some note language to reflect that distinction.
  4. I say share the part entry and post picture alternates like we do on molds. not worth duplicating set for imo. unless the stickers actually differs.
  5. The BL pages have good descriptions explaining the difference. Essentially is mostly due to different packaging when it was re-released over the years. Maersk also has a corporate change which affected the set.
  6. Anyone know the distinction between sets 10152-1, 10152-2 and 10252-3? They contain identical parts and the only difference I can see is in their name but this doesn't seem to be reflected anywhere else. When this set was re-released as 10155, there were at least a few mold changes.
  7. As the work is slowly progressing to add sticker sheets to inventories (an already massively complex task with many equally valid and conflicting opinions of how best to proceed), I've discovered another little wrinkle that seems to be addressed many different ways on the site. I want to raise it so that hopefully some standard can be agreed upon for future work and that, eventually, can be applied to older sets via CRs and active correction efforts by the admins. This is a relatively lower priority task in my mind but best to have a fix in mind and standardizing now will allow for less work later. Some sets with stickers (for example, 75915) have two versions of their sticker sheets produced. One for the North American market (in this example, part 21365) and the other for all other markets (normally referred to as International and in this version part 21364). In all of the cases I've seen so far (and this may not be categorical), there doesn't appear to be visual difference between the sheets except for the printed design/element IDs. Perhaps the difference has to do with a legal issue in copyrighting the designs or it is a technical issue about the size of the sticker sheet itself (similar to NA standard Letter paper and European A4 paper which comes up in instructions). In every case, only one of the two versions is included in a set and the set's box-printed part count. The issues I am seeing are: Standardizing the name of the sticker sheets as Rebrickable parts Standardizing whether the affected set should be presented as distinct sets (i.e., 75915-1 and 75915-2) versus multiple set inventories in a single set Creating appropriate cross-linking between affected parts and sets My proposed solution is that the two parts should be added to the database as distinct parts with names of the format "Sticker Sheet from Set XXXX - North American" or "Sticker Sheet from Set XXXX - International". Notably, I think we should stop using the "-#" suffix from a set name in the part name since this may pose an issue in the future if the set is renumbered for some reason and the part isn't updated (bad enough we use the set number itself but I don't think that is as likely to change in the future as the suffix and should be found with a simple search if a set is being renumbered). Also, I think it best to standardize this naming to avoid current sorting issues with odd uses of dashes, parentheses, brackets, etc. Changing the name to "from" rather than "for" makes these parts more understandable if used in subsets or MOCs. Also, I'd advocate for removing the design ID/element ID information from the part name - this information is already stored elsewhere in the database and just complicates the part name and presents an opportunity for user typos. Comments about the other version should be removed from part notes unless that information is more than just the mere existence of the other version. Finally, the two parts should be cross-linked as "Related Parts" so that they appear on each other's info page/part pop-up page and so that they can be used interchangeably in the build system if the appropriate options are selected. When only one version of the sticker sheet is known to exist the name of that part would be "Sticker Sheet from Set XXXX". If a given sticker sheet is found to exist in multiple sets, then the naming would change to "Sticker Sheet - Descriptive Name" where the Descriptive Name could be anything relevant. Once the two parts are in the database, I propose that affected set be stored as a single set entry (for example 75915-1) but with two set inventories. The two inventories would be identical except for the appropriate sticker sheet part. This seems to be the text-book case of the set inventory system. If there are additional NA vs. International differences in an inventory of the same set, those would also be reflected on the two inventories. If a set is redesigned during production, then additional variants of these two inventories can be added to reflect that change or, if the redesign is significant enough to warrant, an alternative set number suffix can be created and that new suffixed set would include both inventories (this case also reinforces the dropping of the suffix from the part names themselves). Ideally, the North American and International inventories would be auto-selected as the default for a user based on their location settings in preferences but that may be extra coding. The set description notes should be modified to remove mention of the difference unless it is more explicit than the existence of two different sticker sheet versions. This approach removes any need to create cross-references and would only cause errors in user's collections if they don't select the appropriate inventory when adding a set to a set list (an option already provided). Thoughts?
  8. Last week
  9. A short description of the bug in question: When I try to use the build search, I get an error 504 (Gateway time-out) error. How the bug can be reproduced by us (if possible): I only have three sets and I am using the following search criteria: Part color sensitivity: Ignore. Ignore printed and patterned part differences: Checked. Ignore mold variations in parts: Checked. Consider alternate parts: Unchecked. Exclude Minifig and Minifig Accessory parts: Checked. Exclude Non-Buildable LEGO parts: Checked. Filter on Theme: Technic (538). Number of parts: 50 to no limit. Year of Release: From 1990 to 2019. Include official sets: Unchecked. Include Custom Sets: Checked. Include Premium MOCs: Checked. Include Sets I own: Unchecked. Sort by: Highest % Match. What browser (Firefox, Chrome, etc.) you were using when the bug occurred, and which version.: I tested both on Chrome on Windows 10 and Android. Thanks!
  10. 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
  11. Simon

    Updating LDraw Images

    Well, I have python on all my systems, and selecting 450 ldraw definitions that start with 973p and using the filename and description to generate a shortcut like the one you posted can be done in an hour or so. The main problem is getting the color of hands and arms, but if I can relate the ldraw torso to the Rebnrickable torso+arms+hands definition, I might be able to grab those colors from the RB part name, and translate them back into LDraw color codes. Let me think about that some more... If I start generating more unofficial ldraw shortscut, what numbering should I use? Original torso number followed by "c01"? Can I put my name in there as author?
  12. 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
  13. I've updated the doco, thanks. No point switching if you are fine using PayPal. The main functional differences on Rebrickable is that you can upgrade/downgrade Plans if you use Stripe (with PayPal you have to cancel and then re-subscribe to the new plan). Yes, the level 20/25/30 certainly do apply to you. If you hit 25 and are still on Pro, I will manually cancel your subscription and make it a permanent upgrade.
  14. xordis

    Finding parts

    I have tried to search for this but can't seem to find the answer I am chasing. I am wanting to enter all my sets, and a location etc, and then use the search function to find a part. So I might be looking for a 3960 (Dish 4x4 Inverted) I have entered my sets into a list called "Box 2". Now in this box I might have 20 ziplock bags full of lego sorted into sets. I can then search for the part and find it, and go to my My Parts and see I have one in lime green and it's in Box 2, but I don't know which set (bag) to go find it from. Am I missing something here or is there a better way to manage this?
  15. Pretty low priority, but it would be nice if a couple of improvements could be made to this. The most useful, I think, would be to include all the parts that are displayed using a 'similar image'. Right now, they aren't in this list, despite having no images. Another useful addition would be the ability to filter out Stickers and parts in the Non-LEGO category. Somewhat related, I think it would be cool to be able to choose which images are displayed when viewing an inventory - Photo, LDraw, LEGO or 'Best' (which would be the current implementation). Obviously default to best. That way, it would be really easy to see which parts are missing photos when viewing a set inventory. Could be applied to any list of parts for that matter. J
  16. Thank you for your reply and taking the time. I will have a closer look at the pdf you did for me and see if that helps. I have done a few of the MOC now, but only the ones that have PDF Instructions. I will continue to try to get the Instructions to work, the crawler crane really grabbed me, as have a couple of other, but, .IO & .LDD files, so maybe not. Thanks again. Colin
  17. Clearly I misread your intention but on the “HELP - Points/Levels/Badges” page, it says “Once you reach very high levels you can even win some prizes: Level 15 - Receive 3 months of Pro Plan for free”. There is no restriction listed about this only applying to Free users. When you announced the change of the point system in the blog (long prior to my signing up for Pro), you mentioned that existing users who were jumped past Level 15 won’t get the bonus but I read that as a one-time restriction due to the large number of impacted users. You also said “sorry, providing credits/discounts isn’t supported by PayPal” so I read this as a prize only available for Stripe-based users. I want to be very clear that I really appreciate all the work you’ve done on the site and the three month free is by no means a big deal for me but I think the language on the pages needs to be updated. It is misleading to imply it is a prize for being an active member of the community you’ve built and then to not provide that prize to those very people. So that I’m clear moving forward, would there be any reason I would want to switch from PayPal to Stripe? Also, do the prizes at Level 20 (Raffle)/25 (Pro Plan for life)/30 (About Us page) apply to users already signed up for Pro like myself?
  18. I don't give Stripe users the free 3 months either (did I give that indication somewhere?). If you are already on Pro when you hit level 15, nothing happens sorry. If everyone was 100% Stripe I would probably try harder to automate it, but dealing with the two types of payment processors complicates things too much.
  19. I can't reproduce this problem. Can you please provide me the exact URL where this occurs?
  20. Working on it. Thanks for the additional info.
  21. I checked both studio and ldd versions of the main model. Studio loads the model instantly, but as the designer explained (sort of) the model has no defined steps, so Studio can't generate an instruction PDF. You can hide all parts, and then in the parts list unhide each part to build it. Your problem doesn't seem to be with Studio itself, but with LDD. LDD treats every parts as a single step, so the instruction generator is trying to create a 1,783 page instuction webpage. Generation itself took about 20 minutes on a 3 GHz quad-core, saving to disk another 5 minutes. Generating the PDF took 10 minutes. The resulting PDF (25,6 MB) can be downloaded here. In general though, if you are completely new to these programs, you're better off starting with a smaller MOC to get some experience with the software. Your MOC choice has over 2,000 parts, and even with good instructions, it might prove difficult to build. Take care, Simon
  22. Create a new part list, import some parts from a csv and you will see the bug. It seems that is a problem of imported parts...
  23. OOOpps, of course there is, sorry. Refering to MOC-22859.
  24. Hi, Retrieverfalcon, Don't know anything about PayPal, so I have to leave this to @Nathan... Take care, Simon
  25. Hi, Cadman! Rebrickable has almost a dozen Crawler Crane MOCs. Which one are you talking about? Take care, Simon
  26. Simon

    Updating LDraw Images

    @SimLego- Using your example I am confident I can create more of those Unofficial LDraw Shortcuts, but I got a lot going on right now, so it might take a few weeks. Obviously, if you create some others in the mean time, that would be perfect. If needed, you can mail them to simonvanmeygaarden at gmail.com, and I'll take care of it. If you have any other examples of shortcuts we can use, please let me know. Take care, Simon
  27. When I initially signed up for an annual Pro plan, I paid with PayPal. Since then I've came to realize there would be an advantage to using Stripe - namely the three free months I would/should have gotten for achieving Level 15 (I'm now Level 17). If I cancel my subscription in PayPal, I know I'll keep Pro features until my current payment expires. If I re-signup using Stripe, when would the billing start? Would it tack onto the end of my old PayPal subscription? Would I get the three free months? I don't mind changing where I pay but I don't want to double-pay to switch billing systems. Are there any other distinctions between using PayPal vs. Stripe other than the Level 15 bonus? On a side note - the plans page needs to be much more explicit on the restrictions of the PayPal option - especially since that is a much more common online payment system to many users than Stripe (which I know from backend processing but don't think of nearly as much as a payment choice). It would also be useful to have clearer instructions for switching between the two processors.
  1. Load more activity