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

    Mupen64plus update overwrites GLideN64.custom.ini

    Scheduled Pinned Locked Moved Help and Support
    n64mupen64plusupdate
    2 Posts 2 Posters 308 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.
    • S
      sleve_mcdichael
      last edited by

      I'm on RPi4.

      File: /opt/retropie/configs/n64/GLideN64.custom.ini

      I need to edit this file for the Donkey Kong 64 camera glitch. When I update the mupen64plus package, it overwrites the file and returns to the default glitchy camera behavior.

      I first thought, can we use function copyDefaultConfig here when placing the file? Except, when I updated this last time it also added a couple new entries, which I suppose we would not want to miss out on.

      So could we use sed or something, then, to add the fix automatically? Or, why do we even have to do this manually, why is this just not the default already; is the glitch specific to a certain hardware/platform?

      if isPlatform "{something}"; then
          sed -i '/^\[DONKEY%20KONG%2064\]/,/^\[/ s/frameBufferEmulation\\copyDepthToRDRAM=1/frameBufferEmulation\\copyDepthToRDRAM=0/' "$md_conf_root/n64/GLideN64.custom.ini"
      
      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @sleve_mcdichael
        last edited by mitu

        I first thought, can we use function copyDefaultConfig here when placing the file? Except, when I updated this last time it also added a couple new entries, which I suppose we would not want to miss out on.

        You can't use copyDefaultConfig because the file is updated upstream and updates will not copy when a new version is added.

        So could we use sed or something, then, to add the fix automatically? Or, why do we even have to do this manually, why is this just not the default already; is the glitch specific to a certain hardware/platform?

        The default is the opposite (copyDepthToRDRAM=1), so it's clearly a platform (RaspberryPi / GLES3) glitch

        
        [DONKEY%20KONG%2064]
        Good_Name=Donkey Kong 64 (E)(J)(U)
        frameBufferEmulation\copyDepthToRDRAM=1
        frameBufferEmulation\N64DepthCompare=0
        

        The launch script has some overrides for games, but copyDepthToRDRAM is not among the settings considered. Maybe it would be useful to have a GLideN64.local.conf and merge the settings from it in GLideN64.custom.conf, during installation/configuration.

        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.