Author Topic: Neon 64 0.3b  (Read 2865 times)

0 Members and 1 Guest are viewing this topic.

Offline johnson

  • Jr. Member
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Neon 64 0.3b
« on: February 04, 2017, 08:38 PM »
Hi  everyone

this great hack of neon 64 made by Visor lets do savestates with Dezaemon 3D SRAM emulation and screenshots for 64drive also save game  (s-ram) Without using controller pak, and support mapper mmc4 :)

download in:
http://themanbehindcurtain.blogspot.mx/2017/01/neon64-screenshot-functionality.html

however, in everdrive 64 it can not permanent savestates. My question is if someone can change the everdrive menu to start the emulator with Dezaemon 3D SRAM ? and upload the savestates

 
« Last Edit: February 04, 2017, 08:50 PM by johnson »

Offline Arnold101

  • Sr. Member
  • ****
  • Posts: 353
  • Karma: +4/-1
    • View Profile
Re: Neon 64 0.3b
« Reply #1 on: September 03, 2017, 07:03 PM »
i have not understand what need to run it and what is that sram savestate. please explain

Offline johnson

  • Jr. Member
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Neon 64 0.3b
« Reply #2 on: September 07, 2017, 02:47 AM »
with the everdrive 64 can't does permanent savestates because the Dezaemon 3D SRAM never implemented in the OS , unlike  64drive  where marshallh quickly update his menu. I read that maybe works in saturnus alt64 menu  if someone change the OS https://assemblergames.com/threads/neon64-with-savestates.64696/ but  I don't know anything about programming.

With this hack  you can save games like zelda, kirby whithout Controller pak and do temporary savestate  while you do not change games when you play, only press L + R for see the options.

I don't now if krikzz wants to activates the Dezaemon 3D SRAM  in the oficial OS  , in fact i'm thinking of buying the 64drive.


Online saturnu

  • ヽ(^o^)丿
  • Hero Member
  • *****
  • Posts: 1168
  • Karma: +150/-0
    • View Profile
    • :D
Re: Neon 64 0.3b
« Reply #3 on: September 07, 2017, 08:26 AM »

Offline Kerr Avon

  • Hero Member
  • *****
  • Posts: 1339
  • Karma: +119/-3
    • View Profile
Re: Neon 64 0.3b
« Reply #4 on: September 07, 2017, 02:35 PM »
You have to tell the Everdrive 64 to use the Dezaemon 3D SRAM emulation save type for the emulator.

To do this, open the file save_db.txt which is in your SD card's \ED64\ folder.


And add the following lines to the bottom of the 'save_db.txt' file:


0x8979169C=4   (neon64 NES emulator v3 - Press L and R for savestates)
0x1974961C=4   (neon64 NES emulator v3 - Press L and R for savestates)

and it will probably work. It tells the Everdrive 64 to use the Dezaemon 3D SRAM save game method for two different versions of the emulator.

I can't test this, as I don't have my N64 with me, so it might be wrong. If this works, then please post to say so, and if it is wrong, then follow the tutorial:

https://krikzz.com/forum/index.php?topic=6125.0

and please post here the right line to put into the save_db.txt file.
« Last Edit: September 07, 2017, 02:45 PM by Kerr Avon »

Online saturnu

  • ヽ(^o^)丿
  • Hero Member
  • *****
  • Posts: 1168
  • Karma: +150/-0
    • View Profile
    • :D
Re: Neon 64 0.3b
« Reply #5 on: September 07, 2017, 03:33 PM »
this is not going to work.
files with an extension like .nes are set to sram32 instead of sram96 by the OS.
infact it's just 1 byte that needs to be changed.

it looks like there is a 64drive checks in the source of neon 0.3b. (64drive.inc)
but it's just disabling the screenshot usb feature.
« Last Edit: September 07, 2017, 03:38 PM by saturnu »

Offline johnson

  • Jr. Member
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Neon 64 0.3b
« Reply #6 on: September 08, 2017, 10:04 PM »
strange  after all, the emulator has a kind of protecion ? or something like that

Online saturnu

  • ヽ(^o^)丿
  • Hero Member
  • *****
  • Posts: 1168
  • Karma: +150/-0
    • View Profile
    • :D
Re: Neon 64 0.3b
« Reply #7 on: September 08, 2017, 10:37 PM »
it's not a protection, it's even open source. ^^
the usb-screenshot feature is disabled, 'cause it's 64drive specific - the way the usb communication is working.
the 64drive can dump memory cartspace offsets native while running, the ed64 would need fifo routines inside the neon64 program.