silly question on cameras...

[CorSton]

...why must we preserve them in .git files (using CAMedit)?

 

I have tried to delete those values from a custom module .git file, and nothing (by the "camera" PoVs) is changed in the conversation moments.

 

Used for cutscenes?

 

[CorSton]

ok, after some testing, understood what cameras do -_-

 

anyone figured out how to set (easily) up cameras? and where are cam_models some animated cutscenes use? and camera angles?

 

[Xcom]

Originally posted by CorSton

ok, after some testing, understood what cameras do -_-

 

Share the knowledge, bro.

 

Also, maybe you'll find this thread interesting:

http://www.lucasforums.com/showthread.php?s=&threadid=145924

[CorSton]

oh well, I discovered something unknown... just to me (IE, the cameras PoVs must be used to switch "regular" conversations side switching).

 

Not amazing stuff

[tk102]

Back to your original question: why use CamEdit? It's because the CameraList structure list in the .git files contain some new field types for Position and Orientation. Fred Tetra was able to determine that Position (field type 17) was 12 bytes worth of packed floats (3 of them: x, y, z) while Orientation (field type 16) was 16 bytes worth of packed floats (4 of them).

 

Now the venerable GFFEditor.exe utility that we all know and love was created prior to these field specifications. So if a .git file is edited using GFFEditor, those new fields are not stored correctly, resulting in crazy camera locations and angles.

 

CamEdit exports these fields intact and can reimport them after GFFEditor corrupts the original .git during editing.