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

[Morrigan Aensland-Hill]

SubDrag wrote:

What are you asking for? Visual editor right click a couple more options on animation? Can you be specific on exactly what looking for and what flags to set or unset on each. The crashing I can't reproduce so not sure about that.

For the Animations on the DKR Object Editor, there needs to be a few options added on the Properties/Details like switching between types, setting the speed and transitions.

Here is the list of screen transitions used when making a course intro cutscene before the race starts:

Code:

7F Fade Fullscreen 80 Fade Out From White 81 Barndoor Horizontal 82 Barndoor Vertical 83 Fade Circle 84 Waves (unused) 85 Barndoor Diagonal

In the meantime, I'll do some more testing around with the animations. I'll keep you posted with what else I've discovered and documented.
_________________
My beauty can overcome brains and brawn!

...Also, my husband sells propane and propane accessories.

[StupidMarioBros1Fan]

I don't know the inner works of the Model Editor but the "UnreferencedGun" section for GoldenEye is exclusively the models used for the Ejected Casings feature and the slots only change when that feature has been messed with like in the previously shared example patch where I added a fifth Ejected Casings model.



Actually unreferenced gun files like "GdynamiteZ" or "GexplosivepenZ" aren't viewable unless the 21990 file is edited to use them.



Would it be possible to have the editor recognize that the files exist in the rom and then if there is nothing pointing to them like the other categories, they get added a new fifth category that actually is "UnreferencedGun" while the old one is renamed to "EjectedCasings" or something along those lines? Presumbly requiring the file start with "G" so it doesn't just grab every other kind of file, maybe also check if there are any "C" and "P" files that are unused for additional categories like Perfect Dark has. I'm unsure how the Perfect Dark version handles this but it does add/remove files based on if they're referenced, but I know that aspect is handled differently (and much easier) compared to GoldenEye but might be helpful in this regard?

I should specify that those unused gun files are bad, they're either broken or use outdated formats because the textures have bad IDs, the Model Parts section is always blank and sometimes the Editor crashes when trying to view them. This can be solved with replacing it with a different file or using a Model Template but maybe that could be another way of checking? I don't know if there's anything special found in the rest of the gun files but if there is & that stuff is missing from those files (or maybe they're just a mess in general to the point of the editor identifying that something is wrong?) then the editor could have a popup recommending the file is replaced through the Game Configurations' "Inject File" feature.

This got a bit more complicated that I originally intended to suggest.
To be clear, I was suggesting two things:

1. Renaming the existing "UnreferencedGun" section so it's clear that it's just the models used for the EjectedCasings table.
2. An additional category that includes gun files that are actually aren't referenced, with a failsafe for when the detected file is broken to avoid the Editor crashing. (depending on if normal gun files have special stuff the Editor could reliably look for)

I just wanted to bring it up since I've been looking into Gun stuff recently as well as searching for unused files I could delete and found that there were a handful of gun files that were only found through the Games Configurations' File Managment section.
_________________
Stupid Mario Brothers is a YouTube series, get asked about my username a lot.

[SubDrag]

I think I knew this, but said a while ago if you are doing something so crazy, just export your gun and manually import/fix the 05/image counts etc. Like you know what you're doing. I can think about it, but the crashing/needing a warning seems a bit confusing for the average user looking into it.