Collision lost?
by Diogo Rios · in Constructor · 08/05/2007 (8:16 am) · 10 replies
Ok, im getting my head around this but it makes no sense.
Ive created a simple box primitive, then i used a hollow brush to it. then i used option: "Export as Dif" and then i put the dif into a new mission. Everytime there are walls that have no collision, is this normal behaviour??
Ive created a simple box primitive, then i used a hollow brush to it. then i used option: "Export as Dif" and then i put the dif into a new mission. Everytime there are walls that have no collision, is this normal behaviour??
About the author
#2
The stupid thing is that I have a more complex box ... using multiple brushes so that I can texture it better ... and that has colliison working fine... go figure.
edit: I posted at the same time as Jay. I think he's right. If you re-open your file and re-export, it will work ... I've done that on the truck model, but not the basic cube.
How exactly does this *?@! get past QA? Is there a QA department, or are we the QA department? I wouldn't mind being paid for all of the wasted time that I've had dealing with Constructor issues.
08/05/2007 (7:02 pm)
It shouldn't be non-collidible. Constructor seems hosed once again. I couldn't even get the hollow tool to work .. it was giving me double-geometry. So I decided to manually make large shapes for my 3 walls, ceiling, and floor... one end open to walk through... and I had the same collision-not-working problem.The stupid thing is that I have a more complex box ... using multiple brushes so that I can texture it better ... and that has colliison working fine... go figure.
edit: I posted at the same time as Jay. I think he's right. If you re-open your file and re-export, it will work ... I've done that on the truck model, but not the basic cube.
How exactly does this *?@! get past QA? Is there a QA department, or are we the QA department? I wouldn't mind being paid for all of the wasted time that I've had dealing with Constructor issues.
#3
thanks jay, hope a garagegames looks at this.
08/05/2007 (7:04 pm)
Well jays solution worked for me but this is a very simple procedure and to have this bug is quite unsettling :sthanks jay, hope a garagegames looks at this.
#4
08/11/2007 (7:55 am)
Echo on this, closing, opening and re-exporting with the normal Export to Dif works to preserve both collisions and shape exports in 1.03
#5
I export using the DTS exporter in Max and the file has collision in Torque (I always test this first).
I import the DTS into Constructor, make my scene and then "Export as DIF."
There is no collision with the DTS' in Torque.
I had this issue last quarter in school and ended up just hand placing my meshes in Torque which was a pain as we all probably know.
I tried the "save the scene, close it, and then reload it and re-export" but that doesn't work. Is that something that only works in 1.0.3?
What am I doing wrong here?
On a side note: I had told my instructor at school about the issue last quarter and he had posted on the forums about it. I've been searching for the thread but have been unable to find it so far. Don't quote me but I remember that my instructor had posted/said there is a collision issue and a Garage Games employee said it was fixed in 1.0.2 and then posted or edited the post later saying that there was an issue and would be looking into it.
08/11/2007 (8:15 pm)
I'm having a collision issue as well but I haven't upgraded to 1.0.3 yet, still using 1.0.2 as last Monday there were post on the forums saying that is was super buggy.I export using the DTS exporter in Max and the file has collision in Torque (I always test this first).
I import the DTS into Constructor, make my scene and then "Export as DIF."
There is no collision with the DTS' in Torque.
I had this issue last quarter in school and ended up just hand placing my meshes in Torque which was a pain as we all probably know.
I tried the "save the scene, close it, and then reload it and re-export" but that doesn't work. Is that something that only works in 1.0.3?
What am I doing wrong here?
On a side note: I had told my instructor at school about the issue last quarter and he had posted on the forums about it. I've been searching for the thread but have been unable to find it so far. Don't quote me but I remember that my instructor had posted/said there is a collision issue and a Garage Games employee said it was fixed in 1.0.2 and then posted or edited the post later saying that there was an issue and would be looking into it.
#6
09/11/2007 (5:18 am)
Bumping this. Just spent ~1 hour trying to figure out why the collision on my box (!) wasn't working...turned out to be same thing that's been posted here - save, close, re-open scene then export as usual to fix collision. Hopefully this is getting sorted in the next version of Constructor.
#7
This also happened with the floor and walls in a simple box truck that had 1 interior wall with a doorway.
So, no, this is not working. If it is for everyone else, please let me know your techniqes, or if you can and are willing to, please send me the constructor file so that I can see how the buildings were built. I've tried many different methods with the same failing result.
In other news, the portals are seemingly working better.
09/11/2007 (11:05 am)
I'm back, and saying that this issue is NOT FIXED by saving, closing, and reopening and exporting. I have wasted countless hours on this issue again, and it's pissing me off to no end. Every single time, I have one exterior wall that is missing collision. One step further shows that if I break my floor up into more than one brush, only 1 will have colliison and the other(s) will have no collision and has the player falling through the floor. This also happens on my interior walls/floor (2nd story building) ... no collision whatsoever.This also happened with the floor and walls in a simple box truck that had 1 interior wall with a doorway.
So, no, this is not working. If it is for everyone else, please let me know your techniqes, or if you can and are willing to, please send me the constructor file so that I can see how the buildings were built. I've tried many different methods with the same failing result.
In other news, the portals are seemingly working better.
#8
09/11/2007 (5:20 pm)
Did you save it as a .map file, close the scene, and then open the .map file? That's worked for all of my collision issues.
#9
09/17/2007 (4:20 pm)
I've tried saving as both .MAP and .CSX to no avail. I can try again with the .MAP though ... I'm sure that most of the time I tried with .CSX files... maybe when I tried .MAP I did another test instead of the suggested one. Does it matter, .MAP vs .CSX?
#10
If it is the same problem i had it doesnt matter if it is .map or .csx, I actually used .csx file.
Just a notice, my problem was using the hollow brush on any primitive and collision would not work until i saved the file and reopened. only then the dif file that came from that would have the proper collisions in game.
gl
09/17/2007 (4:40 pm)
Well i have read some of ppls posts and my conclusion is that maybe we are talking about different issues of collision problems.If it is the same problem i had it doesnt matter if it is .map or .csx, I actually used .csx file.
Just a notice, my problem was using the hollow brush on any primitive and collision would not work until i saved the file and reopened. only then the dif file that came from that would have the proper collisions in game.
gl
Torque 3D Owner Jay Barnson
It's worked for me so far, but you are right... that's a nasty little bug.