ZombieSoup is an action top-down shooter following the fate of a kid to shoot, loot and dodge tool his way to save a girl from the danger of zombies, monsters, robot and evil genius. You are Ricky, a college kid on backpack seeking his own adventures out in the country. On an ordinary night Ricky woke up on a long journey to a small town. Soon he discovered that the town has been infested by zombies and monsters. Rogue-like top-down shooter Weapons, both melee and ranged Human & Zombie form Secret paths, levels, loots & unlockables Over 50+ challenging levels Story Mode Survival Mode 80’s Aesthetic
As per in the developed game ZombieSoup, it is supposed to be a top down third-person view angle but due to design constraint, it has a twist is that the floor plane is not normal to the camera angle, which means it's not a 90' degree straight view like an usual 2D game does. The problem adds on that perspective view is used instead of orthographic that causes distortions in space that results in the distance like feeling. In ZombieSoup, the camera angle used has a 10' degree offset from the usual normal line from the floor plane. Diagram 1 below shows a sketch of the current scenario. For cursor world location, we used visibility hit result under the cursor which gives us the result of whatever the cursor is pointing in the world space.
On ideal situation, where the character's actor location has the same Z (height) level as the cursor's world location, using the old method to calculate the Z rotation of the player character will not be a problem. However, the problem comes in when there is a height difference. Since we only wants the Z rotation the old calculation will ignore the Z difference. Shown in Diagram 2, you can see what happened to the player's actor location when u transform its Z to the same height as the mouse Z value. As you can see from the spawned particle location based on the player's location and the cursor location, there is an error caused by the non-normal view as the Z height does not go along with the camera's view. However, if you draw a between the two explosion smoke and between player's location and the projectile hit location, we can see that this two lines are perpendicular to each other.
From here we can see that the error is caused by the distorted perspective view and the non-normal camera angle. To attempt to fix this, we need to transpose the player's location in relative to the camera viewport as in, the "correct" Z axis movement. Diagram 3 shows an example scenario of what we need to do.
Based on Diagram 3, to perform the transpose, we need to find O value. According to the trigonometry formula, we would require 2 variable which are the angle and the A value. Angle can be obtained from the Camera Manager of the controller and the A value can be calculated by the difference between the cursor Z value and the player's location Z value. After performing the calculation, the transpose can be applied to the player's location to achieve as shown in Diagram 4.
With this calculation performed, we can dynamically calculate where the player should point to regerdless of the height difference that might be available in the game. The only down side of this approach is that every mouse movement required to go through a formula calculation which may only take a very small amount of processing power that even a calculator can perform in split seconds.
Old Blueprint view
New Blueprint view
By : Alex Chew Hoo Wing (@Aeonsparx)
No articles were found matching the criteria specified. We suggest you try the article list with no filter applied, to browse all available. Post article and help us achieve our mission of showcasing the best content from all developers. Join now to share your own content, we welcome creators and consumers alike and look forward to your comments.
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.
Very interesting read, thank you!