# Problem with PVRGeoPOD and Blender

**URL:** <https://forums.imgtec.com/t/problem-with-pvrgeopod-and-blender/1186>\
**Category:** PowerVR Insider\
**Tags:** pvrgeopod\
**Created:** [September 14, 2011, 6:27pm UTC](https://forums.imgtec.com/t/problem-with-pvrgeopod-and-blender/1186 "2011-09-14T18:27:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![claymontgomery](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/claymontgomery/32/132_2.png) [@claymontgomery](https://forums.imgtec.com/u/claymontgomery)\
**Post date:** [September 14, 2011, 6:27pm UTC](https://forums.imgtec.com/t/problem-with-pvrgeopod-and-blender/1186/1 "2011-09-14T18:27:05Z")

</div>

&nbsp;&nbsp; I have been testing the new POD exporter from the 2.8 SDK with Blender 2.49b and I think I have found a bug.&nbsp; The problem seems to be that I can only use a single solid color material in the scene.&nbsp; Whenever I try to use 2 or more solid colored materials (no textures) every object in the scene gets assigned the same material index (0) when it is exported to POD.&nbsp; If I export the same scene to Collada then use Collada2POD instead, it works correctly.   
  
&nbsp; This problem is very easy to reproduce.&nbsp; Simply create a scene with 2 cubes and assign different solid materials to them, then export it with the POD exporter.&nbsp; Both of the materials are placed into the POD file, but the mesh nodes for both cubes will index the same material.

---

<div class="post-metadata">

**Author:** ![GordonMaclachlan](https://avatars.discourse-cdn.com/v4/letter/g/c68b51/32.png) [@GordonMaclachlan](https://forums.imgtec.com/u/GordonMaclachlan)\
**Post date:** [September 15, 2011, 8:17am UTC](https://forums.imgtec.com/t/problem-with-pvrgeopod-and-blender/1186/2 "2011-09-15T08:17:42Z")

</div>

Thanks for reporting this. We should be releasing a new version of the PVRGeoPOD Blender plugin (for Blender 2.49b) shortly (in the next week or so) and this has several fixes, one of which may clear up this issue.  
  
  
  
  
  
I have filed this issue as BRN34445, however and we will look into it anyway.