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

    PSX "Value too large" to launch after update

    Scheduled Pinned Locked Moved Help and Support
    psx not workinglr-psx-rearmedmultidisc
    38 Posts 6 Posters 3.5k 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.
    • EfriimE
      Efriim
      last edited by Efriim

      Convert to PBP and rename each disc to hide them and write an .m3u

      Sorry for the misinterpreted advice, I edited this so it should work again, and remember it is all case sensitive. The period before the filename denotes a hidden file in unix, that is exactly why it is used to hide the PBP from Emulationstation.

      If an m3u index is made for each disc then it will allow you to both start the game on any disc and change discs in game.

      Final Fantasy 8 (Disc 1).m3u
      
      .FF8(Disc 1).PBP
      .FF8(Disc 2).PBP
      .FF8(Disc 3).PBP
      .FF8(Disc 4).PBP
      

      Order of each .m3u index changes. On disc 2 the index for disc 3 remains remains the same, you could employ your own research method here.

      Final Fantasy 8 (Disc 2).m3u
      
      .FF8(Disc 2).PBP
      .FF8(Disc 1).PBP
      .FF8(Disc 3).PBP
      .FF8(Disc 4).PBP
      
      Final Fantasy 8 (Disc 3).m3u
      
      .FF8(Disc 3).PBP
      .FF8(Disc 1).PBP
      .FF8(Disc 2).PBP
      .FF8(Disc 4).PBP
      
      Final Fantasy 8 (Disc 4).m3u
      
      .FF8(Disc 4).PBP
      .FF8(Disc 1).PBP
      .FF8(Disc 2).PBP
      .FF8(Disc 3).PBP
      

      Then symlink a memory card "pcsx-card1.mcd" for each "*.m3u" name.

      cp pcsx-card2.mcd pcsx-card1.mcd
      for i in *.m3u; do ln -s pcsx-card1.mcd "${i%.*}.srm"; done

      or with "Final Fantasy 8 (Disc 1).srm"

      for i in *.m3u; do ln -s "Final Fantasy 8 (Disc 1).srm" "${i%.*}.srm"; done

      Those will link all .m3u games in a folder to the .srm/.mcd; if there are already .srm entries then the link will not be created.

      The entirety can be done and used by ES in a sub-folder. Game Art can be added for the folder and for each disc though it is a rather manual process to get disc art.

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

        @Efriim said in PSX "Value too large" to launch after update:

        I write multiple .m3u for every disc.

        Why ?

        EfriimE 1 Reply Last reply Reply Quote 0
        • EfriimE
          Efriim @mitu
          last edited by Efriim

          @mitu to start on a disc.
          If I think of a script for writing the .m3u I will share it.

          Why would I want to start disc 1 if I am on Disc 2.
          They share an index so index 4 is always disc 4 unless disc4.m3u and they share a memory card.

          H 1 Reply Last reply Reply Quote 0
          • H
            hhromic @Efriim
            last edited by

            @Efriim thanks but that is not an appropriate solution for the original problem reported in this topic.

            Please do not post unrelated/misleading information until the actual problem is sorted out and resolved. In this way, we don't introduce noise into the topic. Thanks for understanding.

            1 Reply Last reply Reply Quote 2
            • H
              hhromic @SteveXmetal
              last edited by

              @SteveXmetal I tested Riven last night also on my RPI 3B+ and launches fine too.
              Let's see if we can reach to the bottom of this mystery.

              S 1 Reply Last reply Reply Quote 0
              • S
                SteveXmetal @hhromic
                last edited by

                @hhromic Thanks for continuing to look into my issue:

                im running retropie version: 4.4.11
                my retro-arch version/ emulator is : 1.76 - psxreARMed r22 588bf79

                I tried downloading another version of final fantasy 8, that does not work either.
                File sizes:
                Final fantasy 8 (used to work, played through disk1)- 2,160,718 KB
                FF8 new - 1,838,285 kb
                Riven - 2,580,553 kb

                This may not be a file size issue because i also have a FF9 .pbp and that does launch, it is bigger than the new FF8 file. My FF9 file is 1,844,731 KB

                Looking at this log file it may be a RAM issue?
                Also i have tried several BIOS files/versions, all fail.

                here is the pastebin for my issue:

                https://pastebin.com/dAKLWsvg


                Parameters: 
                Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/pcsx_rearmed_libretro.so --config /opt/retropie/configs/psx/retroarch.cfg "/home/pi/RetroPie/roms/psx/Final Fantasy8.PBP" --appendconfig /dev/shm/retroarch.cfg
                Memcard 2: enabled
                Use memcard 2: /home/pi/RetroPie/roms/psx//pcsx-card2.mcd
                Starting PCSX-ReARMed 
                Running PCSX Version 1.9 (Apr  3 2019).
                psxMap: warning: wanted to map @80000000, got 0x6f4b4000
                Init new dynarec
                testing if we can run recompiled code..
                test passed.
                warning: RAM is not directly mapped, performance will suffer
                Mapped (RAM/scrp/ROM/LUTs/TC):
                77000000/1f800000/1fc00000/08000000/70107000
                Loading memory card /home/pi/RetroPie/roms/psx//pcsx-card2.mcd
                found BIOS file: scph1001.bin
                RGB565 supported, using it
                plugin: plugins/builtin_gpu
                plugin: plugins/builtin_spu
                plugin: plugins/builtin_pad
                plugin: plugins/builtin_pad
                Plugins loaded.
                Could't open '/home/pi/RetroPie/roms/psx/Final Fantasy8.PBP' for reading: Value too large for defined data type
                Error opening CD-ROM plugin!
                

                Thanks again any help is appreciated!

                1 Reply Last reply Reply Quote 1
                • Z
                  zeroblu3
                  last edited by zeroblu3

                  Same issue with FFVIII in PBP format on RPI 3B+.
                  Single CD .bin/.cue works without problems.
                  Already tried updating retroarch, core, emulationstation from bin and from source with no luck.

                  Here is the runcommand.log

                  [https://pastebin.com/vSz8HP3K]

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    SteveXmetal @zeroblu3
                    last edited by

                    @zeroblu3 quick question zeroblu3, did yours work before updating like mine did?
                    IF so what disk where you on? i got up to and played partway through the beginning of disk 2.

                    Z 1 Reply Last reply Reply Quote 0
                    • Z
                      zeroblu3 @SteveXmetal
                      last edited by

                      @SteveXmetal
                      yes it worked a few weeks ago before i updated retropie from the update script.
                      I only tested if the game worked like 20 minutes into the first disc but now all i get is just a crash back to emulationstation.

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

                        What version of RetroPie are you using ? The 4.4 image or an older image updated to 4.4 ?
                        @hhromic this looks suspiciously like a missing define for _FILE_OFFSET_BITS 64 (see https://github.com/RetroPie/EmulationStation/pull/468). Maybe caused by the recent zlib changes.

                        Z S H 3 Replies Last reply Reply Quote 0
                        • Z
                          zeroblu3 @mitu
                          last edited by

                          @mitu
                          i started a fresh build using the latest 4.4 image

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

                            @zeroblu3 I don't fully understand your update - are you saying you started from a 4.4 fresh image, you updated and you got this problem ? Or that you're now, after noticing this problem, starting with a fresh 4.4 image ?
                            Can you add more info about your system - https://retropie.org.uk/forum/topic/3/read-this-first ?

                            Z 2 Replies Last reply Reply Quote 0
                            • Z
                              zeroblu3 @mitu
                              last edited by

                              @mitu
                              oh sorry for the confusing answer. ^^
                              I initially started a fresh build using the latest 4.4 image, put my games library on the Pi and just tested a few games including FFVIII, then updated retropie with the update script. Yesterday i decided to start FF and run into this problem.
                              Sorry for my english too btw, i'm not a native speaker.

                              1 Reply Last reply Reply Quote 1
                              • Z
                                zeroblu3 @mitu
                                last edited by

                                @mitu
                                I'm running a Raspberry Pi 3B+ with a 2.5A power supply.
                                Linux retropie 4.14.98-v7+
                                Here is the full verbose runcommand.log https://pastebin.com/C5P65pq1

                                1 Reply Last reply Reply Quote 0
                                • S
                                  SteveXmetal @mitu
                                  last edited by

                                  @mitu I looked into the post that you linked to, this is what i suspected with large game files, however, this doesnt necessarily explain why a different and smaller FF8.pbp does not launch, while my larger FF9 file does. Aslo, i tested a few other larger files, like lunar star story 2, and all of those can work with no issues.

                                  Z 1 Reply Last reply Reply Quote 0
                                  • Z
                                    zeroblu3 @SteveXmetal
                                    last edited by

                                    @SteveXmetal
                                    I tried to run the FFVIII.PBP with the "non libretro" PCSX Rearmed emulator and it runs with no problems. If i try to run it with pcsx-rearmed-libretro it crashes to ES.

                                    1 Reply Last reply Reply Quote 0
                                    • H
                                      hhromic @mitu
                                      last edited by hhromic

                                      @mitu said in PSX "Value too large" to launch after update:

                                      @hhromic this looks suspiciously like a missing define for _FILE_OFFSET_BITS 64 (see https://github.com/RetroPie/EmulationStation/pull/468). Maybe caused by the recent zlib changes.

                                      Yes that is my exact guess about what is going on. However it puzzles me that I can't reproduce it on my system and that now @SteveXmetal reported it works for other games that are large too.

                                      Yesterday I already backported the check for _FILE_OFFSET_BITS from the configure script in here: https://github.com/libretro/pcsx_rearmed/compare/master...hhromic:backport-largefile
                                      Anyway I want to confirm if this works for @SteveXmetal and @zeroblu3, and then submit the patch upstream. Thanks for the heads-up in any case.

                                      @SteveXmetal @zeroblu3 can you guys please try the following steps to patch the core and test the fix to confirm this helps with your problem?

                                      ((now fixed upstream, no need to manual patch anymore))

                                      During the build phase, make sure the flag -D_FILE_OFFSET_BITS=64 can be seen in the compiler commands output. Then test the games and let me know if they launch. Hopefully they do.

                                      If confirmed working, I will send the patch upstream and then report back when is merged. Thanks for testing guys!

                                      EDIT: @SteveXmetal @zeroblu3 guys can you confirm your roms are on th e SD card and not on a USB or network share? just to be sure of all the conditions. Thanks.

                                      S Z 2 Replies Last reply Reply Quote 0
                                      • S
                                        SteveXmetal @hhromic
                                        last edited by

                                        @hhromic Thanks for helping out.

                                        I ran the codesby exiting emulationstation, running typing them in order and reseting my machine when they were done (if there is a better way please let me know, still a bit new to this).

                                        Still did not work. Checking the log, I got the same error.

                                        H EfriimE 2 Replies Last reply Reply Quote 0
                                        • H
                                          hhromic @SteveXmetal
                                          last edited by hhromic

                                          @SteveXmetal said in PSX "Value too large" to launch after update:

                                          @hhromic Thanks for helping out.
                                          I ran the codesby exiting emulationstation, running typing them in order and reseting my machine when they were done (if there is a better way please let me know, still a bit new to this).

                                          That is okay, but resetting the machine is not necessary, you can just go back to emulationstation after building/installing and relaunch the emulator.

                                          @hhromic said in PSX "Value too large" to launch after update:

                                          During the build phase, make sure the flag -D_FILE_OFFSET_BITS=64 can be seen in the compiler commands output.

                                          You verified that, right? (it's important to make sure the patch was applied correctly)

                                          @hhromic said in PSX "Value too large" to launch after update:

                                          EDIT: @SteveXmetal @zeroblu3 guys can you confirm your roms are on th e SD card and not on a USB or network share? just to be sure of all the conditions.

                                          Can you confirm this too please?

                                          One more thing, can you generate the md5sum of your PBP file like this (can take some time!):

                                          md5sum "/home/pi/RetroPie/roms/psx/Final Fantasy8.PBP"
                                          

                                          And report back the hash? To double-check if I have the same file.

                                          1 Reply Last reply Reply Quote 0
                                          • H
                                            hhromic
                                            last edited by

                                            @SteveXmetal I updated the patch now with extra flags that might be needed. It's really hard to debug when I can't reproduce the problem. Can you try again the steps to patch, build and install the core and let me know if that worked?

                                            You should see these in the compiler commands output now: -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64. Please make sure they are in your output.

                                            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.