Skip to content
This repository has been archived by the owner on May 18, 2019. It is now read-only.

Add LEGO logo to studs #122

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

BertVanRaemdonck
Copy link
Contributor

The user now has the possibility to select an option that puts the LEGO logo on top off all studs in the file. A requirement for this is that the "logo3.dat" file from the LDraw parts tracker is located in the standard p folder.

We still have to figure out the best way to deal with this logo3.dat file. I imagine it's better to just store it somewhere with the script, instead of messing with the users LDraw libraries.
Also, some kind of warning would be nice, because this option tends to slow down the import process a lot because for each part, the logo file has to be read. For this reason especially, it would be great to only import each file once in the beginning and then reference the data.
Finally, I didn't really do anything to ensure the logo's face the right direction. I thought I read somewhere they should be defined right, but in unofficial parts that could not be the case. The question is if errors would be very noticeable.

PS: I'm currently modelling a new logo.dat file that represents the logo's with a mold mark in them for added realism. Would be fun to include this as well, although then it will become hard to judge which stud to assing the mold mark to...

The user now has the possibility to select an option that puts the LEGO logo on top off all studs in the file. A requirement for this is that the "logo3.dat" file from the LDraw parts tracker is located in the standard p folder.
Note that I also changed the threshold for the cleanup, because otherwise the logo would loose its geometry because it's so small. To make sure the thershold is fit for all import scales, the threshold is now multiplied by the import scale.
@le717 le717 changed the title Add logo function Add LEGO logo to studs Mar 10, 2016
@le717
Copy link
Owner

le717 commented Mar 11, 2016

I've almost got my laptop back, so I'll try to look at this as soon as I can. :)

@BertVanRaemdonck
Copy link
Contributor Author

I've been getting pretty good-looking results with normal maps, but the thing is that it isn't very evident how to implement it in the code because of the UV map needed. It's something I'll have to look into, but I have the impression that normal maps are the way to go to keep the files manageable. Thoughts?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants