It appears that blender-generated wavefront files wreak havoc with

jit.gl.model when matrixoutput is set to 1. The object outputs nothing

whatsoever and hence there is no visual output nor an ability to use

blender-generated models for morphing purposes, yet if matrixoutput is set

to 0, the object shows-up just fine in the jit.window.

A quick inspection of the obj files and comparing them with mushrooms.obj

file suggests that in the case of blender-generated file, there is a small

header which says "blender v244" etc. If jit.gl.model matrix output is

trying to parse out vertices (I presume those are points with v in front of

them), perhaps this first v in v244 is messing everything up and making

Any ideas as to how this can be circumvented/fixed? Is there a better export

This is using latest blender (2.44) with Jitter 1.63.

Composition, Music Technology, CCTAD, CHCI

http://www.music.vt.edu/people/faculty/bukvic/

It appears that blender-generated wavefront files wreak havoc with
jit.gl.model when matrixoutput is set to 1. The object outputs nothing
whatsoever and hence there is no visual output nor an ability to use
blender-generated models for morphing purposes, yet if matrixoutput is set
to 0, the object shows-up just fine in the jit.window.

A quick inspection of the obj files and comparing them with mushrooms.obj
file suggests that in the case of blender-generated file, there is a small
header which says "blender v244" etc. If jit.gl.model matrix output is
trying to parse out vertices (I presume those are points with v in front of
them), perhaps this first v in v244 is messing everything up and making
output unreadable.

Any ideas as to how this can be circumvented/fixed? Is there a better export
path from blender?

Ivica Ico Bukvic, D.M.A.
Composition, Music Technology, CCTAD, CHCI
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-1137
(540) 231-5034 (fax)
ico@vt.edu
http://www.music.vt.edu/people/faculty/bukvic/
http://ico.bukvic.net


blender-obj-files-and-matrixoutput

> A quick inspection of the obj files and comparing them with mushrooms.obj

> file suggests that in the case of blender-generated file, there is a small

> header which says "blender v244" etc. If jit.gl.model matrix output is

> trying to parse out vertices (I presume those are points with v in front

> them), perhaps this first v in v244 is messing everything up and making

More inspection suggests this is not the case (originally for some

inexplicable reason my editor opened obj files as binary/hex files--let's

just say their plain text inspection showed that the header in question was

commented out). Could it be the fact that my test object (cube for instance

that is in the default scene when Blender is started) did not have any

> A quick inspection of the obj files and comparing them with mushrooms.obj
> file suggests that in the case of blender-generated file, there is a small
> header which says "blender v244" etc. If jit.gl.model matrix output is
> trying to parse out vertices (I presume those are points with v in front
> of
> them), perhaps this first v in v244 is messing everything up and making
> output unreadable.

More inspection suggests this is not the case (originally for some
inexplicable reason my editor opened obj files as binary/hex files--let's
just say their plain text inspection showed that the header in question was
commented out). Could it be the fact that my test object (cube for instance
that is in the default scene when Blender is started) did not have any
texturing info?

For those seeking answer to similar blender+obj+jitter issues, here's a

Symptom(s): blender-exported wavefront obj files are not compatible with

jit.gl.model's matrixoutput but do display fine when matrixoutput is

Cause: apparently blender's export plugin for the wavefront format is not

entirely format-compliant (so far both wings3d and jitter have complained

about it). 3ds export plugin seems to have some problems as well.

1) export blender object in nendo (.ndo) format

3) export from wings3d in wavefront (.obj) format

What is puzzling however, is since both wings3d and blender are open source,

why hasn't blender project adopted apparently correct implementation of

For those seeking answer to similar blender+obj+jitter issues, here's a
work-around:

Symptom(s): blender-exported wavefront obj files are not compatible with
jit.gl.model's matrixoutput but do display fine when matrixoutput is
disabled

Cause: apparently blender's export plugin for the wavefront format is not
entirely format-compliant (so far both wings3d and jitter have complained
about it). 3ds export plugin seems to have some problems as well.

1) export blender object in nendo (.ndo) format
2) import it in wings3d
3) export from wings3d in wavefront (.obj) format

What is puzzling however, is since both wings3d and blender are open source,
why hasn't blender project adopted apparently correct implementation of
wavefront .obj format found in wings3d?

blender obj files and matrixoutput