Jump to content
LaunchBox Community Forums

dov_EL

Members
  • Posts

    669
  • Joined

  • Last visited

Posts posted by dov_EL

  1. On 5/30/2022 at 4:25 PM, cannonwillow said:

    I have the platform named Arcade - FBNEO for fbneo through retroarch. I just went in and renamed the system from "Arcade" to "Arcade - FBNEO". in the AllGames.xml in the plugins.

    I did not understand if they can coexist with the recognition of games, both FBNEO and Arcade, even if the titles are the same.
    If both platforms where Arcade is started with the Mame Core in retroarch and FBNEO is launched with the fbneo core in retroarch, how is it possible then to also have the description of the games and the platform?

    2025-04-02 09_51_38-LaunchBox.png

    2025-04-02 09_51_38-LaunchBox.png

  2. It would be interesting to create a playlist where you can add PlayStation 2 titles that don't use the analog sticks and are therefore suitable for the joystick and Arcade buttons.

    # Tekken 5
    # SoulCalibur 
    # Marvel vs. Capcom 2: New Age of Heroes 
    # PES 2014: Pro Evolution Soccer
    # SoulCalibur III
    # PES 2014: Pro Evolution Soccer
     

    Can you think of any other titles that would fit our cabinets?

    Thanks

  3. 19 hours ago, Retro808 said:

    Like @Lordmonkus the .neo files can be imported without much issue. If your file names have the full game name it should pull data unless you have "Scrape As" set to something other than "Arcade". I tested importing .neo rom files and they imported without issue. My .neo are basically named like Mame roms for NeoGeo are. Hence why there is not issue matching them to the DB. 

     

    Screenshot 2024-02-27 at 6.32.49 AM.png

    Yes, the file names are not like those for mame, the names are complete and written precisely. However, importing the games works perfectly, but not all of them are recognized, so I had to manually correct more than half of the romset, even if the name was correct, it was enough to search for the metadata manually

  4. 8 hours ago, Lordmonkus said:

    I have never tried this core or the rom files but I don't see any reason that you can't import these .neo files.

    Yes, you can import the files, but the games are not recognized, so you will then have to manually recognize the game ID

  5. I've tried a thousand ways, but the only solution to play cuphead perfectly is to add it to STEAM, and configure the generic controller from the Steam settings.
    It would be interesting to have this same possibility on Launchbox

  6. Many people among us use Launchbox in an Arcade cabinet, and since we use Windows we have an endless library of games suitable for the Arcade Joystick and buttons.
    However, we begin to encounter the first difficulties when we find ourselves having to configure the joystick with software to convert the commands from the encoder to those which are the commands of an official gamepad recognized by the system.
    Mainly we used X360 CE and up to a certain point it worked well, but too many new games especially written in UNITY are not compatible with X360ce.
    We have other XInput wrappers using the keyboard as joytokey but often we can't configure the second player.
    There remain other less well-known XInput wrappers such as XOutput, but they do not seem simple to configure lacking the possibility to select the corresponding buttons as with X360CE.
    Have you found a permanent solution?

    2024-02-15 20_58_36-(1) Travis Bickerstaff su X_ _They have a Cuphead arcade machine here! https___t.png

  7. Hi everyone .
    I have always constantly updated Launchbox and retroarch correctly, from a certain point onwards I began to have stuttering problems with retroarch but only if I used the VULKAN drivers. So I continued to use the GLCORE drivers to use the Mega Bezel shaders convinced that this was an AMD driver issue or a Vulkan API issue with AMD.
    I started doing tests by downloading old versions of retroarch which I unpacked on the desktop, C:\user\Desktop
    I noticed that using Retroarch from desktop with the VULKAN drivers, there are no longer any stuttering problems, but if instead I use Retroarch from my default folder, i.e. C:\Launchbox|Emu\Retroarch, as soon as I use the Vulkan drivers I immediately get stuttering problems Stuttering,
    I'm going crazy, I can't solve it.
    Anyone have an idea on how to solve it?

  8. 2 hours ago, faeran said:

    Make sure you don't have any additional apps trying to open, or any other apps that could be trying to pull focus.

    You could try and use Windows Focus Logger to see if it provides you with any insight on any programs that could be pulling focus away: https://www.softpedia.com/get/System/System-Info/Window-Focus-Logger.shtml

    It's not a problem with other programs, this happens only and exclusively with the MAME core, it doesn't happen with the fbneo, mesen, genesisplusfx etc core. only the MAME core causes this problem.
    I have the impression that something happens like a frequency change that fools launchbox

  9. For several months I have been using the FBNEO core on retroarch for many Arcade titles, from Capcom, taito and other classics. I find this Core even superior to MAME.
    I saw that NES games, Megadrive etc. can also be loaded.
    However, I have had no difficulty with Arcade titles, but I cannot get NES games to work.
    I downloaded the specific NES ROMSet for FBNEO, I also tried with the DAT file, but the games do not start.
    Anyone could help me?

    Dat Link
    Non Arcade Guide

  10. You love  play SWOS in the Arcade cabinet?  the problem with this release is that the SWOS launcher requires the mouse to start the game by clicking on RUN SWOS.
    If instead we use swos-port-Release.exe, the graphic setting is not the same as we have if we use the launcher.
    but i have a solution :D



    Cut and past this in command line :)

    swos-port-Release.exe --game-style=1 --screen-mode=1 --window-mode=1 --window-width=1920 --window-height=1200 --new-scoreboard=1 --new-show-result=1 --mouse-cursor=2 --season-year=2019 --career-crash-fix=1111 --alpha-blending-menu=66

     

    -------------------

     

    Full Command
     

    --game-style=0|1
    0: PC gameplay style
    1: Amiga gameplay style
    2: Moon soccer style

    --improved-cpu-tactics=0|1
    0: Original
    1: Mozg's improved tactics

    --screen-mode=0|1|2
    0: Original PC screen
    1: Original Amiga screen
    2: Widescreen

    --window-mode=0|1
    0: Full screen mode
    1: Windowed mode

    --window-width=nnn
    nnn: Window width

    --window-height=nnn
    nnn: Window height

    --new-scoreboard=0|1|2|3|4
    0: Original
    1: New scoreboard (Left-Top)
    2: New scoreboard (Right-Top)
    3: New scoreboard (Left-Bottom)
    4: New scoreboard (Right-Bottom)

    --new-show-result=0:1
    0: Original
    1: Removed left and right spaces in the widescreen mode

    --alpha-blending-menu=nn
    nn: 00 to 99 - Opacity of menu transparency (%)

    --flashing-menu-cursor=0|1|2|3
    0: Original
    1: No flashing
    2: Smooth flashing (Fast)
    3: Smooth flashing (Slow)

    --mouse-cursor=0|1|2
    0: Windows style
    1: Amiga Workbench 2.04 style
    2: Amiga Workbench 1.X style

    --season-year=nnnn
    nnnn: Start year of game season
    (if nnnn=2019, some country and league names changed:
    TAIWAN -> CHINA, TAIWANESE->CHINENSE,
    GHANA -> EGYPT, GHANA -> EGYPT)

    --career-crash-fix=abcd (1:On, 0:Off)
    a: TeamNumFix (Fix up number of teams from team.xxx)
    b: MonthFix ("Jan to Dec" or "Jul to Jun")
    ? EachMatchFix (leagues > 12 -> num. of match = 2)
    d: GreekFix (Greek league fix)
    * --career-crash-fix=1111 recommended

     

    Missing only ESC to back to menu 

     

    :)

    83251705_853673971732070_2971278909611442176_n.png

×
×
  • Create New...