Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nuu

Pages: [1] 2 3 ... 78
1
EverDrive N8 / Re: Which one is your favourite game?
« on: January 17, 2020, 01:16 PM »
Super Mario Bros 3, Dragon Quest III or Rockman depending on the mood.

2
EverDrive N8 / Re: EverDrive-N8 PRO bug reports.
« on: January 17, 2020, 01:09 PM »
Did you try The Immortal on another TV when it worked?

The NES has a number of black colors in its master palette, and one of them glitches on some NTSC TVs that confuses it for the sync signal. The Immortal is one of the games using this bad color for black. Looks like there is a patch that changes the bad black to a good black:
https://www.romhacking.net/hacks/4534/

3
EverDrive 64 / Re: Game not designed for this system - Discussion
« on: January 16, 2020, 11:10 PM »
Byte swapped are usually ".v64" not ".n64". ".N64" are usually either big or little endian. I think ".v64" and ".z64" are stupid names though (they initially comes from the rom format of two copiers), and since the latest no-intro roms are big endian anyway I just rename them to ".n64".

PAL-M uses 60 Hz framerate and 525 lines, just like NTSC. The main difference is that it uses PAL color encoding. That should be why color is right but speed is wrong with a PAL rom. PAL roms are boosted to run faster to compensate for the slower 50 Hz framerate, so it will run too fast on 60 Hz systems such as NTSC and PAL-M.

4
First do you understand that a BIOS update is possibly not compatible with all Everdrives and could break them?

All Everdrives already come with the BIOS they need. You don't update the BIOS.

5
Do all buttons work in games?

6
Sounds to me like there is a hardware problem with the SD2SNES cartridge. Contact Krikzz or the seller.

7
FXPAK (SD2SNES) / Re: some questions about the FXPAK (SD2SNES)
« on: January 12, 2020, 08:11 PM »
1) Not normal. The battery might be loose or dead. Check it and change it if it's dead.

2) I'm not sure but it sounds like you can have a custom time offset to the time the RTC is set to (a secondary time setting). Then games will use the custom time instead when turning this option on. For example if some Satellaview game stops working after a certain date (which it's probably long past now) you can use a custom date in 1997 or something without having to set the RTC. When you play a game where you want real time again, you just turn the option off and the real time will be used instead. I don't know what games would need this though.

8
EverDrive GBA / Re: Negotiating the RTC on the GBA X5
« on: January 12, 2020, 07:36 PM »
So the RTC is reset sometime when you select New Game. In that case getting the offset to be exactly 0 is impossible. 3 minutes is approximate I guess. It depends how fast you press forward the messages, enter your name and you have to manually walk up to the wall clock in your room to set it.

"[Guide] Findings about RTC and quick-fix por Pokémon R/S/E" by otenko
This post is yours? Looks like your account is gone along with all your posts. Strange.
Do you think you could post your test results and guide again?


Ah right! It doesn't have to be midnight in real time. You just set it to a few minutes past midnight in the game to make the offset close to 0 so that setting the RTC to real time in Boktai gets it close to the Pokemon time. Real time can be anything when you do it.

9
EverDrive GBA / Re: Negotiating the RTC on the GBA X5
« on: January 12, 2020, 12:56 AM »
So in other words it could be storing the time that is set on the wall clock at the start of the game as an offset relative to the time the RTC was at, and it uses that to calculate time whenever needed, rather than just use the time value that the RTC reports as is. If you want that offset to be close to 0 you would need to start the game sometime close to 00:00 at midnight, since that's what the RTC is reset to at that point.

Now I see what taiyotenko was talking about.

10
EverDrive 64 / Re: "Save&Quit" not working?
« on: January 12, 2020, 12:31 AM »
I've experienced the ED64 (v2) failing to update the save file on the SD card. I had ended a Mario Party session and before turning off I hit reset to save my earned stars and coins. But the Everdrive hanged instead of going back to the menu and copy the file. I turned it off then on again to see if it saved, and it turned out that whole session was lost.

Is that what happened for you? You didn't say what happened between hitting reset and going to bed.
If it works properly, it should return to the Everdrive menu and a popup window (often really quick) should say that it's writing to SD card or something like that. After that you can turn off the power.

11
EverDrive GBA / Re: Negotiating the RTC on the GBA X5
« on: January 11, 2020, 09:04 PM »
Yes although that's only for taking care of the berry glitch which is mostly unrelated to your question. If I'm right you need to set the RTC in Boktai every time you start a new file in the Pokemon games (or play any other game that resets the RTC).

Why would the wall clock be off if you set the time correctly in Boktai though?

12
EverDrive GBA / Re: Negotiating the RTC on the GBA X5
« on: January 11, 2020, 04:29 PM »
I still don't see an answer to the question. The berry glitch seems to be an unrelated bug (I don't fully understand the explanation at bulbapedia but it seems it never happens again after January 2, 2002) which happens on real Ruby and Sapphire cartridges as well.

If the RTC is reset so that the time goes backwards the game will probably act either like no time has passed or act like a lot of time has passed depending on how it calculates the passed time (I'm guessing). But if the RTC can be set again in Boktai for example (preferably to real time or at least sometime after January 2, 2002 to fix the berry glitch as well), I think everything should be fixed. Player planted berries might wilt when doing this, but after that I think everything should work as it should? If a new save file is created on any other Pokemon game, the RTC will be reset again and it must be fixed using Boktai again. This is how the berry glitch is fixed using the patching methods mentioned so I can't imagine it doing anything bad to the save file.

So more concretely what happens if playing Pokemon after RTC is reset (without fixing it in Boktai)? Given that most time events only seems to be based on days passed since last happening (rather than being based on certain dates) and resets when enough time has passed, they should be fine. Berries might wilt if it acts like a lot of time passed, or nothing will happen at all if it acts like no time has passed. Since day/night cycles, water tides and Eevee evolutions are only based on hours/minutes, those types of events should be fine as long as the RTC is set to match real time of the day (or whatever time you want it to be).

Only problem I could think of is if there is an event that happens at regular intervals and keeps count of it, say something that happens every month and increments a counter every time. In that case the counter would go up a lot when setting the time (by 12 per year you set time forward for the month event example). But this would happen with Nintendo's berry glitch patch as well. I haven't played this game very much so I don't know if such events exists.

Is this correct?

13
EverDrive GB / Re: GB Color Palettes on GBC
« on: January 11, 2020, 01:32 PM »
The logo is messed up when booting a faulty rom (or booting without a cartridge) because the logo graphics data is in the cartridge, not in the bootstrap rom. If the graphics data is missing or broken, the logo will not show up correctly. The bootstrap rom will refuse to boot the cartridge rom if it's missing the logo data or if it isn't 100% correct. This was to prevent unlicensed makers from making games to Game Boy, since it forces them to have the Nintendo logo in the rom, which would be a copyright or trademark violation unless they got permission from Nintendo. There are ways to fool the bootstrap rom though, and people have made homebrew with custom logos showing up.

The bootstrap is a mask rom and can't be overwritten. There are no flash memory or anything in the Game Boy that can brick like on Nintendo DS and other newer systems, so there is no sure way to break it using software.

Which Nintendo Test screen rom?

14
EverDrive GB / Re: GB Color Palettes on GBC
« on: January 10, 2020, 01:49 AM »
If the boot strap rom is run from the everdrive? It would be needed to be hacked to run (Gameboy roms requires a proper header), then it would probably just display a glitchy logo and hang like if you start a Gameboy without a cartridge. GBC, SGB and GBA botstrap roms would display their respective logo then hang.

15
News / Re: EverDrive N8 PRO has been released!
« on: January 09, 2020, 01:18 PM »
It sounds like this is about CPU-PPU clock alignment. There are 4 possible alignments every Famicom and NES could end up with at each boot. If you have a PPU that has this bug and speckles appears in a game you need to boot it into another alignment that works with that game by power cycling it until it works.
Soft reset will not work (not sure if any games even have this). Hard reset might work on a front-loading NES. For a Famicom and a top-loading NES you might need to power cycle since the reset button doesn't reset the PPU on those.

1/4 chances sounds about right, so it's probably this. I guess the root of the problem is on the NESRGB side, though it would be great if a workaround can be introduced on the N8 side, for example by forcing the bug-free CPU-PPU alignment that corresponds to the N8 cart. Maybe KRIKzz can discover if this or another workaround if possible once he gets a NESRGB kit to test.
I don't know for sure, but I don't think it's possible to do force clock alignment using a flashcart. The Hi Def NES can do it probably because it's adding all kinds of stuff to the hardware. It probably has to be fixed on the NESRGB.

Pages: [1] 2 3 ... 78