+- Silgrad Tower from the Ashes (https://www.silgradmodding.net/forum)
+-- Forum: Discussions for Silgrad Tower TES IV (Oblivion) & TES III (Morrowind) (https://www.silgradmodding.net/forum/Forum-Discussions-for-Silgrad-Tower-TES-IV-Oblivion-TES-III-Morrowind)
+--- Forum: FAQ Board TESIV. (https://www.silgradmodding.net/forum/Forum-FAQ-Board-TESIV)
+---- Forum: FAQ Archive (https://www.silgradmodding.net/forum/Forum-FAQ-Archive)
+---- Thread: [3DS] Collision: the easy way out using gundalf's exporter (/Thread-3DS-Collision-the-easy-way-out-using-gundalf-s-exporter)
- Razorwing - 08-26-2006
I got a pleasant surprise just now, as it seems that the new version of NifTools 3D Studio Max NIF exporter is able to export doublesided textures :bananarock:
So now it seems we can have both collision-enabled models and doublesided textures at the same time in exported models, allowing tapestries and awnings and other models which have planar meshes to be visible from both directions without having to doubleback the polys. Neat
- Acrobat Rieder - 08-28-2006
jeah nice.
Hope exporting with mutiple collision meshes is next feature!
- Razorwing - 08-28-2006
Quote:Originally posted by Acrobat Rieder
jeah nice.
Hope exporting with mutiple collision meshes is next feature!
You know, I would agree with you, but I made a 'mistake' with a model I exported the other day and... well... what do you make of it? Sure looks like the new version of the exporter *can* export multiple collision meshes.
![[Image: th_DoubleCollisionObject.jpg]](http://s11.photobucket.com/albums/a177/SilgradTower/DoubleCollisionObject.jpg)
Then again I did talk to one of their developers recently and mentioned gundalf's exporter had that capability at one point. Perhaps they dug through his old code and brought it back?
- Leone - 08-29-2006
Just attach all of your collision meshes together before exporting. Since the model can only be static (no havok data) it doesn't matter. OB supports this just fine, intersections and concavity are not a problem (*tested in-game* :goodjob: ).
- Razorwing - 08-29-2006
Quote:Originally posted by Leone
Just attach all of your collision meshes together before exporting. Since the model can only be static (no havok data) it doesn't matter. OB supports this just fine, intersections and concavity are not a problem (*tested in-game* :goodjob: ).
Huh. Cool
I ran into problems on another model with multiple collision meshes, so your explanation makes perfect sense. The tileset model in my screenshot was indeed grouped.
- Andysaurus - 08-31-2006
The exporter dosent seem to work correctly with Max6
I imported simple nifs from Blender via the WRL formal (old VRML) - it loses the UV's but so what, all I want are the colission meshes.
When exported the colission mesh(s) are invisible, and the mesh(s) are re-oriented. I repeated with one of my Max6 FarCry Mercenary files. The main character meshes were exported ok this time (but I dont know what to make of the boned stuff - it's rotated) - but no visible colission meshes.
Any ideas ???
Its a pity Nifskope cant duplicate/cut&paste colission meshes correctly, then I wouldent need to try using Max, cause the simple scalable colission meshes used in containers,tables, etc work just fine for my static models.
- Acrobat Rieder - 09-03-2006
Quote:Originally posted by LeoneHi,
Just attach all of your collision meshes together before exporting. Since the model can only be static (no havok data) it doesn't matter. OB supports this just fine, intersections and concavity are not a problem (*tested in-game* :goodjob: ).
with this solution I got some great performance problems with large meshes!
This one is a part of our fortress...
![[Image: festung.jpg]](http://www.uni-koblenz.de/~crieder/kram/festung.jpg)
und here the collision mesh, not at all very much polys, 800 or so.
![[Image: collision.jpg]](http://www.uni-koblenz.de/~crieder/kram/collision.jpg)
But the fps goes down because the collision mesh is to big. If a chararcter stands at the gate, all polys of the large object will be tested of collision. So I divided this large mesh into multiple smaller meshes and the problem didn't appear, because just all polys are tested, the character is near by!
In fact the polygon count is the same but the polys are subdivided into smaller meshes! That's why I hope multiple collision meshes solve my problem. Then I don't have to add so much several collision meshes by hand..
greets,
Christian
- Andysaurus - 09-03-2006
quote:
Originally posted by Leone
Just attach all of your collision meshes together before exporting. Since the model can only be static (no havok data) it doesn't matter. OB supports this just fine, intersections and concavity are not a problem (*tested in-game* ).
/quote
Its worth noting that there are TWO path formats (also used in Morrowind) - use '\''s if you are trying to pick up a standard Bethesda Texture, and '/' if you are picking up a local texture. Chances are your editor gnerated this error
- Akatosh - 09-03-2006
It doesn't work! 3ds Max 8 has error when i want to export as nif file.
- Akatosh - 09-14-2006
Nobody helps me?
Oh! Orry for my English, but i'm from Poland.