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

[Bio-hazardousThingy]

I had just got done making a few changes for a level. I tested it out only to find out the level froze when viewing my objectives through James' Watch.
I tried reopening the editor to fix the problem, only to see a "GoldenEye Setup Editor 2.0.0 has encountered a problem and needs to close." window. Restarting my computer didn't help, and I'm leaning on re-installing the SetUp Editor. Any ideas here?

[acceptable67]

The reason for the game freezing when viewing modified text could be because of a plethera of things, but I will say that the editor is in a buggy condition and will crash a ton throughout the editing process, mostly in the visual editor window. If it's crashing upon editor opening, make sure you're running as administrator and have compatibility mode set if you're a Win7/8 user.
_________________

Rare wrote:

Perfect Dark Forever.

[Bio-hazardousThingy]

I'm on Windows XP. And the Editor does crash upon opening. I will check the compatibility mode just in case.
Edit: Changing the Compatibility Mode doesn't help.

[acceptable67]

make sure to grab the latest beta with the BetaGrabber in the GEEdit directory.
_________________

Rare wrote:

Perfect Dark Forever.

[Bio-hazardousThingy]

Running BetaGrabber doesn't help either, or was I supposed to do something else with it?

[acceptable67]

no, that's fine. make sure ROM you set in the preferences menu is OK.
_________________

Rare wrote:

Perfect Dark Forever.

[Bio-hazardousThingy]

The Preferences Menu? On the Emulator?

[acceptable67]

ge editor, assuming you set one
_________________

Rare wrote:

Perfect Dark Forever.

[SubDrag]

That happens when you don't change the text to a digit in the same level as you're playing. It has to be a global bank or the specific level you are using for all objectives, etc. In both briefing file, and in the objectives.

[Bio-hazardousThingy]

SubDrag wrote:

That happens when you don't change the text to a digit in the same level as you're playing. It has to be a global bank or the specific level you are using for all objectives, etc. In both briefing file, and in the objectives.

Well that solves one mystery, but the GE Editor is still crashing whenever I try to run it. I fiddled with Properties when I right-click GE Setup Editor, and I still didn't solve anything.

[SubDrag]

The run as administrator and XP SP3 compatibility mode should make it run fine, with latest beta.

[MultiplayerX]

Okay here is an idea that might help. When you edit TEXT .... BE SURE you save your file UNCOMPRESSED and for the love of God use QUICK INJECT to insert it or this issue seems to be quite common. Converting ROM seems to cause a SLEW of issues and doesn't check tables quite right. It does a much better job when updating coding per Sub's helping me with previous issues like this.

OH and be sure to install visual studio runtimes to create more stability for the editor, etc. Read the FAQ on goldeneyevault.com
_________________
http://codelegends.proboards.com/

[Bio-hazardousThingy]

MultiplayerX wrote:

Okay here is an idea that might help. When you edit TEXT .... BE SURE you save your file UNCOMPRESSED and for the love of God use QUICK INJECT to insert it or this issue seems to be quite common. Converting ROM seems to cause a SLEW of issues and doesn't check tables quite right. It does a much better job when updating coding per Sub's helping me with previous issues like this. OH and be sure to install visual studio runtimes to create more stability for the editor, etc. Read the FAQ on goldeneyevault.com

Okay, I'll keep that in mind, but I did install the Visual Studio 2010, VS2008 x86, and DirectX 9.0c in order to run it before as stated in the FAQ. I did that days before the crashing started. I'm running Windows XP, so I don't have to worry about that administer mode thing. Is there a way to post pictures of what happens?

[zoinkity]

Could you post the contents of the file "geeditor.ini"?

Actually, try renaming that to something else (like "orfblast.ini" or something) and running it again. Will it start then?

The most likely scenario is something is being parsed badly. Most likely culprit is the ROM, which is very likely if data is arranged in a way it doesn't expect due to, say, a text file assignment problem. Don't know if previous project is parsed or not; you'll have to ask Sub what is and isn't.
_________________
(\_/) Beware
(O.o) ze
(> <) Hoppentruppen!

[acceptable67]

thats what i was thinking, something is wrong internally with rom
_________________

Rare wrote:

Perfect Dark Forever.