By  Helios on 12-28-17, 02:05 pm |
| Category 'Camera controllers', known |
==Old==
This sprite has to use together with paths. Unknown 1 is for speed. It should be divisible by 8. Unknown 3 maybe acceleration from former node's speed to this node's speed.
And I've found some interesting formula: x=98k/y. Where k is the number of pixels being passed within x Mario'\s second. And y is the value you entered in unknown 1. It relates together. But it might not always work. It may have something to do with unknown 3 too...
Calculation example: let say you want a sprite to move camera up 4 tiles within 16 Mario seconds. Your formula is x=98k/y. As 4 tiles=64 pixels. Substitute it, then you have to multiply it with 98. 98x64=6272. And substitute x with 16. Then 16=6272/y.
And solve it to find y. After you got y, you insert that number into unknown 1. And test it in the emu, can 4 tiles be passed within 16 Mario seconds or not? But I think it does. Remember unknown 3? 0. Sometimes the time doesn't have to be a whole number.
Also, I think the position where the sprite is first recognized by the game will determine the camera movement along the path. (Camera movement to the right, left, or straightly of the path) And there're some nybbles controlling how the sprite will act; wait for Mario to come near then scroll or scroll immediately when recognized. I don't know which, but it does have.
That's all I've found. :)
Hope this help! |
| Data files: none |
Sprite fields:
• Path ID: value at nybble 10-11. Sets the path the camera will follow while scrolling. Unknown 1 of the first node is target speed and and unknown 3 is something to do with time.
• Loads from?: list at nybble 7: 0=Midway Point,1=Unknown 1,2=Level Start. 1 is unused.
• Scrolling direction: list at nybble 9: 0=Vertical,1=Horizontal
• Starting node: value at nybble 4-5
• Start from both Midway and Level Start: checkbox at nybble 6 with mask 8 |
|
⇨
|
| By Helios on 02-26-18, 03:29 pm |
| Category 'Camera controllers', known |
==Old==
This sprite has to use together with paths. Unknown 1 is for speed. It should be divisible by 8. Unknown 3 maybe acceleration from former node's speed to this node's speed.
And I've found some interesting formula: x=98k/y. Where k is the number of pixels being passed within x Mario'\s second. And y is the value you entered in unknown 1. It relates together. But it might not always work. It may have something to do with unknown 3 too...
Calculation example: let say you want a sprite to move camera up 4 tiles within 16 Mario seconds. Your formula is x=98k/y. As 4 tiles=64 pixels. Substitute it, then you have to multiply it with 98. 98x64=6272. And substitute x with 16. Then 16=6272/y.
And solve it to find y. After you got y, you insert that number into unknown 1. And test it in the emu, can 4 tiles be passed within 16 Mario seconds or not? But I think it does. Remember unknown 3? 0. Sometimes the time doesn't have to be a whole number.
Also, I think the position where the sprite is first recognized by the game will determine the camera movement along the path. (Camera movement to the right, left, or straightly of the path) And there're some nybbles controlling how the sprite will act; wait for Mario to come near then scroll or scroll immediately when recognized. I don't know which, but it does have.
That's all I've found. :)
Hope this help!
This sprite does not work properly with Sprite 84: Zoom. It may result in uneven speed, even with the speed for all nodes set equal. |
| Data files: none |
Sprite fields:
• Path ID: value at nybble 10-11. Sets the path the camera will follow while scrolling. Unknown 1 of the first node is target speed and and unknown 3 is something to do with time.
• Loads from?: list at nybble 7: 0=Midway Point,1=Unknown 1,2=Level Start. 1 is unused.
• Scrolling direction: list at nybble 9: 0=Vertical,1=Horizontal
• Starting node: value at nybble 4-5
• Start from both Midway and Level Start: checkbox at nybble 6 with mask 8 |
|
