MiSTer FPGA Forum

You can also do that native on the core. Just set system type to NTSC with a PAL game and you get 60hz.
But if the game uses more height than NTSC allows or cannot handle the higher speed, it might not work.

if the logo comes up and hangs afterwards, you didn't patch it right. Everything else is likely set up correct.

Patches and patchtool can be found here: https://vampier.net/N64/

Some games unfortunatly use the the NTSC resolution and scale them in the VI for PAL
Examples are WaveRace and Mario Party. It makes these games much blurrier with PAL.

I will play the PAL version regardless

It is a feature to make the screen black in case of resolution switches for 3 frames, because otherwise you would might see garbage on the screen.

Schuetze1111 wrote: ↑Sat Sep 02, 2023 2:24 pm

I'm having trouble with the controller. most of the time I can move everything in the menu but in the game the buttons work but The analog or digital directional buttons only work in the menu and not in the game

Be sure to map the controller and analog axis in the menu core(that comes up after turning on mister), before you select the N64 core.

I converted a eep file by just renaming it.

Check the file sizes: if it's 512bytes or 2048bytes, you can just rename because it's the pure data.

Be aware that the core currently only supports EEPROM saves, no SRAM or Flash. So if you have bigger save files those are likely not EEPROM and you need to wait for the core to support them.

Great that you found the reason.

When the linux is busy, you usually don't notice it at all as most cores run in FPGA only.
It's usually only the consoles with CD or computer cores with HDD access.

Gauntlet is vertical and 240p mode cannot do vertical.

Normal res is 160x102 pixel, vertical is 102x160 and 240p mode is 320x204 pixel centered in the middle with every pixel doubled

So if you play vertical games, i fear you have to modify the settings or use some mra file for those titles.

Here you can find it:
https://github.com/MiSTer-devel/GBA_MiS ... 52C2-L1153

eldritch wrote: ↑Sun May 28, 2023 3:01 pm

we might see games running on it in the next few months!

That seems very optimistic, but i guess it depends on how "many" months is still "few"

That's also possible, but i can't imagine how, as the gameplay of the US version often dips below 30fps on a real psx, so i'm not sure how it works then.

Hard to justify a swap option for this special setup, but you can easily swap the analog stick direction in the source code if you really want to.
Maybe there is also an option in the ini file?

The recent update changed some things related to YC, but it shouldn't make things worse?
Unfortuantly i cannot test on CRT, but maybe someone can try one of these games on any CRT.

I don't get what 480p means for you...did you use some VGA scaler?

PSX:
- updated framework (Add S-Video/CVBS encoder by Mike Simone)
- SPU: fix envelope volume and tick readback for main volume (fixes stereo output in Wipeout 3 US)

where did you get this from? Pokemon Firered is a 128kbyte save, not 32kbyte

Pokemon red? This is the GBA subforum, so i'm not sure if you either talk about Fire Red or about the gameboy core.

In either case: i played both games and saving works.
Are you sure you have autosave on and opened the OSD after saving ingame before turning the mister off?

Strange, it should have worked on a real TV at that time...the output should be like with the real system.

Can you post some image?
Maybe someone else with PAL CRT can verify.

I only tried the game on HDMI some time ago and it worked good there.

He was asking for the special PSX2X build, which runs the CPU at double clock speed.
You posted the link for the unstable build of the normal core.

So both links provide the newest versions, each for it's category

Yes, you can find it here:

https://github.com/RobertPeip/PSX_MiSTe ... n/releases

the newest version is
PSX2XCPU_20230304.rbf

Data exchange from ARM Core to the FPGA fabric is too slow to have that as accurate solution.
Also it only solves like the 3rd biggest problem of a DS core, but introduce several new.