For GetCurrentCamera(), there's more than just Internal mode (0) and External Mode (1).

All known camera modes:
0 - Internal
1 - External
4 - Idle (Circling Kyle)
5 - Death Cam

cams 2 and 3 might exist, but I can't imagine what they might be. I'll test and see what they are, if anything.
Camera modes 2 and 3 crash when you try to change to them.

There is apparently a mode 6 of some sort... the screen freezes and acts like HOM (the only 'HOM' I managed to get was text messages overlapping each other due to JK not refreshing the screen; the overlay map (tab key) might cause it too, I didn't think to try it). The camera might have been outside the level 1 area, because I could still hear bryarbolt impacts (like I was some distance away). But all in all, I think this camera is probably totally useless, which is why I won't add it to the list above.

I also tried cam modes 7-10, but they do nothing, so I assume there are no other working cam modes.

Hopefully this info might help someone... Descent_Pilot I think was going to make a modified death camera thing in his pistol mod wasn't he? This could possibly simplify things for him. (or maybe it won't but it's still nice to know)

Also, if you set the camera to mode 4, JK changes to the idle camera, as one would expect, but JK also acts as if it is idle mode -- that is, it will go back to mode 0 or 1 when you move, press a hotkey, etc. (if you're in mode 5 and go to mode 4, it goes to mode 1 when you move/press a hotkey).

Excellent find!

Nice find man! Too bad we can't make mode 4 stay until we want it to go away. I wonder if the 'frozen player' flags would work. Like say change to mode 4, then freeze the player, then release on a timer. We could possibly make this work for a matrix-like cam. Like on a 'kill' saber attack, fire the projectile, play the key separate. If it hits, run the cam and freeze the controls, allowing the player to see a cool spin cam, then unfreeze with Sleep(GetKeyLen(saber_kill_key));

What do you think?

Question 2: Can you move in mode 5, or does the death cam freeze the player?

Ohh! Ohh! Jedi Kombat!
Kyle beats Jerec... rahn goes "Finish Him!"
Freezeplayer and set to cam 4
Kyle does an awesome saber finishing move in slowmo
that would be cool


Oh, yeah, mode 5 works just like the mode 0 and 1 cameras -- you can move, shoot, etc just the same, and won't exit out of mode 5. The only difference is you can't CycleCamera() to mode 5 -- you have to get to it by SetCurrentCamera(5)

You do know the saber doesn't fire projectiles, but actually looks for collisions with the blade to do damage right?

Anyway, the finds on the camera is wonderful. I'm gonna play with it while I do some more bug smashing in Basilica this afternoon.

QM

This is cool, Darth Slaw.

I will list it in my DM updates to send to SaberMaster.

I had suspected this, just hadn't gotten around to testing. I figured there must be more modes, because of the way a particular camera cog was acting. (It checked for 0 and 1, and switched to a third mode appropriately... On idle / death, the camera acted funky.) Saves me time

Here's camera 5 in action:

VERY cool. If we could use this for a matrix style move, it'd be awesome.

Here's another q:

Does cam 5 rotate with the player, or does the yaw stay static?

No, it stays static a certain distance from the player, no matter where the player moves.

A most interesting discovery - kudos Slaw :). I see Grismath is already putting it to good use

-Jackpot

Hmm, about that Matrix thing...I'll just point out that ParseArg("move","none") results in the player being completely frozen in current frame of animation. You can't shoot, move, and all controls are frozen, even escape to the menu and chat if I recall correctly. It would probably work on a timer, but within that time, the game would be frozen.

I was thinking along the lines of:



I know that's not exactly right, but hey, I haven't coded in 2 or so years. After clearing the actor flags, you wouldn't really have to switch cams since moving would do it automatically.

Dumb questions: When you set camera to 4, do the idle keys start, and what does it look like when you offset the First Person cam backwards a bit? You see fists and a saber? You like that?

Switching to cam 4 via cog will not start the idle keys.

The only way to offset the internal cam and still see the first person weapon model is to use ParseArg(player, "eyeoffset=(x/y/z)"); (changing the x y and z values)
Setting the camera to an object other than the player for 1st person camera will render as in 3rd person -- it will render the player model (like kyle) instead of the internal weapon model (you know how the kyle model is invisible to you in 1st person, aka no legs? well now kyle will be visible)

SetPOVShake(VectorSet(X, Y, Z), VectorSet(0, 0, 0), 0, 0);
will also let you offset the internal camera and still keep the weapon model. Y is the important value, as you can simulate zooming in/out.

SetPOVShake(VectorSet(0, 0, 0), VectorSet(0, 0, 0), 0, 0);
will reset your view back to where it is by default.

QM

Ohhh
I'm gonna try this out!

I for one think that's worth a mention in the DM as well... obvious, but overlooked (anyone else have that tendency to think too hard and miss the simple things? :p)

It actually is mentioned in the DM. Look up SetPOVShake and read the notes at the bottom. It doesn't suggest using SetPOVShake for zooming purposes, but it does mention that setting the reset speed values to 0 will keep the camera at altered coordinates.

QM

Oh, well then my wish is granted
(Obviously I've never looked up that verb before )