Forum Replies Created

Viewing 35 posts - 71 through 105 (of 105 total)
  • Author
    Posts
  • in reply to: Problem with original PS3 controller #112788
    shoothere
    Participant

    gizmo making me look bad with all the AWESOME advice. Basically what gizmo said! Hope it works for you!

    in reply to: Problem with original PS3 controller #112767
    shoothere
    Participant

    Hi Guistino,

    did the pairing from the terminal work as per the tutorial?

    For step 2: did you remove the USB cable after the pairing as per instructions? What I found is I press the PS button once, it starts vibrating/cycling lights and I press it a second time (both times a short press) and it works. Let me know if this works for you!

    in reply to: reset Controller-Settings #112686
    shoothere
    Participant

    If you go to the Retropie submenu in EmulationStation, there should be an option to set up a controller and it will show the menu you get when first running RetroPie.

    Hope this helps!

    in reply to: Cores #112251
    shoothere
    Participant

    My guess is is because there is no core loaded/associated at that moment. Have you tried accessing the same menu from inside a game?

    For a joypad it is SELECT + X and there you should see options for the current core.

    Lemme know if this works!

    in reply to: Cores #112244
    shoothere
    Participant

    I suppose you mean you open up the retroarch menu?

    Where are you not seeing cores?

    in reply to: So Many Names! #111797
    shoothere
    Participant

    Hey there! Glad you enjoy this project!

    It is quite simple really (and now I really hope I don’t get it wrong!):

    Retropie: This is the actual combination of RetroArch/EmulationStation/Scripts/Emulators/etc that work on a Raspberry Pi. This includes the emulators that Retroarch provides, EmulationStation and even emulators that are not party or RetroArch/LibRetro (the lr you see mentioned a lot).

    EmulatioStation: This is the “front end” as people call it. Which is the graphical menu you see when you start everything up. Makes it all a lot nicer and easier to use instead of typing in commands to load ROMs.

    Retroarch: This is a distribution and a more “technical front end” which you see when you press the SELECT and X key on your joypad for example. This allows for for greater configuration than the normal emulator settings. Allowing one to tweak controls, settings, cheats and much per emulator of even PER GAME! Wooohooo!

    Libretro: Is what they they call an API. Think of it as the base ingredients used for every dish, the dishes being the emulators. It gives developers a common ground which takes away a lot of their work by providing default video outputs and control options, sound options and so much more so the developers for the emulators can focus on getting their emulators working the best they can and not having to worry about all the “standard stuff”.

    I hope this is a bit clear and that I didn’t make a mistake in there, otherwise feel free to correct me!

    If you have any more questions feel free to ask!

    EDIT: darnit! Herb beat me to it!

    shoothere
    Participant

    Now this is a noble goal and some of the features (especially the Hidden one) would be welcome in any distribution!

    Showing kids the evolution of home consoles/gaming as well as them being able to enjoy the classics in this day and age of 3D, shooters and violence will surely make them appreciate the current generation even more (or not! :P)

    Although I will not be testing it (too little time to fiddle) I must commend you for your effort!

    shoothere
    Participant

    @jerseywavesurfer: Did you edit the es_systems.cfg? I am running into the same problem as you but cannot resolve it. Which emulator are you using for snes? I found the lr ones to not work. Glad you got it working though! I hope to soon say the same!

    in reply to: Loading ROMs from a USB stick #110019
    shoothere
    Participant

    @jedimaster666: unfortunately per system links do not work either. As stated above not all systems are affected, strangely enough. It seems more emulator related than anything else as switching to some other emulators for, say, SNES work (although these are not the emulators of choice, as one would prefer the libretro ones).


    @dankcushions
    : did you symlink the roms folder in its entirety? I take it you are running 3.X? So I take it your USB stick is read write? The USB stick mounts fine each boot, just as read only. I altered the SRM directory to reside on the SD as the size is not that big of a problem

    in reply to: Loading ROMs from a USB stick #109963
    shoothere
    Participant

    So it seems emulator related. I will have a look at the different emulators although I would like the Libretro ones to work as they seem to work best.

    Is this an issue that is perhaps being adressed? As it seems some people manage to run them off external drives without any troubles.

    Thanx for the tip!

    in reply to: Loading ROMs from a USB stick #109482
    shoothere
    Participant

    @fvargasfrank: the ones that were already scraped will show properly, running a new scrape will result in an error. And oddly, FBA works with the symlink, just not other emulators.

    Happy it works for you but, sadly, does not solve our problem haha!

    oh and PS: gambling games ok but racing?! Come on! :P

    in reply to: Loading ROMs from a USB stick #109467
    shoothere
    Participant

    Changing the paths in /etc/emulationstation/es_systems.cfg did not work for me.


    @momaw27
    : are you running 2.6 or 3.X?

    in reply to: Loading ROMs from a USB stick #109389
    shoothere
    Participant

    Perhaps some additional info after some searching:

    The stick is FAT32 formatted, although it should not matter, perhaps it does?

    The stick is mounted as read only and I cannot get it to mount as read/write. Yet again I would not expect this to matter but again: perhaps it does?

    Is the symlink approach the wrong one? I could not find where to set the path where retroarch looks for its files as it seems online guides apply to 2.6 and not 3.X.

    in reply to: Emulationstation: Screen don't fit after Update #108360
    shoothere
    Participant

    I can confirm the issue is resolved for me too!

    in reply to: NeoGeo AES #108057
    shoothere
    Participant

    As per usual you were completely right Mr. Floob.

    Pressing Select (Coin) + X (Top button) brought up the RetroArch Menu, under Quick Menu in the Core Settings, there was the option I was looking for!

    Found a whole lot of other interesting stuff in there as well!

    Thanx again!

    in reply to: Emulationstation: Screen don't fit after Update #107952
    shoothere
    Participant

    Willing to test but does one use the rpi-update tool for this?

    in reply to: Emulationstation: Screen don't fit after Update #107817
    shoothere
    Participant

    Would further input from me on the ticket/issue help?

    in reply to: Retropie not accepting FTP connections #107696
    shoothere
    Participant

    Port 21 (FTP) doesn’t answer, did it ever?

    SCP should work with this client:

    https://winscp.net/eng/index.php if you are on Windows.

    https://cyberduck.io/ for our Mac OS X friends.

    Hope this helps!

    in reply to: Emulationstation: Screen don't fit after Update #107694
    shoothere
    Participant

    I can confirm going all the way down to 3.18.12 fixed it for me too.

    in reply to: Emulationstation: Screen don't fit after Update #107691
    shoothere
    Participant

    Hi Swampy,

    I made a thread with what seems to be the same problem.

    Issues after update to 3.1 (fresh) from 3.0b

    I went all the way down to 3.18.16 and the problem persisted.

    Which emulators have you tried? The GBA one goes offscreen for me.

    Perhaps it doesn’t matter but what kind of TV do you have? We have a Panasonic Plasma.

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107687
    shoothere
    Participant
    hdmi_group=1
    hdmi_mode=16

    had no effect sadly

    rpi-update bumped me to 4.1.10-v7+ which still shows the same problem.
    Which firmware would I downgrade to? The problem mentioned was on 4.1.7-v7+

    EDIT: downgrading to 4.1.6 had no effect

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107658
    shoothere
    Participant

    Ok editting the /boot/config.txt and setting the overscan values as included shows it helping during boot but the moment EmulationStation pops up (the RetroPie screen is fine) it goes off screen.

    My quest goes on!

    # uncomment the following to adjust overscan. Use positive numbers if console
    # goes off screen, and negative if there is too much border
    overscan_left=32
    overscan_right=32
    overscan_top=32
    overscan_bottom=32

    EDIT: it seems to be this problem. It didn’t happen before 3.1 though. Not sure about 3.0 release as I only had the beta…b4 I think

    https://github.com/Aloshi/EmulationStation/issues/378

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107657
    shoothere
    Participant

    Alrighty here’s an update:

    the lr-pscx-rearmed issue was due to the BIOS files. I tried another batch and the games load fine now (which I found surprising as they worked up til now but hey, not gonna complain!)

    All that is left is the resolution thing. It seems the PSX comes on screen fine, GBA seems off. I’ll try and find a pattern to this.

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107613
    shoothere
    Participant

    From your analysis it does seem I might doubt my BIOS files, although it was never a problem before. I will check that and get back to you.

    PS: no BIOS?

    Will have a clean look at the EmulationStation interface problem too.

    If you have any ideas would love to hear’em but otherwise let me get back to you tomorrow!

    Thanx for all the help so far!

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107609
    shoothere
    Participant

    Ah man! My bad! Force of habit using >> instead of &>!

    RetroArch [INFO] :: === Build =======================================RetroArch [INFO] :: [CPUID]: Features:
    Built: Oct  5 2015
    RetroArch [INFO] :: Version: 1.2.2
    RetroArch [INFO] :: Git: c6c250b
    RetroArch [INFO] :: =================================================
    RetroArch [INFO] :: [CPUID]: Features:
    RetroArch [INFO] :: Config: loading config from: /opt/retropie/configs/psx/retroarch.cfg.
    RetroArch [INFO] :: Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so"
    RetroArch [INFO] :: Environ SET_VARIABLES.
    RetroArch [INFO] :: Remaps: core name: PCSX-ReARMed
    RetroArch [INFO] :: Remaps: game name: /home/pi/RetroPie/roms/psx/Castlevania-SoTN
    RetroArch [INFO] :: Remaps: remap directory: /opt/retropie/configs/psx/
    RetroArch [INFO] :: Remaps: no game-specific remap found at /opt/retropie/configs/psx/PCSX-ReARMed/Castlevania-SoTN.rmp
    RetroArch [INFO] :: Remaps: no core-specific remap found at /opt/retropie/configs/psx/PCSX-ReARMed/PCSX-ReARMed.rmp
    RetroArch [INFO] :: Version of libretro API: 1
    RetroArch [INFO] :: Compiled against API: 1
    Starting PCSX-ReARMed v3.0rc1-212-gb42a95d
    Running PCSX Version 1.9 (Oct  4 2015).
    psxMap: warning: wanted to map @80000000, got 0x749df000
    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):
    78000000/1f800000/1fc00000/08000000/75357000
    RetroArch [INFO] :: Environ SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
    found BIOS file: SCPH5000.BIN
    RetroArch [INFO] :: Environ GET_CAN_DUPE: true
    RetroArch [INFO] :: Environ SET_DISK_CONTROL_INTERFACE.
    RetroArch [INFO] :: Environ GET_RUMBLE_INTERFACE.
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_frameskip:
    RetroArch [INFO] :: 	0
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_region:
    RetroArch [INFO] :: 	Auto
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_pad1type:
    RetroArch [INFO] :: 	standard
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_pad2type:
    RetroArch [INFO] :: 	standard
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_neon_interlace_enable:
    RetroArch [INFO] :: 	disabled
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_neon_enhancement_enable:
    RetroArch [INFO] :: 	disabled
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_neon_enhancement_no_main:
    RetroArch [INFO] :: 	disabled
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_duping_enable:
    RetroArch [INFO] :: 	on
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_drc:
    RetroArch [INFO] :: 	enabled
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_spu_reverb:
    RetroArch [INFO] :: 	on
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_spu_interpolation:
    RetroArch [INFO] :: 	simple
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_pe2_fix:
    RetroArch [INFO] :: 	disabled
    RetroArch [INFO] :: Environ GET_VARIABLE pcsx_rearmed_inuyasha_fix:
    RetroArch [INFO] :: 	disabled
    RetroArch [INFO] :: Environ PERFORMANCE_LEVEL: 6.
    RetroArch [INFO] :: Content loading skipped. Implementation will load it on its own.
    RetroArch [INFO] :: Environ SET_INPUT_DESCRIPTORS:
    RetroArch [INFO] :: 	RetroPad, User 1, Button "B (bottom)" => "Cross"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "Y (left)" => "Square"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "Select" => "Select"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "Start" => "Start"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "D-Pad Up" => "D-Pad Up"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "D-Pad Down" => "D-Pad Down"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "D-Pad Left" => "D-Pad Left"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "D-Pad Right" => "D-Pad Right"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "A (right)" => "Circle"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "X (up)" => "Triangle"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "L" => "L1"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "R" => "R1"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "L2" => "L2"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "R2" => "R2"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "L3" => "L3"
    RetroArch [INFO] :: 	RetroPad, User 1, Button "R3" => "R3"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "B (bottom)" => "Cross"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "Y (left)" => "Square"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "Select" => "Select"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "Start" => "Start"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "D-Pad Up" => "D-Pad Up"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "D-Pad Down" => "D-Pad Down"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "D-Pad Left" => "D-Pad Left"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "D-Pad Right" => "D-Pad Right"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "A (right)" => "Circle"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "X (up)" => "Triangle"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "L" => "L1"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "R" => "R1"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "L2" => "L2"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "R2" => "R2"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "L3" => "L3"
    RetroArch [INFO] :: 	RetroPad, User 2, Button "R3" => "R3"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "B (bottom)" => "Cross"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "Y (left)" => "Square"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "Select" => "Select"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "Start" => "Start"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "D-Pad Up" => "D-Pad Up"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "D-Pad Down" => "D-Pad Down"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "D-Pad Left" => "D-Pad Left"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "D-Pad Right" => "D-Pad Right"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "A (right)" => "Circle"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "X (up)" => "Triangle"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "L" => "L1"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "R" => "R1"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "L2" => "L2"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "R2" => "R2"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "L3" => "L3"
    RetroArch [INFO] :: 	RetroPad, User 3, Button "R3" => "R3"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "B (bottom)" => "Cross"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "Y (left)" => "Square"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "Select" => "Select"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "Start" => "Start"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "D-Pad Up" => "D-Pad Up"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "D-Pad Down" => "D-Pad Down"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "D-Pad Left" => "D-Pad Left"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "D-Pad Right" => "D-Pad Right"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "A (right)" => "Circle"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "X (up)" => "Triangle"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "L" => "L1"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "R" => "R1"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "L2" => "L2"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "R2" => "R2"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "L3" => "L3"
    RetroArch [INFO] :: 	RetroPad, User 4, Button "R3" => "R3"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "B (bottom)" => "Cross"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "Y (left)" => "Square"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "Select" => "Select"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "Start" => "Start"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "D-Pad Up" => "D-Pad Up"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "D-Pad Down" => "D-Pad Down"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "D-Pad Left" => "D-Pad Left"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "D-Pad Right" => "D-Pad Right"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "A (right)" => "Circle"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "X (up)" => "Triangle"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "L" => "L1"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "R" => "R1"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "L2" => "L2"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "R2" => "R2"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "L3" => "L3"
    RetroArch [INFO] :: 	RetroPad, User 5, Button "R3" => "R3"
    RetroArch [INFO] :: Environ SET_PIXEL_FORMAT: RGB565.
    RGB565 supported, using it
    plugin: plugins/builtin_gpu
    plugin: plugins/builtin_spu
    plugin: plugins/builtin_pad
    plugin: plugins/builtin_pad
    Plugins loaded.
    Loaded CD Image: /home/pi/RetroPie/roms/psx/Castlevania-SoTN.bin.
    selected sound output driver: libretro
    CD-ROM Label: SLUS_00067                      
    CD-ROM ID: SLUS00067
    CD-ROM EXE Name: SLUS_000.67;1
    
    shoothere
    Participant

    Perhaps I do not understand the usefulness of Berryboot but with Retropie not having such an image, is this project (WHICH IS MEGASUPERAWESOMESAUCE!) obsolete?

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107604
    shoothere
    Participant

    Well here we go!

    This is the output of loading the ROM manually (hope I did it right!)

    Starting PCSX-ReARMed v3.0rc1-212-gb42a95d
    Running PCSX Version 1.9 (Oct  4 2015).
    psxMap: warning: wanted to map @80000000, got 0x749f9000
    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):
    78000000/1f800000/1fc00000/08000000/75371000
    found BIOS file: SCPH5000.BIN
    RGB565 supported, using it
    plugin: plugins/builtin_gpu
    plugin: plugins/builtin_spu
    plugin: plugins/builtin_pad
    plugin: plugins/builtin_pad
    Plugins loaded.
    Loaded CD Image: /home/pi/RetroPie/roms/psx/Castlevania-SoTN.bin.
    selected sound output driver: libretro
    CD-ROM Label: SLUS_00067                      
    CD-ROM ID: SLUS00067
    CD-ROM EXE Name: SLUS_000.67;1

    Here is my /boot/config.txt

     uncomment if you get no picture on HDMI for a default "safe" mode
    #hdmi_safe=1
    
    # uncomment this if your display has a black border of unused pixels visible
    # and your display can output without overscan
    disable_overscan=0
    
    # uncomment the following to adjust overscan. Use positive numbers if console
    # goes off screen, and negative if there is too much border
    #overscan_left=16
    #overscan_right=16
    #overscan_top=16
    #overscan_bottom=16
    
    # uncomment to force a console size. By default it will be display's size minus
    # overscan.
    #framebuffer_width=1280
    #framebuffer_height=720
    
    # uncomment if hdmi display is not detected and composite is being output
    #hdmi_force_hotplug=1
    
    # uncomment to force a specific HDMI mode (this will force VGA)
    #hdmi_group=1
    #hdmi_mode=1
    
    # uncomment to force a HDMI mode rather than DVI. This can make audio work in
    # DMT (computer monitor) modes
    #hdmi_drive=2
    
    # uncomment to increase signal to HDMI, if you have interference, blanking, or
    # no display
    #config_hdmi_boost=4
    
    # uncomment for composite PAL
    #sdtv_mode=2
    
    # for more options see http://elinux.org/RPi_config.txt
    gpu_mem_256=128
    gpu_mem_512=256
    gpu_mem_1024=256
    
    overscan_scale=1
    arm_freq=700
    core_freq=250
    sdram_freq=400
    over_voltage=0

    Here is tvservice -s

    state 0x12000a [HDMI CEA (31) RGB lim 16:9], 1920x1080 @ 50.00Hz, progressive
    

    tvservice -m CEA

    Group CEA has 16 modes:
               mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
               mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive 
               mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive 
               mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
               mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 
               mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced 
               mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced 
      (native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
               mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive 
               mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive 
               mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 
               mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 
               mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced 
               mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced 
      (prefer) mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive 
               mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive 

    and finally tvservice -m DMT

    Group DMT has 1 modes:
               mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 

    Hope this helps!

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107601
    shoothere
    Participant

    NP! I did explain it in a rather weird way.

    The code was the content of runcommand.log, it happens for all games, just took this one as an example (tried 3 separate ones).

    For the second question you mean running the emulator from the CLI completely?
    Or is there an easy way to add a -verbose argument? For I am a bit at loss at how to do it manually.

    Well it is odd, as I mentioned the bootup sequence and retropie screens look like they are well aligned, it is just the EmulationStation+Emulators that seem to fall offscreen.
    When quitting an emulator it seems to sometimes revert to another setting showing more of the front-end (but still not all of it).

    Sorry to be such a bother!

    in reply to: Issues after update to 3.1 (fresh) from 3.0b #107595
    shoothere
    Participant

    As I mentioned I did a fresh install (flashed the 3.1 img) and started from scratch, just mentioned the 3.0b to mention there was no trouble there.

    I am trying to set it up in an RPi2, no problem on these fronts before.

    So I started with a clean 3.1 install.

    The only thing I altered in the default config is the storage of the SRM files in a separate directory. Other emus start up fine.

    Oddly after trying to boot a PSX game the “resolution” of the front end changes a bit showing a bit more of the interface but still not fitting on screen.

    When I try to launch Castlevania- Symphony of the Night I get the following error:

    /opt/retropie/supplementary/runcommand/runcommand.sh: line 695:  2398 Segmentation fault      /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so --config /opt/retropie/configs/psx/retroarch.cfg "/home/pi/RetroPie/roms/psx/Castlevania-SoTN.bin" --appendconfig /tmp/retroarch.cfg
    
    in reply to: RetroPie 3 RC1 – Video Overview #102258
    shoothere
    Participant

    Yet again Floob you are a godsend!

    Thank you for your tireless efforts making all of our lives easier!

    in reply to: Dear Retropie,NOOBS and RecalboxOS… #101851
    shoothere
    Participant

    The most common problem, in my experience, is a bad MicroSD which keeps giving I/O errors even after formatting it.

    I got RetroPie working like a charm (some MAME titles are slow but still) SNES/PSX/Megadrive all work like a charm and the GBA is also very impressive.

    You mention several different installs all fail so my guess is the problem is on your end.

    Try another MicroSD (2gb one or 4gb one) and try from there, perhaps you will be pleasantly surprised.

    in reply to: Analog stick PS3 on other emulators #101388
    shoothere
    Participant

    Much appreciated! Thank you!

    in reply to: Neo Geo speed issue #100327
    shoothere
    Participant

    Ok gngeopi was the way to go! Although some vsync issues persist that is something that can be looked at.

    What surprises me more though (and this goes for FBA too) is that b4 doesn’t remap the controls “logically” on my ps3 wired joypad.

    Coin used to be select and start used to be start but now they are L2 and R2 (which I could live with) but also it uses the analog stick instead of the dpad and some buttons do not seem mapped at all.

    Where to begin to fix this or am I missing something?

    It seemed to work fine in b3.

    in reply to: Neo Geo speed issue #100326
    shoothere
    Participant

    It is running through FBA for Pi. I guesss I will try gngeopi.

    Quick question: can the BIOS used influence speed?

    in reply to: PSX 7zip not showing #99813
    shoothere
    Participant

    Ah strange! I thought it did support 7zip. Ah well, that explains a *LOT* hahaha!

    Thanx for the reply!

Viewing 35 posts - 71 through 105 (of 105 total)