So I did a bit of looking through the code and I found out it screws up in
TransformAnglesToPlayerSpace. Not sure exactly why this isn't working, but
setting SetIgnorePitch to true deals with the issue, but you loose that
somewhat neat rotation the object is given when you move the object above
you
I just noticed my physgun is also causing this problem, but my normal pickup
isn't. The only difference between the two is the normal pickup doesnt alter
the rotation of the object depending on how you have it in the air. What it
looks like to me is the changes in rotation of the object while being
I really don't recommend doing this. There's no reason you can't modify
CSDKPlayer to do what you want it to do. Also the whole point of subclassing
is so that you can make the subclass have different behavior, or perhaps
multiple subclasses with different behaviors. However, the aforementioned
fac
Cool. Your fellow list mates would be very thankful if you kept them updated. :)
--Bob
On Sun, Aug 30, 2009 at 6:36 AM, Denis Craig wrote:
>
> When you move the prop with the physcannon, it updates the angles on the
> clientside as normal but takes a very long time to update on the server, so
I want to bring up the issue of projectiles hanging in the air for a
moment after spawning again. The last time it was discussed the solution
given was to predict:
http://www.mail-archive.com/hlcoders@list.valvesoftware.com/msg21121.html
This is a bad idea though, because it causes the projecti
When you move the prop with the physcannon, it updates the angles on the
clientside as normal but takes a very long time to update on the server, so
obviously when you drop the prop it'll snap to the server's angles instead.
Working on a fix at the moment, I think it's happening somewhere in th
yes, only a batch compiler solves it. If you wonder it's still compiling or
not go to your task manager and look at mem usage.
About improving hammer, in hammer 3.5 i was able to use the camera when the
texture editor was open. This allowed me to rotate around a object for
example and select all f
Did this ever get resolved? If so I'd love to know the solution, I'm
working through this bug myself.
--Bob
On Wed, Jul 29, 2009 at 2:49 PM, James Murray wrote:
> What file should I look in?
>
> On Mon, Jul 27, 2009 at 2:43 PM, Ryan Sheffer wrote:
>
>> The movement prediction is screwed up, b
8 matches
Mail list logo
