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

[Kerr Avon]

OK. I've not yet started to delete any C++ stuff (still working through my e-mails), so in the

C:\Test\GE430new

folder I have run

BetaGrabberTool.exe

and it starts. I clicked on the update box, and it has done so.

But then starting runwaysetupeditor.exe just does the usual v4.3 problem; nothing changes aside from runwaysetupeditor.exe appearing in the task manager.

So I restarted BetaGrabberTool.exe, and clicked on 'Copy beta to stable release', which didn't seem to do anything (no message or other reaction), so I closed it and started runwaysetupeditor.exe, but again, runwaysetupeditor.exe just appears in the task manager.

[Kerr Avon]

Right, I've uninstalled both the x64 and x86 versions of the 2015 - 2019 distributables.




1. Running PerfectGold.exe from v4.3 of the editor now gives the error message:


"The program can't start because mfc140.dll is missing from your computer. Try reinstalling the program to fix this problem."


Running PerfectGold.exe from v4.2 also gives the same error:

"The program can't start because mfc140.dll is missing from your computer. Try reinstalling the program to fix this problem."








2. You say to install "the latest VS2019 64-bit redistributable". I googled it, and found:


https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads

and downloaded and installed:

x64: vc_redist.x64.exe


and now we're back to whenever I start PerfectGold.exe it does nothing except appear in the task manager.

So, from the same page, I downloaded and installed x86: vc_redist.x86.exe, but the editor is still not starting (other than appearing in
task manager).

Is the above file what you meant, or is there a differerent VS2019 64-bit redistributable that I should be using, please?


Anyway, I remembered that I installed more C++ redistributables last time, two from the looks of the 'sort by date' option in the Programs and Features part of Windows 7's control panel. I had installed Microsoft Visual C++ 2013 Redistributable 12.0.30501, both the x86 and x64 versions, a few days back, so I have uninstalled them, but still the v4.3 version of the editor doesn't start, it just appears in the task manager everytime I start the PerfectGold.exe file.



By the way, when I try to start v4.2 of the editor, it gave the error message

"The program can't start because ChartPro1730vc142x64.dll is missing from your computer. Try reinstalling the program to fix this problem. "

so I copied ChartPro1730vc142x64.dll (from the web page https://github.com/carnivoroussociety/GoldEditor/releases) to the v42 folder, ran PerfectGold.exe, and I received an error message saying that SkinFramework1640vc142x64.dll wasn't found, so I copied SkinFramework1640vc142x64.dll to the v42 folder, ran PerfectGold.exe, and now v42, like v43, doesn't respond to starting, except for becoming listed in the task manager.

Any ideas what I can do next, please?

[CrashOveride]

For 4.3, you should only need the redistributables from here: https://github.com/carnivoroussociety/GoldEditor in the readme. Do you have all of them?

Also, you should be using runwaysetupeditor.exe, not perfectgold (unless you copied the beta)
_________________
Playing old, low poly games since 2003

[Kerr Avon]

CrashOveride wrote:

For 4.3, you should only need the redistributables from here: https://github.com/carnivoroussociety/GoldEditor in the readme. Do you have all of them?

Yes. I'll uninstall the C++ distributables and install only what's on that page, and post the results, thanks.

Quote:

Also, you should be using runwaysetupeditor.exe, not perfectgold (unless you copied the beta)

Oh right, I didn't know that. I've always just ran PerfectGold.exe, either to try the editor (and after thirty seconds being put off by how complex the editor is, because I'm like an ant trying to understand quantum theory ) , or to use the program's ability to apply patches for any new Goldeneye/Perfect Dark/other .xdelta hacks.

But no, running runwaysetupeditor.exe in v4.3 just does the same as running PerfectGold.exe; it seems to do nothing except add PerfectGold.exe to the Task Manager's Processes window (not the Task Manager's Application window).

[SubDrag]

Try running as admin? Not sure where installed but it does try and clean up Temp and Backup folders on start by date.

But yeah pretty mystefied if even the upgrade from 4.2 fails. Got to be dll related if everyone else can do a clean install fine?

[Wreck]

What are the two Alt Tank options for? Kind of a mystery there...

[SubDrag]

Wreck wrote:

What are the two Alt Tank options for? Kind of a mystery there...

They update to support multiple drivable vehicle situations. Alt Tank is GF64's, Alt Tank 2 is TSWLM's.

Stores current drivable vehicle data to here, and the ASM right after it, is what drives the data based on object id.
8005C52C current tank object
8005C52E ignition sound
8005C530 movement sound
8005C532 crush sound
8005C534 tank weapon
8005C538 top speed
8005C53C acceleration


Alt Tank 2
3C0F8006 3B7C0
A5EEC52C 3B7C4
24010120 3B7C8 Car Object Id
142E0011 3B7CC
24010042 3B7D0 Ignition Sound
A5E1C52E 3B7D4
2401003E 3B7D8 Movement Sound
A5E1C530 3B7DC
240100D5 3B7E0 Crush Sound
A5E1C532 3B7E4
24010020 3B7E8
ADE1C534 3B7EC
3C0141A8 3B7F0 Top Speed
ADE1C538 3B7F4
3C013F40 3B7F8 Acceleration
ADE1C53C 3B7FC
8DE4C534 3B800
0FC23122 3B804
AFA500EC 3B808
0BC20ABC 3B80C
00000000 3B810
2401011D 3B814 Car 2Object Id
142E000E 3B818
24010043 3B81C Ignition Sound
A5E1C52E 3B820
2401003F 3B824 Movement Sound
A5E1C530 3B828
240100D6 3B82C Crush Sound
A5E1C532 3B830
2401FFFF 3B834
ADE1C534 3B838
3C0141A0 3B83C Top Speed
ADE1C538 3B840
3C013F40 3B844 Acceleration
ADE1C53C 3B848
0BC20AC0 3B84C
00000000 3B850 [All other object ids]
24010044 3B854 Ignition Sound
A5E1C52E 3B858
24010040 3B85C Movement Sound
A5E1C530 3B860
240100D7 3B864 Crush Sound
A5E1C532 3B868
2401FFFF 3B86C
ADE1C534 3B870
3C014120 3B874 Top Speed
ADE1C538 3B878
3C013F40 3B87C Acceleration
ADE1C53C 3B880
0BC20AC0 3B884
00000000 3B888

Alt Tank 2

//LW $t5, 0x6480($t5)
//BEQL $t5, $zero, 0x7F082C24 #
//LW $t5, 0x0000($s0)
//J 8005C550
//LH T6, 4(A1)
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082AD8 & 0x00FFFFFF) + 0x34B30), 0x8DAD6480);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082ADC & 0x00FFFFFF) + 0x34B30), 0x51A00051);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082AE0 & 0x00FFFFFF) + 0x34B30), 0x8E0D0000);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082AE4 & 0x00FFFFFF) + 0x34B30), 0xAFA500EC);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082AE8 & 0x00FFFFFF) + 0x34B30), 0x08017154);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082AEC & 0x00FFFFFF) + 0x34B30), 0x84AE0004);

/*
8005C550:
LUI T7, 8006
SH T6, C52C(T7)

car:
ADDIU $at, $zero, 0120
BNE $t6, $at, car2

ADDIU $at, $zero, 0042
SH $at, C52E(T7)

ADDIU $at, $zero, 003E
SH $at, C530(T7)

ADDIU $at, $zero, 00D5
SH $at, C532(T7)

ADDIU $at, $zero, 0020
SW $at, C534(T7)

LUI $at, 41A8
SW $at, C538(T7)

LUI $at, 3F40
SW $at, C53C(T7)

LW A0, C534(T7)

JAL 0x7F08C488
SW $a1, 0x00EC($sp)

J 7F082AF0
NOP

car2:
ADDIU $at, $zero, 011D
BNE $t6, $at, car3

; Actually set to FFF and FFFF to match tank, for engine and end
ADDIU $at, $zero, 0043
SH $at, C52E(T7)

ADDIU $at, $zero, 003F
SH $at, C530(T7)

ADDIU $at, $zero, 00D6
SH $at, C532(T7)

ADDIU $at, $zero, FFFF
SW $at, C534(T7)

LUI $at, 41A0
SW $at, C538(T7)

LUI $at, 3F40
SW $at, C53C(T7)

J 7F082B00
NOP

car3:
; Actually set to FFF and FFFF to match tank, for engine and end
ADDIU $at, $zero, 0044
SH $at, C52E(T7)

ADDIU $at, $zero, 0040
SH $at, C530(T7)

ADDIU $at, $zero, 00D7
SH $at, C532(T7)

ADDIU $at, $zero, FFFF
SW $at, C534(T7)

LUI $at, 4120
SW $at, C538(T7)

LUI $at, 3F40
SW $at, C53C(T7)

J 7F082B00
NOP
*/

parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7C0, 0x3C0F8006);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7C4, 0xA5EEC52C);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7C8, 0x24010120);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7CC, 0x142E0011);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7D0, 0x24010042);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7D4, 0xA5E1C52E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7D8, 0x2401003E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7DC, 0xA5E1C530);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7E0, 0x240100D5);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7E4, 0xA5E1C532);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7E8, 0x24010020);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7EC, 0xADE1C534);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7F0, 0x3C0141A8);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7F4, 0xADE1C538);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7F8, 0x3C013F40);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B7FC, 0xADE1C53C);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B800, 0x8DE4C534);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B804, 0x0FC23122);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B808, 0xAFA500EC);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B80C, 0x0BC20ABC);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B810, 0x00000000);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B814, 0x2401011D);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B818, 0x142E000E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B81C, 0x24010043);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B820, 0xA5E1C52E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B824, 0x2401003F);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B828, 0xA5E1C530);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B82C, 0x240100D6);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B830, 0xA5E1C532);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B834, 0x2401FFFF);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B838, 0xADE1C534);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B83C, 0x3C0141A0);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B840, 0xADE1C538);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B844, 0x3C013F40);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B848, 0xADE1C53C);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B84C, 0x0BC20AC0);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B850, 0x00000000);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B854, 0x24010044);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B858, 0xA5E1C52E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B85C, 0x24010040);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B860, 0xA5E1C530);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B864, 0x240100D7);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B868, 0xA5E1C532);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B86C, 0x2401FFFF);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B870, 0xADE1C534);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B874, 0x3C014120);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B878, 0xADE1C538);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B87C, 0x3C013F40);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B880, 0xADE1C53C);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B884, 0x0BC20AC0);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.setupInFileData, 0x0003B888, 0x00000000);



//LHU $a1, C52E(A0)
//LW $a0, 3720(A0)
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F085668 & 0x00FFFFFF) + 0x34B30), 0x9485C52E);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F08566C & 0x00FFFFFF) + 0x34B30), 0x8C843720);

//LHU $a1, C530(A0)
//LW $a0, 3720(A0)
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F08575C & 0x00FFFFFF) + 0x34B30), 0x9485C530);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F085760 & 0x00FFFFFF) + 0x34B30), 0x8C843720);

//LHU $a1, C532(A0)
//LW $a0, 3720(A0)
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F086824 & 0x00FFFFFF) + 0x34B30), 0x9485C532);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F086828 & 0x00FFFFFF) + 0x34B30), 0x8C843720);

parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082F40 & 0x00FFFFFF) + 0x34B30), 0x1000000A);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082F58 & 0x00FFFFFF) + 0x34B30), 0x10000004);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082F60 & 0x00FFFFFF) + 0x34B30), 0x10000002);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082F6C & 0x00FFFFFF) + 0x34B30), 0x3C0F8006);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082FA0 & 0x00FFFFFF) + 0x34B30), 0x8DE1C538);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082FAC & 0x00FFFFFF) + 0x34B30), 0x8DE1C538);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F082FFC & 0x00FFFFFF) + 0x34B30), 0x3C0F8006);
parentFrame->mainSetup.WriteLongToBuffer(parentFrame->mainSetup.GEROM, ((0x7F083018 & 0x00FFFFFF) + 0x34B30), 0x8DE1C53C);

[SubDrag]

These four are required, just to be clear...DirectX installed too?

https://aka.ms/vs/16/release/vc_redist.x64.exe
https://aka.ms/vs/16/release/vc_redist.x86.exe
https://www.microsoft.com/en-us/download/details.aspx?id=40784
https://www.microsoft.com/en-us/download/details.aspx?id=8109

[Wreck]

I've run into a weird issue with two different items being set within a safe as 2C types. One is a 08 Weapon, while the other is a 03 Standard. Everything is set right within the Editor, but I am able to collect the standard object when using Bond Phase (walk through objects). This does not happen with Rare's safes, including Bunker 2, which has three items. Looking at the file inside a Hex Editor, it does appear like something might be wrong with the offsetting within the file for the 03 standard object 2C entry, with what must be the safe body reference. Updating it manually did correct the issue.

[Kerr Avon]

SubDrag wrote:

Try running as admin? Not sure where installed but it does try and clean up Temp and Backup folders on start by date. But yeah pretty mystefied if even the upgrade from 4.2 fails. Got to be dll related if everyone else can do a clean install fine?

Yes, I did try running the editor in Administrator mode, and with and without the various compatibility settings, but with no success.





Are there any C++ or whatever things installed here:



that I should remove?

CrashOveride wrote:

For 4.3, you should only need the redistributables from here: https://github.com/carnivoroussociety/GoldEditor in the readme. Do you have all of them? Also, you should be using runwaysetupeditor.exe, not perfectgold (unless you copied the beta)

OK. I've just uninstalled the 2015 - 2019 C++ distributables, and the 2013, and I'm going to start all over again, using files only downloaded from:

https://github.com/carnivoroussociety/GoldEditor


as you, say, and I will try to run runwaysetupeditor.exe and PerfectGold.exe after every step, to see what changes occur.



1. I create a new folder called C:\GEE43NEW and set it up as a an exclusion in my virus killer (Avast! Anti-virus). I know the virus killer isn't the problem, as I already discounted that, but I want to be able to rule out anything that's perhaps relevant.

I extract the contents of gesetupeditor4.3.0.7z to

C:\GEE43NEW

When I run runwaysetupeditor.exe or PerfectGold.exe I get the error message

"The program can't start because mfc140.dll is missing from your computer. Try reinstalling the program to fix this problem."

This is expected, of course, since I've not yet installed the C++ programs.




2. I install the Microsoft Visual C++ 2013 Redistributable (x64 version), and when I run runwaysetupeditor.exe or PerfectGold.exe I get the error message

"The program can't start because mfc140.dll is missing from your computer. Try reinstalling the program to fix this problem."

So no change, then.




3. I install the Microsoft Visual C++ 2019 Redistributable (x64 version), and this seems to be where the problem begins. I downloaded that file from the address CrashOveride gave (https://github.com/carnivoroussociety/GoldEditor), but now (with it installed) when I run runwaysetupeditor.exe then the program doesn't appear to start, except that it appears in Task Manager, and if I then try to start it again then I get a second runwaysetupeditor.exe in the task manager. And likewise, if I try to start PerfectGold.exe then it does nothing but appear in the task manager, and I get multiple instances in the task manager, one for every time I try to start the program.




4. I install the Microsoft Visual C++ 2019 Redistributable (x86 version), to see if that helps.

No, as expected, it's not changed anything. When I run runwaysetupeditor.exe then the program doesn't appear to start, except that it appears in Task Manager, and if I then try to start it again then I get a second runwaysetupeditor.exe in the task manager. And likewise, if I try to start PerfectGold.exe then it does nothing but appear in the task manager, and I get multiple instances in the task manager, one for every time I try to start the program.






5. I'll try to uninstall the x64 version of Microsoft Visual C++ 2019 Redistributable, and see what happens when only the x86 version is present.

It turns out that when the x64 version of Microsoft Visual C++ 2019 Redistributable (from that web page) isn't installed, but the x86 version is, then I get the same error message as before I installed the x64 version of the redestributable:


"The program can't start because mfc140.dll is missing from your computer. Try reinstalling the program to fix this problem."


So the problem is definitely connected to the x64 version of the Microsoft Visual C++ 2019 Redistributable.

What should I try next, please?

[SubDrag]

Did you install directx? I did not see that in your list.

[SubDrag]

Wreck wrote:

I've run into a weird issue with two different items being set within a safe as 2C types. One is a 08 Weapon, while the other is a 03 Standard. Everything is set right within the Editor, but I am able to collect the standard object when using Bond Phase (walk through objects). This does not happen with Rare's safes, including Bunker 2, which has three items. Looking at the file inside a Hex Editor, it does appear like something might be wrong with the offsetting within the file for the 03 standard object 2C entry, with what must be the safe body reference. Updating it manually did correct the issue.

I can't recreate. I inserted a safe special object in visual editor. As 08 object, can pick up when open, walk through doors cannot. Changed object to a 03 object, and also cannot pick up when walk through doors gameshark on, and could pick up when open (had same flags on 08 object and 03 object). Is there a precise way to recreate this starting with a particular new level or setup? I need more information on how to recreate, it must work some of the time, but possibly a particular nuance of a given setup can be off.

[Kerr Avon]

SubDrag wrote:

Did you install directx? I did not see that in your list.

No, but everything else (PC games, emulators, etc) works fine on the PC, including v4.2 of the editor, so I didn't think I would need to. I will install it now.

[Wreck]

I only know right now of this mission being affected...

http://n64vault.com/ge-levels:storage-wearhouse

There is a 08 PP7, and a 03 keycard (as ID card) both setup inside the safe, each using 2C types. But one can be picked up before the safe door is opened. Might even be if you press up against the one side, if you destroy the table and chair next to it. I think the offset to the safe body entry is incorrect, if you look at the actual file. Not sure why Editor appears to show it all linked up correctly, but seeing it inside a Hex Editor shows at least one thing being wrong.

[SubDrag]

Wreck wrote:

I only know right now of this mission being affected... http://n64vault.com/ge-levels:storage-wearhouse There is a 08 PP7, and a 03 keycard (as ID card) both setup inside the safe, each using 2C types. But one can be picked up before the safe door is opened. Might even be if you press up against the one side, if you destroy the table and chair next to it. I think the offset to the safe body entry is incorrect, if you look at the actual file. Not sure why Editor appears to show it all linked up correctly, but seeing it inside a Hex Editor shows at least one thing being wrong.

This is how the editor parses the objects...can you tell me what is off? The counts seemed ok according to this, so there must be something off in this list It goes way way back to hard to tell.

https://pastebin.com/dVen790V

Can you tell me what's off in this list? It should match order of file.