<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: keeping texture mapping when exporting objects in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/keeping-texture-mapping-when-exporting-objects/m-p/249956#M9179</link>
    <description>Now I understand that the texture mapping is actually kept when defined with coords and all that. &lt;BR /&gt;
It seems that it is just the Picture command that is not translated into correct texture mappings. &lt;BR /&gt;
That's too bad because it is a pain to do basic mapping while it is so easy to use the picture command.</description>
    <pubDate>Fri, 15 Jan 2016 13:31:32 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-01-15T13:31:32Z</dc:date>
    <item>
      <title>keeping texture mapping when exporting objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/keeping-texture-mapping-when-exporting-objects/m-p/249955#M9178</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;As far as I've tried I couldn't find a way to keep correct texture mapping of objects when the texture is defined in the script after exporting to .obj or .3ds&lt;BR /&gt;
It's getting me mad.&lt;BR /&gt;
When it is defined via align texture on a usual tool evrything's fine. &lt;BR /&gt;
But if the texture is defined in a script, as a picture for example it doesn't retain the crrect texture position, although it is alright in the 3d opengl view.&lt;BR /&gt;
You can try with the usual bitmap People object in the library.&lt;BR /&gt;
Is that a bug or am I missing something?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 15 Jan 2016 13:21:31 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/keeping-texture-mapping-when-exporting-objects/m-p/249955#M9178</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-01-15T13:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: keeping texture mapping when exporting objects</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/keeping-texture-mapping-when-exporting-objects/m-p/249956#M9179</link>
      <description>Now I understand that the texture mapping is actually kept when defined with coords and all that. &lt;BR /&gt;
It seems that it is just the Picture command that is not translated into correct texture mappings. &lt;BR /&gt;
That's too bad because it is a pain to do basic mapping while it is so easy to use the picture command.</description>
      <pubDate>Fri, 15 Jan 2016 13:31:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/keeping-texture-mapping-when-exporting-objects/m-p/249956#M9179</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-01-15T13:31:32Z</dc:date>
    </item>
  </channel>
</rss>

