Difference between revisions of "KMP Editing/Cameras"

From Custom Mario Kart
Jump to navigation Jump to search
m
Line 1: Line 1:
 +
This page is a part of the '''Custom Track Tutorial'''. [[Custom Track Tutorial|Back to the main tutorial page]].
 
{{KMP}}
 
{{KMP}}
 
==Introduction==
 
==Introduction==
 +
This page will explain the basics of how [[KMP]] set cameras work in Mario Kart Wii. There are two basic types of camera: opening pan and replay. Opening pans play before the start of VS and Grand Prix races. Replay cameras play after a VS or Time Trial race ends, during live view of an online race and during ghost replay. Good cameras can make your track look much better, but can be difficult to make. Improperly set cameras can make the game crash in any of these points. Make sure you always have backups of your KMP when editing. You can use any KMP editor for this. This page will use pictures of [[KMP Cloud]] with the KMP file from Mario Circuit (castle_course.szs) and the [[KCL]] exported to OBJ with Wiimms Tools used as background.
  
−
Improperly configured camera settings can cause game crashes during opening pans, replays and post-match winning laps. Back up your [[KMP]] before you start editing.<br>
+
When working with cameras, speed values are usually set in units per frame (speeds set in Route entries) or units per hundred frames (speeds set in CAME entry). Mario Kart Wii usually runs at 60 frames per second, so you can divide the values by 60 to convert them to units per second.
−
Good cameras will make your level look much more professional, but editing them can be difficult to master. It's very difficult to make Cameras. [[Wiimms SZS Tools]] will make the Camera Editing easier because all values that you need are noted here.<br>
 
−
In editing Cameras you need some knowledge about calculating in Hex. So if you have no knowledge about it, it will be more difficult to understand. Follow these steps and you will learn how to do it.<br>
 
−
Before editing Cameras have a look at this list. You will need to learn some values for making a good Camera faster:
 
  
−
{{KMP CAME header}}
+
These are the main values set in a Camera point entry. Not all settings are known:
 +
{| class="wikitable"
 +
|+ CAME entry data structure
 +
|-
 +
! Setting
 +
! Description
 +
! Names in<br/>[[Wiimms SZS Tools|Wiimms Tools]]
 +
! Column name in<br/>[[KMP Modifier]]
 +
! Box name in<br />[[KMP Cloud]]
 +
|-
 +
| Type
 +
| '''[[{{PAGENAME}}#Camera types|Camera type]]'''.
 +
| <tt>type</tt>
 +
| Type
 +
| Type
 +
|-
 +
| Next
 +
| '''Next camera''' entry index. Value 0xFF means: no next camera.
 +
| <tt>next</tt>
 +
| Next
 +
| Next
 +
|-
 +
| ?
 +
| Camshake. '''Unknown''' (always 0).
 +
| <tt>unknown</tt>
 +
| Shake
 +
| Shake
 +
|-
 +
| Route ID
 +
| '''Route''' used by the camera. This is index link into the [[#POTI|POTI]] section. -1 (0xFF) means ''"no route"''.
 +
| <tt>route</tt>
 +
| Route
 +
| Route
 +
|-
 +
| Camera Speed
 +
|  '''Velocity of the camera point''' in units per 100 frames (=units/1.67 sec).
 +
| <tt>v(came)</tt>
 +
| V(Cam)
 +
| Pointspeed
 +
|-
 +
| Zoom Speed
 +
| '''Velocity of zooming''' in units per 100 frames (=units/1.67 sec).
 +
| <tt>v(zoom)</tt>
 +
| V(Zoom)
 +
| Zoomspeed
 +
|-
 +
| View Speed
 +
| '''Velocity of the view point''' in units per 100 frames (=units/1.67 sec).
 +
| <tt>v(v.pt)</tt>
 +
| V(View)
 +
| Viewspeed
 +
|-
 +
| ?
 +
| Start flag. '''Unknown'''.
 +
| <tt>unknown</tt>
 +
| Flag<br/>(First 2 digits)
 +
| Start
 +
|-
 +
| ?
 +
| Movie flag. '''Unknown'''.
 +
| <tt>unknown</tt>
 +
| Flag<br/>(Second 2 digits)
 +
| Movie
 +
|-
 +
| Position (X, Y, Z)
 +
| A 3D '''position''' vector of the camera. Ignored if the camera uses routes.
 +
| <tt>position (x,y,z)</tt>
 +
| X, Y and Z
 +
| PositionX, PositionY and PositionZ
 +
|-
 +
| Rotation (X, Y, Z)
 +
| A 3D '''rotation''' vector. Almost always (0, 0, 0).
 +
| <tt>rotation (x,y,z)</tt>
 +
| Roll, Yaw and Pitch
 +
| RotationX, RotationY and RotationZ
 +
|-
 +
| Zoom Start
 +
| '''Zoom start''': Starting field of view. Angles >180 create curious effects.
 +
| <tt>zoom beg</tt>
 +
| Zoom
 +
| Zoomstart
 +
|-
 +
| Zoom End
 +
| '''Zoom end'''. Final field of view. "Zoom speed" controls the speed of zooming.
 +
| <tt>zoom end</tt>
 +
| Zoom2
 +
| Zoomend.
 +
|-
 +
| View Position Start/Relative Position (X, Y, Z)
 +
| Start vector of the '''view point''' ([[Camera#CAME_Types|camera type 5]]) or the relative camera '''position''' ([[{{PAGENAME}}#Camera types|camera type 3]]).
 +
| <tt>view point beg (x,y,z)</tt>
 +
| View(x), View(y) and View(z)
 +
| ViewStartX, ViewStartY and ViewStartZ
 +
|-
 +
| View Position End (X, Y, Z)
 +
| (Destination) vector of the '''view point'''.
 +
| <tt>view point end (x,y,z)</tt>
 +
| View2(x), View2(y) and View2(z)
 +
| ViewEndX, ViewEndY and ViewEndZ
 +
|-
 +
| Time
 +
| The '''time''' for how long this Camera is active, in frames.
 +
| <tt>sec*60</tt>
 +
| Time
 +
| Time
 +
|}
 +
&rarr; See more in-depth information on the page: [[CAME]]
  
−
==Camera Editing/Step by Step guide==
+
[[Image:KMP New8 CAME.png|thumb|right|300px|KMP Cloud open in Mario Circuit's cameras; notice the route for the selected camera is also shown]]
 +
Cameras are found in the [[CAME]] section of the [[KMP Editing|KMP Editor]]. They can be placed like any normal object. The position only matters on certain camera types. Make sure the Route being used by each camera is unique to it; The same route should not be shared between multiple cameras or between cameras and objects.
  
−
Cameras can be placed like any normal object. The position only matters when using certain camera settings. Cameras are found in the [[CAME]] section of the [[KMP Editing|KMP Editor]].<br>
+
==Camera types==
−
Setting a route that belongs to a camera and an object can often cause a freeze. Be sure that you only use one Routes for an object or the camera.
+
{|class="wikitable"
 +
|+CAME Types
 +
|-
 +
! Value !! Name !! Type !! Explication !!Route controlled?
 +
|-
 +
| 00 || Goal || Goal || Activates immediately after passing the goal; with the player as the origin, the camera's ''View Start'' position both follows and looks at the player.<br>It can be reactivated as a Replay Camera if linked to an AREA, but does not display in spectator (online/waiting) mode  || {{no|No}}
 +
|-
 +
| 01 || FixSearch || Replay || Camera stays static in ''View Start'' location, and always looks towards the player || {{no|No}}
 +
|-
 +
| 02 || PathSearch || Replay || Route controlled, always looks at the player || {{yes|Yes}}
 +
|-
 +
| 03 || KartFollow || Replay || With the player as the origin, the camera's ''View Start'' position both follows and looks at the player || {{no|No}}
 +
|-
 +
| 04 || KartPathFollow || Replay/Opening || From its position, it looks at ''View Start'' and shifts view to ''View End'' || {{no|No}}
 +
|-
 +
| 05 || OP_FixMoveAt || Opening || Opening camera, follows route; from its position, it looks at ''View Start'' and shifts view to ''View End'' || {{yes|Yes}}
 +
|-
 +
| 06 || OP_PathMoveAt || Opening || Opening camera onboard with same effects as normal drive Camera ('''unsure''') || {{yes|Yes}}
 +
|-
 +
| 07 || MiniGame || Unknown || Unused || {{maybe|???}}
 +
|-
 +
| 08 || MissionSuccess || Unknown || Unused || {{maybe|???}}
 +
|-
 +
|}
  
−
===Opening Pans===
+
Types 04 and 05 are used for opening pans. Types 01 to 04 are used as replay cameras. Type 00 is the default replay camera, activated as soon as you pass the finish line or when no other camera is active.
−
On VS races a sequence of cameras is shown. The exact time of the complete Opening Pan is 12,8s. It is split in to 3 sections with 3,6s, 4,3s and 4,9s (values ''220'', ''257'' and ''294'' found in all Nintendo Tracks).<br>
 
−
The u8 value at offset 0x06 in the CAME section header is the index of the first camera. The next cameras are linked by the u8 value at offset 0x01. Normally 3 cameras are used, but any number can be used.
 
  
−
[[File:CAME_LuigiM.png|1000px]]
+
==Opening Pans==
 +
Opening pans are a set of cameras that are shown before a race starts. [[Nintendo]] always use three cameras, usually with type 05 (although some tracks use camera type 04) with time values of ''220'', ''257'' and ''294'' in this order. This makes the cameras sync up with the song that plays; each camera is linked by the "Next Camera" value in the entry, the last one being -1 (0xFF). Any number of cameras playing for any amount of time is supported, though. If the cameras are too short, the sound will end early; if they are too long, the sound will finish but the cameras will keep playing.
 +
The first camera of the opening pans is set in the header of the CAME section. It can be edited using KMP Cloud or Wiimms Tools. The next cameras are each set in the CAME entry, as seen above.
  
−
The '''first two digits''' in the '''first settings box''' indicate the type of camera. Opening pans have the setting ''05''.  The length of time each camera is displayed is set in '''z5'''. Their values will be ''220'', ''257'' and ''294''; this is to sync the camera transitions with the opening music. You can change it to any other value.<br>
+
The cameras follow a route, always at the speed set in the route settings. The point where the camera looks at is initially the view point start, and it shifts from it to the view point end in the specified speed. At the same time, the field of view, changes from the starting to the ending one at the specified speed. If any of the movements (route, view point or zoom) ends before the set time for the camera passes, it will just stay where it is.
−
If you found these 3 Cameras, we come to editing them.  
 
  
−
[[File:CAME2_LuigiM.png]]
+
So, to edit the opening cameras, first you should set the routes for them. Make sure the speed set in each point is correct and the camera takes about the same time to follow the route it is set to last. After that, set view point start and end and finally zoom values. Note that the speed of the view point is usually a much higher value, compared to zoom speeds. In KMP Cloud the values are read as hexadecimal.
  
−
The '''last two numbers''' in the '''first settings box''' control the [[KMP_(File_Format)#POTI|Route]] used.  A value of ''FF'' means the camera does not use a route.
+
[[Nintendo]] always shows the racers before the finish line in the third camera pan. You can follow this if you want to.
−
You can find the Opening Route Sections so:
 
  
−
As example in the pic I used SNES Ghost Valley 2. Take the first CAME with the '''z5''' as ''220'', here it is CAME ID 11. Take the Route Settings, here it is "0D", or only D.
+
When testing the camera pans, it's a good idea to set the "Next" value of the last camera for it to loop back to the first one. The cameras will loop endlessly (until you press a button to skip them), allowing you to view them as many times as you want to.
  
−
And now use Hex Calculator:
+
=== Replay Cameras ===
−
D+1=E<br>
+
Replay cameras are much harder to edit and test than opening pans; they require knowledge about KMP [[AREA]]s too. When viewing the replay or live feed, a camera is activated when the player being observed enters an AREA region. It does not deactivate automatically when the player leaves it. See [[KMP Editing#Areas (AREA)|this section]] for information on placing an AREA entry.
−
Now convert it to Decimal:
 
−
E=14<br>
 
−
Finally: The first Opening Route Section is Route Section 14. <br>
 
−
This is the same prinzip like the [[Object]]s choose their Routes.
 
  
−
Do this with the other two values and you know which Routes you have to use for your Opening Pans.<br>
+
Important values for the AREA entry:
 +
{| class="wikitable"
 +
|+ AREA entry data structure
 +
|-
 +
! Setting !! Description
 +
|-
 +
| Type || [[AREA type|Area '''type''']]. Type 0 is the one which refers to a camera.
 +
|-
 +
| Camera ID || '''Index of [[Camera|CAME]]'''. Camera this AREA refers to.
 +
|-
 +
| Position (X, Y, Z) || A '''3D position vector''' of the area.
 +
|-
 +
| Rotation (X, Y, Z) || A '''[[3D rotation vector]]''' of the area.
 +
|-
 +
| Scale (X, Y, Z) || A '''3D scale vector''' of the area.
 +
|}
  
−
After you found, which Routes are used for this cameras, go to these and drag them like you want it. One option is dragging them in the near of special objects or some buildings you made in your Custom Track for making a short review. The Camera will move along this route. It is advisable to drag the last Opening Camera Route to the Startline. Also you can change your Routes:<br>
+
All other AREA settings shouold be left untouched, if you're working with the AREAs only for the cameras. Areas are also used for other things, see [[AREA type]] for this.
−
Search after the Route Section, where the Camera should move, as example Route Section 18.<br>
 
−
Convert the Decimal number to Hex:
 
−
18=12<br>
 
−
Then subtract it with 1 on Hex Calculator:
 
−
12-1=11<br>
 
  
−
And now write down this number in the Route Setting Box where the Route IDs are.<br>
+
With your AREA region moved, rotated and scaled the way you want it to be and linked to the ID of a camera, it's time to set the camera settings. Depending on which camera type you choose (from 00 to 04), it will be set up differently.
−
For testing your Opening Pans it is good to link the last Opening Camera to the first to have an unlimited view. It sounds difficult but with one progress you made it. It's pretty simple.
 
  
−
[[File:CAME5 LuigiM.png]]
+
====Camera Type 00 (Goal)====
 +
This is the default camera that looks directly at you as soon as the race finishes. It does not need an AREA to be activated, but it can be activated by one if needed. It does not use a route, so the route should be set to -1 (0xFF). The camera point place is ignored. It's recommended to just copy all the settings that were present in the type 00 camera of a Nintendo track. There should be only one type 00 camera in your KMP.
  
−
This Settings are the next Camera in Hex, so. ''CAME 11'' has the the next ''CAME 12'' (Convert Hex to Decimal; 0C=12), The ''CAME 12'' has next ''CAME 13'' and ''CAME 13'' has none(=FF). Change the FF to the Hex digit of the first CAME. Example:<br>
+
====Camera Type 01 (FixSearch)====
−
The first Camera is ''CAME 11'' so Convert the 11 to Hex:
+
It does not use a route, so the route should be set to -1 (0xFF). It also does not have a view point start, end or speed; only zoom start, end and speed values are set. This camera stays in the camera point place and looks directly at the player. It's the easiest camera type to set up.
−
11=0B<br>
 
−
So I change the FF to 0B and now the Cameras are looped. You see; it's pretty simple.
 
−
<br>
 
−
<br>
 
−
This was found out by [[user:Wiimm|Wiimm]]. For his analysis go to [[Cameras/Reference#Opening_Pan|Wiimms Opening Pan Analysis]].
 
  
−
[[File:CAME4 LuigiM.png]]
+
====Camera Type 02 (PathSearch)====
 +
This camera is similar to the opening pan. It follows a route at the speed specified in the route, so the camera point place is ignored. It does not have a view point start, end or speed; only zoom start, end and speed values are set. The camera always looks directly at the player.
  
−
Now we define the points where the Cameras watch. The ''Start View Point'' shows where the Camera watch at the begin and the ''End View Point'' at the end of the Camera Intros. ''x3'' and ''y3'' controls the zoom, which is not used in Opening Pans, so you can ignore it.<br>
+
====Camera Type 03 (KartFollow)====
−
This is how to do:<br>
+
''With the player as the origin, the camera's ''View Start'' position both follows and looks at the player, it does not use a route''
−
First you search an object or a place, where your camera should look. Then you take the ''x'', ''y'' and ''z'' values and take it to the ''z3'', ''x4'' and ''y4'' values (''x'' to ''z3''; ''y'' to ''x4''; ''z'' to ''y4'').
 
  
−
=== Cameras while replays and after Race ===
+
====Camera Type 04 (KartPathFollow)====
−
Now we come to the after-race Cameras. Here, you will need knowledge about CAME Types and AREA. It's all explained here what they are and how to use them.
+
This camera is similar to the opening pan, and can be used as an opening pan camera. It stays in the camera point place and does not use a route, so the route should be set to -1 (0xFF). It has a view point start, end and speed; and also zoom start, end and speed. The camera looks from the view start point to the view end point, which moves at the specified speed.
−
 
 
−
==== AREA ====
 
−
First, go to AREA.
 
−
 
 
−
[[File:AREA-LuigiM.png]]<br>
 
−
[[File:AREA LuigiM 2.png]]
 
−
 
 
−
<pre>
 
−
menu      AREAtype  7
 
−
item      Camera  0
 
−
item      ObjClip  1
 
−
item      EfControl  2
 
−
item      FogControl  3
 
−
item      PullControl  4
 
−
item      EnemyFall  5
 
−
item      2DmapArea  6
 
−
</pre>
 
−
 
 
−
The list of the types can be found in the XML file /Race/Course/koopa_course.szs/course.0<br>
 
−
(for other AREA info go to [[KMP_(File_Format)#AREA|AREA]] and [[Cameras/Reference]])
 
−
 
 
−
Important for the after-race Cameras are AREA with Type ''Camera 00'' which are the activators for the CAMEs '''after''' the race. If you drive in the near of one AREA after the race, it will activate the CAME that is written in the Settings (watch at the pics). The other AREA types are unimportant. '''Don't change it!'''<br>
 
−
Drag the first AREA to a point in the near of the Stage. Do it with all other AREAs. Make sure that there are in the right order. It will be easier for CAME Editing.
 
−
 
 
−
==== CAME ====
 
−
 
 
−
[[File:CAME3_LuigiM.png]]
 
−
 
 
−
The cameras after race have some different types:
 
−
*00 = Camera immediately after finishing (the one that looks at you.)
 
−
*01 = ObjClip: Stays in one position but always points to the player. Used during replays.
 
−
*02 = PathSearch
 
−
*03 = KartFollow
 
−
*06 = OP_PathMoveAt<br>
 
−
(for all other types go to [[KMP_(File_Format)#CAME|CAME]] and [[Cameras/Reference]])
 
−
 
 
−
Camera Types 00, 01 and 03 can be used without any routes (Route IDs=FF). Camera Type 02 and 06 need Routes. All these have ''x3'' and ''y3''
 
−
values. If you drive while a replay or after a race in the near of one AREA it will activates the CAME, which is written in the Settings. The Type defines how the Camera is watching at the person:
 
−
*''PathSearch'' activates the Route that is written in the Settings. The Camera follows the Route and looks at you.
 
−
*''OP_PathMoveAt'' activates the Route like ''PathSearch''. But it'll swing around you. It is very difficult to edit and control!
 
−
*''ObjClip'' stays in one position and looks at you.
 
−
*''KartFollow'' is a Camera that follows you all the time. It needs after the Settings ''x3'' and ''y3'' the values from ''z3'' to ''x5''
 
−
*''Camera immediately after finishing'' is a Camera that follows you all the time, if you gone through the finishline, until you drove in the near of one AREA. It needs after the Settings ''x3'' and ''y3'' the values from ''z3'' to ''x5''.<br>
 
−
Finally, you only have to drag the Cameras with type ''01'' and the Routes for Cameratypes ''02'' and ''06''.
 
  
 
{{Camera Links}}
 
{{Camera Links}}
  
−
== Links ==
+
==Links==
 
{{Custom Track Tutorial}}
 
{{Custom Track Tutorial}}
 
[[category:Tutorials]][[category:Custom Track Tutorial]]
 
[[category:Tutorials]][[category:Custom Track Tutorial]]

Revision as of 06:17, 8 November 2016

This page is a part of the Custom Track Tutorial. Back to the main tutorial page.

KMP
File formats
Lists
Tutorials
Tools

Introduction

This page will explain the basics of how KMP set cameras work in Mario Kart Wii. There are two basic types of camera: opening pan and replay. Opening pans play before the start of VS and Grand Prix races. Replay cameras play after a VS or Time Trial race ends, during live view of an online race and during ghost replay. Good cameras can make your track look much better, but can be difficult to make. Improperly set cameras can make the game crash in any of these points. Make sure you always have backups of your KMP when editing. You can use any KMP editor for this. This page will use pictures of KMP Cloud with the KMP file from Mario Circuit (castle_course.szs) and the KCL exported to OBJ with Wiimms Tools used as background.

When working with cameras, speed values are usually set in units per frame (speeds set in Route entries) or units per hundred frames (speeds set in CAME entry). Mario Kart Wii usually runs at 60 frames per second, so you can divide the values by 60 to convert them to units per second.

These are the main values set in a Camera point entry. Not all settings are known:

CAME entry data structure
Setting Description Names in
Wiimms Tools 		Column name in
KMP Modifier 		Box name in
KMP Cloud
Type Camera type. type Type Type
Next Next camera entry index. Value 0xFF means: no next camera. next Next Next
? Camshake. Unknown (always 0). unknown Shake Shake
Route ID Route used by the camera. This is index link into the POTI section. -1 (0xFF) means "no route". route Route Route
Camera Speed Velocity of the camera point in units per 100 frames (=units/1.67 sec). v(came) V(Cam) Pointspeed
Zoom Speed Velocity of zooming in units per 100 frames (=units/1.67 sec). v(zoom) V(Zoom) Zoomspeed
View Speed Velocity of the view point in units per 100 frames (=units/1.67 sec). v(v.pt) V(View) Viewspeed
? Start flag. Unknown. unknown Flag
(First 2 digits) 		Start
? Movie flag. Unknown. unknown Flag
(Second 2 digits) 		Movie
Position (X, Y, Z) A 3D position vector of the camera. Ignored if the camera uses routes. position (x,y,z) X, Y and Z PositionX, PositionY and PositionZ
Rotation (X, Y, Z) A 3D rotation vector. Almost always (0, 0, 0). rotation (x,y,z) Roll, Yaw and Pitch RotationX, RotationY and RotationZ
Zoom Start Zoom start: Starting field of view. Angles >180 create curious effects. zoom beg Zoom Zoomstart
Zoom End Zoom end. Final field of view. "Zoom speed" controls the speed of zooming. zoom end Zoom2 Zoomend.
View Position Start/Relative Position (X, Y, Z) Start vector of the view point (camera type 5) or the relative camera position (camera type 3). view point beg (x,y,z) View(x), View(y) and View(z) ViewStartX, ViewStartY and ViewStartZ
View Position End (X, Y, Z) (Destination) vector of the view point. view point end (x,y,z) View2(x), View2(y) and View2(z) ViewEndX, ViewEndY and ViewEndZ
Time The time for how long this Camera is active, in frames. sec*60 Time Time

→ See more in-depth information on the page: CAME

KMP Cloud open in Mario Circuit's cameras; notice the route for the selected camera is also shown

Cameras are found in the CAME section of the KMP Editor. They can be placed like any normal object. The position only matters on certain camera types. Make sure the Route being used by each camera is unique to it; The same route should not be shared between multiple cameras or between cameras and objects.

Camera types

CAME Types
Value Name Type Explication Route controlled?
00 Goal Goal Activates immediately after passing the goal; with the player as the origin, the camera's View Start position both follows and looks at the player.
It can be reactivated as a Replay Camera if linked to an AREA, but does not display in spectator (online/waiting) mode		 No
01 FixSearch Replay Camera stays static in View Start location, and always looks towards the player No
02 PathSearch Replay Route controlled, always looks at the player Yes
03 KartFollow Replay With the player as the origin, the camera's View Start position both follows and looks at the player No
04 KartPathFollow Replay/Opening From its position, it looks at View Start and shifts view to View End No
05 OP_FixMoveAt Opening Opening camera, follows route; from its position, it looks at View Start and shifts view to View End Yes
06 OP_PathMoveAt Opening Opening camera onboard with same effects as normal drive Camera (unsure) Yes
07 MiniGame Unknown Unused ???
08 MissionSuccess Unknown Unused ???

Types 04 and 05 are used for opening pans. Types 01 to 04 are used as replay cameras. Type 00 is the default replay camera, activated as soon as you pass the finish line or when no other camera is active.

Opening Pans

Opening pans are a set of cameras that are shown before a race starts. Nintendo always use three cameras, usually with type 05 (although some tracks use camera type 04) with time values of 220, 257 and 294 in this order. This makes the cameras sync up with the song that plays; each camera is linked by the "Next Camera" value in the entry, the last one being -1 (0xFF). Any number of cameras playing for any amount of time is supported, though. If the cameras are too short, the sound will end early; if they are too long, the sound will finish but the cameras will keep playing. The first camera of the opening pans is set in the header of the CAME section. It can be edited using KMP Cloud or Wiimms Tools. The next cameras are each set in the CAME entry, as seen above.

The cameras follow a route, always at the speed set in the route settings. The point where the camera looks at is initially the view point start, and it shifts from it to the view point end in the specified speed. At the same time, the field of view, changes from the starting to the ending one at the specified speed. If any of the movements (route, view point or zoom) ends before the set time for the camera passes, it will just stay where it is.

So, to edit the opening cameras, first you should set the routes for them. Make sure the speed set in each point is correct and the camera takes about the same time to follow the route it is set to last. After that, set view point start and end and finally zoom values. Note that the speed of the view point is usually a much higher value, compared to zoom speeds. In KMP Cloud the values are read as hexadecimal.

Nintendo always shows the racers before the finish line in the third camera pan. You can follow this if you want to.

When testing the camera pans, it's a good idea to set the "Next" value of the last camera for it to loop back to the first one. The cameras will loop endlessly (until you press a button to skip them), allowing you to view them as many times as you want to.

Replay Cameras

Replay cameras are much harder to edit and test than opening pans; they require knowledge about KMP AREAs too. When viewing the replay or live feed, a camera is activated when the player being observed enters an AREA region. It does not deactivate automatically when the player leaves it. See this section for information on placing an AREA entry.

Important values for the AREA entry:

AREA entry data structure
Setting Description
Type Area type. Type 0 is the one which refers to a camera.
Camera ID Index of CAME. Camera this AREA refers to.
Position (X, Y, Z) A 3D position vector of the area.
Rotation (X, Y, Z) A 3D rotation vector of the area.
Scale (X, Y, Z) A 3D scale vector of the area.

All other AREA settings shouold be left untouched, if you're working with the AREAs only for the cameras. Areas are also used for other things, see AREA type for this.

With your AREA region moved, rotated and scaled the way you want it to be and linked to the ID of a camera, it's time to set the camera settings. Depending on which camera type you choose (from 00 to 04), it will be set up differently.

Camera Type 00 (Goal)

This is the default camera that looks directly at you as soon as the race finishes. It does not need an AREA to be activated, but it can be activated by one if needed. It does not use a route, so the route should be set to -1 (0xFF). The camera point place is ignored. It's recommended to just copy all the settings that were present in the type 00 camera of a Nintendo track. There should be only one type 00 camera in your KMP.

Camera Type 01 (FixSearch)

It does not use a route, so the route should be set to -1 (0xFF). It also does not have a view point start, end or speed; only zoom start, end and speed values are set. This camera stays in the camera point place and looks directly at the player. It's the easiest camera type to set up.

Camera Type 02 (PathSearch)

This camera is similar to the opening pan. It follows a route at the speed specified in the route, so the camera point place is ignored. It does not have a view point start, end or speed; only zoom start, end and speed values are set. The camera always looks directly at the player.

Camera Type 03 (KartFollow)

With the player as the origin, the camera's View Start position both follows and looks at the player, it does not use a route

Camera Type 04 (KartPathFollow)

This camera is similar to the opening pan, and can be used as an opening pan camera. It stays in the camera point place and does not use a route, so the route should be set to -1 (0xFF). It has a view point start, end and speed; and also zoom start, end and speed. The camera looks from the view start point to the view end point, which moves at the specified speed.

Camera related articles

»Camera«
Technical information, includes an analysis.
»KMP«
File, where the camera setup is hold.
»KMP Editing/Cameras«
A KMP and camera tutorial.
»Wiimms SZS Tools/KMP«
How to edit KMP files using Wiimms SZS Tools.

Links

Custom Track Tutorials

Main Tutorials
Introduction – Textures – Scale – Modeling ⇒ Using Blender – BRRES: CTools
BRRES: BrawlBox – BRRES: RiiStudio – Minimap – Solidity – KCL: Wiimms Tools – KMP Editing
Object Editing – Cameras – Cannons – Post-effects – Videos

Battle Arenas
Battle Arenas – Enemy routes in battle arenas ⇒ Using Wiimm's Tools – Coins

Misc. Tutorials
Getting Files – BrawlBox Tricks – Animations – Shadows – Mipmaps
Custom Effects – Moving Terrain – Music – Ports – Paint Remakes – Tutorial Archive
Extended presence flags: Track Tutorial – LE-CODE Track FAQ

Testing and Reviewing
Testing a Track – Visual Review – Track Transformation – Fixing Errors

Software
3D Tools – BrawlBox – CTools Pack – KMP3D – KMP Cloud – KMP Modifier
Lorenzi's KMP Editor – MagicY – Material Tool – Post-Effect Editor – Wiimms SZS Tools – Wiimm's Tool Manager

Other
KMP Objects – Custom Objects – Model Database – Tutorial Archive

Retrieved from "https://wiki.tockdom.com/w/index.php?title=KMP_Editing/Cameras&oldid=109260"