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

[Carnivorous]

Glide has not been updated since 2012. The newer plugin is gliden64 which is still in development.

For transparent menu to work you need to enable read every frame [under advance emulation options]. This is turned off by default because of the performance impact.

[Stronglime]

Carnivorous wrote:

Glide has not been updated since 2012. The newer plugin is gliden64 which is still in development. For transparent menu to work you need to enable read every frame [under advance emulation options]. This is turned off by default because of the performance impact.

The settings for Perfect Dark are overriden in the Glide64.INI, you would need to change the fb_read_always value to 1. Another way to improve performance is to install a Glide wrapper (I really like nGlide http://www.zeus-software.com/downloads/nglide) and removing the glide 3x.dll file from the emulator folder. Please notice that this way the resolution must be set by the nGlide configuration utility. To remove the black bars when using Glide also add these settings in addition to fb_read_always

adjust_aspect = 1
aspect=2
correct_viewport = 0

It will stretch the aspect ratio, but I prefeer it that way.

Still, for me the framerate is horrible regardless, so I'll stick to the Directx 8 plugin.

[Rekrul]

Just tried the latest bundle and it's still working fine for me.

Stronglime wrote:

Another way to improve performance is to install a Glide wrapper (I really like nGlide http://www.zeus-software.com/downloads/nglide) and removing the glide 3x.dll file from the emulator folder.

I just tried this. I've had good luck using nGlide for Glide2x programs, but I had too many problems trying to use Glide3x with this.

I get marginally better performance, but, the keyboard controls don't work properly. Pressing up only moves me forward a couple steps, then stops. After doing this a couple times, up stops working completely until I press another direction, then it will work a couple more times. If I switch back to windowed mode, not only does it not render the game graphics, but the emulator interface is all screwed up and when I try to switch back to fullscreen, it crashes and I have to use the task manager to kill it off.

[Rekrul]

Something else that players might be interested in;

http://2xdsoft.de.tl/OverlayXhair.htm

A little program that puts a customizable crosshair in the center of the screen. If you set the fullscreen resolution the same as your desktop, the crosshair will stay in the center of the screen while you play the game.

You still need aiming mode for zooming or to lean, but having a crosshair in the center of the screen all the time eliminates the need to use aiming mode for precise shots with the PP7 and other weapons. This is useful because aiming mode disables movement.

I suppose that could be considered cheating, since you normally have to stand still to aim, but for me, it makes the game even more like a modern shooter.

[Carnivorous]

graslu wrote:

For example in GE, it won't render the watch green tint properly over the guns, and in PD the laser for the Falcon 2 is broken.

The laser needs mipmapping turned on.

==

GE:X 5e has been added to ini files.

[Rekrul]

I've been trying each new bundle as I see them, and so far they've all worked fine. Nice work!

One minor oddity I noticed was that when binding most of the keys (mostly the ones that normally generate printable characters), it makes the Windows default beep sound when you press the key. In fact it makes this sound any time you press most of the keys while the Mouse Injector plugin configuration is open. Just go to the Plugins menu, select Input Settings and then press any of the letter keys. Try binding a letter to one of the functions. It doesn't really affect anything, it's just that Windows normally makes that sound when you can't do something, giving the impression that something is wrong.

Also, not a bug, just something I noticed; The ReadMe file uses the word "binded", but the correct word should be "bound".

[Carnivorous]

I don't know how to stop the windows exclamation sound effect. If I figure it out I'll fix it. And thank you for the typo note, English isn't my native tongue.

[Thrix]

Ok so just want to say that it's super awesome what you've accomplished here. I do have an issue that I haven't seen anyone else report on and it's quite worrisome. I tried downloading the latest version from this thread a few weeks ago and immediately got infected by a trojan named Rundas. I almost thought this was a joke at first since it shared its name with the Metroid villain but I googled it and sure enough, it's a really nasty piece of malware. I ended up having to nuke my PC to get rid of it.

Now I'm not going to act like OP was secretly spreading viruses around because I really don't believe this is the case, not to mention that nobody else seems to have had this problem. But here's the thing: I really want to get this and play with it, but I'm honestly too scared to do it again. Does anyone know how this could've happened? I just don't know anymore if the download is safe or not. The rundas trojan is apparently pretty advanced and can dodge up to date scanners so is it possible that OP is unknowingly infected? I've also considered it just being a false alarm (as this tends to happen) but it listed very specifically as that particular trojan.

Now, again, this is not some whining or complaint. I really just want to get to the bottom of this because in the end; I want to play this like everyone else.

[Carnivorous]

I reformatted 2 months ago so I can assure you that my system is clean. The only way that happened is if someone changed the file stored on catbox.moe. I don't know if catbox.moe are tampering with zips uploaded, but if what you say is true then I will find another host to store the bundle. All I can do is provide hashes for each update to ensure they have not been tampered with. I know there is one user recompiling my plugin with unknown code changes, packaging it with roms and putting it behind a paywall, but that's to be expected whenever you release anything on the internet.

BTW, you can compile the code yourself if you do not trust the binaries. All you need is MSVC6 and TDM-GCC 4.9.2-tdm-3. The compile instructions for the mouse injector are listed in the header of main.c and maindll.c.

==

I have now removed catbox.moe and will only be using archive.org. I have confirmed the hashes are the same with my local copy so it is safe to download. You can check for yourself using Quick Hash. Thank you for the report.

[Thrix]

Hahaha I nearly shat myself trying this again. But I can happily confirm that I had no issues this time around. Thank you so much for responding so quick and being so helpful. Also thank you for taking time out of your life to make a mod like this because it's really awesome.

[Carnivorous]

Not a problem If you have any issues please don't hesitate to ask here.

[Fillerthefreak]

Has the emulator been updated to work with the new version of GE:X, yet? Since the Q-Cam/Camspy does not work right with GE:X on the build I'm using, yet it works fine in PD.
_________________
This is a signature, why did you read this?

[Carnivorous]

Glide64 GlideN64 and SoftGraphic are the only plugins that work with Q-Cam. Jabo is hardcoded to only support the effect with Perfect Dark [romhacks have different CRC so it doesn't support it].

[Rekrul]

Is the Mouse Injector plugin supposed to be compatible with other emulators? I tried it with a recent build of Project64 and it said it couldn't detect the emulator.

Also, not really a bug, but I notice that when you press F3 to pause the emulation, it unpauses if you switch between windowed/fullscreen mode. It would be better if the emulator stayed paused until you press F3 again to resume.

[Carnivorous]

Rekrul wrote:

Is the Mouse Injector plugin supposed to be compatible with other emulators? I tried it with a recent build of Project64 and it said it couldn't detect the emulator.

Not it isn't compatible with other emulators. You manually have to add support to every one. PJ64 is difficult because it stores ROM memory in random locations. There is 1.6 support because I did find a reliable pointer. But even with 1.6 it has issues with the plugin. For some reason it blocks input unless you're fullscreen. If you did want me to support a newer version of PJ64, which version were you thinking of?

Rekrul wrote:

Also, not really a bug, but I notice that when you press F3 to pause the emulation, it unpauses if you switch between windowed/fullscreen mode. It would be better if the emulator stayed paused until you press F3 again to resume.

That's actually intentional by 1964. 1964 itself doesn't work very well with pause. It's rather unstable and it's better to use the in-game pause then 1964. I will change this next year. Thanks for the feedback.