Flycast Arcade Standalone | All In One Config | Atomiswave, Naomi 1 & 2 | Controls Pre Mapped, LightGun Games Calibrated & Light Gun Ready, All content pre unlocked & sooo much more 1.0.1

Just to reply to your comment,  like you say its come a long way and hopefully they can add the stacked inputs you want as well to make this a bit easier for you.

BTW is this set up with version 2.3?

I just noticed they released 2.3 stable 6 hours ago and have added Gamepad dead zone and saturation settings which was only available in an old dev branch beforehand.

Edited March 16 by Baggio

Just FYI, i tried playing Dolphin Blue and DemoFist on Atomiswave and neither game allows Analog stick to work (using XBOX 360 wired controller)

D-Pad is fine, but was not sure if you had said all games allowed both.

Thanks again for all your work 👍

Edited March 17 by zugswang

7 hours ago, zugswang said:

Just FYI, i tried playing Dolphin Blue and DemoFist on Atomiswave and neither game allows Analog stick to work (using XBOX 360 wired controller)

D-Pad is fine, but was not sure if you had said all games allowed both.

Thanks again for all your work 👍

Yeah they should. Lemme fix and update

I've been through a few as well and only the D-pad is working (Dirty Pigskin, Beachspikers, Melty Blood, Virtual Striker, Virtual Tennis , WWF and Metal Slug)  This is with an Xbox One Elite Controller

Edited March 17 by Baggio

1 hour ago, Baggio said:

I've been through a few as well and only the D-pad is working (Dirty Pigskin, Beachspikers, Melty Blood, Virtual Striker, Virtual Tennis , WWF and Metal Slug)  This is with an Xbox One Elite Controller

Ahh bum, I'll let yall know when it's fixed.

I've been having a play and I don't even think mine is loading the configs for the most part.  The most obvious is Shootout Pool where the left click isn't pulling the cue, I have to hold the A button on the controller.  So i went into the game and its controls menu and every mapping option says "make game config" instead of delete config if one was already there.

Edited March 17 by Baggio

Right, so I have found out why the controls aren't loading and why the analog didn't work with the D-pad.  It's because the configs are named after the controller's name!!   So mine are called

SDL_Xbox One Elite Controller_ALIEN FRONT_arcade.cfg

and not

SDL_Xbox 360 Controller_ALIEN FRONT_arcade

This is also inside the configs as well, with 

mapping_name = Xbox 360 Controller

being

mapping_name = Xbox One Elite Controller

Now on my end, that's an easy fix but it may throw a spanner in the works for you with the number of controllers out there I don't think you could make a setup that fits everyone.

Regarding the mouse configs not loading though, both configs just start with "RAW_HID-compliant mouse" so I'm not sure where to go with that unless they are set up with device IDs somewhere else, but I'll keep having a play to see if i can figure it out.

Edited March 17 by Baggio

Oh sorry just to add i have another Xbox wireless pad and when that's plugged in thats name is

Xbox One S Controller

So I think if I want to use both I'd have to double up all the profiles and rename one lot to "Xbox One Elite Controller" and the other lot to "Xbox One S Controller"

@zugswang have a look what your controllers named as and try renaming one of the config files to it.

I have just open a can of worms. The Keyboard and mice are by device IDs mine are

Keyboard 
RAW_HID Keyboard Device [VID_062A&PID_4C01&MI_00]_SHOOTOUT POOL_arcade

Mouse
RAW_HID-compliant mouse [VID_062A&PID_4C01&MI_01&Col01]_SHOOTOUT POOL_arcade

So these will be different for each and every person for the most part.  

On a positive note, it seems like the latter (the IDs) were only added in the latest release as the keyboard and mouse configs work out of the box with version 2.2 so that could possibly be fixed.  The joypad controls are still labelled differently though but I think this can be sorted (as well as reverting back to the old keyboard/mouse naming) if someone could put this forward to Flyinghead on his github who can explain this a lot more logically than I can 😂.  All we need is the controller configs just to be named generically like just SDL_Controller_XXXXXXX.cfg so they work for everything like the old mouse and keyboard configs used too.

Edited March 17 by Baggio

@Baggio

Ok, so I'm about to do another pass on every game to make sure everything is at least working my end. The d-pad thing may just be a mapping issue. Did you activate rawinput when playing shootout pool?

For the controller ID's you are probably correct. This may actually potentially kill the Standalone project. I have seen the github request for it to be reverted back to how it was but didn't see it in the changelog.

If I create some mappings using 2.3 can you check to see if you can use them with your elite and s xbox controllers and keyboard?

If we can get basic XINPUT as well as SDL it would be awesome but I doubt it atm. The only other way around it is to put out config files named after every type of xbox controller SDL picks up. Fudge that man, if its like 4 or 5 variants ok, but if it's like loads, naaa. I don't see a way to find a workaround for this one TBH. Unless your controller shows up as 'Xbox 360 Controller' this is pretty much useless. Funny thing is if you have a PS4 controller and use DS4 it'll just work.

How many types of xinput controllers are there that SDL will pick up?  I really thought SDL would pick up XINPUT controllers all the same or at least apply the same mapping. Fuckin school boy error. I cant actually believe this is all but wasted lol. I'm proper miffed with myself more than anything.

Did I mention I hate SDL. I'm gonna put this on ice till I can figure something out. RetroArch for the win AGAIN probably.

Actually, if the ID's thing is fixed for keyboard and mice I could make a hybrid build. The main reason for using standalone is for the trackball games plus a few other outliers like Mushiking and F355. But will be complicated setup.

29 minutes ago, Warped Polygon said:

@Baggio

Ok, so I'm about to do another pass on every game to make sure everything is at least working my end. The d-pad thing may just be a mapping issue. Did you activate rawinput when playing shootout pool?

For the controller ID's you are probably correct. This may actually potentially kill the Standalone project. I have seen the github request for it to be reverted back to how it was but didn't see it in the changelog.

If I create some mappings using 2.3 can you check to see if you can use them with your elite and s xbox controllers and keyboard?

If we can get basic XINPUT as well as SDL it would be awesome but I doubt it atm. The only other way around it is to put out config files named after every type of xbox controller SDL picks up. Fudge that man, if its like 4 or 5 variants ok, but if it's like loads, naaa. I don't see a way to find a workaround for this one TBH. Unless your controller shows up as 'Xbox 360 Controller' this is pretty much useless. Funny thing is if you have a PS4 controller and use DS4 it'll just work.

How many types of xinput controllers are there that SDL will pick up?  I really thought SDL would pick up XINPUT controllers all the same or at least apply the same mapping. Fuckin school boy error. I cant actually believe this is all but wasted lol. I'm proper miffed with myself more than anything.

Did I mention I hate SDL. I'm gonna put this on ice till I can figure something out. RetroArch for the win AGAIN probably.

Actually, if the ID's thing is fixed for keyboard and mice I could make a hybrid build. The main reason for using standalone is for the trackball games plus a few other outliers like Mushiking and F355. But will be complicated setup.

I'll test out the mappings for you yeah, will it just be changing the names like I mentioned or have you thought of something else?  I already changed all the Xbox 360 ones to Xbox One Elite and it worked great my end and using 2.2 everything works perfectly now.   Here's the zip if you want to use them. Xbox One Elite mappings.rar

Where did you see the request on github for the names to be reverted back?  Maybe if we all chime in he will add it in the next dev build so we can as least use a version of 2.3.

BTW you haven't wasted your time doing this, it still works great with 2.2 and when he reverts back to the old keyboard/mouse mapping it will with 2.3 as well with some minor tweaks people will have to do in with a couple of clicks in notepad++ for the controllers so all is good

Oh and I wish you hadn't mentioned Shootout Pool Prize,  i played the other one a bit ago but this prize one is highly addictive for us Brits 😂

Edited March 17 by Baggio

20 minutes ago, Baggio said:

I'll test out the mappings for you yeah, will it just be changing the names like I mentioned or have you thought of something else?  I already changed all the Xbox 360 ones to Xbox One Elite and it worked great my end and using 2.2 everything works perfectly now.   Here's the zip if you want to use them. Xbox One Elite mappings.rar

Where did you see the request on github for the names to be reverted back?  Maybe if we all chime in he will add it in the next dev build so we can as least use a version of 2.3.

BTW you haven't wasted your time doing this, it still works great with 2.2 and when he reverts back to the old keyboard/mouse mapping it will with 2.3 as well with some minor tweaks people will have to do in with a couple of clicks in notepad++ so all is good

Oh and I wish you hadn't mentioned Shootout Pool Prize,  i played the other one a bit ago but this prize one is highly addictive for us Brits 😂

It was the keyboard ID thing i saw a github request for, not controller ID's.

The mapping names will need to be changed to match your controller. The upshot of this is that it may also work for any controller. I need to test that.

I was thinking just provide the xinput ones, simply bulk rename them to the ID's for the common xinput controllers for everyone to select from or just include all of em so you cant miss. 

I don't think bombarding Flyinghead will help TBH, it will require an entire input system to be implemented that for all intents and purposes isn't really needed. It's only us that really want it for pre config purposes. I cant say I'd fix something that isn't really broken to help everyone be lazy lol. Maybe I would but......

So really the only thing that can save this project is to duplicate & rename all the mapping files to every possible xinput controller ID that SDL will pick up, and include them all. Thank christ for Bulk Rename Tools.

So to start lol we have - 'Xbox 360 Controller' - Xbox One S Controller' - Xbox One Elite Controller'.........

Do Logitec and other 3rd party xinput controllers show as xbox controllers with SDL? Mate, I hate SDL......Khhhaaaaaaaaaaaan.

 

Edited March 17 by Warped Polygon

22 minutes ago, Warped Polygon said:

It was the keyboard ID thing i saw a github request for, not controller ID's.

The mapping names will need to be changed to match your controller. The upshot of this is that it may also work for any controller. I need to test that.

I was thinking just provide the xbox ones, simply bulk rename them to the ID's for the common controllers for everyone to select from or just include all of em so you cant miss. 

I don't think bombarding Flyinghead will help TBH, it will require an entire input system to be implemented that for all intents and purposes isn't really needed. It's only us that really want it for pre config purposes. I cant say I'd fix something that isn't really broken to help everyone be lazy lol. Maybe I would but......

So really the only thing that can save this project is to duplicate & rename all the mapping files to every possible xinput controller ID that SDL will pick up, and include them all. Thank christ for Bulk Rename Tools.

So to start lol we have - 'Xbox 360 Controller' - Xbox One S Controller' - Xbox One Elite Controller'.........

 

I'm just thinking that the controller is just the same as the mouse/keyboard. 2.2 worked without the devices ID's so i don't see why the controllers need IDs on the as well, but then again i know nothing about this 😂

I'll add a bug report tomorrow anyway because I would imagine the keyboard/mouse changes with this latest version will have broken a lot of people's configs as well with the new renaming.

As for controllers, @zugswang wired one isn't working so his may be different to the 3 we have, then maybe Xbox Series X, Xbox Series X Elite etc  and we won't even mention controllers outside of Xbox and PS 😂

 

Edited March 17 by Baggio

2 minutes ago, Baggio said:

I'm just thinking that the controller is just the same as the mouse/keyboard. 2.2 worked without the devices ID's so i don't see why the controllers need IDs on the as well, but then again i know nothing about this 😂

I'll add a bug report tomorrow anyway because I would imagine the keyboard/mouse changes with this latest version will have broken a lot of people's configs as well with the new renaming.

As for controllers, @zugswang wired one isn't working so his may be different to the 3 we have and we won't even mention controllers outside of Xbox and PS 😂

 

Ahh Fuck IT. RetroArch for the majority of games and Standalone for the ones that absolutely need it like trackball games and a few other outliers. Maintaining a database of mappings for this is not the one, I actually don't have the time lol. I really would like every game under one emulator but alas...

8 hours ago, Warped Polygon said:

Ahh Fuck IT. RetroArch for the majority of games and Standalone for the ones that absolutely need it like trackball games and a few other outliers. Maintaining a database of mappings for this is not the one, I actually don't have the time lol. I really would like every game under one emulator but alas...

@Baggio was right.

It's a simple Bulk Rename Utility change of all XBOX 360 Controller names to the name of your controller.

I did it on mine (renamed inside and out outside of the mappings to my controller) and all now works perfectly 👍

Now I know why others were not working in the past.

Thanks again

Edited March 18 by zugswang

8 hours ago, Baggio said:

I'm just thinking that the controller is just the same as the mouse/keyboard. 2.2 worked without the devices ID's so i don't see why the controllers need IDs on the as well, but then again i know nothing about this 😂

I'll add a bug report tomorrow anyway because I would imagine the keyboard/mouse changes with this latest version will have broken a lot of people's configs as well with the new renaming.

As for controllers, @zugswang wired one isn't working so his may be different to the 3 we have, then maybe Xbox Series X, Xbox Series X Elite etc  and we won't even mention controllers outside of Xbox and PS 😂

 

I have a PDP Rock Candy XBOX Controller.

Changed names as stated and all now working fine 👍

9 hours ago, Warped Polygon said:

Ahh Fuck IT. RetroArch for the majority of games and Standalone for the ones that absolutely need it like trackball games and a few other outliers. Maintaining a database of mappings for this is not the one, I actually don't have the time lol. I really would like every game under one emulator but alas...

I’d stick with this mate tbh.  Like we said it’s only a simple change in a bulk renamer and it’ll work for everyone. 
 

As we are all here I’m sure we have spent waaayy more time doing a lot more than that (don’t mention image renaming to me 😂 )

You’ve done all the leg work so I’m sure nobody is going to mind doing that little change if needed.  

Amazing work as usual! So no luck with the Brightness hack on Metal Slug 6 right?

Can you please advise how to get to the debug menu on this config? I wanted to change the brightness myself on the debug, then Save State. That way, when I run Mslug6, I would just Load State and Brightness is at the right level!

Also,can you please upload the NVRAM for 'Kenju' with the English language and all characters unlocked? And NVRAM for 'Force Five' as well.

Thanks!

Edited March 19 by GodElite

Hi @Warped Polygon!

While playing with a xbox one controller using left analog stick, its pretty easy to press left stick button, so game enters in "test mode" and when you press it again to exit "test mode" it starts the game again.

Not sure if is this a right behaviour or not, but i would like to know if is there any chance to remove this assignment or at least change it to right stick button instead.

Thanks in advance.

On 4/3/2024 at 6:46 PM, ci2own said:

Hi @Warped Polygon!

While playing with a xbox one controller using left analog stick, its pretty easy to press left stick button, so game enters in "test mode" and when you press it again to exit "test mode" it starts the game again.

Not sure if is this a right behaviour or not, but i would like to know if is there any chance to remove this assignment or at least change it to right stick button instead.

Thanks in advance.

Hi @ci2own

Yes I was thinking this may crop up. It was a hard choice to keep or discard test & service on L3&R3. I kept it in to make it easy to adjust stuff if needed. But now....yeah I'll remove those inputs from the controller entirely so they cannot be accidentally pressed. You can map test and service to the keyboard in the global settings. Just set it without a game loaded to make sure only global defaults are being adjusted.

Keep an eye out over the next couple of days.

@Warped Polygon Hi mate i had an alert about what i used to edit the files but it's disappeared.

I sent you a script a while back but have made a new one that's easier to use and has a GUI.

It's here if you want to add it to your post.

 Controller_Name_Changer.zip

 

You can either put the .exe in the \Flycast\mappings folder and it will populate the path automatically or run it from anywhere and browse for that path.  Pressing the Escape button will close the script.

Edited June 22 by Baggio

29 minutes ago, Baggio said:

I sent you a script a while back but have made a new one that's easier to use and has a GUI.

It's here if you want to add it to your post.

@Baggio

Cheers man. Windows defender came down on it hard. I'm sure prob & false positive but.... people are weary.

I figured out you only need to rename the mapping cfg file to match your controller. It'll still have 'Xbox 360 Controller' in the file itself but seems to have no impact ad it's just an ID marker.

38 minutes ago, Warped Polygon said:

@Baggio

Cheers man. Windows defender came down on it hard. I'm sure prob & false positive but.... people are weary.

I figured out you only need to rename the mapping cfg file to match your controller. It'll still have 'Xbox 360 Controller' in the file itself but seems to have no impact ad it's just an ID marker.

No worries.

I can assure everyone it's safe,  for some reason Windows Defender doesn't like complied Ahks. https://www.autohotkey.com/boards/viewtopic.php?t=56520

Here's the original file so anyone can see what it does and if you have Autohotkey installed you can just run the Ahk if you want as is for it to work or right-click it and compile it yourself into an executable but that's not needed if you have ahk installed aready.

Controller_Name_Changer.ahk

Edited June 22 by Baggio

@Baggio @zugswang

Yooo, I've had a thought but wanna get your opinions. 

With the SDL controller remaps for XINPUT it may be better to have a 'master' folder containing as many xinput controller variants as possible. This way even if your 2nd, 3rd or 4th controllers are different you'll still be able to play without having to rename anything or move files about. Flycast will just pickup what you happen to have plugged in at the time (if there are mappings for that variant).

As for RawInput devices, these are now ID specific. Meaning these will absolutely need to be renamed. I'm prob gonna provide mappings with [VIDMOUSE1]/[VIDMOUSE2] & [VIDKEY1]/[VIDKEY2] in the mapping name so you can easily use find/replace for 2 players using separate devices aka. mice/lightgun &/or keyboards.

Ya'll think that's a better way forward?

Edited June 26 by Warped Polygon

18 minutes ago, Warped Polygon said:

@Baggio @zugswang

Yooo, I've had a thought but wanna get your opinions. 

With the SDL controller remaps for XINPUT it may be better to have a 'master' folder containing as many xinput controller variants as possible. This way even if your 2nd, 3rd or 4th controllers are different you'll still be able to play without having to rename anything or move files about. Flycast will just pickup what you happen to have plugged in at the time (if there are mappings for that variant).

As for RawInput devices, these are now ID specific. Meaning these will absolutely need to be renamed. I'm prob gonna provide mappings with [VIDMOUSE1]/[VIDMOUSE2] & [VIDKEY1]/[VIDKEY2] in the mapping name so you can easily use find/replace for 2 players using separate devices aka. mice/lightgun &/or keyboards.

Ya'll think that's a better way forward?

That sound good to me mate, I currently have Xbox Elite and Xbox one configs in there and it works great.  

The only issue with the master folder would be actually finding the names of the controllers.  It’s @zugswang PDP Rock Candy Controller that has me thinking the there will be quite a lot of Xbox variants, and as for third party ones who knows.

Edited June 26 by Baggio