The Bliss-Box 4-play Thread!

[ulao]

Quote

If you use RetroPad mapping for BlissBox, it creates issues with XBOX360, since you're changing that mapping...

That's why Bliss-Box has a 360 mapping option.

[newoski]

If you use RetroPad mapping for BlissBox, it creates issues with XBOX360, since you're changing that mapping...

That's why Bliss-Box as a 360 mapping option.


1. Where is an explanation of the feature, how it works, how to enable it etc
2. I don't think this will help, as the button mappings would still be different, no? Or are you saying that it essentially mirrors RetroArch's 360 mappings???

Sent from my HTC6535LVW using Tapatalk

[iNTiGOD]

newoski FIY I'm not using xpadder at all (why are you using it? Is your ipac in game pad mode?
I don't have Xbox controllers.

My 4-play is being used for nes, snes, n64, megadrive, ps1, ps2, and pcengine controllers.

It's late here and I just read your setup. Wow it sounds super complicated, my head can't make sense of it. I'll reread in the morning.

[ulao]

I'm not sure it will help either but I think its good to know the options exist. As with all products on the market nowadays, Bliss-Box also has a live manual. http://skunx7.wixsite.com/bliss-box/support

Directly from the manual.

Firmware 1.56 or higher
Alternative Mapping: Two main Buttons + Start, then D-Pad direction to set mode, Up = Normal Mode; Down = Sony Playstation 3 Mode; Right = Xbox 360/One Mode; LEFT = Arcade Mode (available since 1.57).

Modes:
Sony Playstation 3 – Mimics a PS3 controller layout. Start + select, is the HOME button.
Xbox 360/One - Mimics a XBOX controller layout. Start + select, is the HOME button
Arcade – This mode is for arcade setups. All buttons map in an 6 button arcade like style and all d-pad controllers without analog will send the d-pad as digital buttons.  
Normal – This is the normal mode best set up for running emulators.

 

 

 

[newoski]

Respectfully, the manual needs some additional info. There's not enough info or context to make sense if it. Based on that description, the only benefit is the ability to press XBOX guide button?

Sent from my HTC6535LVW using Tapatalk

[iNTiGOD]

ulao just a quick question.
I am having trouble with one particular nes controller of mine. Not sure if the board is gone. It doesn't seem to detect consistently when I'm plugging it in across any of the ports (i have another nes controller that works fine).

I'm suspecting it is in "Atari mode". I press a or b and the input is left.
What should I try? Should I unplug the USB? Or press the reset button or hold the reset button? Or something else.
Thanks in advance.

[newoski]

intigod... xpadder for xbox360 and gamepads. Ultimarc MinIPAC is in keyboard mode. Complicated, yes, but necessarily so to do all that I have it setup to do. The hurdles I'm trying to overcome are basic though

Sent from my HTC6535LVW using Tapatalk

[ulao]

Well that was taking out of contents. the above lines may help a bit where it explain that you press buttons on a controller to activate modes. naturally pasting a live doc here would be very counter productive.

Quote

I'm suspecting it is in "Atari mode". I press a or b and the input is left.
What should I try? Should I unplug the USB? Or press the reset button or hold the reset button? Or something else.
Thanks in advance.

 

Your guess is correct, its a loose wire inside the nes controller.

 

[newoski]

Well naturally that was taking out of contents. the above lines may help a bit where it explain that you press buttons on a controller to activate modes. Pasting a live doc here would be very counter productive.
 
 

I've read the live doc. I'd love to chat with you to try to assist cleaning up some ID the manual /docs. There's some gaps that could be easily addressed. The functionality has so much potential, I'm sure a lot of it is just needing a bit better explanation. Would love to volunteer to help address some of the confusion. Shoot me a PM

Sent from my HTC6535LVW using Tapatalk

[ulao]

Here is a small glimpse at the new API and how it will handle button mappings. In the image each button follows this.

//default: []  X   /\  0   st sl  L1  R1  L2  R2  up  dn  lf  rt  lck rck *   home
The code in the image is setting HID assignments to that set up. It's based from the psx controller but you can use it for anything as Bliss-Box has a global mapping. The API will also be able to give you the controller connected and with that you can apply  new mapping to the adapter.

 

[ulao]

newoski, please just get with AVAR. He has pretty much done what you are offering. I'm not really the "document" type. I thought he did a pretty good job but maybe send him a PM. He'd be happy to help.

[newoski]

newoski, please just get with AVAR. He has pretty much done what you are offering. I'm not really the "document" type. I thought he did a pretty good job but maybe send him a PM. He'd be happy to help.

Genuinely nog trying to be critical of anyone. Just looking to help. Will do

Sent from my HTC6535LVW using Tapatalk

[ninja2bceen]

I really think if you switch from xpadder to joytokey all your problems will be solved. Just map the same as what you did with xpadder in terms of keys. That is what I had to do

[newoski]

Doesn't fix my issue, which has little to so w xpadder directly... unless you can do multiple layouts per system

Sent from my HTC6535LVW using Tapatalk

[ninja2bceen]

Yes you can. In joy to key I have a profile for each port essentially for each player

[newoski]

Yes you can. In joy to key I have a profile for each port essentially for each player

I can do that in xpadder. No mapper will solve the problem I'm describing, outside of being able to remap bliss box mappings.

Can you send me your joy2key full folder and mappings? Want to take a look

Sent from my HTC6535LVW using Tapatalk

[ninja2bceen]

Nintendo Entertainment System.cfg

[newoski]

Thanks, but I'm looking for your joy2key folder/mappings

Sent from my HTC6535LVW using Tapatalk

[ninja2bceen]

which file do you need exactly?

[newoski]

which file do you need exactly?

I'm not sure, as I only know xpadder. The equivalent of your controller layouts and per say mappings.

Sent from my HTC6535LVW using Tapatalk

[Avar]

Auditing Bally Astrocade brought to mind something I wanted to remind Bliss-Box users of. Namely that Bally Astrocade controllers do work via Bliss-Box, are super cool and unique, and kinda hella rare. As one of the oldest detachable controllers in existence it might be worth your while to track some down while they're still relatively reasonable to find online if they interest you. I had to buy a full working Astrocade to get mine due to time constraints for firmware testing. In general, there are several controllers and peripherals with pretty limited release runs that are only going to become more scarce as Bliss-Box opens up the market to basically everyone who has a PC, so you can anticipate rare controllers to become even more of a commodity, particularly following Bliss-Box's next big release. Some other things that are particularly hard to find: Atari Jaguar Pro Controllers (the Jag is pretty much useless w/o this baby), GCE Vectrex controllers (really cool to have and hard to find in good working condition), and basically any non-JP controller. Anything that released in Asia for the most part is still extremely common with a few exceptions.

[Avar]

There have been two pretty awesome Bliss-Box updates today! First, Ulao's started a nice dev vlog to tease what's coming in Bliss-Box firmware 2.0:

 

and Bliss-Box has also started showing off some of the world's cool controllers on their FB:

Enjoy!

[ulao]

Avar, as always thank you for spreading the word. I did want to add one of the more impressive new features, LCD writing.  This is going to be a very easy mechanism for emulation developers. I strongly encourage everyone to spread the word on this. You do not need any drivers or plugins just  way to send data to basic HID calls. I'll be releasing the source code for the command line and C# to show how simple this will be.

 

[/video]

[newoski]

On 6/4/2017 at 2:33 PM, ulao said:

Avar, as always thank you for spreading the word. I did want to add one of the more impressive new features, LCD writing.  This is going to be a very easy mechanism for emulation developers. I strongly encourage everyone to spread the word on this. You do not need any drivers or plugins just  way to send data to basic HID calls. I'll be releasing the source code for the command line and C# to show how simple this will be.

 

[/video]

Will command line / API programming of controllers be available on the controllers level, or the Port level only?

Which, for simplicity sake, is to say... 

If we were only using Port1, would we be able customize the button programming for NES, SNES, and N64 controllers, independently of eachother? Or would we only be able to make changes at the Port, not controller, level?

[ulao]

All API function go to port's, the controllers are not part of the Bliss-Box. The Bliss-Box interfaces with controllers.  In many cases we send data directly to the controller but that still goes thru the ports. 2.0 will have 4 port ID's like the 4-play fix. When you first flash 2.0 to all ports the ID's will be the same. In the software you set what ports you want to be what players just like the 4-play but with a GUI. Then you set each port up the way you want it, options, config, etc. And communicate with a controller attached to that port. Once the software is done it would be like saying player 1 -> send LCD image. or player 3-> set mappings.