Black Screen?

[Bashmelek]

I am trying to run the template in ePSXe but I only get a black screen. I am following the instructions in installation.md under "Creating a project". Here is the output when I do cmake --preset default .:

`Preset CMake variables:

  CMAKE_BUILD_TYPE="Debug"
  CMAKE_TOOLCHAIN_FILE="C:\RandomMe\PSn00bSDK-0.20-win32\lib\libpsn00b/cmake/sdk.cmake"
  PSN00BSDK_TARGET="mipsel-none-elf"
  PSN00BSDK_TC=""

System is unknown to cmake, create:
Platform/PlayStation to use this system, please post your config file on discourse.cmake.org so it can be added to cmake
Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please post that file on discourse.cmake.org.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/gfray/Documents/Visual Studio 2022/Projects/PSnoobTest/template/build`

and then when I: cmake --build ./build

`C:\Users\gfray\Documents\Visual Studio 2022\Projects\PSnoobTest\template>cmake --build ./build
[1/1] Building CD image template
MKPSXISO 2.02 - PlayStation ISO Image Maker
2017-2022 Meido-Tek Productions (John "Lameguy" Wilbert Villamor/Lameguy64)
2021-2022 Silent, Chromaryu, G4Vi, and spicyjpeg

Building ISO Image: template.bin + template.cue
Scanning tracks...

  Track #1 data:
    Identifiers:
      System       : PLAYSTATION
      Application  : PLAYSTATION
      Volume       : PSN00BSDK_TEMPLATE
      Volume Set   : PSN00BSDK_TEMPLATE
      Publisher    : MEIDOTEK
      Data Preparer: PSN00BSDK 0.20
      Copyright    : README.TXT;1

    Parsing directory tree...
      Files Total: 3
      Directories: 0
      Total file system size: 2495472 bytes (1061 sectors)

Writing ISO
    Writing files...
      Packing C:\Users\gfray\Documents\Visual Studio 2022\Projects\PSnoobTest\template\system.cnf... Done.
      Packing template.exe... Done.
      Packing template.map... Done.

    Writing CDDA tracks...

    Writing directories... Ok.
ISO image generated successfully.
Total image size: 2495472 bytes (1061 sectors)`

For what it's worth. running the .cue file gives me this in ePSXe's debug:

`* Running ePSXe emulator version 2.0.5.
 * Memory handlers init.
 * ePSXe: using HLE BIOS (compatibility limited)
 * Loading Single CUE File ok
 * Loading ISO Format [MDF/BIN/IMG2352] ok
 * First/Last track: 1 1
 * Track 1: (DATA)  - Start 1: (00,02,00) -  Length 00:12
 * NTSC cdrom detected. (SLU__006.74)
 * GPU supports GTE Accurate
 * Doing init gpu[0]...
 * Init OpenGLv2...
OpenGL Screen Resolution 800x600 Ratio: StretchVendor: Intel
Renderer: Intel(R) UHD Graphics 620
 * Gpu open[0]...
 * Direct input init ok.
 * Init core spu ...  ok
 * Frames per second (14.942) - Time 59 frames -> 4.147 seconds.
 * Frames per second (18.1040) - Time 59 frames -> 3.220 seconds.
 * Frames per second (18.2552) - Time 59 frames -> 3.136 seconds.
 * Frames per second (18.2642) - Time 59 frames -> 3.131 seconds.
 * Frames per second (18.1454) - Time 59 frames -> 3.197 seconds.
 * Frames per second (19.024) - Time 59 frames -> 3.104 seconds.
 * Frames per second (18.2444) - Time 59 frames -> 3.142 seconds.
 * Frames per second (17.2764) - Time 59 frames -> 3.308 seconds.
 * Frames per second (17.1353) - Time 59 frames -> 3.391 seconds.
 * Frames per second (17.3121) - Time 59 frames -> 3.287 seconds.
 * Frames per second (18.410) - Time 59 frames -> 3.255 seconds.
 * Frames per second (18.644) - Time 59 frames -> 3.242 seconds.
 * Frames per second (18.482) - Time 59 frames -> 3.251 seconds.
 * Frames per second (17.2220) - Time 59 frames -> 3.340 seconds.
 * Frames per second (16.1272) - Time 59 frames -> 3.608 seconds.
 * Frames per second (17.3172) - Time 59 frames -> 3.284 seconds.`

Any idea what is going wrong? I am running a 64 bit Windows 10. I am using for the sdk "PSn00bSDK-0.20-win32", is that wrong for my system? What would be correct? Thank you!

[ijacquez]

Try using a different emulator, like DuckStation or Mednafen.

[Bashmelek]

DuckStation did indeed work. I am closing this and hope that this serves as a reminder to anyone in the future that epsxe will have this issue