Tripwire Interactive Forums

Go Back   Tripwire Interactive Forums > Red Orchestra 2 / Rising Storm Forums > RO2/RS Modifications > Level Design

Reply
Click here to go to the first Dev post in this thread.  
Thread Tools Display Modes
  #1  
Old 06-24-2012, 09:35 PM
Srinidhalaya Srinidhalaya is offline
Senior Member
 
Join Date: Jan 2011
Posts: 594
Default FBX vs ASE and Collision

When exporting static mesh objects, if I do FBX, the collision does not import at all. If I do the same exact objects but ASE, the collision is imported correctly, but anytime I import an ASE, I get a "too many vertacies generated" error, but the mesh loads just fine.

The naming is obviously correct, or it wouldn't work in ASE. Is there something that has to be done to import FBX with collision? I'm using the UDN website documentation, but its very limited. Does the error even matter when importing ASE, is there something I need to do to prevent it?
Reply With Quote
  Click here to go to the next developer post in this thread.   #2  
Old 06-25-2012, 10:57 AM
[TW]Swag [TW]Swag is offline
Tripwire Interactive Staff
 
Join Date: May 2009
Location: Yonder, Georgia
Posts: 304
Default

I am gathering information. Please stand by.
Reply With Quote
  #3  
Old 06-25-2012, 11:01 AM
Srinidhalaya Srinidhalaya is offline
Senior Member
 
Join Date: Jan 2011
Posts: 594
Default

Ohh, and Im using the UBX_meshname prefix. UCX_ didnt work with .FBX file extension either, didn't try with .ase, it would have takeen too long to rename all 78 collision box's, for the one section of wall im trying to export..

Last edited by Srinidhalaya; 06-25-2012 at 11:03 AM.
Reply With Quote
  Click here to go to the next developer post in this thread.   #4  
Old 06-25-2012, 11:18 AM
[TW]Swag [TW]Swag is offline
Tripwire Interactive Staff
 
Join Date: May 2009
Location: Yonder, Georgia
Posts: 304
Default

Oh, if you are using numerous collision boxes then you may be potentially exceeding the capability of the engine to digest them all. The engine will break down a convex collision model into small "bite size" pieces. Try super simplifying your collision model down to < 4 and see what the import process does to your collision model.
Reply With Quote
  #5  
Old 06-25-2012, 11:26 AM
Srinidhalaya Srinidhalaya is offline
Senior Member
 
Join Date: Jan 2011
Posts: 594
Default

That makes since. Essentially its just a wall with windows. My problem is I don't want to lose all my windows, and I don't want to break it up into too many mesh to import. I'll see what I can do though.

What about the vertacies error, that occurs when importing anything ASE, including a basic cube, without collision mesh or texture.

EDIT:
Yeah, FBX did import the collision with low number box's. Is there a more simple way to make proper window collision, besides surrounding it with box's?
I'll try breaking down my structure walls into quadrants...This is the beast I'm working on....
http://forums.tripwireinteractive.co...ad.php?t=80614

There will be roughly 260 windows in this building intact, both sides totaled. I plan to blow several chuncks of the building away from "bombing runs", so mabye half that, 130 finshed product...

Last edited by Srinidhalaya; 06-25-2012 at 11:33 AM.
Reply With Quote
  Click here to go to the next developer post in this thread.   #6  
Old 06-25-2012, 01:42 PM
[TW]Swag [TW]Swag is offline
Tripwire Interactive Staff
 
Join Date: May 2009
Location: Yonder, Georgia
Posts: 304
Default

To be honest, I'd suggest avoiding having a collision model on the building itself and just use engine's BlockingVolume to get the collision on the building model. You'd want to maintain the floors with proper mesh with collision or BSP but the bulk of the collision work can be handled by BlockingVolumes.
Reply With Quote
  #7  
Old 06-25-2012, 03:42 PM
Srinidhalaya Srinidhalaya is offline
Senior Member
 
Join Date: Jan 2011
Posts: 594
Default

EDIT:
Can blocking volumes overlap each other? If so, that would cut down on work load. I assume they would work just like any volume, and the volume would need to be limited to basically that same "space" the collision mesh would, but collision mesh cannot overlap. It would reduce the collision box count from my 78 box's (not overlapping), to about 15-20 volumes (overlapping).
Is there a limit on blocking volumes? I know with the brushes, once I passed about a hundred or so, textures and entire brushes would disappear; and if so, then I would have to be very selective about what I volume block vs collision mesh.
Thanks for the tip! Can we rename you, from Swag to, DaKind? :P

Last edited by Srinidhalaya; 06-25-2012 at 05:07 PM.
Reply With Quote
  This is the last developer post in this thread.   #8  
Old 06-25-2012, 05:27 PM
[TW]Swag [TW]Swag is offline
Tripwire Interactive Staff
 
Join Date: May 2009
Location: Yonder, Georgia
Posts: 304
Default

Quote:
Originally Posted by Srinidhalaya View Post
EDIT:
Can blocking volumes overlap each other? If so, that would cut down on work load. I assume they would work just like any volume, and the volume would need to be limited to basically that same "space" the collision mesh would, but collision mesh cannot overlap. It would reduce the collision box count from my 78 box's (not overlapping), to about 15-20 volumes (overlapping).
Is there a limit on blocking volumes? I know with the brushes, once I passed about a hundred or so, textures and entire brushes would disappear; and if so, then I would have to be very selective about what I volume block vs collision mesh.
Thanks for the tip! Can we rename you, from Swag to, DaKind? :P
I am not aware of any reason why BlockingVolume cannot intersect each other. You can use the console command STAT COLLISION to get a read on the collision time. It usually stays super, super low < 1ms normally.

You can call me anything you like except late for supper.

EDIT:

Post 256, aw yeah. My posts are finally on the grid.
Reply With Quote
  #9  
Old 06-26-2012, 06:07 PM
Srinidhalaya Srinidhalaya is offline
Senior Member
 
Join Date: Jan 2011
Posts: 594
Default

wow wow, we barely know each other, I think dinner is a bit...soon? I haven't even seen the inside of your tank yet.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 11:58 AM.


Powered by vBulletin®
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2005 - 2013, Tripwire Interactive, LLC