So I figured out my modeling, compiling and all that.
I get into Gmod, and the collision model is not lined up with the visual model.
Could this be a problem with my .qc or just the way I did something.
They are in the same spot in 3ds Max, and I can't seem to figure this out.
[editline]07:27PM[/editline]
I've been trying for a while.
I really don't want to go into 3ds max and move the model to the side, especially when I start doing larger, more advanced models.
its has nothing to do with your QC just your phymodel.smd
can you post a screenshot?
Yeah, if you dont mind waiting a bit. It takes a while for Gmod to load.
[editline]07:56PM[/editline]
[IMG]http://img.photobucket.com/albums/v496/phil5555/teee.gif[/IMG]
[editline]07:56PM[/editline]
[IMG]http://img.photobucket.com/albums/v496/phil5555/tele.gif[/IMG]
[editline]07:57PM[/editline]
Sorry for the large image size.
[editline]07:58PM[/editline]
You see though, I'm pushing the plate into the collision part. In the top pic, anything to the right is not actually there, I can go right through it.
Have you tried resetting the transforms on your collision model? That's a potential cause for this, too.
[QUOTE=OpethRockr55;19586246]Have you tried resetting the transforms on your collision model? That's a potential cause for this, too.[/QUOTE]
That is the cause.
He just needs to either move the pivots to the same location in each smd, add bones to each smd or compile with $staticprop.
Any 3 of those will fix the problem.
I was thinking bones actually.
Just add two bones in the same spot?
I'll try that, thanks!
[editline]07:31AM[/editline]
well i didn't try that, i found out how to move the pivot points and that was easier.
Alright, now I have a new problem. I go to compile it with GUIStudioMDl... and it tells me I have something less than .5 inches thick.
I had that before and I just went in and messed around with some things and it was fine.
But now it's happening every time and it gives me the message once, then tells me it needs to close GUIStudio.
Sorry, you need to Log In to post a reply to this thread.