GoldenEye 007 Nintendo 64 Community, GoldenEye X, Nintendo 64 Games Discussion

[Wreck]

Whatever you've done with this version of the patch, definitely seems to work. I've been able to run around firing wildly in four different mp maps without a single lock up. Also, the textures that used to feature the glass impact types are back to normal. I'll try it out on my other ROM quick, but this seems to have done the trick.

Scorpion: No, this has nothing to do with your Editor problems.
_________________

YOUTUBE | TWITTER/X | FACEBOOK | VAULT | MOD DB | RHDN

[DELETED]

DELETED

[zoinkity]

Uhm...

Whatever you did when you put in the three lines from yesterday, do the same with the fourth one.

---
Scorpion:
Is the 21990 broken? It is altogether possible that at one point or another an editted 21990 may be larger than the expected size for the file. In these cases, the editor will cut off bytes, then try to decompress an incomplete file. This, needless to say, is a bad thing.

Best guess would be to check that the rom selected in the options is a valid, nice, working rom. By default, regardless any other file you may have openned, it will try to open the one you set as default in the preferences when you start the 21990 editor.

Do you have a hex editor? If so, try this:
Open the rom, then jump to the address 0x331E0. You should see many 00's on screen. If you do, then the 21990 is a proper length. If not, then this is the culprit.
Otherwise, copy the thing out manually. Copy the binary from 21990 to 331E0, save it as a .1172 file, then use the editor's tool to decompress a file. If it decompresses fine, then send it to me. If not, then it is screwed up in some random way.

I have no bloody clue why the editor hates you. Short of a critical error in whatever 21990 happens to be in the rom you happen to have, I can't say what's wrong. As for deleting half the files, that's new. Really new. I don't even think the editor *can* delete anything.
You aren't running off a ram drive or something crazy that would cause access violations and perform erratically on error conditions?

Seriously, I've run the stupid thing off of a CDRW, flash drives, in a ramdisk on both 95 and 98 after masking the dlls and being really careful not to bring up anything visual to get around that whole 'direct3D not supported on graphics card' issue. We're talking systems that should, by all rights, not be able to use the editor due to either ram limitations, hardware limitations, or just shear system limitations. I have no blasted clue why anyone shouldn't be able to find some way to use it.
_________________
(\_/) Beware
(O.o) ze
(> <) Hoppentruppen!