Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[alelink]

hello,
I've created a simple mesh in Blender,
I've renamed in a proper manner all the object (walk_, ...).
The scene editor loads the file, display the camera's name, but not the mesh.
If I override the FOV, I can see the walkpoint I've inserted from blender.
If need I can post the 3ds file.

is this a know problem?
is a scale problem?

thanks

[Jerrot]

I've created a simple mesh in Blender,
The scene editor loads the file, display the camera's name, but not the mesh.

I assume you used my extended exporter script for it? Hmm, I don't know this problem yet, though I didn't test the exporter with newer Blender builds. But there shouldn't be a problem about that actually... so I've got no idea, but feel free to send a link to the 3DS - or even better the Blender file - and I'll look into.

[alelink]

Hello Jerrot,
this is the link to the blender file: www.overcast.it/sample/3dsWalkMap.zip
there's a cube in the scene that I use to target the camera, because I render in Maya and then I create the
collision mesh in blender.
I use the 2.37a version.

thanks

[Jerrot]

Ok, I'll have a closer look into later today, couldn't find what's wrong on the first sight. Just a first remark for now: Unfortunately you must not used targeted cameras, they don't work (3DS doesn't support them correctly, although it "somehow" saves them).

[alelink]

Hello,
thanks for helpin' me.

Blender doesn't support target cameras, I've constrained the camera to look
to the cube.
It isn't proper a camera with target, I think

[Jerrot]

Blender doesn't support target cameras, I've constrained the camera to look
to the cube.

Ah, right, I saw the constraint and mismatched it with 3ds max, which supports them, sorry. Still too much to do here on work, I'll retry in about 5 hours (ugh... darn, it's too hot to work!).

[Jerrot]

I didn't get why it's not working yet. Maybe there is really something different in newer Blender versions, but right now I can't test it. But I keep it in mind and will check it out later - if necessary I'll try to upgrade the exporter somewhen. I hope not though.

[alelink]

Hello,
I've tryied to export using Blender 2.36, and did'nt work again.

[Nihil]

I think I found the bug (at least it worked here):

In Blender 2.35 they changed the API, so that the object-matrix is calculated differently now - that's why the geometry is out of place now. To overcome this just open the script and change the lines containing

matrix = obj.getMatrix()

to

matrix = objGetMatrix('old_worldspace')
(should be there 3 times)

Hope that works.

[alelink]

HEllo,
thanks for reply,

are you sure that the right method is objGetMatrix() and not obj.GetMatrix('old_worldspace') ?

[Nihil]

No, you are right, I missed the dot :-) Oh, and it's getMatrix, not GetMatrix.

[alelink]

HEllo,
the right method was: obj.getMatrix('old_worldspace'), or so the script works....
....but for me WME doesn't display the mesh correctly.

Nihil, which Blender release you use? I use the 2.37.
WME loads and display the mesh right?


thanks

[Nihil]

I use 2.37a, but it should work with all versions from 2.35 on.

What exactly is wrong? Does it at least display something now or has nothing changed yet?

[alelink]

no,
it doesn't display anything....
only if I change manually the FOV can see the 3 walkpoint I inserted.

you can see everything?

[Nihil]

Hmm, I look into it, don't know what could have happened there.

[Nihil]

Ok, meta pointed me in the right direction: The other problem is the size - the files exported with Blender are simply to small. So just scale anything up (don't know the right value, guess we have to try and error), and then export again, that should work (I just tried it with your file, it worked).

No no one shall ever say again that size doesnt matter :-)

[alelink]

Thanks Nihil!
now works!

[metamorphium]

no,
it doesn't display anything....
only if I change manually the FOV can see the 3 walkpoint I inserted.

you can see everything?

Try to resize the walk plane -> make it way way bigger. ;-)