RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    ZDoom issues launching Sigil and other Doom Mods

    Scheduled Pinned Locked Moved Help and Support
    zdoomsigilpwads
    3 Posts 1 Posters 433 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dult.np
      last edited by

      Hello everyone,
      I've been banging my head and can't seem to understand what am I doing wrong.
      I have a Raspberry Pi 3B, updated, all installations from Retropie-Setup script.
      I've been trying to run Sigil with ZDoom, and I've followed the Wiki instructions but it goes straight back to the EmulationStation menu.
      The only way I managed to have it "hanging" on the Options menu (the one to select video resolution, emulator, etc.) was by having my sigil.sh like this:
      #!/bin/bash
      "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 PORT "doom" "-iwad /home/pi/RetroPie/roms/ports/doom/doomu.wad -file /home/pi/RetroPie/roms/ports/doom/sigil.wad"
      But, as I said, it sits hanging in that menu. If I read /dev/shm/runcommand.log aftewards it says to select a wad using the number keys, and I can do that, but It launches the iwad without loading and wad afterward.
      I have to issues with any iwad (Strife, Hexen).
      I hope someone manages to help me,
      Thanks.

      1 Reply Last reply Reply Quote 0
      • D
        dult.np
        last edited by

        So I found out about an option in zdoom to not give the option of selecting the wad at the start menu, and I changed my sigil.sh to this:
        #!/bin/bash
        #"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 PORT "doom" "/home/pi/RetroPie/roms/ports/doom/doomu.wad -file /home/pi/RetroPie/roms/ports/doom/sigil.wad"
        "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 PORT "doom" "/home/pi/RetroPie/roms/ports/doom/sigil.wad"

        But my /dev/shm/runcommand.log give this:
        Parameters:
        Executing: DOOMWADDIR=/home/pi/RetroPie/roms/ports/doom /opt/retropie/ports/zdoom/zdoom +set fullscreen 1 -iwad "/home/pi/RetroPie/roms/ports/doom/sigil.wad"
        ZDoom <unknown version> - - SDL version
        Compiled on Mar 25 2019

        M_LoadDefaults: Load system defaults.
        Gameinfo scan took 0 ms
        W_Init: Init WADfiles.
        adding /opt/retropie/ports/zdoom/zdoom.pk3, 584 lumps
        adding /home/pi/RetroPie/roms/ports/doom/doomu.wad, 2306 lumps
        I_Init: Setting up machine state.
        I_InitSound: Initializing OpenAL
        Opened device ALSA Default
        EFX enabled
        V_Init: allocate screen.
        S_Init: Setting up sound.
        ST_Init: Init startup screen.
        Checking cmd-line parameters...
        S_InitData: Load sound definitions.
        G_ParseMapInfo: Load map definitions.
        Texman.Init: Init texture manager.
        ParseTeamInfo: Load team definitions.
        LoadActors: Load actor definitions.
        R_Init: Init Doom refresh subsystem.
        DecalLibrary: Load decals.
        M_Init: Init menus.
        P_Init: Init Playloop state.
        ParseSBarInfo: Loading default status bar definition.
        ParseSBarInfo: Loading custom status bar definition.
        D_CheckNetGame: Checking network game status.
        player 1 of 1 (1 nodes)
        Using video driver RPI
        libEGL warning: DRI3: xcb_connect failed
        libEGL warning: DRI2: xcb_connect failed
        libEGL warning: DRI2: xcb_connect failed
        Resolution: 640 x 360
        Playing demo DEMO1
        Cannot play non-ZDoom demos.
        Playing demo DEMO2
        Cannot play non-ZDoom demos.

        What's happenning?

        1 Reply Last reply Reply Quote 0
        • D
          dult.np
          last edited by

          This is just for future reference.
          I don't know what was happening, but installing lzdoom and changing all zdoom references to lzdoom seemed to have solved the issues.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.