Bliss Box 4-play compatibility

[ninja2bceen]

My Nes ones work. Be sure after you have a controller in to recalibrate it and it will work every time. Recalibrate can be found by right clicking the port, game settings and is in the first tab.

The only problem I've discovered is if you plug in ps2 controller in port one or any other analog type controller and you try and plug in port two another analog controller that port two will disappear. If you unplug blissbox and try again but with player two insert snes or another non analog controller discover it, unplug and plug in ps2 in port two things will work. Other than this it should work flawlessly on 1.54

Tapatalk signature

[ulao]

. I'm finding that I have to constantly press the reset button for 2-3 controllers to register correctly otherwise the "a" button only registers as a direction input.

 

iNTiGOD, I'm not sure the issue but this may help. First, the a button mapping to a direction means the 4-play has not detect the nes and it in atari mode. When pressing reset you should wait 5 seconds before pressing any buttons. Also If the controller works once, it's not the controller that is at fault. Lastly if you are swapping you do not need to hit reset.

 

Calibration is an OS level command and will not effect what you are describing. Any calibration that appears to fix this issue is purely coincidence. Calibration will reduce the empty space at the top and bottom of analog responses. So it will take this [_____##########_____] and make it  [#################].  Resetting calibration undoes this. So if you tried to calibrate and messed it up, you can reset the OS back to the default calibration. The NES does not use analogs thus is not going to change anything about it. Also calibrating the 4-play is largely pointless as each controller responds a different way. If you calibrate for n64, the GC will not work as it has a different response. Most emulators have their own calibration (range/dead zones) and is suggested to use that instead. 

[ninja2bceen]

I had the same issue before and only pressing reset after you plug in the controller in the one port is needed. That helped but I had to reset calibration. It only happened to nes but I did the calibration for all my controllers just to be safe havnt had an issue with the buttons since

For swapping, an example is this

Plug in bliss,

Plug in nes in port 1

Press reset so it reads nes

If you want to change controllers to say snes... Unplug nes and plug ini snes in port 1. No reset is needed since bliss already knows port 1 is being used

Sent from my iPad using Tapatalk

[iNTiGOD]

iNTiGOD, I'm not sure the issue but this may help. First, the a button mapping to a direction means the 4-play has not detect the nes and it in atari mode. When pressing reset you should wait 5 seconds before pressing any buttons. Also If the controller works once, it's not the controller that is at fault. Lastly if you are swapping you do not need to hit reset.

 

Calibration is an OS level command and will not effect what you are describing. Any calibration that appears to fix this issue is purely coincidence. Calibration will reduce the empty space at the top and bottom of analog responses. So it will take this [_____##########_____] and make it  [#################].  Resetting calibration undoes this. So if you tried to calibrate and messed it up, you can reset the OS back to the default calibration. The NES does not use analogs thus is not going to change anything about it. Also calibrating the 4-play is largely pointless as each controller responds a different way. If you calibrate for n64, the GC will not work as it has a different response. Most emulators have their own calibration (range/dead zones) and is suggested to use that instead. 

 

I tried and tried to get this nes controller detected but It always stays in atari mode. Pressed the button 5 times and its still stuck in atari mode. 

I'm sure its the controller as my other nes controller works everytime (could be the board). I have another 3 on order. Will report soon.

[ninja2bceen]

Make sure all the switches are down on the back of the device? Did you recalibrate the controller yet?

Tapatalk signature

[iNTiGOD]

Make sure all the switches are down on the back of the device? Did you recalibrate the controller yet?

Tapatalk signature

 

I'll have to check the dipswitches... but AFAIK they arent all down but nor should they be?? Maybe ULAO can confirm.

Re-calibrating the controller makes no difference because it windows doesnt recognise the inputs in the first place.

[ninja2bceen]

On the back is a pic. 5 and 6 need to be down for 4 play to be on

Try this

Plug in bliss and notice 4 ports show up

Plug in nes in port 1

Preset reset once in port 1, notice port 1 disappears and reappears in device manager

Right click port one in device manager and go to game controller

Click port 1 and click properties

Do you see buttons flash when you push the buttons? If not go to the settings tab in this window and reset to default/recalibrate

Tapatalk signature

[ulao]

yeah I don't know what he is talking about with calibration, its clearly not the issue. Calibration is for analogs not buttons.

 

I tried and tried to get this nes controller detected but It always stays in atari mode. Pressed the button 5 times and its still stuck in atari mode. 

I'm sure its the controller as my other nes controller works everytime (could be the board). I have another 3 on order. Will report soon.

 

If one controller works and not the other it's the 1)plug, the 2)controller, or the 3)speed in the code.

 

1) Its possible one of the pins are not making contact. Many ways to figure that out, if you need tips ask.

2) if it works on a nes or another adapter this is not it.

3) You could send the controller in and I can take a look.

[ninja2bceen]

Can anyone confirm if this happens to you or not?

Basically what I'm seeing is if you plug in two analog controllers by themselves, player two vanishes. I have a work around though. Do you see this too?

Plug in bliss

Plug in ps2 in port 1 press reset

Plug in n64 in port 2, press reset

Port 2 disappears

If you do the same thing above but do the following first it works

Plug in bliss

Plug in ps2 in port 1 press reset

Plug in snes in port 2, press reset

Unplug snes from port 2

Plug in n64 in port 2

It works

Tapatalk signature

[iNTiGOD]

Can anyone shed some light on getting dreamcast controllers setup in nulldc?

Which plugins are used? Perhaps a screenshot or two?

/update

I've managed to setup most of the DC controller user the pakupaku plugin (all buttons and triggers).

Where I get stuck is that nulldc doesn't seem to detect my analog sticks (2 different controllers).

/update 2

Found a different pakupaku plugin and all is working perfectly. Will link it in the coming days.

Merry Christmas everyone.

[ninja2bceen]

I think I'm getting these as stocking stuffers. If so I'll be testing them :-)

Tapatalk signature

[iNTiGOD]

Just an update peepz on the bliss box, with dreamcast controllers in nullDC (ver 104).

I have attached an updated dll file which helped me setup these controllers.

Place this file within nulldc\plugins\       and overwrite (backup of course) the .dll file if you have a copy already.

The inputs are then recognised.

 

Hope this helps others.

 

PuruPuru_01.zip

[JoeC3109]

Quick question, didn't see anything in the earlier pages. Did anyone have trouble initially getting controllers recognized at all? I plugged in my bliss box, and 4 items called 4 play pop up in the control panel. However, I read that once I plug my controller in, a sound should be made and the controller should be recognized in windows. Nothing pops up, and I've tried with 5 different controllers. Flashed to the newest firmware as well (im on windows 10). I contacted blissbox directly, but I'm wondering if anyone else had a similar problem in the beginning.

[iNTiGOD]

Quick question, didn't see anything in the earlier pages. Did anyone have trouble initially getting controllers recognized at all? I plugged in my bliss box, and 4 items called 4 play pop up in the control panel. However, I read that once I plug my controller in, a sound should be made and the controller should be recognized in windows. Nothing pops up, and I've tried with 5 different controllers. Flashed to the newest firmware as well (im on windows 10). I contacted blissbox directly, but I'm wondering if anyone else had a similar problem in the beginning.

Yes.

For me it was more about the way I was connecting everything.

Have you followed all the steps outlined in this thread on flashing the device?

Have you checked you jumper settings are correct?

Also remember to connect your controllers to the HDMI cables first, then connect them to the 4play. Once connected, the last step is to plug in the USB cable (not the other way around). They should initialize then.

If not try pressing the reset button for the the port that is giving you trouble.

Lastly I should note that I did have a faulty USB cable. I wasn't getting consistent connections until I tried a spare USB cable.

I changed my USB cable then flashed.

You may have had a bad flash???

ULAO should be floating around here to give some tips about this or just follow Ninjas great guide in the thread and reflash.

[atarigalore]

So every one know what ninja keeps saying for flashing tutorial is wrong and unneeded....

My 4-play fix custom flasher..:

It does not just rename ports.. it says so on my site... And if you read the box

That comes up when first double clicking it.

It flashes hex edited (aka hacked) firmware files so each port has sequential usb product id's (aka. PID's).

You ONLY need to use my flasher when you want to update 4-play firmware.

If you ever run the OFFICIAL flashtool it will UNDO and OVERWRITE my hacked pid's and make all ports identical again causing the port order to become random again.

I haven't even used the official flashtool that's on Ulao's site since i had the beta box before the retail units even came out.

And when I got my retail unit I have ONLY updated the firmware with my custom flasher.

If you completly comprehend all of the details about my flasher you would understand.

If you ever have a problem flashing, exiting my flasher then reopening does nothing... If you have winrar or 7zip installed you can just extract my flasher as all it is is a self extracting zip file made with winrar that runs the main file.

The reason for not needing to close my flasher is that it just runs a whole lot of .bat files.

The main file is just the menu.

After picking the port to flash it runs a different .bat file and if there is an error like the button was not held it stops running that .bat file and hence the flasher.exe file.

And goes back to the prompt asking for port number when picking port number again it then relaunches the .bat file that starts the flash all over again.

So if there is an error no matter what worked for you it is IMPOSSIBLE and confusing to others for that long flashing tutorial.

My flasher I made for it to TELL the person flashing what to do step by step.

It's far from confusing and no tutorial needed.

Not yelling at you ninja, just sounds like that tutorial is long not needing those steps and a few people have sounded almost afraid to update firmware now.

Tutorial:

1. Download my flasher.

2. Right click run as admin.

3. Follow prompts.

4. Done.

[atarigalore]

https://m.facebook.com/4playfix

[atarigalore]

And I do try to update my custom flasher every other week or less to keep up with his newest firmware.

Also a good thing about my firmware flasher all versions are hacked down to 1.0 so if you have something not quite right, like some specific case where say a certain model controller doesn't work right or doesn't work right after using a specific system controller or something.

So then you could use my flasher and flash an older firmware and maybe find it works on say 1.43 or something then maybe it could help ulao figure out what changed in the code.

Or if the older firmware works for what ever your problem might be and all the other controllers work too then just stay on the older firmware.

Updating the firmware is only needed if you have some issue with your controller or controller combination and it's fixed in newer firmware.

Otherwise updating just to do it does nothing.

[ninja2bceen]

Thanks atari! Correct my tutorial was a description of every step I took and its problems things brought. Integrating with hyperspin was uncharted territory and there was no documentation in general. You are correct that the flashing is simple once you understand what is needed. I will say your unofficial version is the only way for me at least to be able to utilize bliss with hyperspin. Each port needs to be unique. Thanks for coming up with this

Hey while I have you, I have the unofficial 1.54 flash from the first week of dec and I have a bug here but a clear work around, things only freak out in the specific combination of things. If you speak with Sean a lot then I'm sure he can share those threads but it sounds like you are unaffiliated there

The instance is plug in ps2 in port 1, press reset so the controller reads. Then plug in ps2 (or n64) controller in port two (or any port), press reset and notice that player two (or whatever you chose) never comes up again. In order for the port to come up again I have to unplug bliss and the controllers to try again.

The work around is if you plug in ps2 in port one, press reset so player one reads, then plug in snes or Nes controller in port two (or whatever port you choose), press reset on that port so it reads THEN unplug the controller and plug in ps2 in that same port. Since port two had already been read, I don't have to press reset and player one and two can be used with ps2 or n64

The bottom line is dream cast controllers don't have this thing happen however if I want two players for n64 or ps2 then I have to ensure player two port has been put in discovery mode first otherwise the port will not reappear after reset (aka I just plug in a non analog controller first to use reset and swap out the controller)

Tapatalk signature

[atarigalore]

I have updated my flasher since then with newer 1.54 firmware. Try that.... As far as the rest I don't know... I don't know any code so I can't fix anything, all I really know is old .bat files and old basic on commodore64.

So all I can really do is update my flasher as often as I get time when he updates the firmware.

But yeah we (me and sean) talk, I live like 10min from him.

[ulao]

Quick question, didn't see anything in the earlier pages. Did anyone have trouble initially getting controllers recognized at all? I plugged in my bliss box, and 4 items called 4 play pop up in the control panel. 

This is correct

However, I read that once I plug my controller in, a sound should be made and the controller should be recognized in windows. Nothing pops up, and I've tried with 5 different controllers.

 

Nope, that is incorrect. Plugging a controller in will not do a thing to the OS. 

 

Once the 4 play shows all for ports you need to figure out the port that is connected to the physical port. This is where atari's fix comes in handy. Then you can plug in a controller and hit reset (now its in discovery mode), hot-swap and enjoy.

If you ever run the OFFICIAL flashtool it will UNDO and OVERWRITE my hacked pid's and make all ports identical again causing the port order to become random again.

 

This is not correct. The official flash will only over right what port you flash to. 

If you flash over port 1, port one becomes port 1.

If you flash over port 2, port one becomes port 1.

If you flash over port 3, port one becomes port 1.

If you flash over port 4, port one becomes port 1.

So if you only flash one port the other are not effected.This is a good way to test beta stuff. Flash port one with the beta firmware and nothing changes as far as port ordering goes. 

 

Ninja's issue: So far I'm not able to get this to happen. I think there was one other person that reported it on the forums. I'd like to see this issue so that I can fix it but it really does not make sense for the port to reset when you plug in a controller. Now I have see this on occasion and it has to do with how you plug in the controller and when is being detected at that time but the chances of this causing a reset are very low and most certainly not consistent. If anyone can shed more light it would be great. 

[atarigalore]

Ulao that 3rd party 3do controller i have we thought was dead, it works on the real 3do and I just tested it again on the 4-play and when I plug it in nothing happens just like when we tested it before, but if I press the reset button for that port the port disapears untill I unplug it and the bliss box updater never comes up either if it's plugged in.

Don't know if it's can help on the stange issue ninja has but I can bring it over saturday night.

[ninja2bceen]

This is similar to my experience. Atari, try this work around. Plug in Nes or snes, then press reset so bliss reads the controller. Then swap out that controller with the 3do, I'll bet it works then

I don't have a 3do controller but do realize it does not have an analog stick. This is weird to me. My issue is only when you have the official ps2 controller or official n64 controller and I want to use two players. Any combination of those two controllers have this issue regardless of ports used. The first controller will read but as soon as I plug in the second controller that is either ps2 or n64 things get wacky if I don't use my workaround. I assumed it had something to do with the analog base controllers so I got dreamcast controllers to test but those work flawlessly. So of the controllers I have tested the Nes, snes, dreamcast work flawlessly. Now the n64 and ps2 controllers work great if you only use one controller however if you decide to plug in a second controller for n64 or ps2 within any port without my workaround bliss flips a brick. Thanks for entertaining my complaint and good luck

Tapatalk signature

[ulao]

Atari as you know the 3do issue is now solved. Was that alternative power set up.

[ninja2bceen]

So are you suggesting I try and flash to the Jan 3 2016 custom flasher and do 1.54 testing to see if it fixes my oddity?

Tapatalk signature

[ulao]

No... If you are referring to my last post, I was just commenting that Atari's issue was purely related to the 3do controller. We are still looking for anyone with your issue.