ok not too sure what happened here, was doing some more testruns with blender to FPSCR. I created what is going to be a base for a water way, however when I exported the model into FPSCR, it looked like it was inside out, or as in like the texture was inside the models faces instead of on the outside.

it all looks right in blender. so I do not know what is going on here, or what I did wrong. any one have any ideas?

I have included some screen shots of what it looks like in blender and two images of what it looks like in FPSCR.

Go back to 2.69, newer versions mess up the direct x export.

yup DVader that was the problem, thank you.

I didn't go back to 2.69, but I took the X export and import script out of 2.69 and put it in the 2.71 folder, because I do like the new layout in 2.71. and it now looks right in FSPCR.....thanks again.

Didn't even know you could do that

to be honest I wasn't sure if it would work or not, but I figured it was worth a try, blender is open source. so I figured there was that chance of it working and it did. wooohooo.

Well you'll have to keep us posted and let us know after several model exports if still no issues I will also redownload the latest blender and copy the scripts over

will do

is it just the io_scene_x folder in addons that you copied over?

Interesting. I have both 2.71 and 2.69 installed and switch between them as and when I need. I never thought to try that.

This is very strange.

When I had 2.70, I tried to swap the Direct X exporter from 2.69 and it didn't work for me?!

Weird. Well done though!

Cheers

Jay.

I've just downloaded Blender 2.72b and it seems to work better with the DirectX-export

Nice, I might have to try this later. I have been wanting the newer features of blender with a working X Exporter!

Good spot Steohl

Cheers

Jay?

Hmm.. I think I jumped to conclusions



After looking closer to Blender 2.72b it seems like some issues still remains. For an example there is a problem when using boolean.

I took a cube and made a hole in it. If I made it in 2.72b but export it to DirectX in 2.69 - the problem still exists.

If I make the same cube with a hole in 2.69, and export to DirectX in 2.72b - it still works.

(the problem that occur is that the hole gets partially obscured)



So the problem doesn't seem to be the DirectX-exporter itself, it seems to have to do with changes in the boolean function. In 2.69 you got more "support edges" for the made hole then in 2.72b. And that is what seems to cause the problem.

Strange.

What do you make out of this?

It's quite rare that I use the boolean feature! I use it purely for high poly renders when manually moving each poly wouldn't be feasible. If i am making game assets, i would always just make the hole myself by moving individual polys and joining the faces. I can't comment on the newer features of blender, i am still using 2.69. I'm not moving anywhere until they release a new version with a stable direct x exporter!

Cheers

Jay.