3023a?

[Steve]

Hi,

Upon downloading the latest part pack the 3023 part appears to have been split, I now have 3023a in my parts list instead. This is a real pain as it no longer has a simple 3023 (1x2 plate). All my previous models now have to be updated, but even worse the conversion tool for bricklink parts list no longer will recognize this so have to be manually amended, which is a huge frustration. Why has this change happened? It seems pedantic in the extreme. Is there a way to rename parts in the parts list simply? I would love to get rid of all the "a" variants as they simply mess up the MLCad 2 Bricklink Converter. 

Many thanks

[Orion Pobursky]

3023.dat should still work as it's just a "Moved To" to 3023b. This happens when LEGO makes a mold change and doesn't update the part number. Not super common but it does happen.

[Steve]

3023.dat should still work as it's just a "Moved To" to 3023b. This happens when LEGO makes a mold change and doesn't update the part number. Not super common but it does happen.

Thanks - I see it as a "b" - but its such a common plate - is the differential that important that we need two part records for a simple 1x2 plate? No other simple plate has this issue. How do I edit the parts list to remove/edit the "3023b" back to just plain simple "3023"?

Can the authors do this would save so much time with old models and importing part lists..

[Rene Rechthaler]

Sorry if my 3023a caused such a big mess, but thats the old version of the 1x2 (like the waffle plates of the bigger ones).

Maybe it gets clearer if 3023a gets certified (Holly-Wood still has his hold).

[Orion Pobursky]

I'm still confused on what the issue is. 

3023 can still be used and points to the correct file.

[Roland Melkert]

I'm still confused on what the issue is. 

3023 can still be used and points to the correct file.

I think he's mainly concerned about how it broke 3rd party tools which might be slow to update (if ever).

But I agree this is not a LDraw problem

I'm happy he reported it though, as it made me realise it also broke over 40 part snapping shadow files (which I will correct).

[Magnus Forsberg]

... it also broke over 40 part snapping shadow files (which I will correct).

Could you please tell us why a single renumbering has such a big impact?

[Roland Melkert]

Could you please tell us why a single renumbering has such a big impact?

There are lots of parts which are basically a 1x2 plate/tile with some attachment, but they aren't using a common subpart.

So I used the SNAP_INCL meta to add 3023.dat's anti studs to them, but the meta is non recursive so the moved to nullified the inclusion.

Similar changes won't go unnoticed in the future as I added a check for it to the new shadow validation tool.

I'm also considering depreciating SNAP_INCL as it causes potential maintenance problems while you just as easily could've add native antistuds.

[Jaco van der Molen]

I got a bit scared too once I noticed the snapping of good old 1x2 plate didn't work anymore.
Only then today doing some modelling again to notice 3023 was moved to 3023b....
All models that use 3023 still work fine though as to be expected, since 3023.dat still exists.

[Steve]

  folder.JPG (Size: 17.98 KB / Downloads: 87)
   
Yeah - the reason is that all of my tools that I use after MLCad do not recognize 3023b. It is causing me, and I guess many others, issues with StudiO, 3Dpub, exports to Bricklink and just about every other tool I use.

I have both 3023.dat & 3023b in my parts files folder (image provided) yet only 3023b shows in the parts selection panel, so I can't use the old part. I just need it (3023.dat) to show in my parts panel and all will be solved... I have obviously updated my parts list too, to no effect. It really is a huge issue for me, see pics.

If you are not able can you please advise on how I can amend my parts list to change this part number, please? I just need a 3023 (not a 3023a & 3023b) to show in my select panel.. I should say I am not a power user (I'm rather too old and not exactly tech savvy to start delving too deeply into the mechanics behind the magic) so a simple procedure would be much appreciated.

If I was to put in my pennies worth, i'd have to ask why we need to cover all the different variants of parts. Is MLCad a design tool or a catalogue? If its the former, then I see no reason why physically identical parts need multiple entries. All it does is make this great tool frustrating to use with other design software.  

Thanks again.

[Steve]

I have a work around now, but it is clumsy.

Every time I select a 3023b from the parts panel and place it, I can them modify it to a standard 3023 with a right click.

For some reason the 3023 part appears in the drop down modify list but not in my parts panel images or plate list.

Hope this helps others or future releases. Very odd that it features in one section but not the main menu.

[Roland Melkert]

For some reason the 3023 part appears in the drop down modify list but not in my parts panel images or plate list.

I'm not sure as I haven't used MLCad in some time, but you might fix the whole issue by editing 3023.dat (in the parts folder of ldraw).

Change its first line from:
0 ~Moved To 3023b

to something like
0 Plate  1 x  2 (old)

Because I think MLCad excludes 'moved' parts from the main parts palette.

You might need to regenerate parts.lst after as I'm not sure how/if MLCad detects changes.

ps:
The library itself is not going to be 'fixed' as it is not broken, those tools you mentioned need to update their mapping files.

[Nathan S]

I'm not sure as I haven't used MLCad in some time, but you might fix the whole issue by editing 3023.dat (in the parts folder of ldraw).

Change its first line from:
0 ~Moved To 3023b

to something like
0 Plate  1 x  2 (old)

Because I think MLCad excludes 'moved' parts from the main parts palette.

You might need to regenerate parts.lst after as I'm not sure how/if MLCad detects changes.

ps:
The library itself is not going to be 'fixed' as it is not broken, those tools you mentioned need to update their mapping files.

I found an easier fix for MLCad:

Take file 3023a and rename it to 2023.  MLCad's error is with 2023b (the part won't even show up in the individual file).  I renamed 3023a to 3023 and it is back in the part tree and back in my builds.  Thankfully I had only opened up two builds.  I will be keeping this adjusted file to always replace any update.

[Jaco van der Molen]

Could you please tell us why a single renumbering has such a big impact?

I gave this some more thought.

The main pain is opening an LDraw model in Stud.io.
I know many users model in LDraw (MLCad or LDCad) and open in Stud.io for easy rendering.

I use Stud.io for that too.
I also make use of Stud.io's connection to Bricklink to see if any colors I might use do or do not exist.
The direct link to Bricklink from Stud.io to see weather a part is available, how much it costs, etc. is also very usefull.

Now opening a model with 3023b in Stud.io gives a Null brick.
Also, the part is not shown in the partslist and when you upload a model to My Bricklink gallery to say, create a wishlist for the model (I use that all the time), the good old plate 1x2 is not in the inventory.

So yeah, big impact.

The easiest workaround for this however is simple:
Just model in LDCad and use 3023b.
Once the model is complete open the ldr or mpd file in your favorite texteditor and rename all instances of 3023b.dat to 3023.dat.
Save the file and open it in Stud.io or do whatever you do with it to use 3023.

[Jaco van der Molen]

UPDATE on this:
After Stud.io update (don't know which) the "problem" seems to be fixed.

I have a model with 3023b (in white) and this now opens just fine in Stud.io.
I notice that Stud.io has replaced the 3023b with 3023...
Then I uploaded the model to My Studio.
Then I created a wishlist and the white 1x2 plate shows up just fine in the inventory.

HOWEVER...
Doing a building step preview, I noticed my model had a submodel that had a 3023.dat in LBG in the LDraw file.
Stud.io sees this, corrected the part and added a prefix "rename_3023" to the description.

Taking another look in Stud.io I noticed a yellow exclamation mark at the LBG 1x2 plate saying this part is not available in BL.
Examining my new created wishlist in Bricklink, the LBG 1x2 plate is missing!

Also the tooltip for the yellow ! in Stud.io at a 2023.dat says: "Alternative LDraw part. Please replace with an official Stud.io part"

So...
It now seems we can just use 3023b in LDraw and convert to Stud.io or BL with no problem.

Confusing, but OK, I guess...