search

ryerrabelli / jmonkeyengine

Automatically exported from code.google.com/p/jmonkeyengine
0 stars 0 forks source link

Conversion of Blend-Files include Texturedata uncompressed #419

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. open SDK 
2. unzip attached files to Models-Folder
3. convert. File is huge.

I'm not sure if that is a SDK-Issue but here I saw the symptoms.
It doesn't matter if the texture is packed infile or as external file. 
Blender-Importer's Texture-Helper looks fine.

Original issue reported on code.google.com by thomas.t...@googlemail.com on 13 Nov 2011 at 6:31

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by normen667 on 14 Nov 2011 at 12:45

GoogleCodeExporter commented 8 years ago 
Ok, this seems to be a blender 2.5 only problem! Using a blend 2.49 file with 
the "Import Model"-Tool in jme worked as intended. The same workflow with more 
or less the same file (just created with 2.5) resulted in a j3o with the 
texture included.

Original comment by thomas.t...@googlemail.com on 14 Nov 2011 at 4:51

GoogleCodeExporter commented 8 years ago 
Sry, due to a mistake in my test the 2.49-file only seemed to work (it actually 
only mapped the image that was connected via uv-editor and I didn't apply any 
image). So the problem is the same for 2.49
Normen and me have tracked down the problem that when loading a blend-file a 
new texture is genereated. If you try to export an object and the exporter 
tries to locate the texture in the asset-manager! If that doesn't exists the 
whole data is attached (uncompressed) to the j3o.

Original comment by thomas.t...@googlemail.com on 16 Nov 2011 at 2:30

GoogleCodeExporter commented 8 years ago 
As this is not an issue per se but expected behavior as of now I close this 
issue.

Original comment by normen667 on 16 Nov 2011 at 2:33