I really would like if you paid more attention. Enabling DualShock should be doable from a configuration file. If you don’t know what option is that, you don’t need to say it’s fine. I would check that by myself, but everytime I want to save a configuration file for this core RA crashes.
I said that part was fine.
input_player1_up = “up” input_player1_up_btn = “-1” input_player1_up_axis = “nul” input_player1_down = “down” input_player1_down_btn = “+1” input_player1_down_axis = “nul” input_player1_left = “left” input_player1_left_btn = “-0” input_player1_left_axis = “nul” input_player1_right = “right” input_player1_right_btn = “+0” input_player1_right_axis = “nul”
This isn’t the complete player 1 config. Dualshock is 517 for me
Yes, 517 is DualShock, but doesn’t fix the issue. If I disable the analog, no joystick response as stated above. I’m gonna wait for a developer, or until stable release is out.
As I said, repeatedly, if you’re using Beetle, that’s a known issue, and the “dev” told me he is busy right now so I may have to try to fix it… dunno how.
If you use the mednafen core I provided, that works ok here on 3 different PCs, 2 with XBOX controllers and one with a Logitech F310. I still think your config is the problem but you never posted it.
Anyway. Good luck I’m done with your attitude
The above was my response as nice as it can get to a nonsense discussion you bring with you. I couldn’t care less for “your issue”, you even haven’t explained why “dualshock” is so important (food for another thread?).
My config has always been on OP, so stop whining like a little boy. I’m uniquely talking about borked controls (press A=jump+right, press B=another action+down) which you seem to ignore at whim.
Try deleting all of the input_player(1, 2, ect.) lines from your config and see if that helps. You have input_autodetect_enable = “true” in your config which should override any inputs you have set up in your config file. But maybe having that enabled and having some inputs defined manually in your config is conflicting somehow. You could also try setting input auto detect to false and then doing all your mappings manually via RGUI’s input options.
I thought it was the other way around, config file overrides the auto RA buttons. In any case I did what you said. Deleted all p1 and p2 entries and as expected Joystick didn’t work, only d-pad. If I turn input_autodetect_enable to false, nothing works, even buttons I configured on the config file.
Did you try those games and didn’t detect any issues? It is important to know if this is MY problem, or RA’s problem.
It’s not the first time you are a prick to the only one trying to help you. You are always defensive and demanding at the same time. I gave you many options. I even taught you how to use the windows terminal.
After a week or more trying to diagnose an issue I would have guessed your config might have changed at least a bit. And your issue doesn’t appear here. I’ve shown you videos of me trying the games you’re having issues with and I don’t have the issue.
Dualshock is important because that’s the controller that has analogs. With PS1 pad and analog dpad emulation you are only simulating inputs that don’t really exist.
Bottom line. Your issue can’t be reproduced. At least not by me. I have fairly recent builds of both RA and beetle. And as I mentioned the last mednafen-psx you’ll ever find.
If you disable autodetection then you need to hit configure retropad to set you inputs again.
I don’t have any of the control issues you described with SotN (USA or Japan with the English fanpatch) or RE 2 DualShock Edition USA. I don’t have the normal USA or Spain versions of RE2 or any version of TPS2 to test. I’m using a 64bit RA build I made a few days ago and a Mednafen-PSX core from lordashram’s 2014-06-09 test build. I haven’t tried beetle yet since it sounds like it has issues.
Here’s my PSX config for non analog games. I use a Wii U Pro Controller with a Mayflash USB adapter in Xinput mode, so the mappings are the same as a 360 controller. I use an add on config for games that support the DualShock controller that I tell HyperSpin to load with:
-c Config\PSX.cfg --appendconfig Config\PSX-DualShock.cfg
I fixed analogs and rumble in beetle, tested extensively, you might be interested https://github.com/libretro/beetle-psx- … 4325f7e277
Cool, thanks!
@awakened: I tested with your files and from the point I use DualShock (input_libretro_device_p1 = “517”) no buttons response. So I have to switch to PS1 joypad. Then obviously only the d-pad works because you didn’t configure joystick in your config (you did for the dualshock joysticks). So the problem is DualShock, do I need something else? This was tested on a “clean sheet” with latest build “17-07” and its medafen_psx core. I’m debugging this with Castlevania in case that makes a difference…
Your configs were a bit strange too, in order to run the game smooth I had to change a few things to: video_hard_sync_frames = “0” video_swap_interval = “1”
Could you hand me your retroarch.cfg file? I think this is the global configuration file RetroArch fallbacks to.
Castlevania doesn’t have DualShock support, so you’d want to use PS1 Joypad as your device type for that specific game. I have the left stick mapped and d-pad analog mode set to left stick in that config, so 8-way movement on that stick should work. But only in PS1 Joypad mode. If it’s not working with that device type selected I’m not sure what could be wrong; are you using RetroArch’s per-core config setting? I’ve found that can be buggy with some things.
The majority of PS1 games don’t support DualShock. Which is why it was fairly easy for me to use a non-Dualshock config as my base for most games and have the add-on config with it enabled for the few that do. There’s a decent list of DualShock enabled games at NGEmu. It’s not complete; just checking it quickly I notice it misses Chrono Cross. If you wanted to be thorough you’d have to see if you can find a better list or try enabling Dualshock in each game and seeing if analog movement or vibration works.
My retroarch.cfg is much like my other configs actually; I use it for trying out new cores before I officially add and launch them through HyperSpin. So it’s basically like my PSX.cfg, but set up for Saturn right now since I’m trying out Yabause. I don’t like the huge messy configs you get with save config on exit enabled. My configs only have things that are different from the defaults. I can merge the changes from my DualShock add-on config with my standard one if that helps: Link. I changed hard sync frames back to 0; I needed it at 1 for better performance with CRT-Royale, but I switched to CRT-Easymode which is much less demanding. I removed the swap interval line (which makes it default to 1) as well; that’s for hitchless scrolling on my 120hz monitor :). You’d of course still only use that config for games that support the DualShock controller though.
Thanks for the help Awakaned, it gave me a base to work with. I spent the last 2 hours trying to figure out what was wrong, it happens to be a bug (again!). I always default input_autodetect_enable to “true”, so I don’t need to do any mappings, only on those that weren’t auto-mapped (i.e. +0,-0,+1,-1 for the left stick) (like you I only change what is needed from default). Problem is that by default the B and A buttons had two actions each bound to them. So when you jump it also shifts to one side, etc. You can remap those two conflicting buttons and it will solve the problem.
Another thing I tested is if I could run one config for both types of games, those with DualShock support and without, and they both worked. I could play Crash and I can make him walk or run, and in Castlevania I can manage the character with joystick. Can you confirm, or is there something I missed?
By the way, also wanted to ask, what is exactly analog_dpad_mode option? should be on for DS and off for PS1? This is all I found and didn’t make it clear: “Allows to use an analog to simulate the d-pad, it’s configured in a per player basis”
Castlevania doesn’t have DualShock support, so you’d want to use PS1 Joypad as your device type for that specific game. I have the left stick mapped and d-pad analog mode set to left stick in that config, so 8-way movement on that stick should work. But only in PS1 Joypad mode. If it’s not working with that device type selected I’m not sure what could be wrong; are you using RetroArch’s per-core config setting? I’ve found that can be buggy with some things.
The majority of PS1 games don’t support DualShock. Which is why it was fairly easy for me to use a non-Dualshock config as my base for most games and have the add-on config with it enabled for the few that do. There’s a decent list of DualShock enabled games at NGEmu. It’s not complete; just checking it quickly I notice it misses Chrono Cross. If you wanted to be thorough you’d have to see if you can find a better list or try enabling Dualshock in each game and seeing if analog movement or vibration works.
My retroarch.cfg is much like my other configs actually; I use it for trying out new cores before I officially add and launch them through HyperSpin. So it’s basically like my PSX.cfg, but set up for Saturn right now since I’m trying out Yabause. I don’t like the huge messy configs you get with save config on exit enabled. My configs only have things that are different from the defaults. I can merge the changes from my DualShock add-on config with my standard one if that helps: Link. I changed hard sync frames back to 0; I needed it at 1 for better performance with CRT-Royale, but I switched to CRT-Easymode which is much less demanding. I removed the swap interval line (which makes it default to 1) as well; that’s for hitchless scrolling on my 120hz monitor :). You’d of course still only use that config for games that support the DualShock controller though.[/quote]
Ive found the best way to handle multi systems is to have one base config and use.the appendconfig option with only the stuff you want to override from the main config.
Works well with auto save and everything since all changes are only saved to the main cfg.
Analog dpad mode simulates a digital dpad on an analog stick. That’s all. If you want to use just one config the best would be to use dual shock and in core options disable analog toggle. Then you would have to use the in-game witch to enable analogs on the games that support them. That’s Start+Select+all the shoulder buttons.
What’s difference between that and simply map a d-pad to a joystick directly? Or in other words, when would you want to use that?
I had it enabled and as I said my config was working for both types without doing anything.
Analogs are analog. They provide finer control. You can move them a little or all the way allowing you to crawl or walk or run.
What do you mean with anything. Noo inputs at all? Or no analog inputs?
I’m sorry I don’t know where you want to get at. You either do this: input_player1_left_axis = “-0” (use the joystick, digital or analog if supported) or this: input_player1_left_btn = “h0left” (Use d-pad, digital -or analog?-) what you mean is something like this?: input_player1_left_axis = “h0left”
“Without doing anything”. I didn’t need to change device type back and forth between ps1 and DualShock to play on both types of games, 1 config plays both, as I said on analog too, Crash walks and runs if pushed further.