Difference between revisions of "MiSTer FPGA"
Jump to navigation
Jump to search
m |
m |
||
Line 11: | Line 11: | ||
Use latest [https://github.com/MiSTer-devel/Main_MiSTer/blob/master/MiSTer.ini Mister.ini] file and enable DV1 | Use latest [https://github.com/MiSTer-devel/Main_MiSTer/blob/master/MiSTer.ini Mister.ini] file and enable DV1 | ||
<pre style="width:5%">direct_mode=1</pre> | <pre style="width:5%">direct_mode=1</pre> | ||
− | To ensure you can see the Menu core, add this to bottom of Mister.ini: | + | To ensure you can see the Menu core, add this to the bottom of Mister.ini: |
<pre style="width:5%">[Menu] direct_mode=0</pre> | <pre style="width:5%">[Menu] direct_mode=0</pre> | ||
=== Cores Lacking Direct Video Support === | === Cores Lacking Direct Video Support === | ||
− | Add to bottom of Mister.ini: | + | Aside from the Menu core, some arcade cores do not support direct video. |
+ | |||
+ | Add this to the bottom of Mister.ini: | ||
<pre style="width:5%">[ao486] | <pre style="width:5%">[ao486] | ||
direct_video=0 | direct_video=0 |
Revision as of 17:14, 12 October 2024
The following system settings are relative to Morph 4K's HDMI input and come recommended by the community after thorough testing. Make sure Morph 4K is on the latest firmware before proceeding.
Contents
MiSTer FPGA
- Advanced Video
- RX DV1: on
- RX EDID: Default.bin
Cores Using Direct Video Support
Use latest Mister.ini file and enable DV1
direct_mode=1
To ensure you can see the Menu core, add this to the bottom of Mister.ini:
[Menu] direct_mode=0
Cores Lacking Direct Video Support
Aside from the Menu core, some arcade cores do not support direct video.
Add this to the bottom of Mister.ini:
[ao486] direct_video=0 [Garegga] direct_video=0 [Cave] direct_video=0 [zerowing] direct_video=0 [1941] direct_video=0 [jt1942] direct_video=0 [jt1943] direct_video=0 [19xx] direct_video=0 [Arkanoidj] direct_video=0 [Arkanoid] direct_video=0 [Arknoid2] direct_video=0 [armedf] direct_video=0 [Batrider] direct_video=0 [ngp] direct_video=0
Analogue
Mega Sg
- Advanced Video
- RX EDID: h-dac.bin
Super Nt
- Advanced Video
- RX EDID: h-dac.bin
Pocket Dock
- Advanced Video
- RX EDID: h-dac.bin
Microsoft Xbox
Original Xbox
- Advanced Video
- RX EDID: Default.bin
Xbox 360
- Advanced Video
- RX EDID: Default.bin
Xbox One
- Advanced Video
- RX EDID: Default.bin
Xbox Series S/X
- Advanced Video
- RX EDID: Default.bin
< pulled from console page, needs revision >
- Black crush when using full range RGB - The Series S (and probably the series X) appears to send the wrong HDMI EDID metadata when using full range RGB. This option is called "Colour Space - PC RGB" on the console. In order to avoid crushing dark grey parts of the image, use the console in limited range RGB mode. A workaround to force default input RGB range, as with OSSC, should be added in a later firmware.
Nintendo
NES/Famicom
- Coming soon!
SNES/Super Famicom
- Coming soon!
N64
Retro GEM / Digital Direct Mode
- Advanced Video
- RX DV1: on
- RX FXD: on
- RX EDID: Default.bin
GameCube
- Coming soon!
Wii
- Coming soon!
Wii U
- Coming soon!
Switch
- Advanced Video
- RX EDID: Default.bin
Panasonic 3DO
FZ-1 and FZ-10
- Coming soon!
Sega
Genesis/Mega Drive
- Coming soon!
32X
- Coming soon!
CD
- Coming soon!
Saturn
- Coming soon!
Dreamcast
Retro GEM / Digital Direct Mode
- Advanced Video
- RX DV1: on
- RX FXD: on
- RX EDID: Default.bin
Sony PlayStation
PS1
Retro GEM / Digital Direct Mode
- Advanced Video
- RX DV1: on
- RX FXD: on
- RX EDID: Default.bin
PS2
Retro GEM / Digital Direct Mode
- Advanced Video
- RX DV1: on
- RX FXD: on
- RX EDID: Default.bin
PS3
HDCP cannot be disabled - must use an HDMI splitter (or similar)
- Advanced Video
- RX EDID: Default.bin
PS4
- Coming soon!
PS5
- Coming soon!
PSP
- Coming soon!
PS Vita
- Coming soon!
Vita TV
HDCP cannot be disabled - must use an HDMI splitter (or similar)
- Advanced Video
- RX EDID: Default.bin
Consoles with Unresolved Issues
< TBD >
Console | Reason/symptom | Fix if any |
---|---|---|
C64 with VIC-II Kawari DVI output | Incorrect colours in 60hz mode | Under investigation, but no ETA on a fix as yet. |