Register - Login
Views: 99395268
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 12:22:00 PM
Jul - SM64 Hacking (Archive) - Toad's Tool 0.6.0 (On hiatus for an indefinite amount of time) New poll - New thread - Thread closed
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 ... 19 20 21 22 23 24 25 26 27 28 Next newer thread | Next older thread
Polygon model importer, how soon do you want it?
Please vote or be transformed into Walluigi!
Now! Even if it means it will be buggy and limited to a single untextured model!
 
11.4%, 14 votes
I could wait a month for more features and textured model import.
 
22.8%, 28 votes
I want all the features you can cram in, even if it means waiting indefinitely!
 
56.9%, 70 votes
You shouldn't have announced anything and released it when ready!
 
4.1%, 5 votes
Me don't care!
 
4.9%, 6 votes
Multi-voting is disabled. 123 users have voted.

messiaen
Catgirl
Level: 68


Posts: 532/1085
EXP: 2594175
For next: 134625

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 04-01-09 08:28:27 PM Link
Originally posted by "VL-Tone"
If you take RAM/ROM limitations out of the equation, do you have any idea if there's a limit on the number of polygons a level can contain? I would guess that the main limitation will be slow-downs if there are too many polygons on screen (and I'd guess that the collision map would also things slow-down if it gets too complex).

Note that complex levels that have doors and rooms in the original game (Inside Castle, Hazy Maze Cave, Haunted House) have some management techniques that involve displaying a limited number of rooms at a time (and it's a little buggy, as you can see other rooms disappearing while Mario crosses the doors inside the castle, even though a transition state where both rooms are visible was included in the game.)


I don't know anything about polygon/vertex limits, however if I remember correctly the values for Zelda 64 are known so maybe they can be used as reference for some experiments. I don't know this information, but try to contact xdaniel, he might be of help. It would be interesting at some point to test some low level video-plugins, as it may be hard to know for sure the limits because of all the high level emulation. You should include a polygon/vertex counter, so users can report the results.

About space, what about 1MB for each new level? If the ROM runs out of space, expand to 32MB and then if needed to 48MB. By the way, this brings a point: the differences between the padding produced by the Windows and Mac version of the ROM Extender. The Windows version pads with 0x01 bytes while the Mac pads with 0xFF.

This is troublesome when it comes to producing patches or writing any kind of tool that 'searches' for free space in the ROM. I know that by now it's hard to deal with it since the ROM Extender is widespread, but it would be interesting to provide a new version of the extender with this bug fixed, especially because there will be renewed interest in TT64 after the polygon importer and patches will be more common than they are now. At least, I think a warning about this should be included in TT64/ROM Extender documentation.

By the way, you'll also need a GIANT warning about extended memory. Emulators such as Mupen enable it by default, however Project 64 requires changing this configuration in its advanced settings, and I'm sure a LOT of people will get lost on that seemingly simple task because they haven't read the documentation. Providing screenshoots will be probably necessary so we don't have to face this question one thousand of times.
FieryIce

Luigi
Level: 119


Posts: 134/4161
EXP: 18741389
For next: 187902

Since: 12-18-08

From: Chicago

Since last post: 179 days
Last activity: 5 days
Posted on 04-02-09 12:39:42 AM Link
Don't worry about the delay VL-Tone, I can wait patiently I hope you can find a way to get through the RAM limitations and space issues you're having with the polygon importer.
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 423/621
EXP: 1135562
For next: 21557

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 1.2 years
Posted on 04-03-09 02:21:19 AM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Originally posted by messiaen
About space, what about 1MB for each new level? If the ROM runs out of space, expand to 32MB and then if needed to 48MB. By the way, this brings a point: the differences between the padding produced by the Windows and Mac version of the ROM Extender. The Windows version pads with 0x01 bytes while the Mac pads with 0xFF.

This is troublesome when it comes to producing patches or writing any kind of tool that 'searches' for free space in the ROM. I know that by now it's hard to deal with it since the ROM Extender is widespread, but it would be interesting to provide a new version of the extender with this bug fixed, especially because there will be renewed interest in TT64 after the polygon importer and patches will be more common than they are now. At least, I think a warning about this should be included in TT64/ROM Extender documentation.


I guess that since Mac users are fewer, I should fix the ROM extender so that it only pads with 0x01 on both platform. TT64 could warn users trying to open a ROM padded with 0xFF, but should it still allow them to open the ROM?
Originally posted by messiaen
By the way, you'll also need a GIANT warning about extended memory. Emulators such as Mupen enable it by default, however Project 64 requires changing this configuration in its advanced settings, and I'm sure a LOT of people will get lost on that seemingly simple task because they haven't read the documentation. Providing screenshoots will be probably necessary so we don't have to face this question one thousand of times.


People publishing mods should also have big warnings and instructions about extended memory with their ROM, since most people using them won't have TT64. Couldn't we eventually add a special screen in the game that warns about the lack of "expansion pack" much like Donkey Kong 64 and Majora's Mask? That would help for modders who didn't include documentation or users that didn't read it.
Originally posted by FieryIce
Don't worry about the delay VL-Tone, I can wait patiently I hope you can find a way to get through the RAM limitations and space issues you're having with the polygon importer.


Thanks for the kind encouragements

____________________
Me-me
340
Level: 41


Posts: 67/341
EXP: 461703
For next: 18442

Since: 08-05-07


Since last post: 9.7 years
Last activity: 8.1 years
Posted on 04-03-09 04:37:31 AM Link
Maybe I should ask this in another thread but anyways:
Any recommendations on wich 3D model maker I should use, 'cause I can't find a reliable one, (or am I just too lazy?)
Thank you!

____________________
Wow! SM64 is totally turned upside-down!
gamekrazzy
Member
Level: 32


Posts: 53/199
EXP: 194436
For next: 12006

Since: 03-06-09


Since last post: 10.4 years
Last activity: 8.6 years
Posted on 04-03-09 07:45:10 PM Link
I probably should not ask this, but will this have the option to use premade objects that are in the game as well as imported. This is for the level editor. Because for some reason Messian's "Platform Battlefield" does not work on TT64 for my computer. And I need to be able to add objects to my level. I also do not have knowledge of 3d modelling. And what I want to make only requires the premade objects/platforms. Just the simple cube would work.

____________________
Vinnyboiler
Catgirl
Level: 66


Posts: 40/1044
EXP: 2439906
For next: 21945

Since: 12-27-07

From: London, England

Since last post: 7 days
Last activity: 3 days
Posted on 04-05-09 05:24:01 PM (last edited by vinnyboiler at 04-05-09 02:32 PM) Link
Can we be able to change the level propertys such as adding snow or having mario fall into the like in the snow levels and will the all the models have the same texture?
gamekrazzy
Member
Level: 32


Posts: 56/199
EXP: 194436
For next: 12006

Since: 03-06-09


Since last post: 10.4 years
Last activity: 8.6 years
Posted on 04-05-09 05:51:37 PM Link
You should be able to do that now, if you have a hex editor. I believe you change the terrain type. Go to the adress of Terrain type for castle grounds(Expert) and copy the decimal form. Go to that location, change the 4th byte in that address to 02 and the terrain is now snow. Now it doesn't look like snow, but the game thinks it is. as you might see when walking on the dirt path. Note:This also makes the water deal damage. I think this might mak it so that if you fell you would fall into it, but that might be part of the solidity.

____________________
wwwarea
Member
Level: 21


Posts: 31/74
EXP: 45037
For next: 4906

Since: 08-10-08


Since last post: 9.7 years
Last activity: 9.4 years
Posted on 04-07-09 06:29:03 PM Link
Hey, its April 7th. And im wondering if its going to be released today. I mean its 2:28PM here.xD
Sorry for asking. Its getting more hard to wait. xD
Bob-omb8194
Still Explodin'
Level: 80


Posts: 115/1654
EXP: 4666049
For next: 116920

Since: 02-19-09

From: NC, US

Since last post: 10.8 years
Last activity: 10.8 years
Posted on 04-07-09 06:54:04 PM (last edited by Bob-omb8194 at 04-07-09 03:56 PM) Link
Originally posted by wwwarea
Hey, its April 7th. And im wondering if its going to be released today. I mean its 2:28PM here.xD
Sorry for asking. Its getting more hard to wait. xD



He may do it later, probably around 7:00 Eastern Standard Time (Eastern U.S. and Eastern Canada). That is only if he had to delay it again.
wwwarea
Member
Level: 21


Posts: 32/74
EXP: 45037
For next: 4906

Since: 08-10-08


Since last post: 9.7 years
Last activity: 9.4 years
Posted on 04-07-09 06:58:11 PM Link
Oh OK. I will see but I mite have to go somewhere before I can check.
RDX

Level: 32


Posts: 41/198
EXP: 193370
For next: 13072

Since: 02-14-09


Since last post: 10.8 years
Last activity: 10.5 years
Posted on 04-07-09 08:05:54 PM Link
He's probably at work right now.

Or doing life things.

____________________
messiaen
Catgirl
Level: 68


Posts: 534/1085
EXP: 2594175
For next: 134625

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 04-07-09 08:09:41 PM (last edited by messiaen at 04-07-09 05:12 PM) Link
Originally posted by VL-Tone
I guess that since Mac users are fewer, I should fix the ROM extender so that it only pads with 0x01 on both platform. TT64 could warn users trying to open a ROM padded with 0xFF, but should it still allow them to open the ROM?


That would work . Since TT64 is going through such drastic change, I'm not sure if you should bother to include backward compatibility. It users want only to make small edits they can have the same functionality with older versions of TT64.

Originally posted by VL-Tone
People publishing mods should also have big warnings and instructions about extended memory with their ROM, since most people using them won't have TT64. Couldn't we eventually add a special screen in the game that warns about the lack of "expansion pack" much like Donkey Kong 64 and Majora's Mask? That would help for modders who didn't include documentation or users that didn't read it.


Probably a screen could be added before the Nintendo logo (if I'm not mistaken, there is a very early Crazy Nation trainer that hooks a intro screen when the ROM boots). Perhaps a TT64 logo and something like "please enable extended memory on the emulator for proper functionality".

Here's a summary of the modifications to be patched into the ROM for extended memory support:

http://sites.google.com/site/messiaen64/extended-memory-support

You can change the ROM/RAM offsets with minor adjustments.
wwwarea
Member
Level: 21


Posts: 33/74
EXP: 45037
For next: 4906

Since: 08-10-08


Since last post: 9.7 years
Last activity: 9.4 years
Posted on 04-07-09 09:21:09 PM Link
Umm, I went back to page 7th and he said it will be release at the 15th... He marked out 7th and put it to 15th.
RDX

Level: 32


Posts: 43/198
EXP: 193370
For next: 13072

Since: 02-14-09


Since last post: 10.8 years
Last activity: 10.5 years
Posted on 04-07-09 10:33:37 PM Link
That's actually kind of funny.

Thanks for letting us know.

____________________
luigiman1928
Member
Level: 17


Posts: 12/46
EXP: 21632
For next: 3111

Since: 02-23-09

From: Gscentral

Since last post: 12.0 years
Last activity: 11.3 years
Posted on 04-08-09 01:23:31 AM Link
I have a suggestion for the Importer. Why not add the feature of adding Your own texture!

____________________
Gscentral forever!!
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 427/621
EXP: 1135562
For next: 21557

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 1.2 years
Posted on 04-08-09 03:37:41 AM (last edited by VL-Tone at 04-08-09 12:39 AM) Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Originally posted by wwwarea
Umm, I went back to page 7th and he said it will be release at the 15th... He marked out 7th and put it to 15th.


Well... hmmm... yeah... Sorry again.

I'll have 4 days off next weekend (from saturday to tuesday) because of Easter, so I thought it would be much more logical to finish it over the weekend release it just after that. Besides, messiaen just gave me the code to patch to enable extended RAM use (but don't blame him for the delay, I didn't exactly put any pressure on him to give me the code earlier).

Now, there's one thing that didn't help with the delay, is that I don't know exactly how to deal with a particular feature of the importer. Maybe you guys could help me figure out the best way to implement it.

Note: it's a very complicated problem that's hard to easily explain, and that's essentially why I stumbled and stopped working on TT64 two days ago, trying to find a viable solution...

Here's my problem:


When you want to change any parameters, or import an updated version of the .obj polygon file, the whole level data will be deleted and re-created. To avoid losing all your level objects (0x24 objects for example), I thought about having the 0x24 command list optionally saved so that when you "re-create" the level you can keep the existing objects. There's already a planned feature (which almost fully works now) which enables you to save to and load from a "level file" which will contain all the polygon importer parameters (scale, offset, terrain type, bank selections) and will also include the .obj data and the texture data inside the same file. So I planned to also include in the level files the 0x24 commands, which will be nice since a level file can be used to recreate the exact same level in a different ROM.

Here's the problem with that approach:

It's all about when the 0x24 objects should/can be saved to the level file. Logically, when you press "Save Level File" all parameters AND the 0x24 will be saved into the currently open level file. But 0x24 editing happens in the main level editor window, so you'd have to go back and forth between the importer and the editor to save anytime you make a change. Unless I add an option to automatically save 0x24 commands to the level file when the ROM is saved (either by pressing the Save ROM button, or with the auto-save option).

That's all fine, when the level you're editing happens to be the one that was created using the currently open level file (only one level file can be open at a time, and the "create/save level to ROM" button will create the level in the currently selected slot, replacing the currently selected replacing level). But what if you try to edit another custom level for which you don't have the level file open? Changes to 0x24 commands wouldn't be saved to the level file unless TT64 tracks where are the level files for all the custom level slots in a given ROM. One way to do that would be to save the file path of each one in the "File table" list that TT64 will be writing to the ROM.

But I really dislike the idea of having your ROM dependent on the path of multiple files possibly scattered around your HDD. What if you move one of the level files? It's simply too much things to track down and it complicates the process needlessly.

To avoid these problems entirely, the best thing is to use the existing 0x24 commands found in the ROM if you want to keep them when "re-creating" the level when importing or changing importation parameters. But if I only give this option, you lose the very useful feature of being able to use a saved level file to re-create the same level in multiple ROMs, mixing and matching levels if you want. It would be especially sad not to include the ability to save 0x24 objects to the level file when it contains everything needed to re-create a specific level.

My solution involves having three option when saving a custom level to ROM:
1. "Keep objects from ROM"
2. "Use objects from level file"
3. "Use empty objects".

Since option 2 would now only be really useful when wanting to move a level from a ROM to another, I guess I could let go of all the auto-save problems and only save the 0x24 objects to the file when the "Save level file" button is pressed. Still, there could be a problem where you'd import a level, go edit the 0x24 objects, save them to the file, go back to the editor, edit 0x24 objects in another custom level slot, and comming back to the importer to save, without realizing that you'd only save 0x24 objects from the last imported level into the last open level file... Saving the 0x24 objects to the previously imported level would require re-opening the right level file.

Ultimately, a solution to all these problems would be to use a single file for all levels of a given ROM, instead of one file for each level. But it would change the whole paradigm of the current importer, and I would have to create another complex interface to individually manage levels found in that file (to enable you to mix and match levels from multiple files into a single ROM). Furthermore, this single "levels file" could end up being relatively big, especially with the additional space that the extended RAM will provide.
Originally posted by luigiman1928
I have a suggestion for the Importer. Why not add the feature of adding Your own texture!

I'm not sure if that's what you're suggesting, but it was already planned to work like that. You'll have to import your own texture in the level importer interface.

____________________
luigiman1928
Member
Level: 17


Posts: 13/46
EXP: 21632
For next: 3111

Since: 02-23-09

From: Gscentral

Since last post: 12.0 years
Last activity: 11.3 years
Posted on 04-08-09 10:35:56 PM Link
Like i can use a NES SMB Brick and still have all the other textures!? Man, i, Love, You. ( I'm not Homo!)

____________________
Gscentral forever!!
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 429/621
EXP: 1135562
For next: 21557

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 1.2 years
Posted on 04-10-09 05:41:40 AM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Ok since nobody here seems to be able to help me with my problem (probably because of my overly complicated explanation), I'll take a decision.

I'll keep the one file per level format, and 0x24 objects will only be saved to the level file when you press the "Save level file" button. Users will be responsible of having the corresponding level file open if they want to copy changes made to the 0x24 objects in the level file. Like I said, this feature will only really be useful if you want to copy a custom level to another ROM.

If you only want to update/change the polygon data or other importation parameters while keeping the original objects, while keeping the 0x24 objects currently in the custom level, the "Keep objects from ROM" option will be the best (and default) choice.



____________________
messiaen
Catgirl
Level: 68


Posts: 537/1085
EXP: 2594175
For next: 134625

Since: 11-20-07


Since last post: 8.1 years
Last activity: 7.2 years
Posted on 04-10-09 12:20:27 PM (last edited by messiaen at 04-10-09 09:23 AM) Link
Once the first importer version is released it will be easier to give feedack on this, I suppose. It doesn't seems like this 3 options ("Keep objects from ROM", "Use objects from level file", "Use empty objects") will be overly complicated. However, wouldn't it be easier to make TT64 work straight with inidividual level files and have a "commit level" to ROM button which would ask then what level is to be replaced?

Anyway, modularity is a big plus and will be a nice way to work on team hacks, so I think you should discard having all the levels on a single file. Let the users manage their own mess .
FieryIce

Luigi
Level: 119


Posts: 194/4161
EXP: 18741389
For next: 187902

Since: 12-18-08

From: Chicago

Since last post: 179 days
Last activity: 5 days
Posted on 04-10-09 03:36:06 PM Link
Originally posted by messiaen
However, wouldn't it be easier to make TT64 work straight with inidividual level files and have a "commit level" to ROM button which would ask then what level is to be replaced?

Anyway, modularity is a big plus and will be a nice way to work on team hacks, so I think you should discard having all the levels on a single file. Let the users manage their own mess .


I totally agree with you here, if you store each level in a different file then team hacks would be so much easier to work on.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 ... 19 20 21 22 23 24 25 26 27 28 Next newer thread | Next older thread
Jul - SM64 Hacking (Archive) - Toad's Tool 0.6.0 (On hiatus for an indefinite amount of time) New poll - New thread - Thread closed


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

39 database queries, 9 query cache hits.
Query execution time:  0.125336 seconds
Script execution time:  0.036802 seconds
Total render time:  0.162138 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
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 233 - 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 320 - Warning: unescaped & or unknown entity "&page"
line 149 column 352 - Warning: unescaped & or unknown entity "&page"
line 149 column 385 - Warning: unescaped & or unknown entity "&page"
line 149 column 419 - Warning: unescaped & or unknown entity "&page"
line 149 column 457 - Warning: unescaped & or unknown entity "&page"
line 149 column 491 - Warning: unescaped & or unknown entity "&page"
line 149 column 525 - Warning: unescaped & or unknown entity "&page"
line 149 column 559 - Warning: unescaped & or unknown entity "&page"
line 149 column 593 - Warning: unescaped & or unknown entity "&page"
line 149 column 627 - Warning: unescaped & or unknown entity "&page"
line 149 column 661 - Warning: unescaped & or unknown entity "&page"
line 149 column 695 - Warning: unescaped & or unknown entity "&page"
line 149 column 729 - Warning: unescaped & or unknown entity "&page"
line 149 column 763 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 800 - Warning: missing </font> before </table>
line 152 column 73 - Warning: missing </b> before </td>
line 155 column 210 - Warning: discarding unexpected </a>
line 156 column 131 - Warning: missing <tr>
line 159 column 195 - Warning: discarding unexpected </a>
line 160 column 133 - Warning: missing <tr>
line 163 column 209 - Warning: discarding unexpected </a>
line 164 column 132 - Warning: missing <tr>
line 167 column 195 - Warning: discarding unexpected </a>
line 168 column 133 - Warning: missing <tr>
line 171 column 144 - Warning: discarding unexpected </a>
line 172 column 131 - Warning: missing <tr>
line 175 column 66 - Warning: missing </font> before </td>
line 175 column 140 - Warning: plain text isn't allowed in <tr> elements
line 175 column 25 - Info: <tr> previously mentioned
line 182 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 184 column 9 - Warning: missing <tr>
line 202 column 13 - Warning: missing <tr>
line 219 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 221 column 9 - Warning: missing <tr>
line 239 column 13 - Warning: missing <tr>
line 245 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 247 column 9 - Warning: missing <tr>
line 265 column 13 - Warning: missing <tr>
line 268 column 74 - Warning: <style> isn't allowed in <td> elements
line 268 column 9 - Info: <td> previously mentioned
line 268 column 1512 - Warning: missing </font> before <blockquote>
line 268 column 1591 - Warning: inserting implicit <font>
line 268 column 1591 - Warning: missing </font> before <hr>
line 269 column 1 - Warning: inserting implicit <font>
line 269 column 1 - Warning: missing </font> before <hr>
line 271 column 1 - Warning: inserting implicit <font>
line 271 column 1 - Warning: missing </font> before <blockquote>
line 274 column 2786 - Warning: inserting implicit <font>
line 274 column 2786 - Warning: missing </font> before <hr>
line 274 column 2851 - Warning: inserting implicit <font>
line 274 column 2851 - Warning: missing </font> before <hr>
line 275 column 1 - Warning: inserting implicit <font>
line 275 column 1 - Warning: missing </font> before <blockquote>
line 278 column 3711 - Warning: inserting implicit <font>
line 278 column 3711 - Warning: missing </font> before <hr>
line 278 column 3776 - Warning: inserting implicit <font>
line 278 column 3776 - Warning: missing </font> before <hr>
line 279 column 1 - Warning: inserting implicit <font>
line 268 column 138 - Warning: missing </div>
line 283 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 285 column 9 - Warning: missing <tr>
line 303 column 13 - Warning: missing <tr>
line 311 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 313 column 9 - Warning: missing <tr>
line 331 column 13 - Warning: missing <tr>
line 337 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 339 column 9 - Warning: missing <tr>
line 357 column 13 - Warning: missing <tr>
line 363 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 365 column 9 - Warning: missing <tr>
line 383 column 13 - Warning: missing <tr>
line 389 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 391 column 9 - Warning: missing <tr>
line 409 column 13 - Warning: missing <tr>
line 416 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 418 column 9 - Warning: missing <tr>
line 436 column 13 - Warning: missing <tr>
line 446 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 448 column 9 - Warning: missing <tr>
line 466 column 13 - Warning: missing <tr>
line 472 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 474 column 9 - Warning: missing <tr>
line 492 column 13 - Warning: missing <tr>
line 500 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 502 column 9 - Warning: missing <tr>
line 520 column 13 - Warning: missing <tr>
line 538 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 540 column 9 - Warning: missing <tr>
line 558 column 13 - Warning: missing <tr>
line 564 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 566 column 9 - Warning: missing <tr>
line 584 column 13 - Warning: missing <tr>
line 592 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 594 column 9 - Warning: missing <tr>
line 612 column 13 - Warning: missing <tr>
line 618 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 620 column 9 - Warning: missing <tr>
line 638 column 13 - Warning: missing <tr>
line 641 column 74 - Warning: <style> isn't allowed in <td> elements
line 641 column 9 - Info: <td> previously mentioned
line 641 column 1512 - Warning: missing </font> before <blockquote>
line 641 column 1591 - Warning: inserting implicit <font>
line 641 column 1591 - Warning: missing </font> before <hr>
line 641 column 1655 - Warning: inserting implicit <font>
line 641 column 1655 - Warning: missing </font> before <hr>
line 642 column 1 - Warning: inserting implicit <font>
line 642 column 1 - Warning: missing </font> before <h3>
line 649 column 2428 - Warning: inserting implicit <font>
line 652 column 1 - Warning: inserting implicit <font>
line 652 column 1 - Warning: missing </font> before <blockquote>
line 673 column 7007 - Warning: inserting implicit <font>
line 673 column 7007 - Warning: missing </font> before <hr>
line 673 column 7076 - Warning: inserting implicit <font>
line 673 column 7076 - Warning: missing </font> before <hr>
line 674 column 1 - Warning: inserting implicit <font>
line 641 column 138 - Warning: missing </div>
line 677 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 679 column 9 - Warning: missing <tr>
line 697 column 13 - Warning: missing <tr>
line 703 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 705 column 9 - Warning: missing <tr>
line 723 column 13 - Warning: missing <tr>
line 726 column 74 - Warning: <style> isn't allowed in <td> elements
line 726 column 9 - Info: <td> previously mentioned
line 726 column 138 - Warning: missing </div>
line 735 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 737 column 9 - Warning: missing <tr>
line 755 column 13 - Warning: missing <tr>
line 763 column 9 - Warning: <div> isn't allowed in <table> elements
line 178 column 17 - Info: <table> previously mentioned
line 765 column 9 - Warning: missing <tr>
line 783 column 13 - Warning: missing <tr>
line 793 column 17 - Warning: missing <tr>
line 793 column 17 - Warning: discarding unexpected <table>
line 796 column 35 - Warning: missing <tr>
line 796 column 94 - Warning: unescaped & or unknown entity "&page"
line 796 column 126 - Warning: unescaped & or unknown entity "&page"
line 796 column 158 - Warning: unescaped & or unknown entity "&page"
line 796 column 190 - Warning: unescaped & or unknown entity "&page"
line 796 column 222 - Warning: unescaped & or unknown entity "&page"
line 796 column 254 - Warning: unescaped & or unknown entity "&page"
line 796 column 286 - Warning: unescaped & or unknown entity "&page"
line 796 column 320 - Warning: unescaped & or unknown entity "&page"
line 796 column 352 - Warning: unescaped & or unknown entity "&page"
line 796 column 385 - Warning: unescaped & or unknown entity "&page"
line 796 column 419 - Warning: unescaped & or unknown entity "&page"
line 796 column 457 - Warning: unescaped & or unknown entity "&page"
line 796 column 491 - Warning: unescaped & or unknown entity "&page"
line 796 column 525 - Warning: unescaped & or unknown entity "&page"
line 796 column 559 - Warning: unescaped & or unknown entity "&page"
line 796 column 593 - Warning: unescaped & or unknown entity "&page"
line 796 column 627 - Warning: unescaped & or unknown entity "&page"
line 796 column 661 - Warning: unescaped & or unknown entity "&page"
line 796 column 695 - Warning: unescaped & or unknown entity "&page"
line 796 column 729 - Warning: unescaped & or unknown entity "&page"
line 796 column 763 - Warning: unescaped & or unknown entity "&page"
line 796 column 50 - Warning: missing </font> before </td>
line 796 column 800 - Warning: missing </font> before </table>
line 798 column 35 - Warning: missing <tr>
line 798 column 50 - Warning: missing </font> before </td>
line 799 column 37 - Warning: unescaped & or unknown entity "&id"
line 798 column 233 - Warning: missing </font> before </table>
line 800 column 17 - Warning: discarding unexpected </textarea>
line 800 column 28 - Warning: discarding unexpected </form>
line 800 column 35 - Warning: discarding unexpected </embed>
line 800 column 43 - Warning: discarding unexpected </noembed>
line 800 column 53 - Warning: discarding unexpected </noscript>
line 800 column 64 - Warning: discarding unexpected </noembed>
line 800 column 74 - Warning: discarding unexpected </embed>
line 800 column 82 - Warning: discarding unexpected </table>
line 800 column 90 - Warning: discarding unexpected </table>
line 802 column 9 - Warning: missing </font> before <table>
line 814 column 25 - Warning: discarding unexpected </font>
line 823 column 57 - Warning: discarding unexpected </font>
line 801 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 216 - Warning: <img> proprietary attribute value "absmiddle"
line 155 column 70 - Warning: <img> proprietary attribute value "absmiddle"
line 155 column 70 - Warning: <img> lacks "alt" attribute
line 156 column 70 - Warning: <table> attribute "width" has invalid value "11.4%"
line 159 column 70 - Warning: <img> proprietary attribute value "absmiddle"
line 159 column 70 - Warning: <img> lacks "alt" attribute
line 160 column 70 - Warning: <table> attribute "width" has invalid value "22.8%"
line 163 column 70 - Warning: <img> proprietary attribute value "absmiddle"
line 163 column 70 - Warning: <img> lacks "alt" attribute
line 164 column 70 - Warning: <table> attribute "width" has invalid value "56.9%"
line 167 column 70 - Warning: <img> proprietary attribute value "absmiddle"
line 167 column 70 - Warning: <img> lacks "alt" attribute
line 168 column 70 - Warning: <table> attribute "width" has invalid value "4.1%"
line 171 column 70 - Warning: <img> proprietary attribute value "absmiddle"
line 171 column 70 - Warning: <img> lacks "alt" attribute
line 172 column 70 - Warning: <table> attribute "width" has invalid value "4.9%"
line 172 column 70 - Warning: <table> attribute "bgcolor" has invalid value "grey"
line 187 column 22 - Warning: <img> lacks "alt" attribute
line 187 column 63 - Warning: <img> lacks "alt" attribute
line 187 column 111 - Warning: <img> lacks "alt" attribute
line 187 column 161 - Warning: <img> lacks "alt" attribute
line 198 column 15 - Warning: <img> lacks "alt" attribute
line 223 column 11 - Warning: <img> lacks "alt" attribute
line 224 column 23 - Warning: <img> lacks "alt" attribute
line 224 column 64 - Warning: <img> lacks "alt" attribute
line 224 column 113 - Warning: <img> lacks "alt" attribute
line 224 column 163 - Warning: <img> lacks "alt" attribute
line 225 column 11 - Warning: <img> lacks "alt" attribute
line 235 column 15 - Warning: <img> lacks "alt" attribute
line 242 column 132 - Warning: <img> proprietary attribute value "absmiddle"
line 242 column 132 - Warning: <img> lacks "alt" attribute
line 250 column 22 - Warning: <img> lacks "alt" attribute
line 250 column 63 - Warning: <img> lacks "alt" attribute
line 250 column 112 - Warning: <img> lacks "alt" attribute
line 250 column 162 - Warning: <img> lacks "alt" attribute
line 261 column 15 - Warning: <img> lacks "alt" attribute
line 268 column 694 - Warning: <img> lacks "alt" attribute
line 278 column 3834 - Warning: <img> proprietary attribute value "absmiddle"
line 278 column 3834 - Warning: <img> lacks "alt" attribute
line 280 column 4063 - Warning: <img> proprietary attribute value "absmiddle"
line 280 column 4063 - Warning: <img> lacks "alt" attribute
line 280 column 4195 - Warning: <img> lacks "alt" attribute
line 280 column 4354 - Warning: <img> lacks "alt" attribute
line 287 column 15 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 15 - Warning: <img> lacks "alt" attribute
line 287 column 58 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 58 - Warning: <img> lacks "alt" attribute
line 287 column 101 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 101 - Warning: <img> lacks "alt" attribute
line 287 column 144 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 144 - Warning: <img> lacks "alt" attribute
line 287 column 187 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 187 - Warning: <img> lacks "alt" attribute
line 287 column 230 - Warning: <img> proprietary attribute value "absmiddle"
line 287 column 230 - Warning: <img> lacks "alt" attribute
line 288 column 22 - Warning: <img> lacks "alt" attribute
line 288 column 63 - Warning: <img> lacks "alt" attribute
line 288 column 112 - Warning: <img> lacks "alt" attribute
line 288 column 162 - Warning: <img> lacks "alt" attribute
line 289 column 11 - Warning: <img> lacks "alt" attribute
line 299 column 15 - Warning: <img> lacks "alt" attribute
line 316 column 22 - Warning: <img> lacks "alt" attribute
line 316 column 63 - Warning: <img> lacks "alt" attribute
line 316 column 112 - Warning: <img> lacks "alt" attribute
line 316 column 162 - Warning: <img> lacks "alt" attribute
line 317 column 11 - Warning: <img> lacks "alt" attribute
line 327 column 15 - Warning: <img> lacks "alt" attribute
line 334 column 556 - Warning: <img> lacks "alt" attribute
line 342 column 22 - Warning: <img> lacks "alt" attribute
line 342 column 63 - Warning: <img> lacks "alt" attribute
line 342 column 112 - Warning: <img> lacks "alt" attribute
line 342 column 162 - Warning: <img> lacks "alt" attribute
line 343 column 11 - Warning: <img> lacks "alt" attribute
line 353 column 15 - Warning: <img> lacks "alt" attribute
line 368 column 22 - Warning: <img> lacks "alt" attribute
line 368 column 63 - Warning: <img> lacks "alt" attribute
line 368 column 112 - Warning: <img> lacks "alt" attribute
line 368 column 162 - Warning: <img> lacks "alt" attribute
line 369 column 11 - Warning: <img> lacks "alt" attribute
line 379 column 15 - Warning: <img> lacks "alt" attribute
line 386 column 644 - Warning: <img> lacks "alt" attribute
line 394 column 22 - Warning: <img> lacks "alt" attribute
line 394 column 63 - Warning: <img> lacks "alt" attribute
line 394 column 112 - Warning: <img> lacks "alt" attribute
line 394 column 162 - Warning: <img> lacks "alt" attribute
line 405 column 15 - Warning: <img> lacks "alt" attribute
line 421 column 22 - Warning: <img> lacks "alt" attribute
line 421 column 63 - Warning: <img> lacks "alt" attribute
line 421 column 112 - Warning: <img> lacks "alt" attribute
line 421 column 162 - Warning: <img> lacks "alt" attribute
line 422 column 11 - Warning: <img> lacks "alt" attribute
line 432 column 15 - Warning: <img> lacks "alt" attribute
line 451 column 22 - Warning: <img> lacks "alt" attribute
line 451 column 63 - Warning: <img> lacks "alt" attribute
line 451 column 112 - Warning: <img> lacks "alt" attribute
line 451 column 162 - Warning: <img> lacks "alt" attribute
line 462 column 15 - Warning: <img> lacks "alt" attribute
line 477 column 22 - Warning: <img> lacks "alt" attribute
line 477 column 63 - Warning: <img> lacks "alt" attribute
line 477 column 112 - Warning: <img> lacks "alt" attribute
line 477 column 162 - Warning: <img> lacks "alt" attribute
line 488 column 15 - Warning: <img> lacks "alt" attribute
line 497 column 167 - Warning: <img> lacks "alt" attribute
line 505 column 22 - Warning: <img> lacks "alt" attribute
line 505 column 63 - Warning: <img> lacks "alt" attribute
line 505 column 111 - Warning: <img> lacks "alt" attribute
line 505 column 161 - Warning: <img> lacks "alt" attribute
line 516 column 15 - Warning: <img> lacks "alt" attribute
line 525 column 418 - Warning: <img> proprietary attribute value "absmiddle"
line 525 column 418 - Warning: <img> lacks "alt" attribute
line 543 column 22 - Warning: <img> lacks "alt" attribute
line 543 column 63 - Warning: <img> lacks "alt" attribute
line 543 column 112 - Warning: <img> lacks "alt" attribute
line 543 column 162 - Warning: <img> lacks "alt" attribute
line 554 column 15 - Warning: <img> lacks "alt" attribute
line 569 column 22 - Warning: <img> lacks "alt" attribute
line 569 column 63 - Warning: <img> lacks "alt" attribute
line 569 column 112 - Warning: <img> lacks "alt" attribute
line 569 column 162 - Warning: <img> lacks "alt" attribute
line 580 column 15 - Warning: <img> lacks "alt" attribute
line 589 column 171 - Warning: <img> lacks "alt" attribute
line 597 column 22 - Warning: <img> lacks "alt" attribute
line 597 column 63 - Warning: <img> lacks "alt" attribute
line 597 column 112 - Warning: <img> lacks "alt" attribute
line 597 column 162 - Warning: <img> lacks "alt" attribute
line 598 column 11 - Warning: <img> lacks "alt" attribute
line 608 column 15 - Warning: <img> lacks "alt" attribute
line 623 column 22 - Warning: <img> lacks "alt" attribute
line 623 column 63 - Warning: <img> lacks "alt" attribute
line 623 column 112 - Warning: <img> lacks "alt" attribute
line 623 column 162 - Warning: <img> lacks "alt" attribute
line 634 column 15 - Warning: <img> lacks "alt" attribute
line 641 column 694 - Warning: <img> lacks "alt" attribute
line 674 column 7439 - Warning: <img> lacks "alt" attribute
line 674 column 7598 - Warning: <img> lacks "alt" attribute
line 682 column 22 - Warning: <img> lacks "alt" attribute
line 682 column 63 - Warning: <img> lacks "alt" attribute
line 682 column 112 - Warning: <img> lacks "alt" attribute
line 682 column 162 - Warning: <img> lacks "alt" attribute
line 683 column 11 - Warning: <img> lacks "alt" attribute
line 693 column 15 - Warning: <img> lacks "alt" attribute
line 708 column 22 - Warning: <img> lacks "alt" attribute
line 708 column 63 - Warning: <img> lacks "alt" attribute
line 708 column 112 - Warning: <img> lacks "alt" attribute
line 708 column 162 - Warning: <img> lacks "alt" attribute
line 719 column 15 - Warning: <img> lacks "alt" attribute
line 726 column 694 - Warning: <img> lacks "alt" attribute
line 732 column 2469 - Warning: <img> lacks "alt" attribute
line 732 column 2628 - Warning: <img> lacks "alt" attribute
line 740 column 22 - Warning: <img> lacks "alt" attribute
line 740 column 63 - Warning: <img> lacks "alt" attribute
line 740 column 111 - Warning: <img> lacks "alt" attribute
line 740 column 161 - Warning: <img> lacks "alt" attribute
line 751 column 15 - Warning: <img> lacks "alt" attribute
line 760 column 686 - Warning: <img> proprietary attribute value "absmiddle"
line 760 column 686 - Warning: <img> lacks "alt" attribute
line 767 column 11 - Warning: <img> lacks "alt" attribute
line 768 column 23 - Warning: <img> lacks "alt" attribute
line 768 column 64 - Warning: <img> lacks "alt" attribute
line 768 column 113 - Warning: <img> lacks "alt" attribute
line 768 column 163 - Warning: <img> lacks "alt" attribute
line 769 column 11 - Warning: <img> lacks "alt" attribute
line 779 column 15 - Warning: <img> lacks "alt" attribute
line 788 column 522 - Warning: <img> proprietary attribute value "absmiddle"
line 788 column 522 - Warning: <img> lacks "alt" attribute
line 799 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 799 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 799 column 216 - Warning: <img> proprietary attribute value "absmiddle"
line 808 column 25 - Warning: <img> lacks "alt" attribute
line 813 column 267 - Warning: <img> lacks "alt" attribute
line 268 column 1512 - Warning: trimming empty <font>
line 641 column 1512 - Warning: trimming empty <font>
line 793 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 203 column 27 - Warning: <nobr> is not approved by W3C
line 240 column 27 - Warning: <nobr> is not approved by W3C
line 266 column 27 - Warning: <nobr> is not approved by W3C
line 268 column 158 - Warning: <table> proprietary attribute "height"
line 268 column 223 - Warning: <td> proprietary attribute "background"
line 268 column 319 - Warning: <td> proprietary attribute "background"
line 268 column 409 - Warning: <table> proprietary attribute "height"
line 268 column 489 - Warning: <td> proprietary attribute "background"
line 268 column 1444 - Warning: <td> proprietary attribute "background"
line 304 column 27 - Warning: <nobr> is not approved by W3C
line 332 column 27 - Warning: <nobr> is not approved by W3C
line 358 column 27 - Warning: <nobr> is not approved by W3C
line 384 column 27 - Warning: <nobr> is not approved by W3C
line 410 column 27 - Warning: <nobr> is not approved by W3C
line 437 column 27 - Warning: <nobr> is not approved by W3C
line 467 column 27 - Warning: <nobr> is not approved by W3C
line 493 column 27 - Warning: <nobr> is not approved by W3C
line 521 column 27 - Warning: <nobr> is not approved by W3C
line 559 column 27 - Warning: <nobr> is not approved by W3C
line 585 column 27 - Warning: <nobr> is not approved by W3C
line 613 column 27 - Warning: <nobr> is not approved by W3C
line 639 column 27 - Warning: <nobr> is not approved by W3C
line 641 column 158 - Warning: <table> proprietary attribute "height"
line 641 column 223 - Warning: <td> proprietary attribute "background"
line 641 column 319 - Warning: <td> proprietary attribute "background"
line 641 column 409 - Warning: <table> proprietary attribute "height"
line 641 column 489 - Warning: <td> proprietary attribute "background"
line 641 column 1444 - Warning: <td> proprietary attribute "background"
line 698 column 27 - Warning: <nobr> is not approved by W3C
line 724 column 27 - Warning: <nobr> is not approved by W3C
line 726 column 158 - Warning: <table> proprietary attribute "height"
line 726 column 223 - Warning: <td> proprietary attribute "background"
line 726 column 319 - Warning: <td> proprietary attribute "background"
line 726 column 409 - Warning: <table> proprietary attribute "height"
line 726 column 489 - Warning: <td> proprietary attribute "background"
line 726 column 1444 - Warning: <td> proprietary attribute "background"
line 756 column 27 - Warning: <nobr> is not approved by W3C
line 784 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 410 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