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

[Prenihility]

Carnivorous wrote:

Most likely a corrupt save occurred and broke the file, sorry

Not really a big deal. At least it's an excuse to play the game again.

So what is generally best practice to prevent corrupt saves? And what do I do now? Delete all mempak files?

[Carnivorous]

Update 1964, delete all mempak files and save to internal game storage instead of memory pak (less likely to corrupt).

[Prenihility]

Ok, I just extracted the newer Zip into the directory where I have 1964 installed and replaced everything, that should be the right way to do it. Readme is the updated version so i'm assuming all is well.

But what exactly do you mean by saving to internal game storage? Sorry, you lost me there.


EDIT: I create a new Agent and it asks for the location to save. Controller: and Game Pak:

? I can't select either and change it.

[Carnivorous]

Extract to a new directory (not replacing a previous install) and try again - internal game storage means game pak.

[madmax386]

is it possible to get retro achievements working with this emulator??

[Carnivorous]

It's possible - check discord.c to see how to read game state

[NutShot]

I am not sure if i asked this before already, but Autohotkey can´t send any Keys to the 1964 Window. Are you familiar with AHK by some chance and do know what´s maybe causing this? It works in other Programs, but only here in 1964 i have no luck at all.

[PeCho222]

I apologize for the irrelevant post, but I saw the sporadic inactivity in this thread and just wanted Carnivorous to know (again) that he is doing fantastic work. After requesting a TimeSplitters-compatible injector back when he was just doing GE/PD a year ago, the newest Dolphin injector literally got me through a deployment while maintaining my sanity. Thank you!

[Carnivorous]

NutShot wrote:

I am not sure if i asked this before already, but Autohotkey can´t send any Keys to the 1964 Window. Are you familiar with AHK by some chance and do know what´s maybe causing this? It works in other Programs, but only here in 1964 i have no luck at all.

If you are referring to the mouse injector plugin itself - that is likely due to it's use of the raw input API via ManyMouse.

PeCho222 wrote:

I apologize for the irrelevant post, but I saw the sporadic inactivity in this thread and just wanted Carnivorous to know (again) that he is doing fantastic work. After requesting a TimeSplitters-compatible injector back when he was just doing GE/PD a year ago, the newest Dolphin injector literally got me through a deployment while maintaining my sanity. Thank you!

No problem, glad it helped

[williansti]

there is a problem with gliden64 x carnivorous

vsync is not working, when activating the frame rate drops to 30, and the emulation keeps crashing unbearable lag.

turning off vsync works normal at 60fps, but with the screen cutting in 4k.

on project64 2.4.0 works normal with vsync on and off.

1964 Carnivorous (2019/11/02)
Project 64 (2019/11/04)
Plugin GLideN64 (2019/11/04)

[williansti]

1964 carnivorous + Last Dev GlideN64 Vsync Off
with or without overclocking, normal fluency but with screen cuts, when in full screen (missing vsync active).
https://imgur.com/zpN6R2K

1964 carnivorous + Last Dev GlideN64 Vsync On
with or without overclocking, frames drops to half 30fps, emulation features lags slowness...
https://imgur.com/CFzMc9R


Project64 2.4.0 + Last Dev GlideN64 Vsync Off
works well in any setting, vsync enabled and running lossless.
https://imgur.com/MiYxSlz


everything leads to believe that the error is in the carnivorous code, Could you check the question?

[Carnivorous]

Hi

Are you using my GLideN64 fork or this build?
Have you tried comparing at stock overclock for 1964?
Did you try overclocking PJ64 and comparing against 1964?

[williansti]

[quote="Carnivorous"]Hi

Are you using my GLideN64 fork or [url=https://github.com/gonetz/GLideN64/issues/2037#issuecomment-549394708]this build[/url]?
I tested with both, both yours and the gonetz has the same defect.


Have you tried comparing at stock overclock for 1964?
yes, defective either in stock or 6x, 9x, 12x, 15x and 18x same problem.


Did you try overclocking PJ64 and comparing against 1964?[/quote]
tested, overclock via configuration and cheat codes, it works normal...

same plugin, same configuration.

[williansti]

For ease I photographed the settings (they are the same).

I also recorded videos with my cellphone, demonstrating the problems.

forgive me for the humming my wife was in the kitchen, using pressure cooker, lol.


download both and see please, thank you for all your patience.

http://www.mediafire.com/file/lra3z7wqrh1grkp/Config_Screenshots.zip

http://www.mediafire.com/file/o3x5rcckq6ztzu2/Problem_V%25C3%25ADdeos.zip

[Carnivorous]

Thank you for the videos. I can see that the v-sync issue is not related with overclocking or CPU usage. If you could, can you try 1964 using this build of GLideN64?