![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
It turns out I celebrated too soon.
I got Wings to export a textured cube that I could import into a DirectX
program (via XNA). Worked great.
However, as soon as I make anything more complicated, like a "T" shape, I
find that some of the faces behave like they're wound in the wrong
direction, with the normal pointing into the object instead of outwards.
It's correct in Wings, just not when being drawn.
Has anyone here been playing with this?
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> However, as soon as I make anything more complicated, like a "T" shape, I
> find that some of the faces behave like they're wound in the wrong
> direction, with the normal pointing into the object instead of outwards.
> It's correct in Wings, just not when being drawn.
>
> Has anyone here been playing with this?
No, but I found it equally hard to export to a .X from Blender. I struggled
for ages with files that wouldn't even open with the .X viewer (and the
error messages weren't very helpful). In the end after much trial and error
I realised that none of the material names can have spaces in them (I think
there was some maximum length too), all modifiers must be "Applied" to the
meshes before you export, and the exporter recalculates all normals itself
no matter how you have them set up in Blender. This is quite annoying, but
I guess I need to improve it myself if I want better for free. I don't
really fancy learning a new programming language for this...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
scott wrote:
> No, but I found it equally hard to export to a .X from Blender.
Oh good. I won't bash my head against that one, then. :-)
I'm going to try installing poseray, and see if I can go
wings->.obj->PoseRay->.X or something.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
scott wrote:
> No, but I found it equally hard to export to a .X from Blender.
Well, it seems PoseRay doesn't *output* .X files.
However, if I use the DirectX Viewer (thanks for reminding me of that) it
looks like the model itself is OK. It's possibly just XNA messing up the
import or something. Or newer versions of DirectX perhaps.
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |