Jump to content
LaunchBox Community Forums

SavingPrincess

Members
 View Profile  See their activity

  • Posts

    24

  • Joined

  • Last visited

 Content Type 

Everything posted by SavingPrincess

  1. SavingPrincess
    Gotcha... consider it a feature request then!
  2. SavingPrincess
    It's more of like, I have US SNES roms but the auto-scrape is showing JP (first) release dates on metadata download (i.e. all the SNES roms).
  3. SavingPrincess
    Is there any way for LB or some plugin to scrape ROM metadata for regional release dates based on the region of the ROM?
  4. SavingPrincess
    Disabling selective suspend is always something I do (side effect of being a musician). Plus, this happens WHEN I'm playing.
  5. SavingPrincess
    I posted on the libretro forums as well, but people here are really helpful and maybe someone else is running into this issue. No matter if I have a single controller or five different ones plugged in (either direct to the motherboard or via a powered USB hub), Retroarch will occasionally show that the controller(s) disconnect and reconnect immediately. This creates a small 3-4 frame "hiccup" in whatever game I'm playing and then yellow text stating that the controllers are configured (one by one) in the lower left corner. Any ideas?
  6. SavingPrincess
    Definitely got it working right using -c config\whateverthingy.cfg per core. This also lets me set up my fightstick and SNES controller per core too. Thanks for helping me understand how it works.
  7. SavingPrincess
    So retroarch lies... when you press "save new config" it says "Saved new config to c:\Retroarch\retroarch.cfg" but it actually saves the core name to the config folder... =/ lol
  8. SavingPrincess
    Sorry one more quick question: about the config saving, when I choose "save new config" it just says it saves retroarch.cfg and not a new file... is a new file generated somewhere other than the retroarch\ root dir?
  9. SavingPrincess
    It will definitely detect it as a PlayStation Controller likely because the firmware is designed to be recognized by PS3/PS4. =/ Thanks for your help.
  10. SavingPrincess
    Did you see the picture of my controller? It makes a lot of sense when you see the actual controller.
  11. SavingPrincess
    Yeah, I know, sorry if I'm not being clear. Here's how I want the controller mapped out X = A Square = B Circle = C-Down Triangle = C-Left R1 = C-Up R2 = C-Right i.e. I want to use dedicated buttons for the c-buttons and not a modifier.
  12. SavingPrincess
    Right, that's... I mean, I understand HOW the default controls work, but that's not what I want I don't want to use a modifier, I want to map direct... button for button, like my controller is laid out. Sorry if I wasn't clear on that!
  13. SavingPrincess
    A pic of my controller is in the op, I'll add it here too and how I want it mapped: You can see that it's a single-analog stick, with a D-pad, and six face buttons (exactly the mapping of the n64 controller).
  14. SavingPrincess
    Also, what are you trying to show me? I still see that B and C-Down are being mapped together?
  15. SavingPrincess
    How do you "get rid of a button?"
  16. SavingPrincess
    This doesn't change mapping options in either User 1 Input Binds or Core Remap. Still showing as C button X/Y axis? Am I missing something?
  17. SavingPrincess
    It's literally one of the only 6-face button, single analog, 2 shoulder button, +D-pad pads out there beside N64 repros. Plus it's by a good company with a warranty!
  18. SavingPrincess
    Thanks. Worst-case I can fall back on the janky-mapping R-stick to buttons and loading the -c param, but I'd love to make this work pretty natively.
  19. SavingPrincess
    So I DL'd the nightly build and I am still not seeing a way to map C-buttons to individual buttons. I see the "A Button (C-Right)" and the "C Buttons X/Y" axis mapping. Am I doing something wrong? You can see that I have GLupeN64 vf308bbf loaded. So confused.
  20. SavingPrincess
    will have to try when I get home... it makes sense though... I think the missing component is the "-c filename.cfg" command line. Also, when I say "save new config" it just says "saved as C:\blahblah\retroarch\retroarch.cfg So even if I save a "NEW" config, is it just overwriting the old one?
  21. SavingPrincess
    As long as it lets me map my controller for real without the hoop-jumping nonsense that currently exists
  22. SavingPrincess
    You can't do that with N64 though, because it forced the "C" buttons to be mapped to Axis only. It only gives you two binds, i.e. a +/- instead of buttons in the remap file. So you have to bind the R-stick axis to buttons in the Input Binds vs. just using the Remap (which I use for all OTHER cores).
  23. SavingPrincess
    Okay, I thought it pulled the config based on the core loaded automagically... but I will try to specify the config file. Is there a good tutorial on how to create/modify config files? The only way it seems to save a config file within Retroarch is to save it over Retroarch.cfg.
  24. SavingPrincess
    Here's my issue and my repro steps: 1. Load N64 ROM with Retroarch (Mupen64Plus) 2. Configure User 1 Input binds (to allow per-button C-mapping) 3. Test in-game, works 4. Quit 5. Re-load N64 rom, configuration is lost I have "save configuration on exit" turned on. The "underlying issue" is that I need N64 to configure the controller differently than any other emulator because of the C-Stick mapping issue (I bind buttons to R-stick axis to allow C-buttons to work normally. Here's the controller and how I have it mapped: [Picture] (attached as well) In order to do this, I have to map the buttons marked with Yellow Arrows to Right-stick axis. I can get it working, but as soon as I reload, it goes back to a different config. What am I missing? I want to configure the controller this way for ONLY this system. Other systems I can use a normal mapping and the "rebind" features per-core.
×
×
  • Create New...