Register - Login
Views: 99393826
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 10:51:31 AM
Jul - SM64 Hacking (Archive) - Mario 64 Level Importer New poll - New thread - New reply
Pages: 1 2 3 4 5 6 7 8 9 10 ... 16 17 18 19 20 21 22 23 24 ... 46 47 48 49 50 51 52 53 54 55 Next newer thread | Next older thread
Rena
I had one (1) message in Discord deleted and proceeded to make a huge, huge mess about how it was a violation of free speech and how moderators are supposed to be spam janitors and nobody should have the right to tell me not to talk about school shootings
Level: 135


Posts: 2954/5390
EXP: 29051736
For next: 283269

Since: 07-22-07

Pronouns: he/him/whatever
From: RSP Segment 6

Since last post: 333 days
Last activity: 333 days
Posted on 03-25-10 09:38:57 PM Link | Quote
03-25-10 04:38:57 PM
Post #2954
Well if RAM is the only issue, 4MB would hold well over 250,000 vertices... probably better to use that for textures, but still, I take it there are more limitations?
Originally posted by Emoluvjd2
I just figured out a way how to fix collision data errors, but my textures appear upside down. Can this be looked into?
Try explaining your method so someone can point out the problem.

____________________


witty comment
why not?
messiaen
Catgirl
Level: 68


Posts: 824/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 03-25-10 09:57:58 PM Link | Quote
With emulators, one probably could push the limits way beyond the N64 hardware can handle (if we aren't already, which is very likely). For instance, enabling the z-buffer is a very costly operation to the GPU, and since high-level emulators don't enable the RCP at all (actually, I think audio is low-level in most plugins nowadays) they probably don't even take this in account.

Emoluvjd2: Well, I hope you are talking about the back face issues in SketchUp, which may generate collision errors.
DarkSpacer
Member
Level: 30


Posts: 3/184
EXP: 165833
For next: 36

Since: 03-23-10


Since last post: 5.6 years
Last activity: 5.0 years
Posted on 03-26-10 12:26:57 AM Link | Quote
Most of the time when I export a level with a building in it that you can go inside of, the building collision gets really glitchy. That's because the OBJ exporter, even when set to "guess which faces to export", exports both sides of the faces. And that can get very glitchy very fast if you're not careful.
messiaen
Catgirl
Level: 68


Posts: 825/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 03-26-10 01:53:31 AM Link | Quote
Originally posted by DarkSpacer
Most of the time when I export a level with a building in it that you can go inside of, the building collision gets really glitchy. That's because the OBJ exporter, even when set to "guess which faces to export", exports both sides of the faces. And that can get very glitchy very fast if you're not careful.


Not sure if that's the case, but remember that you have to model with solids all the time. That is, never leave "open" faces that should be solid on "both sides", but instead use cubes. I think if you respect that, it will work nicely.

If that's not the case, send me the .obj and .skp file so I can give a look.
Rena
I had one (1) message in Discord deleted and proceeded to make a huge, huge mess about how it was a violation of free speech and how moderators are supposed to be spam janitors and nobody should have the right to tell me not to talk about school shootings
Level: 135


Posts: 2956/5390
EXP: 29051736
For next: 283269

Since: 07-22-07

Pronouns: he/him/whatever
From: RSP Segment 6

Since last post: 333 days
Last activity: 333 days
Posted on 03-26-10 02:33:31 AM Link | Quote
03-25-10 09:33:31 PM
Post #2956
I know emulators tend to HLE everything without enforcing the original limitations, but I'm wondering what all would limit the number of faces a level can have. I know in Mario Kart, the game divides tracks into sections so it can draw only the nearby faces, so the total number in a track is basically only limited by memory, as it's only rendering a small portion at any time. I suppose Mario 64 doesn't have such a system?

____________________


witty comment
why not?
Emoluvjd2
Member
Level: 20


Posts: 24/70
EXP: 39568
For next: 2871

Since: 10-24-09


Since last post: 4.1 years
Last activity: 2.6 years
Posted on 03-26-10 03:54:18 AM Link | Quote
Originally posted by messiaen
Emoluvjd2: Well, I hope you are talking about the back face issues in SketchUp, which may generate collision errors.

Yes, I am. I fixed it by making all the back faces untextured and checking the export textured only feature in the plugin you supplied us with. It works really well for me now.
DarkSpacer
Member
Level: 30


Posts: 4/184
EXP: 165833
For next: 36

Since: 03-23-10


Since last post: 5.6 years
Last activity: 5.0 years
Posted on 03-26-10 01:57:04 PM (last edited by DarkSpacer at 03-26-10 11:11 AM) Link | Quote
Originally posted by HyperHacker
I know emulators tend to HLE everything without enforcing the original limitations, but I'm wondering what all would limit the number of faces a level can have. I know in Mario Kart, the game divides tracks into sections so it can draw only the nearby faces, so the total number in a track is basically only limited by memory, as it's only rendering a small portion at any time. I suppose Mario 64 doesn't have such a system?


It does for the inside of the castle and for Wet-Dry World. Those are the only levels I can think of.

Also there are more if youi count warps like the warp in Jolly Roger Bay to get inside the sunken ship (otherwise I think they would've allowed you to actually swim inside the ship without any type of warps).

Originally posted by messiaen
Not sure if that's the case, but remember that you have to model with solids all the time. That is, never leave "open" faces that should be solid on "both sides", but instead use cubes. I think if you respect that, it will work nicely.


But if you use cubes you're more likely to reach the polygon limit. But I see where you are: If you export faces which need to be solid on both sides, SM64 collision goes nuts and you're left with Mario stuck in a wall (and usually the only way to get out is to run into a corner).

We have a delima (or however you spell it). Which is better: More polygons or glitches fit for a king?
messiaen
Catgirl
Level: 68


Posts: 827/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 03-26-10 03:35:45 PM Link | Quote
Mario 64 usually renders (almost) everything all the time, unless the level uses the room system such as "Haze Maze" and "Inside Castle". I'm not even sure that system is to prevent useless rendering or to avoid unwanted parts of the level to be displayed because of the primitive camera system.

Also, There's no dillema. You can have incredible detailed levels, far surpassing any of the original ones in SM64 with 5000 faces or so. Surely I may test more and increase this limit, but it's too early since we haven't even seen a decent full level yet (imports don't count). With proper care and respect to the game limits, there probably won't be any serious collision problems.

Remember the playing area isn't that big (already tried expanding but ran into many collision and camera problems).
Emoluvjd2
Member
Level: 20


Posts: 25/70
EXP: 39568
For next: 2871

Since: 10-24-09


Since last post: 4.1 years
Last activity: 2.6 years
Posted on 03-26-10 03:48:22 PM Link | Quote
Originally posted by HyperHacker
Try explaining your method so someone can point out the problem.

If you mean the textures, then I exported the model, the textures were right side up, but when imported they came out upside down. I re-imported it after vertically flipping the textures and it works just fine now, but the question is is this not supposed to happen?
DarkSpacer
Member
Level: 30


Posts: 7/184
EXP: 165833
For next: 36

Since: 03-23-10


Since last post: 5.6 years
Last activity: 5.0 years
Posted on 03-26-10 04:59:22 PM (last edited by DarkSpacer at 03-26-10 02:01 PM) Link | Quote
Originally posted by Emoluvjd2
Originally posted by HyperHacker
Try explaining your method so someone can point out the problem.

If you mean the textures, then I exported the model, the textures were right side up, but when imported they came out upside down. I re-imported it after vertically flipping the textures and it works just fine now, but the question is is this not supposed to happen?


I have a similar problem. When I export a level, it flips it left to right. So say I have a cube in the middle, and a cube on the left in Sketchup. When I import it into the game, I now have a cube in the middle, and a cube on the right.

And no, I don't have the level backwards. It dosen't turn it 180 degrees (at least I don't think it does). I don't know how to explain it. The cube idea was just an example.

EDIT: Better example: Say I have a building with stairs along the left wall in Sketchup. WHen I import it, the stairs are now along the right wall, the rest of the building (assuming it's symmetrical) stays the same.
Emoluvjd2
Member
Level: 20


Posts: 26/70
EXP: 39568
For next: 2871

Since: 10-24-09


Since last post: 4.1 years
Last activity: 2.6 years
Posted on 03-26-10 05:57:15 PM Link | Quote
Originally posted by DarkSpacer
I have a similar problem. When I export a level, it flips it left to right. So say I have a cube in the middle, and a cube on the left in Sketchup. When I import it into the game, I now have a cube in the middle, and a cube on the right.

And no, I don't have the level backwards. It dosen't turn it 180 degrees (at least I don't think it does). I don't know how to explain it. The cube idea was just an example.

EDIT: Better example: Say I have a building with stairs along the left wall in Sketchup. WHen I import it, the stairs are now along the right wall, the rest of the building (assuming it's symmetrical) stays the same.

I also have this problem, it seems that once it's imported it is flipped horizontally. To fix it just flip it horizontally in your 3D modeler before exporting it to .obj.
Lyskar
12210
-The Chaos within trumps the Chaos without-
Level: 192


Posts: 5104/12211
EXP: 99240050
For next: 633521

Since: 07-03-07

From: 52-2-88-7

Since last post: 7.4 years
Last activity: 7.3 years
Posted on 03-28-10 11:05:04 PM Link | Quote
Stats
Time/Date
03-28-10 05:05:04 PM
Posts
5104
Days Here
999
Level
104
Metal_Man88's Post
That is... that is a million times too complex for SM64 to handle.

I would suggest you try smaller, simpler models. And leave that one behind.

Otherwise, your silly questions will just have to be deleted.

____________________
Don't let an old saying get in the way of a good idea.
Eisnaught - SSQ² - Mobius Roleplay - SSS
messiaen
Catgirl
Level: 68


Posts: 828/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 03-28-10 11:18:18 PM Link | Quote
Actually, that specific model would work, but you haven't exported it to the .obj format (it's a SketchUp file).
The fact that you are using a very old version of the importer really puzzles me (or else, why should I even bother to reply your message when you don't follow this seemingly obvious 'rule') ?

Anyway, I'm taking a break from SM64 hacking (too much stuff to do and not much motivation), no idea when I will release a new version of the level importer.
Lyskar
12210
-The Chaos within trumps the Chaos without-
Level: 192


Posts: 5105/12211
EXP: 99240050
For next: 633521

Since: 07-03-07

From: 52-2-88-7

Since last post: 7.4 years
Last activity: 7.3 years
Posted on 03-28-10 11:52:09 PM Link | Quote
Stats
Time/Date
03-28-10 05:52:09 PM
Posts
5105
Days Here
999
Level
104
Metal_Man88's Post
Hm. My bad... partially.

(Seeing as I was... correct in assuming something was very wrong with that question, just not what.)

In any case, Mr. "Zelda Immortal", do try updating to the latest version, otherwise your chances will remain zero.

____________________
Don't let an old saying get in the way of a good idea.
Eisnaught - SSQ² - Mobius Roleplay - SSS
Zelda Immortal
Member
Level: 16


Posts: 10/43
EXP: 19491
For next: 765

Since: 03-24-09


Since last post: 8.1 years
Last activity: 9.5 years
Posted on 03-29-10 11:00:41 AM Link | Quote
Sorry Metal Man...
I Took a long break from SM64 Hacking To try and exterminate my inside Noob...
Lyskar
12210
-The Chaos within trumps the Chaos without-
Level: 192


Posts: 5113/12211
EXP: 99240050
For next: 633521

Since: 07-03-07

From: 52-2-88-7

Since last post: 7.4 years
Last activity: 7.3 years
Posted on 03-29-10 06:12:50 PM Link | Quote
Stats
Time/Date
03-29-10 12:12:50 PM
Posts
5113
Days Here
1000
Level
104
Metal_Man88's Post
Well, as long as you're trying to do that, you'll be okay.

____________________
Don't let an old saying get in the way of a good idea.
Eisnaught - SSQ² - Mobius Roleplay - SSS
Rez2
User
Level: 13


Posts: 19/24
EXP: 8073
For next: 2194

Since: 05-27-09

From: England

Since last post: 10.5 years
Last activity: 4.1 years
Posted on 03-30-10 04:18:50 PM Link | Quote
So, at what point did you include the hidden 'Easter Eggs'?
messiaen
Catgirl
Level: 68


Posts: 833/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 04-05-10 04:06:09 PM Link | Quote
Rez2: They have been around since the first GUI version.

Decided to release v12 of the importer. New features are limited water/toxic haze/myst support (just one box), some bug fixes and an option to vertically flip textures. Also, the background importer now works much better (no more wrap problems), but the textures may still look a bit "blocky".
Hectamatatortron
Member
Level: 35


Posts: 205/232
EXP: 258003
For next: 21933

Since: 09-19-07


Since last post: 7.2 years
Last activity: 5.3 years
Posted on 04-05-10 10:06:27 PM Link | Quote
Blocky, eh? When you import backgrounds, is your program having to actually massage the data to make it appropriate? Or is it just putting the user's input where it goes in the ROM after stripping the meta data associated with common image formats?

I know from experience what a pain it can be to format input image in a full color format to one that a Gameboy Advance, for example, can display...

____________________
messiaen
Catgirl
Level: 68


Posts: 834/1085
EXP: 2594160
For next: 134640

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 04-05-10 11:49:26 PM (last edited by messiaen at 04-05-10 09:20 PM) Link | Quote
Images are converted to 256x256, then to 32x32 tiles and finally to the RGBA 5551 format. All of this (except the final RGBA 5551 conversion) is done through an external program: ImageMagick's convert tool.

The "blocky" issues happens because I haven't taken care of this yet:

Originally posted by VL-Tone
Another thing to note: the relevant image part of each tile is actually 31x31 pixels. The horizontal and vertical 1 pixel lines that are left should be a repetition of the line before, or else you'll see "seam lines" in the sky around each tile. So the imported and exported background in TT64 will be 248x248 (8 lines are lost horizontally and vertically because they are repetitions).


Edit: Forgot to include in the previous post. V12 supports correctly 32x64 and 64x32 textures, which will allow for more detailed textures.
Pages: 1 2 3 4 5 6 7 8 9 10 ... 16 17 18 19 20 21 22 23 24 ... 46 47 48 49 50 51 52 53 54 55 Next newer thread | Next older thread
Jul - SM64 Hacking (Archive) - Mario 64 Level Importer New poll - New thread - New reply


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

34 database queries, 9 query cache hits.
Query execution time:  0.089774 seconds
Script execution time:  0.036228 seconds
Total render time:  0.126002 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 300 - 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 194 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 94 - Warning: unescaped & or unknown entity "&page"
line 149 column 126 - Warning: unescaped & or unknown entity "&page"
line 149 column 158 - Warning: unescaped & or unknown entity "&page"
line 149 column 190 - Warning: unescaped & or unknown entity "&page"
line 149 column 222 - Warning: unescaped & or unknown entity "&page"
line 149 column 254 - Warning: unescaped & or unknown entity "&page"
line 149 column 286 - Warning: unescaped & or unknown entity "&page"
line 149 column 318 - Warning: unescaped & or unknown entity "&page"
line 149 column 350 - Warning: unescaped & or unknown entity "&page"
line 149 column 382 - Warning: unescaped & or unknown entity "&page"
line 149 column 419 - Warning: unescaped & or unknown entity "&page"
line 149 column 453 - Warning: unescaped & or unknown entity "&page"
line 149 column 487 - Warning: unescaped & or unknown entity "&page"
line 149 column 521 - Warning: unescaped & or unknown entity "&page"
line 149 column 558 - Warning: unescaped & or unknown entity "&page"
line 149 column 592 - Warning: unescaped & or unknown entity "&page"
line 149 column 626 - Warning: unescaped & or unknown entity "&page"
line 149 column 660 - Warning: unescaped & or unknown entity "&page"
line 149 column 698 - Warning: unescaped & or unknown entity "&page"
line 149 column 732 - Warning: unescaped & or unknown entity "&page"
line 149 column 766 - Warning: unescaped & or unknown entity "&page"
line 149 column 800 - Warning: unescaped & or unknown entity "&page"
line 149 column 834 - Warning: unescaped & or unknown entity "&page"
line 149 column 868 - Warning: unescaped & or unknown entity "&page"
line 149 column 902 - Warning: unescaped & or unknown entity "&page"
line 149 column 936 - Warning: unescaped & or unknown entity "&page"
line 149 column 970 - Warning: unescaped & or unknown entity "&page"
line 149 column 1004 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 1041 - 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 101 - Warning: unescaped & or unknown entity "&postid"
line 179 column 85 - Warning: <style> isn't allowed in <td> elements
line 179 column 9 - Info: <td> previously mentioned
line 182 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 184 column 9 - Warning: missing <tr>
line 202 column 13 - Warning: missing <tr>
line 203 column 101 - Warning: unescaped & or unknown entity "&postid"
line 210 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 212 column 9 - Warning: missing <tr>
line 230 column 13 - Warning: missing <tr>
line 231 column 101 - Warning: unescaped & or unknown entity "&postid"
line 236 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 238 column 9 - Warning: missing <tr>
line 256 column 13 - Warning: missing <tr>
line 257 column 101 - Warning: unescaped & or unknown entity "&postid"
line 266 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 268 column 9 - Warning: missing <tr>
line 286 column 13 - Warning: missing <tr>
line 287 column 101 - Warning: unescaped & or unknown entity "&postid"
line 289 column 85 - Warning: <style> isn't allowed in <td> elements
line 289 column 9 - Info: <td> previously mentioned
line 292 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 294 column 9 - Warning: missing <tr>
line 312 column 13 - Warning: missing <tr>
line 313 column 101 - Warning: unescaped & or unknown entity "&postid"
line 319 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 321 column 9 - Warning: missing <tr>
line 339 column 13 - Warning: missing <tr>
line 340 column 101 - Warning: unescaped & or unknown entity "&postid"
line 355 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 357 column 9 - Warning: missing <tr>
line 375 column 13 - Warning: missing <tr>
line 376 column 101 - Warning: unescaped & or unknown entity "&postid"
line 385 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 387 column 9 - Warning: missing <tr>
line 405 column 13 - Warning: missing <tr>
line 406 column 101 - Warning: unescaped & or unknown entity "&postid"
line 412 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 414 column 9 - Warning: missing <tr>
line 432 column 13 - Warning: missing <tr>
line 433 column 101 - Warning: unescaped & or unknown entity "&postid"
line 445 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 447 column 9 - Warning: missing <tr>
line 465 column 13 - Warning: missing <tr>
line 466 column 101 - Warning: unescaped & or unknown entity "&postid"
line 476 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 478 column 9 - Warning: missing <tr>
line 496 column 13 - Warning: missing <tr>
line 497 column 101 - Warning: unescaped & or unknown entity "&postid"
line 499 column 74 - Warning: <style> isn't allowed in <td> elements
line 499 column 9 - Info: <td> previously mentioned
line 499 column 1365 - Error: <z> is not recognized!
line 499 column 1365 - Warning: discarding unexpected <z>
line 499 column 1377 - Warning: discarding unexpected </z>
line 501 column 1409 - Error: <z> is not recognized!
line 501 column 1409 - Warning: discarding unexpected <z>
line 501 column 1417 - Warning: discarding unexpected </z>
line 503 column 1433 - Error: <z> is not recognized!
line 503 column 1433 - Warning: discarding unexpected <z>
line 503 column 1445 - Warning: discarding unexpected </z>
line 505 column 1460 - Error: <z> is not recognized!
line 505 column 1460 - Warning: discarding unexpected <z>
line 505 column 1468 - Warning: discarding unexpected </z>
line 511 column 2414 - Warning: discarding unexpected </td>
line 514 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 516 column 9 - Warning: missing <tr>
line 534 column 13 - Warning: missing <tr>
line 535 column 101 - Warning: unescaped & or unknown entity "&postid"
line 543 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 545 column 9 - Warning: missing <tr>
line 563 column 13 - Warning: missing <tr>
line 564 column 101 - Warning: unescaped & or unknown entity "&postid"
line 566 column 74 - Warning: <style> isn't allowed in <td> elements
line 566 column 9 - Info: <td> previously mentioned
line 566 column 1365 - Error: <z> is not recognized!
line 566 column 1365 - Warning: discarding unexpected <z>
line 566 column 1377 - Warning: discarding unexpected </z>
line 568 column 1409 - Error: <z> is not recognized!
Tidy found 426 warnings and 12 errors! Not all warnings/errors were shown.

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