Instead of using
Vector3 targetPosition = target.TransformPoint(new Vector3(0, 5, -10));<\/em>
I used
Vector3 targetPosition = new Vector3(some stuff here that I’m about to show you);<\/em><\/p>\n
First, the code that works:<\/p>\n
![\"\"](\"https:\/\/www.munchou.com\/biwa-chan\/wp-content\/uploads\/2020\/07\/20200715b.png\")
<\/p>\n
I’m not sure that’s the right way to do it, but Jack65423 (one of my most diligent neurons) suggested me to consider the camera as a moving object between 2 positions (each position being given specific coordinates x, y, z). So the camera’s position at the start would be (relative to the followed object, here the truck) (3, 3, -15).
Little Jacky then told me to set the camera as I wished it to be at full speed (moved and zoomed out) and to write down the coordinates. I got (9.8, 4, -26). Those would be the numbers we’d get when the truck is at its maximum speed (50km\/h in that case). So at 0km\/h, we have (3, 3, -15), and at 50km\/h (9.8, 4, -26).
By doing an extremely complicated subtraction, we can see how much the coordinates must “evolve”.
For example, for the Z axis, I created the speedZ <\/i>value that is equal to the vehicle speed divided by 4.55. Where does 4.55 come from? I divided 50 (the max speed) by 11 (the difference between the final coordinates and the original ones). 50\/11=4.55 (approximately).
Actually, for speedX<\/i>, it should be around 7.4, but I wanted the camera to move much more to the right side in order to let the truck appear on the left, hence giving the player a better view of what’s to come on the road.<\/p>\n
speedX<\/em>, Y<\/em> and Z<\/em> vary depending on the speed, which means they are equal to 0 when the truck isn’t moving, and they’ll reach the desired end value when the speed is at its maximum. The special case of speedX<\/em><\/strong> <\/p>\n","protected":false},"excerpt":{"rendered":" Buenos dias muchachos! The truck’s behavior being satisfactory, I decided to get the final in-game view (or close to what it’ll be). So I switched to a more classic side view (I’ll keep it like that for now, maybe forever) and decided to create a “dynamic” camera that reacts to the speed of the truck […]<\/p>\n","protected":false},"author":1,"featured_media":1520,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[42],"tags":[],"_links":{"self":[{"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/posts\/1506"}],"collection":[{"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1506"}],"version-history":[{"count":10,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/posts\/1506\/revisions"}],"predecessor-version":[{"id":1521,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/posts\/1506\/revisions\/1521"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=\/wp\/v2\/media\/1520"}],"wp:attachment":[{"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.munchou.com\/biwa-chan\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Knowing that, Bob687 finished the job with the Vector3<\/em> formula.
In case you don’t know, it’s Vector3(x, y, z)<\/em>.
Which gives us:![\"\"](\"https:\/\/www.munchou.com\/biwa-chan\/wp-content\/uploads\/2020\/07\/20200715c-e1594777138168.png\")
For x<\/em>: target.position.x + 3 + speedX<\/em>
For y<\/em>: target.position.y + 3 + speedY<\/em>
For z<\/em>: target.position.z – 15 – speedZ – Mathf.Abs(target.position.y \/2)<\/em>
Why is z so different? Because I noticed that when the truck goes high and jumps, the ground disappears and it’s not possible to anticipate anything (and honestly, it doesn’t look pretty). So I added one more thing that depends on the position of the truck on the Y axis. I divided by 2 so that the zoom out wouldn’t be extreme. Now it looks quite natural.
Oh yes, to zoom out (on the Z axis), the camera goes into the negatives, therefore it is necessary to subtract.
Also, because the truck goes up and down on the Y axis, I added the Mathf.Abs<\/i> so that even when the Y is negative, it’s converted into a positive and the camera won’t zoom in unexpectedly (although I haven’t tested it, but I believe it should work).<\/p>\n
You may have noticed I used a condition to define speedX<\/em>. The reason is simple: if the truck moves forward, the camera will behave as intended the truck appears at the left side of the screen). But I the truck moves backward, then what? It’ll disappear! To counter that, I made a simple condition based on either the truck is moving to the left (Truck.rb.velocity.x < 0<\/em>) or not. And depending on that, the value of speedX<\/em> is different.
That simple!
\/!\\ NOTE :<\/strong> in order to have access to Truck.rb<\/em>, you must change (if you haven’t done it yet), in the truck’s script, private<\/strong> Rigidbody2D rb;<\/i> into public <\/b>Rigidbody2D rb;<\/i> .<\/p>\n\n\n