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

[Carnivorous]

Johnny Thunder wrote:

My antivirus detects it as a virus and deletes it, and then asks me to restart the computer

This has been a common problem since the beginning of the bundle's conception. Even stolen had this issue. Try whitelisting all the files located in the bundle I promise they are perfectly fine
~~
I tweaked the command line interface. 1964 removes spaces intentionally from command arguments and it's tied to a lot of things so I couldn't be bothered to fix it right - I just made it easier to use this is from the readme

Code:

1964 needs a active ROM directory already configured. The command line syntax for 1964 is the following: Syntax: 1964 [-f fullscreen_flag] [-v video_plugin_filename] [-a audio_plugin_filename] [-c controller_plugin_filename] [-g rom_name_inside_rom_directory] Example 1: 1964x9 -f -v Jabo_Direct3D8.dll -a AziAudio0.56WIP2.dll -c Mouse_Injector.dll -g Perfect_Dark.z64 Example 2: 1964x9 -g goldeneye.z64 1964 ignores spaces in arguments so the ROM filename must also contain no spaces. The plugin arguments are optional & if not provided will use registry settings.

Last edited by Carnivorous on Mon Feb 06, 2017 11:49 pm; edited 1 time in total

[Johnny Thunder]

I better use the emulator that uses '' graslu '', since it is more stable in my CPU.

mejor utilizaré el emulador que usa ''graslu'', ya que es mas estable en mi CPU.
_________________
Johnny Thunder masterpiece:
RickRollEye 64

Visit my youtube channel:
Johnny Thunder: The Revenger

Visit My discord:
Afterwards Studios

[Carnivorous]

Try 1964x6 or 1964x1 and see if it improves - more info in the readme

[Johnny Thunder]

I tried it and the antivirus deletes it, it does not work, and that the 30-day trial period of the antivirus was expired.

lo intente y el antivirus me lo borra, no funciona, y eso de que el periodo de prueba de 30 dias del antivirus se vencio.
_________________
Johnny Thunder masterpiece:
RickRollEye 64

Visit my youtube channel:
Johnny Thunder: The Revenger

Visit My discord:
Afterwards Studios

[deuxsonic]

Uninstall the antivirus then.

[Rekrul]

deuxsonic wrote:

[Or I guess I could draw a dot on my screen. It's not default behavior for the game but I would certainly appreciate having the option to use it, even if it were just a little red dot.

Don't draw dots on your monitor, use OverlayXHair instead;

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

Run the configuration program and adjust the color and size to your liking. Then run OverlayXHair and it will put a crosshair in the center of the screen. Note that for it to render on top of the game in fullscreen mode, you have to set the emulator's fullscreen resolution to the same as your desktop.

Presto, a persistent crosshair. On the downside, it will render on top of the menus and FMVs as well, but you get used to it. I actually posted about this program back on page 6.

Anyway...

I just tried the latest version and it's still working fine for me. I tried the FOV slider, but to be honest, I really don't like the fish-eye effect it causes, even at 70. Going through the tunnel at the start of the Dam mission in Goldeneye with it set to 140 was a surreal experience. It looked like it was a mile long and it took forever to zoom in when I activated aiming mode. I think I'll just stick with the default.

BTW, I upgraded my graphic drivers and GLideN64 works for me now. The performance isn't very good though. Also, what's supposed to be improved over Glide64? As far as I could see, it has all the same graphical glitches (flicking water at the start/end of Frigate, depth rendering problems with the fences in Goldeneye, etc.) as Glide64. Being able to adjust the gamma in the game with the GLideN64 plugin is nice, but other than that and the performance, it didn't seem any different than Glide64.

[deuxsonic]

Rekrul wrote:

Don't draw dots on your monitor, use OverlayXHair instead; http://2xdsoft.de.tl/OverlayXhair.htm Run the configuration program and adjust the color and size to your liking. Then run OverlayXHair and it will put a crosshair in the center of the screen. Note that for it to render on top of the game in fullscreen mode, you have to set the emulator's fullscreen resolution to the same as your desktop. Presto, a persistent crosshair. On the downside, it will render on top of the menus and FMVs as well, but you get used to it. I actually posted about this program back on page 6. Anyway... I just tried the latest version and it's still working fine for me. I tried the FOV slider, but to be honest, I really don't like the fish-eye effect it causes, even at 70. Going through the tunnel at the start of the Dam mission in Goldeneye with it set to 140 was a surreal experience. It looked like it was a mile long and it took forever to zoom in when I activated aiming mode. I think I'll just stick with the default. BTW, I upgraded my graphic drivers and GLideN64 works for me now. The performance isn't very good though. Also, what's supposed to be improved over Glide64? As far as I could see, it has all the same graphical glitches (flicking water at the start/end of Frigate, depth rendering problems with the fences in Goldeneye, etc.) as Glide64. Being able to adjust the gamma in the game with the GLideN64 plugin is nice, but other than that and the performance, it didn't seem any different than Glide64.

Thanks for the program.

Having tried both Glide64 and GlideN64, the former, despite being described as faster, actually runs terribly on my system and no matter what Glide wrapper I use, be it the one this comes with or another. The Jabo plug-ins work but look awful, but GLideN64, despite being listed as a slower option in the readme, actually runs quite well and is very accurate with a little tinkering to the frame buffer configuration to speed it up (the options in it marked to be faster.) I re-enabled noise as, on my system at least, I see no difference in performance and then in the custom ini I have it disabled for PD since I don't think PD uses it at all. There is a visual bug on Frigate with the water at the starting point but once you climb onto the ship the problem seems togo away so it's only at certain angles.

On the GLideN64 discussion, a possible issue of system timer resolution being increased when certain programs like Firefox are running. I was told that the Project64 emulator has a parameter to increase its thread priority, "CN64TimeCritical=1", to counteract this potential issue so perhaps something similar exists in a newer version of 1964 that could be backported or potentially added to increase thread priority and/or system timer resolution?

[Carnivorous]

deuxsonic wrote:

The Jabo plug-ins work but look awful, but GLideN64, despite being listed as a slower option in the readme, actually runs quite well and is very accurate with a little tinkering to the frame buffer configuration to speed it up (the options in it marked to be faster.)

I have a PC which runs Glide64 faster than GLideN64 so it depends on each system

deuxsonic wrote:

On the GLideN64 discussion, a possible issue of system timer resolution being increased when certain programs like Firefox are running. I was told that the Project64 emulator has a parameter to increase its thread priority, "CN64TimeCritical=1", to counteract this potential issue so perhaps something similar exists in a newer version of 1964 that could be backported or potentially added to increase thread priority and/or system timer resolution?

Try this https://files.catbox.moe/bxrgez.zip

[deuxsonic]

Tried, shows an error:

---------------------------
Error
---------------------------
Error opening this file. Please refresh the ROM list.
---------------------------
OK
---------------------------

[Carnivorous]

The -g command was changed last update to not require the full directory, just specify the rom name instead

[deuxsonic]

I tested your new builds and there doesn't appear to be any difference. However, using a tool called TimerResolution, I discovered that it is indeed a timing issue with 1964. When Firefox is running, the resolution is set to 0.977 milliseconds. When it is not running, the resolution is set to 15.625 milliseconds. By using the tool to force it to the former resolution, the performance problem goes away.



1964 needs to set the timer resolution to the maximum value to solve it.

[Carnivorous]

Thanks I'll investigate it now

[Rekrul]

deuxsonic wrote:

Thanks for the program.

No problem.

It's just one of the many little programs I've collected over the years thinking "This might come in useful some day." I've also used it with Alien Trilogy and Dark Forces running in DOSBox.

deuxsonic wrote:

Having tried both Glide64 and GlideN64, the former, despite being described as faster, actually runs terribly on my system and no matter what Glide wrapper I use, be it the one this comes with or another. The Jabo plug-ins work but look awful, but GLideN64, despite being listed as a slower option in the readme, actually runs quite well and is very accurate with a little tinkering to the frame buffer configuration to speed it up (the options in it marked to be faster.) I re-enabled noise as, on my system at least, I see no difference in performance and then in the custom ini I have it disabled for PD since I don't think PD uses it at all. There is a visual bug on Frigate with the water at the starting point but once you climb onto the ship the problem seems togo away so it's only at certain angles.

As far as I can see, with the default options, GLideN64 and Glide64 both look exactly the same. They both have the rendering error with the water at the start of Frigate and the depth error with the fences in some levels. For example, on the second level, Facility, in the bottle room at the end, there's a fenced off room on the upper level (take a left as soon as you go through the entry door). As you look through the fence into the room, some of the details on the right appear in front of the fence. I believe this happens in some other levels as well, but I can't recall any specific examples at the moment.

deuxsonic wrote:

I tested your new builds and there doesn't appear to be any difference. However, using a tool called TimerResolution, I discovered that it is indeed a timing issue with 1964. When Firefox is running, the resolution is set to 0.977 milliseconds. When it is not running, the resolution is set to 15.625 milliseconds.

I was a little skeptical of this, but I tested it using the test build provided and the same thing happens on my system. I never noticed it before because I nearly always have Firefox open and because for me, using the Glide64 plugin, there's no noticeable difference in framerate.

[deuxsonic]

Excellent, it works!

I actually didn't catch it right away either because I do the same thing with Firefox running almost all the time.

Firefox is a resource hog so I thought "what if I try playing this with other stuff not running" and what surprised me was the performance was a lot worse rather than the same or better. Early on I wasn't paying attention to when Firefox was open and when it wasn't so sometimes it would seemingly have performance issues and other times be fine.

I thought that I couldn't be the only person affected by it.

[Carnivorous]

I'm 99% sure Jabo max out Kernel frequency which is why I had in the readme to change plugins as a solution. IDK if this is something the emulator or plugin should do but I'm keeping the option - thank you very much for getting to the bottom of this bug I wouldn't have ever figured it out