Register - Login
Views: 99379000
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
04-23-22 10:38:08 PM
Jul - SM64 Hacking (Archive) - SM64 Water Hex Hacking (Geeky stuff) New poll - New thread - New reply
Pages: 1 2 3 4 Next newer thread | Next older thread
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 279/621
EXP: 1135502
For next: 21617

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 1.2 years

Posted on 09-23-08 04:43:50 AM Link | Quote
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Hmm I just realized that I missed a few posts in this thread. There are interesting developments happening.

It's a shame that the 0x18 command requires a ram pointer that refers to another pointer instead of using the actual polygon data pointer as a parameter, I wonder why they choose such a convoluted method. This will make integration of water areas in the importer a much complicated affair.

Using a 0x24 object to make the water polygon is a good idea, and with the object importer you'll be able to do something like this. But, standard water/lava polygons have some particularities that the imported objects wouldn't have. The water and lava is animated, and the water texture is scrolling in a direction and speed linked to the current that's defined by some special collision commands that are used on the floor of some water areas. The current can dynamically change depending on where Mario is, and 0x24 objects wouldn't provide this nicety.

____________________
messiaen
Catgirl
Level: 68


Posts: 267/1085
EXP: 2594034
For next: 134766

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years

Posted on 09-27-08 12:33:09 PM (last edited by messiaen at 09-27-08 10:59 AM) Link | Quote
It gets more messy than that! I looked at this other "water" function found in the Castle Grounds Level Mesh Geo Layout:

1800 1601 802D 104C <-- Loads two water polygons areas (under the bridge and near the start)

It seems to be a very general water function, and the "1601" is an argument which leads to a hardcoded pointer (not loaded from the checksum area but as immediate instructions) value 0x07011738.

Here is what is found at 0x11738 of Castle Grounds:

00FD8F3F 0000 0000 0701 16F8 0001 0000 0701 1718
00FD8F4F FFFF

Two more (numbered) pointers, which seems logical because there are two water area polygons loaded by the 0x18 command above. Subtracting 0x11718 - 0x116F8 = 20, so that's probably the lenght of each command. Look at the data:

0x116F8:
0001 0000 0014 000F E427 E3CA E427 FFC6
203D FFC6 203D E3CA 0001 0096 0000 0000

Hmm, are these coordinates of some type? [Rememer the water polygons are a simple rectangle]

0x11718:
0001 0000 000F 000A 0400 FFC6 0400 1FC9
2026 1FC9 2026 FFC6 0000 0096 0000 0000

The value pointed by the "Waterfall" function is 0x11750. I'll just paste everything from this point
to the end of the Bank 0x07:

Edit: It's been a long time since I read this thread, so I just realized now that this is the same data found by VL-Tone on the first post, I just found the pointers which calls them. With some ASM work, these can probably be flexibilized to create new water areas (in custom levels). Waterfall data, however, seems to be different.

____________________
Mario 64 notes @ http://sites.google.com/site/messiaen64/
Pages: 1 2 3 4 Next newer thread | Next older thread
Jul - SM64 Hacking (Archive) - SM64 Water Hex Hacking (Geeky stuff) New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

30 database queries.
Query execution time:  0.096037 seconds
Script execution time:  0.007821 seconds
Total render time:  0.103858 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 291 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 207 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 93 - Warning: unescaped & or unknown entity "&page"
line 149 column 124 - Warning: unescaped & or unknown entity "&page"
line 149 column 155 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 192 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 98 - Warning: unescaped & or unknown entity "&postid"
line 179 column 73 - Warning: <style> isn't allowed in <td> elements
line 179 column 9 - Info: <td> previously mentioned
line 179 column 137 - Warning: missing </div>
line 186 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 188 column 9 - Warning: missing <tr>
line 206 column 13 - Warning: missing <tr>
line 207 column 98 - Warning: unescaped & or unknown entity "&postid"
line 238 column 17 - Warning: missing <tr>
line 238 column 17 - Warning: discarding unexpected <table>
line 241 column 35 - Warning: missing <tr>
line 241 column 93 - Warning: unescaped & or unknown entity "&page"
line 241 column 124 - Warning: unescaped & or unknown entity "&page"
line 241 column 155 - Warning: unescaped & or unknown entity "&page"
line 241 column 50 - Warning: missing </font> before </td>
line 241 column 192 - Warning: missing </font> before </table>
line 243 column 35 - Warning: missing <tr>
line 243 column 50 - Warning: missing </font> before </td>
line 244 column 37 - Warning: unescaped & or unknown entity "&id"
line 243 column 207 - Warning: missing </font> before </table>
line 245 column 17 - Warning: discarding unexpected </textarea>
line 245 column 28 - Warning: discarding unexpected </form>
line 245 column 35 - Warning: discarding unexpected </embed>
line 245 column 43 - Warning: discarding unexpected </noembed>
line 245 column 53 - Warning: discarding unexpected </noscript>
line 245 column 64 - Warning: discarding unexpected </noembed>
line 245 column 74 - Warning: discarding unexpected </embed>
line 245 column 82 - Warning: discarding unexpected </table>
line 245 column 90 - Warning: discarding unexpected </table>
line 247 column 9 - Warning: missing </font> before <table>
line 259 column 25 - Warning: discarding unexpected </font>
line 268 column 37 - Warning: discarding unexpected </font>
line 246 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 244 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 179 column 693 - Warning: <img> lacks "alt" attribute
line 183 column 2628 - Warning: <img> lacks "alt" attribute
line 183 column 2787 - Warning: <img> lacks "alt" attribute
line 191 column 22 - Warning: <img> lacks "alt" attribute
line 191 column 63 - Warning: <img> lacks "alt" attribute
line 191 column 111 - Warning: <img> lacks "alt" attribute
line 191 column 161 - Warning: <img> lacks "alt" attribute
line 202 column 15 - Warning: <img> lacks "alt" attribute
line 244 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 244 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 244 column 244 - Warning: <img> proprietary attribute value "absmiddle"
line 253 column 25 - Warning: <img> lacks "alt" attribute
line 258 column 267 - Warning: <img> lacks "alt" attribute
line 238 column 17 - Warning: trimming empty <tr>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 179 column 157 - Warning: <table> proprietary attribute "height"
line 179 column 222 - Warning: <td> proprietary attribute "background"
line 179 column 318 - Warning: <td> proprietary attribute "background"
line 179 column 408 - Warning: <table> proprietary attribute "height"
line 179 column 488 - Warning: <td> proprietary attribute "background"
line 179 column 1443 - Warning: <td> proprietary attribute "background"
line 207 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 90 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md