Jump to content
For users that lost completed data migrating to 13.22... ×
LaunchBox Community Forums

Rlad

Members
 View Profile  See their activity

  • Posts

    490

  • Joined

  • Last visited

 Content Type 

Posts posted by Rlad

    LaunchBox 13.13 - Beta Thread

    in Beta Testing

    Posted

    2 hours ago, faeran said:

    We looked into this. As you know, LaunchBox has a feature designed to help display media files from external sources based on matching filenames. Unfortunately, we discovered a bug in this code that caused unintended consequences. This bug sometimes linked media to the wrong games, or even multiple incorrect games at once. The bug also allowed this association even if the filenames didn't perfectly match the game files, which sounds like what you have going in your library.

    The bad really outweighted the good here, so we fixed the bug to ensure accurate media association, which then also broke the association for any external media that only loosely matched the game's file name. 

    We will continue to support media from outside sources in the way it was intended, but really for optimal functionality throughout LaunchBox, we strongly recommend using the in-app media tools. 

    Thanks for the explanation, I'll just re-add the videos.

    A gameboy filter I used now applies by default to every game for several systems in my collection

    in Noobs

    Posted

    7 hours ago, Reaper978 said:

    Ok everything seems to be in order but I'm still having having the problem with the Lynx emulator in RetroArch not saving the shader, even after I used a core override.  Using the core override is saving other things though, like when I disable the bezels it saves that.  I guess it's not that big a deal but it would be nice because I found a shader for the Lynx that is apparently very similar to the actual Lynx's display.

    You use 'save' in the shader menu for shaders, if it's saving other things then you're trying to use the overides menu to save the shader.

    PCSX2 windows keep popping up in Manage Emulators

    in Troubleshooting

    Posted

    3 hours ago, C-Beats said:

    After review I think I know what is occurring. This is related to beta changes. The code we use to get the version of PCSX2 to display in the version column is causing the app to throw this message. We'll see if we can find a way to handle this a bit better.

    I think it's the WX version that's causing it, i need that one still for the qemu plugin (FFB for steering wheel).

    Images folder creating folder

    in Troubleshooting

    Posted · Edited by Rlad

    Not sure about that as i already knew what the file was, mine was a weird one that existed in a playlist (unable to delete) but wasnt showing anywhere else. It later decided to show up in search which allowed me to delete it and the folder.

    I like the new Games DB layout and all....but....Recommendations

    in Features

    Posted

    On 2/11/2024 at 2:37 AM, Thanatos_Prime said:

    Alternately, maybe Neo Geo just needs people to stop *MOVING* cabs to Arcade and creating dupes.

    Sure, but there's no way to stop that. I wouldn't be against some 'Super Moderators' or being able to lock things down, but the current system some things just seem to go around in circles.

    10 minutes ago, MJF said:

    The NEO GEO AES Section is for the HOME CONSOLE not the Arcade machines. Unless you are talking about the MVS, which is not the same.

    I put MVS in my post.

    RPCS3 with original Dualshock 3 Controllers

    in Emulation

    Posted · Edited by Rlad

     

    I just checked mine with DSHidMini and all axis work.

    There are different versions according to this https://www.psdevwiki.com/ps3/DualShock_3

    Quote

     

    MicroController Unit (MCU)

    QFP package, 80pin

    The pinout of the Toshiba T6UN6EFG-003 was traced in a VX4 board. Has not been verifyed if the pinout matches with T6UN6EFG-001 or T6UN6EFG-002 or other boards. It seems the pins can be remapped at bootloder as can be seen in the photos of the PP1 prototype (note the sensors in that photo are connected to pins 77, 78, 79, 80, this doesnt matches with newer dualshocks 3 models). Some people said in most older versions of the controller it was posible to update the controller firmware by USB with a tool that uploads a rom to the controller, this update procedure should be made by using the BT module because all USB connections are managed by it (so in some way it was the BT module the responsible to update the toshiba controller)

    Cant remember if updating through PS3 was a thing or not.

×
×
  • Create New...