Jump to content
LaunchBox Community Forums

Nocta

Members
  • Posts

    125
  • Joined

  • Last visited

Posts posted by Nocta

  1. On 9/16/2024 at 6:53 PM, EvoluZion3 said:

    So I deleted all my Vita games from LB so the Platform was removed, deleted Vita3K from the Emulators list and restarted LB, then followed ETA Prime's 13.15 video of how to add Vita3K (as if I'd never had it installed before), and after another restart LB finally worked its magic!

    This works for me too! Thanks a lot! 😀

    • Like 1
  2. On 7/19/2024 at 3:19 PM, SiriusVI said:

    OK thx, would be nice to have, though.

    I agree, being able to tune the way the auto-importer works would be great. The mix of convenience and personalization is what makes LB special imo.

    • Like 1
  3. 9 hours ago, sundogak said:

    Assuming you have auto import turned on

    I don't use auto import because it creates several empty folders and I prefer to not have this (faster to get to my roms when I tinker with retro handhelds). Is pulling directly from emulator virtual drive vs file scanning something that will be added as a general option and be useable even without auto import on?

  4. I have an issue when scanning for new roms for all platforms or for the PS Vita only, I get a bunch of garbage files for the PS Vita.

    They all come from the vita3l/ux0/app folder the despite the fact that I set another folder as my rom folder (one where I have txt files as shortcuts to the real game files) for the PS Vita.

     

    Anyone know how to fix that?

  5. Right now adding modern arcade games - mostly done via TeknoParrot - ends up with them being added to the Arcade platform - a few in the Taito Type X or Triforce systems. For example Senjin Aleste (amazing game) can't be classified under it's real platform because it's not in the DB - the Sega ALL.Net P-ras MULTI version 3.

    I believe it would be more consistent to strictly keep all MAME games under Arcade and have a Modern Arcade platform for everything covered by TeknoParrot - cherry on the top would be the real platforms added in Platform Category just like MAME systems, Naomi, etc...

    That way everything is nicely compartmentalized and easier to maintain.

    What do you think?

     

  6. Thanks to @Special T, I found the solution to my fullscreen problem while keeping ares functional for multiple systems!
    You need to set a default command-line in associated platforms as follow - eg N64:

    --fullscreen --system "Nintendo 64"

     

    Nonetheless, It seems to me that we are trying to hard code something that Launchbox could handle for us in a cleaner way.
    @Jason Carr, any chance you are looking into implementing the native support and configuration of Ares into Launchbox in the near future?

    • Like 1
  7. I'm glad I found this thread!

    Thanks to you guys I managed to make F-Zero X launch with the DD expansion and in fullscreen!
    I like to keep my launchbox portable so I try to use only relative paths but I cannot make it work for the F-Zero DD expansion sadly.

    On 6/2/2024 at 2:11 PM, JoeViking245 said:

    In addition to those, there's %romlocation% (added sometime early in 2022) which will give the "full\Path\To\Rom\".  Path only. 

    I tried %romfile% "%romlocation% /F-Zero X (USA)-expansion.ndd" and I believe the issue is that romlocation adds the quotes already so it breaks the syntax, right?

    On 6/2/2024 at 1:26 AM, Special T said:

    So, how can I make the --fullscreen parameter move to the end?

    Instead of ares.exe --fullscreen "FULL\PATH\TO\ROM\FILE" it would need to be ares.exe "FULL\PATH\TO\ROM\FILE" --fullscreen

    All the games I launch using ares are NOT in fullscreen despite using the --fullscreen parameter and I believe it's due to the issue you mentioned because F-Zero has no trouble being fullscreen with its parameter at the very end. Did you set custom command-line parameters for every single game?

×
×
  • Create New...