Hey guys. I was playing around with the AddCameraShot values earlier today and I found out some things that I thought would be convenient to post.

_____________________________________________

Function layout:

AddCameraShot(rotate_y, rotate_z, UNKNOWN, rotate_x, position_x, position_y, position_z)

The rotate values are most likely in radians (instead of degrees - i.e., the value can range from -1.0 to 1.0) and the position values are most likely individual grid units (or possibly quarters of them) in Zero Editor with the center - 0,0,0 - being the very center of the grid.


Example code with comments:
Notes regarding 'UNKNOWN':

The unknown value is...weird. Here's a snippet of a conversation regarding it (in italics) between me and AQT:

Maybe the UNKNOWN value is a zoom of some sort.

That's what AQT and I originally thought, but it seems to rotate the camera diagonally in a weird way without any sort of zoom.

GAB wrote:Maybe the UNKNOWN value is a zoom of some sort.

Or an FOV change?

Teancum wrote:

GAB wrote:Maybe the UNKNOWN value is a zoom of some sort.

Or an FOV change?

Possibly, but not likely, considering the value's range seems to be -1.0 to 1.0 like with the rotation values, though one could somewhat argue that the maximum (1.0) and minimum (-1.0) field of view "final" values are hardcoded. It would be a weird thing to hardcode, though. Also, judging from my tests, the camera's actual field of view never appeared to change, but rather the rotation of the camera did instead.

you can use the debug executable and use free cam, use the command thing and type "dumpcamera" to print coordinates. they are saved in a text file in the gamedata folder.

hope this helps (sounds like you were editing the numbers manually in map script)

anthonybf2 wrote:sounds like you were editing the numbers manually in map script

...to find out what each value does.

You could also try changing the camera shot in real time via LUA in the debug console (SetCameraPosition, etc.). I'm not sure if any of those functions will have all the parameters you want though.

The rotation values being displayed are likely quaternions.

I can't find my notes on this (I used to have some of this commented on in a test script; I'll update this if I can dig it up), but an easier way to test this is going to be with CreateMatrix(), which uses the same inputs. You'll be able to examine position and rotation much easier (and externally) that way.

AceMastermind wrote:The rotation values being displayed are likely quaternions.

That would make a lot more sense, especially considering quaternions consist of four values/dimensions (or something like that).

Maveritchell wrote:I can't find my notes on this (I used to have some of this commented on in a test script; I'll update this if I can dig it up), but an easier way to test this is going to be with CreateMatrix(), which uses the same inputs. You'll be able to examine position and rotation much easier (and externally) that way.

Notes would be great. I'll also try to mess around with CreateMatrix().