Register - Login
Views: 99797091
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
05-03-22 05:49:23 AM
Jul - SM64 Hacking (Archive) - TT64 Version 0.5.9b Released! Bug reports here. New poll - New thread - Thread closed
Pages: 1 2 3 4 5 6 7Next newer thread | Next older thread
Junk
Random nobody
Level: 6


Posts: 2/5
EXP: 816
For next: 91

Since: 09-21-07

From: JAPAN

Since last post: 14.6 years
Last activity: 14.5 years

Posted on 09-21-07 02:33:31 PM Link
I think Rom extender cannot run on Japanese OS...
My rom must be correct US version ROM.
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 94/621
EXP: 1136482
For next: 20637

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 6 days

Posted on 09-21-07 05:17:34 PM; last edit by VL-Tone on 09-21-07 05:20 PM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Originally posted by Junk
I think Rom extender cannot run on Japanese OS...
My rom must be correct US version ROM.


Hi! Welcome to the forum.

It's a shame if the ROM Extender doesn't work on Japanese OSes I would sure like to fix that, because after all, Japanese people made SM64 in the first place

First, if you're on a Mac, make sure the ROM name is less than 32 characters. For some obscure reason one of the command-line utility truncates the name and add a unique ID number if it's more than that , which makes the ROM Extender fail. (Some legacy name-length bug which I usually never encounter on OS X).

If you're not on a Mac and/or this doesn't work, I would need to see the debug log. Click on the little debug arrow icon before opening a ROM. Open the ROM, dismiss the error dialog, then copy the debug log, paste it in a post here so I can look at it.

Edit: Another suggestion, make sure you avoid using Japanese characters in the ROM name.

____________________
Junk
Random nobody
Level: 6


Posts: 3/5
EXP: 816
For next: 91

Since: 09-21-07

From: JAPAN

Since last post: 14.6 years
Last activity: 14.5 years

Posted on 09-22-07 03:57:30 AM Link
Thank you for advice.


Debug mode log

M64 ROM Extender v1.2b Debug Mode
Currently running on Windows
File Open dialog box.
Opening ROM...
ROM opened.
Wrong ROM version. Checksum not matching
Current checksum is: 635A2BFF02232600
Checksum must be: 635A2BFF8B022326 or 5A63FF2B028B2623

It seems wrong rom.
But I checked checksum by binary editer.
The checksum at that time was 635A2BFF8B022326.

Some Japanese installed VPC2007 then they succeeded in Rom Extend.
Therefore, I think my rom is correct,,i@OƒÖOj
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 95/621
EXP: 1136482
For next: 20637

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 6 days

Posted on 09-22-07 07:40:04 AM; last edit by VL-Tone on 09-22-07 07:43 AM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Thanks for that debug log, it's very useful.

I want to know, once the ROM is extended correctly (using VPC for example), can you open it without problems in TT64 running on the Japanese system without VPC?

I believe that you do have the right ROM, but there's a problem in the ROM Extender on Japanese systems. You can see that somehow the 0x8B byte was skipped while reading the checksum...

I've read that Director may have issues with the chartonum function on asian systems. The ROM Extender was using the chartonum function to convert the binary-string data from the "readbytes" command provided by the Binary IO Xtra into hex data. It was a little silly to use this command to read the checksum, but readbytes command is used in all the rest of the ROM Extender to read/write large chunks of data quickly.

Here's a version that reads the checksum as numbers directly instead of converting an ascii binary string into numbers.

http://homepage.mac.com/qubedstudios/M64ROMExtender1.3a.zip

It should fix that checksum check problem... Try it and tell me what happens (with a debug log if you get an error).

But I suspect that there's a much bigger problem behind all this, and that fix won't really help your case.

Still, let's try this first, and if it doesn't work I'll explain what the problem might be and that it may require a partial rewrite of the ROM Extender, and a switch to a different file access plug-in (Xtra). TT64 itself shouldn't be affected by this since it already uses another file access Xtra and deal with data as lists instead of ASCII strings.

____________________
Junk
Random nobody
Level: 6


Posts: 4/5
EXP: 816
For next: 91

Since: 09-21-07

From: JAPAN

Since last post: 14.6 years
Last activity: 14.5 years

Posted on 09-22-07 01:59:44 PM Link
It was impressed by the speed that your tool made...


>I want to know, once the ROM is extended correctly (using VPC for example), can you open it without problems in TT64 running on the Japanese system without VPC?

No.
If Extend on VPC, It can run only on VPC.


I tried Rom extender 1.3a but It failed

It came to be able read rom but
Rom extender says

Index out of range
Script error.continue?

debug log is
M64 ROM Extender v1.2b Debug Mode
Currently running on Windows
File Open dialog box.
Opening ROM...
ROM opened.
ROM Checksum is valid.
This ROM will be Byte-Swapped
swapper stdout:
Shell command: swapper.exe "D:\TOOLS\ToadsTool64Betav055b\M64ROMExtender1.3a\Super Mario 64 (U) [!].v64" -v "D:\TOOLS\ToadsTool64Betav055b\M64ROMExtender1.3a\Super Mario 64 (U) [!].ext.z64"
Extending ROM, Current ROM size= 8388608
ROM extension successful.

Decompressing and Moving MIO0 data

Shell command: mio0dec.exe "D:\TOOLS\ToadsTool64Betav055b\M64ROMExtender1.3a\Super Mario 64 (U) [!].ext.z64" 1083968 "D:\TOOLS\ToadsTool64Betav055b\M64ROMExtender1.3a\MIO0files\00108A40"
mio0dec stdout:
MIO0 file from 00108A40 is decompressed at 00800000 to 0081852D as raw data with a MIO0 header
~~~~~~~~~
Re-pointing Segments


I'm sorry about unskilled English


John2k4
490
Bubble Bobble
Level: 48


Posts: 264/499
EXP: 817953
For next: 5590

Since: 08-05-07

From: Arizona

Since last post: 8.9 years
Last activity: 7.8 years

Posted on 09-22-07 04:16:34 PM; last edit by roger3245 on 09-23-07 04:01 AM Link

OS: Windows XP Pro
RAM: 1GB
HD SPACE: A lot
Version: 0.5.8B

When I open my emulator to check on my hack, I put the emu in full screen mode. When I am done and close the emulator, the TT64 preview space is darkened and all the wireframe boxes around things are solid color boxes. The rendering switches from DX 7, to software.



____________________
I GET NEW LAYOUT!
Roger3245
The Glitch
Member
Speaks his mind
Level: 32


Posts: 121/199
EXP: 205650
For next: 792

Since: 08-23-07

From: Pittsburgh, PA.

Since last post: 14.5 years
Last activity: 14.5 years

Posted on 09-22-07 11:41:25 PM Link
Hey, I found a bug in the re-texture system, the last two thumbnails cannot be selected.

____________________
Why are you reading this?
Join N00b Arena!!
Deleted User
Collection of nobodies
Posted on 09-23-07 01:28:19 AM Link
The "freezing-after-choosing-a-file-when-playing-the-game" is still bugging. I can't play the game with that.

____________________


===================
[Posted by Diglidi-Dude]
bweeno
Random nobody
Level: 8


Posts: 3/9
EXP: 1977
For next: 210

Since: 08-26-07

From: australia

Since last post: 14.6 years
Last activity: 14.4 years

Posted on 09-23-07 03:40:18 AM Link
Originally posted by Me-me
Sience i started using TT64 0.57 everything have went wrong.
If i change something the game crashes. I can just change a
texture and the game crashes.
I've remaked a mod 3 times but the same thing happens.
After the select file section the game crashes.

I am using Windows XP and i extend ROMs with M64 Romextender 1.2



that is exactly what happened to me, exept i downloaded 0.5.8 after that and all my hard time spent on it was gone, it erased the data.

I am using Windows XP and i extend ROMs with M64 Romextender 1.2
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 97/621
EXP: 1136482
For next: 20637

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 6 days

Posted on 09-23-07 06:25:59 AM; last edit by VL-Tone on 09-25-07 06:50 AM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Ok guys, I'm really sorry about this bug... I'm a little ashamed to admit this, but for this bug I didn't even try to reproduce it myself. I assumed that since I made zero changes in the texture saving part of the editor, these were weird issues that only some people were having.

But no, this bug was actually affecting everyone since 0.5.6b. Simply going to the texture editor and back would corrupt the ROM.

This had something to do with a new feature I was toying with but that was writing its changes at the wrong place, and corrupting a command in the ROM.

The new feature will resize Mario's shadow to match any change in its overall size. Since the size data is saved automatically when you quit the texture editor, the corruption would happen just by visiting the texture editor.

I just released version 0.5.9b which will fix this crashing ROM bug. To fix your ROM, open it with TT64 0.5.9b, and just go to the texture editor (then back to the level editor). This will automatically save the size and shadow data, AND fix the corrupted data. You don't need to click save, and you don't even need to edit anything, but you must go to the texture editor once. Further changes won't corrupt the ROM (obviously).

You can download version 0.5.9b at the usual address: http://homepage.mac.com/qubedstudios/ToadsTool64.htm





Version 0.5.9b attempts to fix an issue with checksum verification that would happen on Japanese and other asian Windows systems. Opening an already correctly extended ROM should now work on Japanese systems.

Note that this DOESN'T fix the problem with the ROM Extender on Japanese systems. This problem will require a partial rewrite of the app.

The problem with the ROM Extender is from the Binary IO Xtra. This Xtra enables very fast reading and writing abilities to Director MX. It's fast because it loads the binary data in ASCII string variables, instead of converting them to lists variables (arrays). The problem is that on Japanese systems, Director seems to have a different internal representation of string variables, which corrupts the binary data read into those strings. To fix it I'll need to use another Xtra, and read/write large amount of data with some conversion to list variables, and that will make it much slower. I'll probably have to split the program in two version, so that the fast, but less compatible version is still available.

This leads me to this question:

Is anyone here experienced enough in C or C++ command-line programming to help me write an all-in-one portable command-line version of the ROM Extender?

I could provide the source code for all the hard parts (MIO0 decompression, checksum calculation). Essentially, the rest is relatively simple, it's a matter of decompressing the MIO0 data, adding 16MB of padding to a copy of the ROM, then copy the decompressed data at some specific addresses, modify all the related pointers, then recalculate the checksum.

Having such a program would be very useful for TT64. First, it would fix a few issues some people are having with the program on some systems. It would work on Japanese OSes, amongst other things.

It would also provide better Linux support for TT64. While TT64 doesn't run natively on Linux, it does run under WINE. But the ROM Extender doesn't because on its reliance on Windows-specific command line utils. A C or C++ version of the ROM extender could be easily ported to Linux, Windows and OS X.

____________________
Junk
Random nobody
Level: 6


Posts: 5/5
EXP: 816
For next: 91

Since: 09-21-07

From: JAPAN

Since last post: 14.6 years
Last activity: 14.5 years

Posted on 09-23-07 09:42:04 AM Link
Thank you for update.
We still can't extend rom, however we can run on Japanese OS if I'm having Extended rom.
Me-me
340
Level: 41


Posts: 8/341
EXP: 462078
For next: 18067

Since: 08-05-07


Since last post: 9.7 years
Last activity: 8.1 years

Posted on 09-23-07 11:30:18 AM Link
Thanks for the new verision!
It works a lot better.
The Glitch
Member
Speaks his mind
Level: 32


Posts: 124/199
EXP: 205650
For next: 792

Since: 08-23-07

From: Pittsburgh, PA.

Since last post: 14.5 years
Last activity: 14.5 years

Posted on 09-24-07 04:50:16 AM; last edit by The Glitch on 09-24-07 04:51 AM Link
Just thought I'd report these two bugs, The last two textures in the texture editor can't be selected for some reason, and when I maximize TT64, and go to texture editor, the window resizes itself, but returns to normal when I go back.
I'm also having trouble getting modded textures to save, even though the thumbnail updates.

____________________
Why are you reading this?
Join N00b Arena!!
nevum
Member
m'kay?
Level: 17


Posts: 8/43
EXP: 20652
For next: 4091

Since: 08-25-07


Since last post: 13.6 years
Last activity: 12.8 years

Posted on 09-24-07 11:56:40 PM Link
Hey guys sorry about not posting anything at all for the past million years and how late this comment is. (The reason for this is I've been really busy studying C++) Anyhow, I wanted to say that I had the same problem that Me-Me did. It crashed afer I selected a file.

____________________
The post above has been typed by: THE BEST FREAKIN' COMPUTER GURU IN THE WORLD!!! WOOT!!!
VL-Tone
Member
Super Mario 64 forum moderator
Level: 53


Posts: 100/621
EXP: 1136482
For next: 20637

Since: 07-27-07

From: Montreal, Canada

Since last post: 4.7 years
Last activity: 6 days

Posted on 09-25-07 06:49:22 AM; last edit by VL-Tone on 09-25-07 06:49 AM Link
Time: Now - Date: Today - Weather: What can be seen outside. - Mood: How it feels. Answer to the universe: 42
Originally posted by The Glitch
Just thought I'd report these two bugs, The last two textures in the texture editor can't be selected for some reason, and when I maximize TT64, and go to texture editor, the window resizes itself, but returns to normal when I go back.
I'm also having trouble getting modded textures to save, even though the thumbnail updates.


Hmm yeah, some few versions ago two textures were added to the list, and I forgot to change that hard-coded value that sets the maximum texture number you can select. It'll be easy to fix.

When you say "returns to normal when I go back" do you mean that it goes back to the same size it was before going to the texture editor? (in this case, maximized). Because if so this is how it should behave. But if your window was maximized before you did go to the texture editor, then when you go back it gets smaller than maximized, then it's a bug.

Originally posted by nevum
Hey guys sorry about not posting anything at all for the past million years and how late this comment is. (The reason for this is I've been really busy studying C++) Anyhow, I wanted to say that I had the same problem that Me-Me did. It crashed afer I selected a file.


Well it's late because Me-me's problem was fixed with version 0.5.9b, which was released before your post, right on this page.

Did you actually read my last post? You know, the part in bold letters?


____________________
NintendoMasters
Member
Level: 22


Posts: 52/84
EXP: 56488
For next: 1862

Since: 08-06-07


Since last post: 14.3 years
Last activity: 13.2 years

Posted on 09-26-07 06:43:19 PM Link
I'm not sure if this counts as a bug, but i edited a texture and all the star select screen backgrounds have gone black making it impossible to read my act names.
I've changed the texture back but they're still black. Is there any way to fix this?

____________________
Click to see my site. And Here for my mini forum.
wowfunhappy
Member
Level: 16


Posts: 10/40
EXP: 18502
For next: 1754

Since: 09-10-07


Since last post: 13.0 years
Last activity: 13.0 years

Posted on 09-26-07 08:18:48 PM Link
VL-tone, have you any idea as to what is causing the bug I reported earlier?

Originally posted by wowfunhappy
This is bug that was in the old version and hasn't been fixed, looking back it seems this bug hasn't been mentioned to you.

When you change the music of the castle grounds, it the music doesn't play. Instead, the original Castle ground "Music" plays.

Also, if you change the music for the castle grounds and then start a new game, the first two seconds of the music you selected will play during the opening sequence, but after those two seconds have passed the normal opening sound track will play, and the castle grounds plays the original "Music"

I'm using Windows XP.



I did some more research into it... the bug ONLY happens when you start a new game. Once you walk inside the castle and walk back out into the castle grounds, the music that was applied using TT64 plays.

Please... it's a real bug... I'm not trying to trick you or give you extra work or anything.

Sorry if I'm being impatient, but I'm REALLY getting the feeling that I'm being totally ignored.

********

On an unrelated note, about the problem with the rom extender on Japanese systems, What would happen if an emulator was used? Might that fix the problem. Keep in mind I don't really know what I'm talking about, I'm just using my common sense to try to figure out what may help.

rstewart215804
User
Crazed Mario 64 Hacker!!!
Level: 11


Posts: 4/18
EXP: 5583
For next: 402

Since: 09-13-07


Since last post: 13.2 years
Last activity: 11.7 years

Posted on 09-27-07 06:04:32 PM; last edit by rstewart215804 on 09-28-07 05:51 PM Link
wowfunhappy the bug you are getting is not a problem with TT64. When you start a new game an assembly language script is run. It changes the music for the intro, and when the intro animation is over the script turns the music off. There is actually no music playing outside the castle normally. The bird and the waterfall sounds are generated by the objects TT64 calls “camera controllers?” or something like that. So what I am basically saying is this…

IT IS HARD CODED INTO THE
GAME!!!


But don’t dispare I am working with the assembly language of SM64 and it is only a matter of time until I find the function that deals with the background music. I already found the function that plays sounds. I was able to alter what Mario said at the “Press Start Screen”.


____________________
Just you wait until next time. Until then, keep that Control Stick smokin’! Buwaa ha ha!
Plareon
User
Level: 13


Posts: 1/24
EXP: 8584
For next: 1683

Since: 09-28-07

From: North America

Since last post: 13.8 years
Last activity: 13.8 years

Posted on 09-28-07 08:58:04 PM Link
http://home.comcast.net/~jstsnyder/Home.htmlHey, It's me. I wanted to see how this works, so I just made this test post.
Sorry it took me so long :-)
I'm also sorry for spam.

____________________
Plareon
John2k4
490
Bubble Bobble
Level: 48


Posts: 277/499
EXP: 817953
For next: 5590

Since: 08-05-07

From: Arizona

Since last post: 8.9 years
Last activity: 7.8 years

Posted on 09-28-07 10:18:25 PM Link
Just FYI next time, you can see a sample post by clicking on your username.

____________________
Roger3245

Pages: 1 2 3 4 5 6 7Next newer thread | Next older thread
Jul - SM64 Hacking (Archive) - TT64 Version 0.5.9b Released! Bug reports here. New poll - New thread - Thread closed


Rusted Logic

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

36 database queries, 7 query cache hits.
Query execution time: 0.083359 seconds
Script execution time: 0.043608 seconds
Total render time: 0.126967 seconds