Tweet
Dear Andrei,
There appears to be a bug in the way proxies are rendering using 2.69. If I create a proxy of a mesh, with either an old version of VRB, or with 2.69, the mesh loads properly with 2.68, but only faces on one of the materials renders when the proxy is loaded using 2.69. So the problem appears to be with loading / assigning materials to the proxy with 2.69 custom build, not with creating the proxy.
I tried to create a test file which shows this, but the problem couldn't be reproduced. The file I created had no textures, but the problematic file had several textures on the materials. Unfortunately I can't post the file with the problem on the site.
I'm using the latest custom build from cgdo.ru, and I amended the utils.py manually to correct texture mapping. I don't think that this build is successfully updating the exporter using the button. The button seemed to work (told me exporter was updated) but updates I knew had been added weren't being made to VRB. When I manually updated the utils.py, the only way to get blender to update was to open it as Administrator and click the update export button (which only applied the manually changed utils.py).
The reason I say this, is because I am not sure if I'm using the latest exporter, and don't want to report a bug that's already been fixed.
Many thanks for your hard work.
Rob.
There appears to be a bug in the way proxies are rendering using 2.69. If I create a proxy of a mesh, with either an old version of VRB, or with 2.69, the mesh loads properly with 2.68, but only faces on one of the materials renders when the proxy is loaded using 2.69. So the problem appears to be with loading / assigning materials to the proxy with 2.69 custom build, not with creating the proxy.
I tried to create a test file which shows this, but the problem couldn't be reproduced. The file I created had no textures, but the problematic file had several textures on the materials. Unfortunately I can't post the file with the problem on the site.
I'm using the latest custom build from cgdo.ru, and I amended the utils.py manually to correct texture mapping. I don't think that this build is successfully updating the exporter using the button. The button seemed to work (told me exporter was updated) but updates I knew had been added weren't being made to VRB. When I manually updated the utils.py, the only way to get blender to update was to open it as Administrator and click the update export button (which only applied the manually changed utils.py).
The reason I say this, is because I am not sure if I'm using the latest exporter, and don't want to report a bug that's already been fixed.
Many thanks for your hard work.
Rob.
Comment