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

    [Solved] Resolution doesn't change when core override is present?

    Scheduled Pinned Locked Moved Help and Support
    core overridesresolutionlibretro core
    13 Posts 2 Posters 773 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.
    • ectoE
      ecto
      last edited by ecto

      Hi,
      I'm experimenting with midi out for the lr-PX68K and the lr-NP2Kai cores. I have a core override (i.e. /opt/retropie/config/all/retroarch/config/PX68K/PX68K.cfg) which sets midi_out="Standard"and nothing else. When this file is present, I cannot change the resolution through the runcommand menu.

      The logs show the correct KMSDRM modes, and the resolution appears in /dev/shm/retroarch.cfg. Yet the resolution stays in the standard resolution.

      Is this to be expected or is this a bug?

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        Get a verbose log and post it on pastebin.com. Does the same happen if you add the midi option to the system's retroarch.cfg ?

        ectoE 1 Reply Last reply Reply Quote 1
        • ectoE
          ecto @mitu
          last edited by

          @mitu I put in the midi_outinto the main retroarch.cfg, removed the PX68K.cfgcore override and made a verbose log:
          https://pastebin.com/zW9GGFHM

          As soon as I have an override, the log looks completely different:
          https://pastebin.com/yCS94aby

          I even tried a fresh, completey empty override file (touch PX68K.cfg) and it made no difference.

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @ecto
            last edited by

            @ecto said in Resolution doesn't change when core override is present?:

            As soon as I have an override, the log looks completely different:
            https://pastebin.com/yCS94aby

            The log file is not complete, can you upload the complete log ?

            ectoE 1 Reply Last reply Reply Quote 0
            • ectoE
              ecto @mitu
              last edited by

              @mitu That's all there is... you can even see the runcommans-onend prompt I have in there.
              It seems as if the log just stops after loading the override.

              mituM 1 Reply Last reply Reply Quote 0
              • mituM
                mitu Global Moderator @ecto
                last edited by

                Are you sure you don't have any other options in the core override (/home/pi/.config/retroarch/config/PX68K/PX68K.cfg) ?
                I'll give it a test, as a workaround you can use the x68000/retroarch.cfg file to enable the MIDI out, instead of the core override.

                ectoE 1 Reply Last reply Reply Quote 0
                • ectoE
                  ecto @mitu
                  last edited by ecto

                  @mitu This also happens when I have a completely empty (0b) core override file.

                  EDIT
                  The workaround... well... works. ;) I'll need to check though, if game specific overrides also trigger this issue.

                  1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator
                    last edited by

                    Can't seem to reproduce this. I've added a core override through the menu (basically just toggled the FPS counter and hid some notifications), but this doesn't seem to affect the resolution chosen from the runcommand launch menu.

                    My monitor seems to have this odd video mode (800x600@56hz, not the preferred video mode) which I've chosed for Chourensha's 768x512@59hz resolution:

                    Executing: SDL_VIDEO_KMSDRM_CRTCID=105 SDL_VIDEO_KMSDRM_MODEID=10 /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-px68k/px68k_libretro.so --config /opt/retropie/configs/x68000/retroarch.cfg "/home/pi/RetroPie/roms/x68000/Chourensha 68K v1.01 (1995)(Famibe No Yosshin).dim" --verbose --appendconfig /dev/shm/retroarch.cfg
                    [INFO] [Config]: Loading config from: "/opt/retropie/configs/x68000/retroarch.cfg".
                    [INFO] [Config]: Appending config "/dev/shm/retroarch.cfg".
                    [..]
                    [INFO] RetroArch 1.10.0 (Git 24a9378)
                    [...]
                    [INFO] [Core]: Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-px68k/px68k_libretro.so"
                    [INFO] [Overrides]: Core-specific overrides found at "/home/pi/.config/retroarch/config/PX68K/PX68K.cfg".
                    [INFO] [Overrides]: No content-dir-specific overrides found at "/home/pi/.config/retroarch/config/PX68K/x68000.cfg".
                    [..]
                    
                    [INFO] [Video]: Timings deviate too much. Will not adjust. (Display = 56.00 Hz, Game = 59.94 Hz)
                    [INFO] [Video]: Game FPS > Monitor FPS. Cannot rely on VSync.
                    [INFO] [Video]: Set video size to: **800x600.**
                    [INFO] [Video]: Starting threaded video driver ...
                    [INFO] [DRM]: Found 2 connectors.
                    [INFO] [DRM]: Connector 0 connected: no
                    [INFO] [DRM]: Connector 0 has 0 modes.
                    [INFO] [DRM]: Connector 1 connected: yes
                    [INFO] [DRM]: Connector 1 has 16 modes.
                    [INFO] [DRM]: Connector 1 assigned to monitor index: #1.
                    [INFO] [DRM]: Mode 0: (1280x1024) 1280 x 1024, 60.019741 Hz
                    [INFO] [DRM]: Mode 1: (1280x1024) 1280 x 1024, 75.024673 Hz
                    [INFO] [DRM]: Mode 2: (1152x864) 1152 x 864, 75.000000 Hz
                    [INFO] [DRM]: Mode 3: (1024x768) 1024 x 768, 75.028580 Hz
                    [INFO] [DRM]: Mode 4: (1024x768) 1024 x 768, 70.069359 Hz
                    [INFO] [DRM]: Mode 5: (1024x768) 1024 x 768, 60.003841 Hz
                    [INFO] [DRM]: Mode 6: (832x624) 832 x 624, 74.551270 Hz
                    [INFO] [DRM]: Mode 7: (800x600) 800 x 600, 75.000000 Hz
                    [INFO] [DRM]: Mode 8: (800x600) 800 x 600, 72.187569 Hz
                    [INFO] [DRM]: Mode 9: (800x600) 800 x 600, 60.316540 Hz
                    **[INFO] [DRM]: Mode 10: (800x600) 800 x 600, 56.250000 Hz**
                    [INFO] [DRM]: Mode 11: (640x480) 640 x 480, 75.000000 Hz
                    [INFO] [DRM]: Mode 12: (640x480) 640 x 480, 72.808800 Hz
                    [INFO] [DRM]: Mode 13: (640x480) 640 x 480, 66.666664 Hz
                    [INFO] [DRM]: Mode 14: (640x480) 640 x 480, 59.940475 Hz
                    [INFO] [DRM]: Mode 15: (720x400) 720 x 400, 70.081665 Hz
                    [...]
                    **[INFO] [GL]: Using resolution 800x600.**
                    [INFO] [GL]: Default shader backend found: glsl.
                    [...]
                    [INFO] [Environ]: SET_SYSTEM_AV_INFO: 800x600, Aspect: 1.333, FPS: 59.94, Sample rate: 44100.00 Hz.
                    [INFO] [Audio]: Set audio input rate to: 44100.00 Hz.
                    [INFO] [Video]: Timings deviate too much. Will not adjust. (Display = 56.00 Hz, Game = 59.94 Hz)
                    [INFO] [Video]: Game FPS > Monitor FPS. Cannot rely on VSync.
                    [INFO] [ALSA]: Using floating point format.
                    [INFO] [ALSA]: Period size: 768 frames
                    [INFO] [ALSA]: Buffer size: 3072 frames
                    [INFO] [ALSA]: Can pause: yes.
                    [INFO] [Display]: Found display driver: "gl".
                    [INFO] [Input]: Game Focus => OFF
                    [INFO] [Environ]: SET_FRAME_TIME_CALLBACK.
                    [INFO] [Environ]: SET_GEOMETRY: 768x512, Aspect: 1.333.
                    [INFO] [KMS]: New FB: 800x600 (stride: 3200).
                    [INFO] [KMS]: New FB: 800x600 (stride: 3200).
                    [INFO] [Environ]: SET_SYSTEM_AV_INFO: 768x512, Aspect: 1.333, FPS: 55.50, Sample rate: 44100.00 Hz.
                    [INFO] [Audio]: Set audio input rate to: 44497.30 Hz.
                    

                    Using an override .cfg with just a couple of manually added options yields the same results, so I don't think the override file is at fault.

                    Can you try removing the onstart commands from your script and try again ?

                    ectoE 1 Reply Last reply Reply Quote 0
                    • ectoE
                      ecto @mitu
                      last edited by

                      @mitu I retried different things, now with a completely empty runcommand-onstart.sh.

                      The results are always the same: as soon as I have a

                      • core override
                      • content directory override or a
                      • game specific override

                      the runcommand.logis truncated after loading the override (as in the Pastebin above) and the standard resolution (1920x1080 in my case) is applied. Idk if the loading of the basic /opt/retropie/configs/all/retroarch.cfg is also stopped. I would think not, as I can play normally. But maybe I could try that by changing someting like your idea with enabling the FPS counter in the base retroarch.cfg?

                      I reinstalled the runcommand scipt and retroarch, but I still get the same results. The last thing that comes to my mind is that I started this RetroPie image with the release of 4.7 (with support of the Pi4). Maybe something else borked up in all this time? I really like trying out different things with RetroPie. ^_^;

                      1 Reply Last reply Reply Quote 0
                      • mituM
                        mitu Global Moderator
                        last edited by

                        @ecto said in Resolution doesn't change when core override is present?:

                        I reinstalled the runcommand scipt and retroarch, but I still get the same results.

                        It's not a binary version problem, since you're using the same version of RetroArch as mine.
                        Can you post your retroarch.cfg files:

                        • the main one, from /opt/retropie/configs/all/
                        • the system one, from /opt/retropie/configs/x68000/
                        ectoE 1 Reply Last reply Reply Quote 0
                        • ectoE
                          ecto @mitu
                          last edited by

                          @mitu OK, here are my

                          /opt/retropie/configs/all/retroarch.cfg

                          and my

                          /opt/retropie/configs/c68000/retroarch.cfg

                          I justfound out, that this problem happens in every (?) retroach core.
                          I tried it with duckstation, NP2kai and Beetle PC-FX. Probably all acrade cores, because I use the Bezel Project, where I have a game override for (almost) every game...
                          I haven't noticed it before, because I usually use 1920x1080 anyway...

                          1 Reply Last reply Reply Quote 0
                          • mituM
                            mitu Global Moderator
                            last edited by

                            The config from /opt/retropie/configs/all/ seems to have been saved from RetroArch and this may influence the way it behaves w.r.t. overrides.
                            I'd suggest to rename it, then re-install RetroArch immediately - this will add the - much simpler - default RetroPie configuration for the emulator. Try to see if the issue still happens in this scenario.

                            ectoE 1 Reply Last reply Reply Quote 2
                            • ectoE
                              ecto @mitu
                              last edited by

                              @mitu That's it! That was the solution.

                              Thanks for helping me out. I'd probably never had guessed that. Thanks a lot!

                              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.