Difference between revisions of "Position Jump Bug"

Revision as of 20:38, 22 May 2017

Bugs

Bugs in alphabetic order

Advanced information

The page will explain what the Position Jump Bug is, and how to fix it.

Position Jumping

If a player is meant to be in a different position than the one shown on screen then this is classed as a position tracker bug. In fact it is a group of bugs which can occur for several reasons.

A minor problem caused by this bug is that the player gets incorrect information about his ranking in the race. However an altogether more major issue is that the position tracker is the thing that determines which items should be granted to a player. Due to the face that the items selection is based on the shown position, the real leading player could have the opportunity to acquire more powerful items such as mushrooms which could then be used to dodge a blue shell unfairly - thus leading to poorly balanced racing where players in lower positions struggle to catch up to the leader.

That said, once people start crossing the finish line at the end of the race all positions are shown correctly again because the game compares the racing time of all players.

Symptoms

Temporary switching of positions

This kind of glitch mostly occurs if a player is outside of all valid check point quadrilaterals. If the player enters a valid quadrilateral again, the glitch is gone. Likely it is a problem of old tracks, that used the old check point line model to define the check points.

Incorrect positions after respawning

This is another version of a temporary positioning bug. The cause is quite simple: a respawn point is set so that when a player uses it they are placed after one of the mandatory checkpoints, therefore players will pass them in the wrong order and the game will get confused and provide the wrong position information. Occasionally this bug results in a lap not counting and obviously this can lead to a huge disadvantage to anyone unfortunate enough to fall victim to it.

Missing a mandatory checkpoint

Sometimes a player drives a little outside of a mandatory checkpoint line, resulting in a failed lap count. When this happens the position tracker of the aforementioned player will often be shown as last place, but should correct itself after a while.

Because of the simulation of other drivers until the next data transfer, other Wiis do not notice that the player has missed the checkpoint and will count them as being on another position.

All players at position 1

Some custom tracks are too long for the 5 minutes limit if playing online. One trick commonly used to overcome this is to set more than 1 lap counting check point. This works offline fine, but online each player is permanently registered as first after crossing the first lap counting check point.

If the real first place player finishes the race then all other players are registered as being in second place until the next player finishes, and so on.

→ More details

Fixing The Bug

New Check Point Model

First read the article »Check Point« about the new quadrilateral model. It will help to understand, how check points function.

Fixing it is quite easy, and should be a pretty quick fix if done correctly.

Step 1

In your course locate the areas in which this glitch takes place.

Once you have found each one, note down the area on the Minimap where it occurred.

Step 2

Open your KMP file and then the "Checkpoints" section.

Look for the same areas on the Minimap Shown in a KMP editor (such as the KMP Modifier or KMP Cloud) where you saw that the position jump glitch occured.

Now click a checkpoint that is placed slightly before the glitch occurs. Change the key setting to any number that follows up the previous key checkpoint.

Place more in the area ahead, and go in order of 1, to 2, to 3, and so on.

Do this step in every area that this happens, and in each section right before two paths cross over/under eachother.

Look through the rest of you courses checkpoints and make sure every single other key checkpoint that occurs after the new ones you added are one number above the one before it, so if the key checkpoint before it was 5, you would change it to 6.

Step 3

Try your course in-game and see if this glitch still occurs. In the case that it does, repeat steps 1 and 2 until the glitch is gone.

Also read the next section to make sure that your course turns out okay after doing this.

Important Info

Make sure that none of your respawn points try to drop you past a key checkpoint. This means that you fall down behind a point, and get respawned past it. If this happens, the lap will not count. There may be various ways to fix this depending on your course; you may have to change the model, move the checkpoint, or reset the respawn position.

Make sure that ALL key checkpoints go in numerical order. Failing to do so may also result in the lap not counting.

@@ Line 1: / Line 1: @@
-The page will explain what the Position Jump Bug is, and how to fix it.
+{{Bugs}}
+The page will explain what the '''Position Jump Bug''' is, and how to fix it.
-==Position Jumping==
-The Position Jump Bug is a glitch that allows the Player to rapidly switch positions with other players on the course without truly being in that position.
+__TOC__
-This is glitch Mostly occurs there may be a small circular turn, or in an area where the Player's path will cross over.
+== Position Jumping ==
-Allowing this glitch to be present in a course may cause un fair item advantages/disadvantages, and may cause the players to finish in a position that they are not currently in.
+If a player is meant to be in a different position than the one shown on screen then this is classed as a position tracker bug. In fact it is a group of bugs which can occur for several reasons.
-Although this glitch may cause some trouble, it is quite easy to fix.
+A minor problem caused by this bug is that the player gets incorrect information about his ranking in the race. However an altogether more major issue is that the position tracker is the thing that determines which items should be granted to a player. Due to the face that the items selection is based on the shown position, the real leading player could have the opportunity to acquire more powerful items such as mushrooms which could then be used to dodge a blue shell unfairly - thus leading to poorly balanced racing where players in lower positions struggle to catch up to the leader.
-==Fixing The Bug==
+That said, once people start crossing the finish line at the end of the race all positions are shown correctly again because the game compares the racing time of all players.
-Fixing it is quite easy, and should be done fast if done properly.
+== Symptoms ==
+=== Temporary switching of positions ===
-===Step 1===
+This kind of glitch mostly occurs if a player is outside of all valid [[Check Point|check point quadrilaterals]]. If the player enters a valid quadrilateral again, the glitch is gone. Likely it is a problem of old tracks, that used the old ''check point line model'' to define the check points.
-In your course locate the areas in which this glitch takes place.
+=== Incorrect positions after respawning ===
+This is another version of a temporary positioning bug. The cause is quite simple: a respawn point is set so that when a player uses it they are placed after one of the mandatory checkpoints, therefore players will pass them in the wrong order and the game will get confused and provide the wrong position information. Occasionally this bug results in a lap not counting and obviously this can lead to a huge disadvantage to anyone unfortunate enough to fall victim to it.
+=== Missing a mandatory checkpoint ===
+Sometimes a player drives a little outside of a mandatory checkpoint line, resulting in a failed lap count. When this happens the position tracker of the aforementioned player will often be shown as last place, but should correct itself after a while.
+Because of the simulation of other drivers until the next data transfer, other Wiis do not notice that the player has missed the checkpoint and will count them as being on another position.
+=== All players at position 1 ===
+Some custom tracks are too long for the 5 minutes limit if playing online. One trick commonly used to overcome this is to set more than 1 lap counting check point. This works offline fine, but online each player is permanently registered as first after crossing the first lap counting check point.
+If the real first place player finishes the race then all other players are registered as being in second place until the next player finishes, and so on.
+&rarr; [[Check_Point#Lap_counter|More details]]
+== Fixing The Bug ==
+{{textbox||New Check Point Model|
+First read the article »'''[[Check Point]]'''« about the new '''quadrilateral model'''. It will help to understand, how check points function.}}
+Fixing it is quite easy, and should be a pretty quick fix if done correctly.
-Once you've found each one, note down which area in the Minimap in Which this happened.
+=== Step 1 ===
-===Step 2===
+In your course locate the areas in which this glitch takes place.
-Next open up your course in the [[SZS Modifier]].
+Once you have found each one, note down the area on the [[Minimap]] where it occurred.
-Ope your KMP and open up the "Check Points" section.
+=== Step 2 ===
+Open your KMP file and then the "Checkpoints" section.
-Look for the same areas on the Minimap Shown in the KMP Editor where you saw that the position jump glitch occured.
+Look for the same areas on the Minimap Shown in a KMP editor (such as the [[KMP Modifier]] or [[KMP Cloud]]) where you saw that the position jump glitch occured.
-Now click a Check Point that is placed slightly before the Glitch occurs. See the Key Check Point setting, and change it to 0.
+Now click a checkpoint that is placed slightly before the glitch occurs. Change the key setting to any number that follows up the previous key checkpoint.
 Place more in the area ahead, and go in order of 1, to 2, to 3, and so on.
@@ Line 35: / Line 60: @@
 Do this step in every area that this happens, and in each section right before two paths cross over/under eachother.
-Look through the rest of you courses Check Points and make sure every single other Key Check Point That occurs after the new ones you added are one number above the one before it.
+Look through the rest of you courses checkpoints and make sure every single other key checkpoint that occurs after the new ones you added are one number above the one before it, so if the key checkpoint before it was 5, you would change it to 6.
-So if the Key Check Point before it was 5, you would change ot to 6.
-===Step 3===
+=== Step 3 ===
-Try your course in Game and see if this Glitch Still occurs. In the case that it does, repeat steps 1 & 2 until the glitch no longer occurs.
+Try your course in-game and see if this glitch still occurs. In the case that it does, repeat steps 1 and 2 until the glitch is gone.
 Also read the next section to make sure that your course turns out okay after doing this.
-===Important Info===
+=== Important Info ===
-Make sure that not a single Respawn Point tries to drop you past a Key Check Point. This means that you fall down behind a point, and get respawned past it. If this happens, the Lap will not count. There may be various way to fix this depending on your course. You may have to change the model, move the Check Point, or Move the Respawn Position.
-Make sure that '''ALL''' Keys check points go in numerical order. Failing to do so may also result in the lap not counting.
-==Tracks Currently Known To Have This Bug==
+Make sure that none of your respawn points try to drop you past a key checkpoint. This means that you fall down behind a point, and get respawned past it. If this happens, the lap will not count. There may be various ways to fix this depending on your course; you may have to change the model, move the checkpoint, or reset the respawn position.
-*None
+Make sure that '''ALL''' key checkpoints go in numerical order. Failing to do so may also result in the lap not counting.
 [[category:Bug]]