-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing textures on minifig torsos exported out of Studio. #64
Comments
The method that ldraw uses for textures is different that the one that stud.io uses, which will cause missing textures when viewing your part in anything but stud.io. LDraw used projection of image files on your disk to display textures, where stud.io textures are base64 encoded PNGs stored in the file itself. I'm working on implementing texture support in my plugin. https://github.com/cuddlyogre/ExportLdraw At a quick glance, implementing stud.io texture support appears possible. stud.io support in general is certainly something I'm researching. The problem is that stud.io files are really just password protected zip files, so due to legalities concerning DRM, it might not be legal. |
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->Awesome. Thanks for letting me know and supporting the plugin. I don’t think the original author Is developing it further. Sent from Mail for Windows 10 From: cuddlyogreSent: Monday, 26 April 2021 8:25 AMTo: TobyLobster/ImportLDrawCc: webdogk9; AuthorSubject: Re: [TobyLobster/ImportLDraw] Missing textures on minifig torsos exported out of Studio. (#64) The method that ldraw uses for textures is different that the one that stud.io uses, which will cause missing textures when viewing your part in anything but stud.io.I'm working on implementing texture support in my plugin. https://github.com/cuddlyogre/ExportLdrawstud.io support is certainly something I'm researching. The problem is that stud.io files are really just password protected zip files, so due to legalities concerning DRM, it might not be legal.—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
|
Some official parts - for instance 973p13 don't seem to carry over texture information into Blender.
https://www.ldraw.org/parts/official-part-lookup.html?folder=parts&partid=973p13
Other parts that have been custom made by BrickLink also can be affected, such as 973pb1161 - which is an unofficial part, so you sort of expect that to get a bit wonky.
Is there a way to import parts with textures that aren't vertex based? I know one workaround is to just apply the texture with UV mapping, but it would be nice to not have to do that for complex scenes.
This post seems to allude to a method.
https://www.eurobricks.com/forum/index.php?/forums/topic/175033-converting-parts-with-textures-from-studio-to-ldraw/
The text was updated successfully, but these errors were encountered: