chiffie Posted November 27, 2018 Share Posted November 27, 2018 I'm having problem with using imported `.obj` into blender and then exported to babylonJS. I've downloaded `.obj` model containing `.dds` textures. Imported to babylonJS which looked fine. Import automatically assigned these textures to model. Blender view Then after export to babylonJS these textures went dark. BabylonJS view I noticed that while exporting to babylonJS exporter already processed textures as dark. Image bellow is auto-generated in export Exported image What did I wrong and how can I fix it? * blender v2.79 * babylonJS export v5.6.4 * babylonJS availible at http://chiffie.yweb.sk/bak/ * blender file availible at http://chiffie.yweb.sk/bak/kamion.blend [1]: https://i.imgur.com/oSPM83y.png [2]: https://i.imgur.com/bOVUWHZ.png [3]: https://i.imgur.com/dvtRPMb.jpg Quote Link to comment Share on other sites More sharing options...
JCPalmer Posted November 27, 2018 Share Posted November 27, 2018 I did do a quick look, and have a best guess. I do not believe that blender uses .dds file. Combine that with the version of the exporter you are using can only bake from the cycle render. This is going to bake black. There seems to be a .dds add-on, but you are on your own. I am working on a version of the exporter for Blender 2.80, which does not always bake, but it is a ways off. In that case, the files could just pass through, maybe. I would look at loading the .obj file directly. Quote Link to comment Share on other sites More sharing options...
chiffie Posted November 27, 2018 Author Share Posted November 27, 2018 47 minutes ago, JCPalmer said: I did do a quick look, and have a best guess. I do not believe that blender uses .dds file. Combine that with the version of the exporter you are using can only bake from the cycle render. This is going to bake black. There seems to be a .dds add-on, but you are on your own. I am working on a version of the exporter for Blender 2.80, which does not always bake, but it is a ways off. In that case, the files could just pass through, maybe. I would look at loading the .obj file directly. Actualy you were right about `.dds`. After exporting I converted dds files to jpg and replaced auto generated jpegs by converted one. Is there any way to tell blender/babylon exporter to stop auto-generating pictures? Because it takes way too long (10+ mins). EDIT: I also changed `.dds` texture to `.jpg` texture in node editor, but it didn't help. Is there possibility to only copy texture file and stop creating new one? Quote Link to comment Share on other sites More sharing options...
JCPalmer Posted November 27, 2018 Share Posted November 27, 2018 If you are referring to auto baking, yes and no. If you switch to the Internal Render and change the inputs for it, then yes. If you are staying with the Cycles render, no (but that is what I am working on for 2.80, since the internal render is going away) trevordev 1 Quote Link to comment Share on other sites More sharing options...
V!nc3r Posted November 28, 2018 Share Posted November 28, 2018 Yep, as JCPalmer said, switch to Internal Render (and pay attention to texture influence assignation). For now if you absolutly wants keep Cycles, use gltf file format instead (by using this your file will use the PBR workflow). You'll also maybe be interested in a tutorial I made about Blender to BJS workflow. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.