let me just say that I feel a little boxed in with the current pcactormove, since it seems like it has a lot of support for thirdperson movement, but firstperson movment is a lot worse, and I have to do a lot of the movement by hand, such as mouse movement. How difficult would it be to write or extend the current one? I do like a lot of the functionality available right now (cal3d actions, etc.), but I want to customize it for a firstperson shooter. Any suggestions?

let me just say that I feel a little boxed in with the current pcactormove, since it seems like it has a lot of support for thirdperson movement, but firstperson movment is a lot worse, and I have to do a lot of the movement by hand, such as mouse movement. How difficult would it be to write or extend the current one? I do like a lot of the functionality available right now (cal3d actions, etc.), but I want to customize it for a firstperson shooter. Any suggestions?

Thanks.

Well I gladly accept patches for enhancements. Especially a mouselook would be very nice to have. I don't think extending pcactormove is too hard as it is really a relatively simple class.

That is something I am also concerned about. Do you know, perhaps, why yaw movements and transformations of the actual iCamera in a pcdefaultcamera don't affect the camera view? I will look into some of these things, see if there is anything I could mess with.

That is something I am also concerned about. Do you know, perhaps, why yaw movements and transformations of the actual iCamera in a pcdefaultcamera don't affect the camera view? I will look into some of these things, see if there is anything I could mess with.

You shouldn't touch the iCamera indeed. The camera property class assumes full control. It is perfectly possible to do mouselook by using the api in the camera property class instead. I believe there are some posts about this topic on this forum somewhere.

Yes, and one of them was mine. The small detail that I couldn't figure out and that no one really told me why is that you can only move the camera property class's pitch, not the yaw, which makes full camera mouse look difficult to impossible. Instead I mixed it with actormove rotations and a camera move pitch, but that is only a hack and the movement is still not perfect.

Yes, and one of them was mine. The small detail that I couldn't figure out and that no one really told me why is that you can only move the camera property class's pitch, not the yaw, which makes full camera mouse look difficult to impossible. Instead I mixed it with actormove rotations and a camera move pitch, but that is only a hack and the movement is still not perfect.

Is this a problem you are aware of or is it desired functionality?

This might depend on the current mode you're using. Yaw probably only works in some of the modes. Which camera mode are you using?

BTW. I'd like to add that you should perhaps wait a bit with this. Someone is busy making a totally new camera class (more or less compatible) in CEL. It should be working relatively soon. It will handle mouse look natively.

Really? Great. Well, about the mode, I was using firstperson mode, but it works in a few other ones. And you know what, when I think about it, that makes perfect sense why it doesn't work it firstperson mode. It is only moving the camera, and not the actor. That's why the pitch moves...hmm...I guess I was expecting that functionality to be built into the actor class. But, like you said, it seems such functionality is coming soon, so I will wait

Really? Great. Well, about the mode, I was using firstperson mode, but it works in a few other ones. And you know what, when I think about it, that makes perfect sense why it doesn't work it firstperson mode. It is only moving the camera, and not the actor. That's why the pitch moves...hmm...I guess I was expecting that functionality to be built into the actor class. But, like you said, it seems such functionality is coming soon, so I will wait

Also, is there currently a feature/limitation where you can't see any bit of your mesh when in firstperson camera mode? An example of this is seeing the hands hold a weapon, or looking down at the feet/knees.

Also, is there currently a feature/limitation where you can't see any bit of your mesh when in firstperson camera mode? An example of this is seeing the hands hold a weapon, or looking down at the feet/knees.

At this moment the camera automatically makes the mesh invisible if it switches to first person mode. The reason is to avoid various limbs floating in front of the camera. Handling of a weapon should be done differently I think.

What if you have sockets connecting weapons on the hands? Couldn't it be a nice way to show an extension of the character holding a weapon, rather than just the weapon itself or fake hands? Are submeshes hidden too? Is there anyway to turn this off to see the effect?

What if you have sockets connecting weapons on the hands? Couldn't it be a nice way to show an extension of the character holding a weapon, rather than just the weapon itself or fake hands? Are submeshes hidden too? Is there anyway to turn this off to see the effect?

You can only turn this off by modifying the code right now. Look for CS_ENTITY_INVISIBLE.