T3d Beta 1 Bug - Weapon Goes through terrain

#1 That's an old, old problem. Happens in every version of Torque. It looks like there's a thing called a pushback node, I think, that can be added to a weapon's tip that just might fix that -- but I don't believe anyone has ever made use of it.

Have you noticed that the rifle is about the scale of a punt gun? Freaking huge it is ;)

#2 yeah i noticed, its ridicuosly big!

well if its been in every previous version of torque, nows the time to eradicate it!:D

#3 The Combat Starter Kit had a unique work-around for it, but a side effect of their solution was that it allowed you to see into and through Interiors & objects. It was also unfortunate that when looking through a wall with a small weapon mounted it caused you fall into and through the object and then through the terrain.

#4 thats incredibly annoying, iv seen other engines where this does not happen, how do they acheive it =S do they extend the bounding box around the player + the weapon, rather than just the player (this is an assumption).

#5 ..or don't clip the mounted weapon in 1st person when you render.

#6 what a good idea Andreas, but how simple is that to implement? if it where surely somebody would have done it by now =]

#7 Would probably look strange either way. Will try and look into this tonight and post my findings here.

#8 well it will look better than what we currently have for sure! How comes nobody @ GG has gotten round to fixing this? it seems like a pretty essential flaw =[

#9 This is no engine bug
This is a setup issue
If your character can walk that far up to the object (-> collision sphere) / bend down that much (break himself appart), its really your fault.

if you don't care about physical correctness, there is naturally always the possibility to set the object to always render on top by putting it in the corresponding render queue.
But otherwise you would give the weapon its own capsule collider and prevent it from penetrating objects.

#10 Having physics (collision) on mounted weapons isn't that of a great idea always, especially in an FPS. Think about a player turning around real fast and having a weapon mounted with collision. Resolving that collision in a reasonable way could have hilarious consequences.

I do agree on it not being an engine bug however, but more of an implementation specific thing.

#11 can we change the collision sphere (is it a sphere or a box?) of an object(player) at run time? if so, is it not possible that we can extend the collision sphere of a player to include his weapon when he switches to it?

So if we have a large rifle like the sniper rifle in the demo, it would extend our collision sphere so that we cant poke our gun through walls?

Does that sound like a reasonable allround solution? it would make it look physicly correct, and *shouldnt* have a detrimental effect on performance? what do you guys think?

#12 I think it's a box, and you can change it on runtime (at least I've done it in previous Torque versions with some modifications to the engine).

Doing it that way would mean you'd have a huge hitbox on the players for other to hit with their weapons, so you'd probably want to handle collision testing differently for projectiles (which I'm not sure if Torque has support for atm, but should be done anyways).

#13 Torque cant use the collision sphere for projectile hit detection surely? that would be insanely inacurate......

The hitbox, should be a dumbed down skeletel group of boxes based off of your players skeleton. And the collision mesh/sphere should be entirely seperate used to handle bumping against objects and physical interactions, no?

They must be 2 seperate things? however i am very very new to the torque scene.... so dont slay me if im wrong.

#14 I honestly don't remember at the moment, but I seem to remember at least older versions doing that, and I haven't seen anything about changes to this in T3D. Please correct me if I'm wrong here!

#15 Would be nice to have some input from GG here.

If the hitboxes and collision meshes are seperate then the solution outlined in post#11 should work, and should be an engine feature as it effects most if not all game genres.

If they are the same (god forbid) then it will require serious rethinking. And you cant have that sort of hit detection in a mordern engine! Accuracy is a critical component of any game!

Edit: A thread worth looking at, that is similair to this todo with the hitbox/collision system located here: www.garagegames.com/community/forums/viewthread/91463

#16

Quote:It looks like there's a thing called a pushback node

Actually the Muzzlepoint will do the same thing in code if its exported with the weapon model. Basicly it acts as a simple collision detection and will push the mounted image back into the camera a bit (the hope of course being that its enough that it goes into the players collision box far enough you don't get a nasty clip).

#17 I take it then that the weapon models that where included in the FPS kit dont have this node on them then? as it happens to all the weapons?

Could we see a working example of this?