Often problems during exporting
Here you could see from the log that latest material processed was named <TireRubber>, and for this scene we were lucky the name was obvious and this material associated to an object with same name
Desktop: Ubuntu 13.04 x64 - i7-3770K @ 3.5GHz - 32GB DDR3 - GTX670 2048MB
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
-
liquid orange
- Posts: 54
- Joined: Sat Dec 11, 2010 11:43 pm
Got it 
Thank you. I think the best is to remove every texture before exporting.
Thank you. I think the best is to remove every texture before exporting.Hardware: Nvidia GTS 450, core 2 quad q6600, 8 GB Ram
Software: Win 7 64, Blender 2.65, OctaneV1.0 RC3
Software: Win 7 64, Blender 2.65, OctaneV1.0 RC3
One thing that I noticed about texture is that disabled textures slots in Blender give an error message when exporting. I think that error messages are necessary for missing textures, but disabled textures are generally willingly disabled, in order to not export them.
Currently, if we want to not export some textures to Octane while not deleting these textures from the project, we have to work on a copy of the original blend file with the textures actually removed.
Currently, if we want to not export some textures to Octane while not deleting these textures from the project, we have to work on a copy of the original blend file with the textures actually removed.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.