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

    Amiberry needs an update of the setup script

    Scheduled Pinned Locked Moved Help and Support
    amiberrysetup scriptcrashes
    4 Posts 2 Posters 715 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.
    • P
      PARALAX
      last edited by

      I've been trying to get the latest version of Amiberry to work correctly for days, until yesterday I realized that the problem has something to do with Retropie's setup script. I manually updated this to the current version 4.8.8 yesterday. However, the new folder structure of the current Amiberry version is not taken into account. According to the Amiberry author, the "capsimg. so" file is still copied to the main folder instead of the "plugin" directory, which is why Amiberry crashes when trying to use IPF images. This only works after you manually create the folder with a program like "Midnight Commander" and copy the corresponding file into it. It is possible that other files are affected by this and are still copied to the wrong folders.

      On the other hand, the Retropie team is lagging far behind when it comes to compiling the Amiberry files. While version 5.7.3 is now available, Retropie still downloads version 5.7.1 via the update function (Update from Binary). This should be fixed as soon as possible.

      There are also problems with the 50 Hz display, so that the new VSync function does not work correctly or the sound interrupts. Only when the chipset is set to "NTSC" does it work normally and with smooth scrolling, but then the emulator clearly runs too fast.

      It would be nice if there was better and more reliable cooperation with the emulator programmers to ensure that such problems do not occur in the future. Recently there have only been endless problems and crashes.

      S 1 Reply Last reply Reply Quote 1
      • S
        sleve_mcdichael @PARALAX
        last edited by sleve_mcdichael

        @PARALAX the plugins folder is used since this update last week. It is possible the precompiled binary has not updated to the latest build yet -- and so it still looking in the old location -- but not finding it there since the configure function is updated to new location already -- and that's why the crash?

        You can try update from source or else wait a few week for the update from binary to catch up with source/configure.

        P 1 Reply Last reply Reply Quote 0
        • P
          PARALAX @sleve_mcdichael
          last edited by

          @sleve_mcdichael "Update from Source" reinstalls the old version 5.2, which I already had before. So I'll have to wait a few more weeks. Maybe I can manually copy the Amiberry start file from the download file "amiberry-v5.7.3-debian-buster-armhf-rpi4" into the Retropie emulation folder to get the current version 5.7.3 (instead of 5.7.1). It would at least be worth a try.

          P 1 Reply Last reply Reply Quote 0
          • P
            PARALAX @PARALAX
            last edited by

            I have now gained new insights into the VSync problem, because it seems that the TV or the HDMI detection is really to blame. I just had my Raspberry Pi connected to my 13-year-old Panasonic 3D TV and the VSync option works exactly as it should. What I also noticed is that the screen modes are swapped in the video setup menu, which you can select when selecting a game before starting Amiberry via Retropie. On my old TV, the 50 Hz modes are first in the list and only then do the 60 Hz entries follow. On my Philips TV from 2014, it is the exact opposite, so that I have to set the correct mode every time I change TVs. However, it does not seem to take the 50 Hz modes into account at all or does not switch despite the selection and only runs at 60 Hz instead of 50 Hz, which I find very strange, because the TV is definitely capable of handling both refresh rates. This also works with all other emulators, whether with VICE (C64) or all RetroArch cores such as NES, SNES, Mega Drive, Arcade, etc. Just not with Amiberry, which I find very unfortunate. The Retropie team would probably have to release an update to detect the connected screen in the Amiga Setup Menu. I actually thought that HDMI screens were all standardized by now and the only explanation I can think of is that it has something to do with an error in the setup script for Amiga core.

            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.