Miru
Well-known member
But then we wouldn’t have 3D movement, and it would be unlikely if we had items or interactive stage hazards.
There’s also the challenge mode from the Master System SOR2.
In Progress Streets of Rage X (Windows / Android) Beta 34
- Thread starter Kratus
- Start date
-
- Tags
- streets of rage
The project is currently under development.
There’s also the challenge mode from the Master System SOR2.
Hey guys, I have great news!
Now F-Games and MaestroDraven are working together. All SOR Remake musics will be replaced by his enhanced and extended tracks in the SORX game.
I will record some videos to show our collaboration in action.
Here's the Maestro Draven links:
https://gettr.com/user/maestrodraven
https://rumble.com/c/c-889197
Now F-Games and MaestroDraven are working together. All SOR Remake musics will be replaced by his enhanced and extended tracks in the SORX game.
I will record some videos to show our collaboration in action.
Here's the Maestro Draven links:
https://gettr.com/user/maestrodraven
https://rumble.com/c/c-889197
oldyz
Well-known member
@Kratus ;
i finally had some 4 player fun this weekend with sor2X, but did notice a minor bug with the controllers:
aside from that, no button crossovers like in other builds, just a bit of confusion.
i finally had some 4 player fun this weekend with sor2X, but did notice a minor bug with the controllers:
Code:
Nightslashers Widescreen 21C using:
Test Build 6392 by Kratus, aka ;
openbor v3.0 build february 15 2021
3 controllers
detects controller 1 as P1
detects controller 2 as P3
detects controller 3 as P2
4 controllers
detects controller 1 as P1
detects controller 2 as P4
detects controller 3 as P3
detects controller 4 as P2
#############################################################
NS & Sor2X using
Test Build 7123 by Kratus, aka ;
openbor v3.0 build 7123 (commit hash: 7123) May 18 2021
3 controllers
detects controller 1 as P1
detects controller 2 as P3
detects controller 3 as P2
4 controllers
detects controller 1 as P1
detects controller 2 as P4
detects controller 3 as P3
detects controller 4 as P2aside from that, no button crossovers like in other builds, just a bit of confusion.
@oldyz
Strange, for me it is working fine. Tested with 4 xbox 360 wireless controllers and every player ID number on the controller matches with every OpenBOR player number.
Some controller problems are related to the operating system detection, not OpenBOR. Try rebooting your system and try again, sometimes it happens in Windows 10.
But where do you get this log? It's a bit different.
@danno
Yeah, it's true
. Did some tests and I think that the new tracks will increase around 40mb compared to remake tracks, the SORR ones are bigger than the original too.
Last edited:
oldyz
Well-known member
Its something i wrote a few hours ago, i am documenting how controllers interact to warn users of what they need to look out for.
OS i am currently running tests with windows 7, using a 360 controller (wired) (xinput), a generic usb (direct input), adaptiod 1 (direct input) & adaptoid 2 (direct input). - they where connected in that order & i can change the ID order using a program called joyID & i get the same results.
maybe having all 4 360's will work well, i will have to test using the wired & other 3 using the dongle, but during the weekend we used Four of this:
sorry for the big image...
anyway 4 of these things (direct input) had us confused a bit & with a simple swap everything was fine...
EDIT: JoyID has no effect on OPenbor, html5 online tests & emulator detect the change but not Openbor
Last edited:
yerboydrew
Member
@oldyzIts something i wrote a few hours ago, i am documenting how controllers interact to warn users of what they need to look out for.
OS i am currently running tests with windows 7, using a 360 controller (wired) (xinput), a generic usb (direct input), adaptiod 1 (direct input) & adaptoid 2 (direct input). - they where connected in that order & i can change the ID order using a program called joyID & i get the same results.
maybe having all 4 360's will work well, i will have to test using the wired & other 3 using the dongle, but during the weekend we used Four of this:
sorry for the big image...
anyway 4 of these things (direct input) had us confused a bit & with a simple swap everything was fine...
Hmm maybe mixing xinput with direct input can cause some unknown issues. I will do the same test as yours to see the results, thanks for the feedback.
Please, would be good to know your new tests after. About the joyID, I did some tests but it seems that it does not work well with xinput.
It's good to know that there's no button crossover anymore
@yerboydrew
Great job! Thanks buddy
oldyz
Well-known member
@Kratus
the test using 4 360 controllers was successful, 1 wired 3 wireless - green light ID's match & no button cross during gameplay.
7123 is very likely to work with parsec with no issues
But i made a test using a couple of dual adapters & this are the results:
all where direct input, no button crossing, so as long as players pay attention to the P# they should have no problems & just swap controllers.
but there is one bad effect
if by any chance one of the dual adpater's port is considered a 5th controller , or one of the other controllers goes beyond Windows order #5, it wont be detected
the test using 4 360 controllers was successful, 1 wired 3 wireless - green light ID's match & no button cross during gameplay.
7123 is very likely to work with parsec with no issues
But i made a test using a couple of dual adapters & this are the results:
Code:
#############################################################
NS & Sor2X using
Test Build 7123 by Kratus, aka ;
openbor v3.0 build 7123 (commit hash: 7123) May 18 2021
controllers
1 mayflash dual adapter n64 1 - n64 2
1 raphnet dual adapter n64 3 - n64 4
no matter how they are plugged, windows orders them this way?
1 controller
detects controller 1 as P2 (n64 adapter port 1, either brand)
2 controllers - two n64 controllers in one adapter, either brand
detects controller 1 as P2 (n64 adapter port 1, either brand)
detects controller 2 as P1 (n64 adapter port 2, either brand)
2 controllers - one in adapter A , other in adapter B
detects controller 1 as P4 (Dominant n64 adapter port 1)
detects controller 2 as P2 (Second in list n64 adapter port 1)
3 controllers
detects controller 1 as P4 (n64 1)
detects controller 2 as P3 (n64 2)
detects controller 3 as P2 (n64 3)
4 controllers
detects controller 1 as P4 (n64 1)
detects controller 2 as P3 (n64 2)
detects controller 3 as P2 (n64 3)
detects controller 4 as P1 (n64 4)all where direct input, no button crossing, so as long as players pay attention to the P# they should have no problems & just swap controllers.
but there is one bad effect
if by any chance one of the dual adpater's port is considered a 5th controller , or one of the other controllers goes beyond Windows order #5, it wont be detected
John_Couey
Member
@oldyz
To be honest, I don't know the compatibility level of OpenBOR with dual adapters.
About the 5th controller, if I'm not wrong the original source code was developed to recognize only 4 devices. I did the same test with 5 xinput controllers and had the same result, the controller 5 was not recognized by OpenBOR, even in previous builds.
To be honest, I don't know the compatibility level of OpenBOR with dual adapters.
About the 5th controller, if I'm not wrong the original source code was developed to recognize only 4 devices. I did the same test with 5 xinput controllers and had the same result, the controller 5 was not recognized by OpenBOR, even in previous builds.
oldyz
Well-known member
@Kratus
i see 2 reasons why dual adapters have problems.
One , i see that dual adapters have the tendency of taking into account the empty port, so you end up with a situation where if an adapter appears after controller #1 in window's device list, it will take up the 2nd & third place, no matter if you only have one device connected to it, so the next controller becomes 4th & any other controller after that becomes 5th - & thus "invisible" to openbor
Two is the way windows orders the devices, if there was a way to change the order easily, then people could change the adapter so it appears as the last in the list, & this way openbor can detect the first(or second) port of the thing as P4.
So far i have noticed that emulators have no problems with devices , because they feature a drop-down menu where you get to choose a device from the list of all available (no matter if there are 5 6 or more) & after you choose, you map - the only issue i have with that technique is that it limits the custom mapping to only one device.
So it seems that the 'easiest' thing to do is to allow Openbor to recognize beyond 4 devices, it would help with the "windows order" issue without resorting to 3rd party programs
i see 2 reasons why dual adapters have problems.
One , i see that dual adapters have the tendency of taking into account the empty port, so you end up with a situation where if an adapter appears after controller #1 in window's device list, it will take up the 2nd & third place, no matter if you only have one device connected to it, so the next controller becomes 4th & any other controller after that becomes 5th - & thus "invisible" to openbor
Two is the way windows orders the devices, if there was a way to change the order easily, then people could change the adapter so it appears as the last in the list, & this way openbor can detect the first(or second) port of the thing as P4.
So far i have noticed that emulators have no problems with devices , because they feature a drop-down menu where you get to choose a device from the list of all available (no matter if there are 5 6 or more) & after you choose, you map - the only issue i have with that technique is that it limits the custom mapping to only one device.
So it seems that the 'easiest' thing to do is to allow Openbor to recognize beyond 4 devices, it would help with the "windows order" issue without resorting to 3rd party programs
Yes, it makes sense. There's some controller updates in test that maybe can solve this problem.
It will treat each device separately, no matter if there are adapters or not.
oldyz
Well-known member
@Kratus , honestly, don´t try to fix the way Openbor assigns the P# - it really does not matter if a controller identified as 1 in windows shows up as P4 in the engine, as long as the mappings match the player you are trying to control, the P# is irrelevant.
I just re-visited the latest official build, while it detects & assigns the P# correctly, it makes a huge crisscrossing twister digital Strabismic mess:
input crossover guide
@oldyz
Don't worry, the update is in test yet and needs some fixes first. In addition, this update is under development by other devs, not me.
To be honest, I think that the current code present in the build 7123 is working well, once it's working as intended with xinput (the most recent driver) and sometimes has only small issues with direct input, like the P# number when using adapters.
Don't worry, the update is in test yet and needs some fixes first. In addition, this update is under development by other devs, not me.
To be honest, I think that the current code present in the build 7123 is working well, once it's working as intended with xinput (the most recent driver) and sometimes has only small issues with direct input, like the P# number when using adapters.
lol
Why Shiva's belt look like guts?
Bloodbane
Well-known member
The 3rd stage of Nightslashers starts from dungeon with prisoners. There's prison stage in Maximum Carnage (not sure which stage but it's not early stages for sure).
Or if you'd like, you can paxplode Marvel Infinity War by zvitor and copy prison background.