why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
I would hot-plug a receiver for all the same reasons I might hot-plug a regular controller.
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
The same reasons you would plug in or unplug a wired controller:
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
The firmware needs to be worked on and i would suggest forwarding this to them, but i would assume this adaptor is drawing more power then a normal controller.
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
I would hot-plug a receiver for all the same reasons I might hot-plug a regular controller.
I signed up for 8bitdo forums and downloaded it.
So I have to sign up somewhere to get the firmware update? Booo...
Originally posted by: CZroe
Originally posted by: zredgemz
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
+1. Even my custom made arcade controllers do not crash the system when I plug them.
Originally posted by: zredgemz
The firmware needs to be worked on and i would suggest forwarding this to them, but i would assume this adaptor is drawing more power then a normal controller.
If it's drawing too much current, then a firmware upgrade won't fix it. But the NES 8bitdo never crashed my NES or AV Famicom. The datasheet in the manual claims 5V, 100mA, but that may just be what it reports over USB. I hope it's less than that. Four recievers in a four score or multitap would pull 400mA; that's half the power rating of the console right there.
I guess I could wire an ammeter in line with the VCC of the 8bitdo using a scrap USB, but I ain't that motivated to find out.
Edit: I can forsee a danger if you use the mutli tap with 3 units to play secret of mana on a SD2snes while using hd retrovision cables since all of those draw power from the power supply.
There is a bit of wiggle room when using these wireless units but you have to take into account that it draws more power then a normal controller and did not have to go through the standards that nintendo did for their add ons and licensed controllers from third parties.
So can't use more than two. That's good to know. Reading the thread, there's a ton more games with incompatibility problems, fixed by v1.21_beta_2. Is there a link to download the non-beta v1.21 firmware fix without registering for their forum? The download link on their main page is broken.
Yikes. As I recall, they were claiming 4p support when I ordered three and they were still claiming 4p support for the NES version where I also had three. I had every intention of trying to put SNES firmware on a couple of the NES adapters for 4p Secret of Mana. The SNES supports up to 5p.
I wonder how difficult it would be to mod a multitap with a separate power source to power them all.
Traditional wireless receivers are receive-only and draw very little power because there is no transmitter. That's the real reason the Wavebird has no force feedback: adding it means adding another transmitter/receiver. Bluetooth, OTOH, has to exchange two-way pairing data and receive acknowledgements and such but at least it's a modern standard with a focus on energy efficiency, so I'd expect it to be fine. Too bad it doesn't use BT LE. If they got rid of the LED lights when not pairing I wonder if that would cumulatively lower their power draw enough to enable another player or two.
I'll probably do some testing in an NES Satellite soon since it does not draw power from the console.
Edit: OK, I see now that it likely isn't a power problem contributing to lack of 4p support, it was the initial problem with the shift registers not responding correctly to bits over 12, since the multitaps and such likely use these bits, but I would still be concerned if we had an extra 500mA+ running off the controller ports. Even if they really do use up to 100mA, I doubt they use the full 100mA unless they are pairing an making themselves discoverable. As long as you pair one at a time they are probably good to go. Hopefully syncing doesn't use just as much. It seems that this may be another reason to hot-plug: to stagger controller syncs. Yes, you can stagger when each syncs, but all adapters will be scanning for them simultaneously at boot if you can't hot plug to insert them one at a time.
EDIT2: Went to the movies with the fiance and saw Sausage Party. I updated my firmware in my SNES reciever but have not tested it yet. I'm keeping the original firmware in my NES reciever though because I'm one of those "weirdos" who prefer to use A+B on the diamond instead of B+Y. Still good to know the 16-bit reciever should also work with a patch cable on my NES with B+Y if backwards compatability is maintained.
Well, my brother just went to sleep and left the SNES on reminding me to come back to this thread. You see, this is at least the second night in a row that he has left the SNES on because he's trying to do a no-death play-thru of a particular game that counts saving as a death and he hasn't been able to put much time into it each day. When I noticed that he had a wired controller plugged in I asked why he wasn't using the Retro Receiver and his answer was "because I can't turn off the SNES and it will screw up the game to switch to it."
Well, there you have it, folks. He's been forced to play with a wired controller for three days now despite owning a Retro Receiver purely because of a problem that shouldn't be there. Hot-plugging should be possible! I'm very tempted to wire up an external PSU to see if it solves the problem.
EDIT2: Went to the movies with the fiance and saw Sausage Party. I updated my firmware in my SNES reciever but have not tested it yet. I'm keeping the original firmware in my NES reciever though because I'm one of those "weirdos" who prefer to use A+B on the diamond instead of B+Y. Still good to know the 16-bit reciever should also work with a patch cable on my NES with B+Y if backwards compatability is maintained.
Infrared controllers are the problem with the later Atari Flashbacks and AtGames Sega Genesis consoles and a big reason why they should be avoided like the plague.
FTR, I am perfectly happy with the original firmware of the NES receiver. Short of custom firmware, I'm not sure how you would remap the controllers as there doesn't appear to be a configuration utility.
Plugging the receiver into USB boots it as a HID gamepad. Plugging the receiver into USB with the sync button held down boots it into firmware mode.
The current firmware flashes to both retro receivers. I have reason to suspect that both retro recievers are identical from a hardware perspective, aside from form factor of the plugs. NES and SNES share the same mapping and byte order (A + B NES = B + Y SNES) for the first 8 bits. The extra two buttons function as turbo mode on an NES, but A + Y on SNES. This works because the firmware can count the number of bits requested by the console to detect 8-bit or 16-bit modes of operation. If the console requests 16 or more bits, it responds like an SNES controller. If the console requests 8 bits, A + Y become turbo buttons.
The only downside to enabling NES mode Turbo through firmware is said turbo functions will not work on a minority of Four Score enabled NES games which send 24 clock pulses per controller poll whether four people are playing or not. Pressing A, Y, LT, or RT on such games won't affect input anyway since the Four Score key for bits 17-24 will be incorrect, thus the game only processes the first 8 bits. "Turbo" buttons in SNES mode won't register as input in such circumstances.
I think there were a few 2-in-1 NES/SNES clones that used SNES clone controllers with firmware that detected 8-bit mode to use the additional buttons as turbo.
Originally posted by: CZroe
Infrared controllers are the problem with the later Atari Flashbacks and AtGames Sega Genesis consoles and a big reason why they should be avoided like the plague.
There were several options for infrared wireless. Akklaim had one too. Heck, even Nintendo had IR for the NES Satellite receiver. Infrared requires direct line-of-sight, like a TV remote. No. it does not work well.
We're talking about a Bluetooth receiver that works with practically any Bluetooth game controller you might already own. That's radio frequency and does not require you to keep the remote pointed straight at it. The signals won't be disrupted by someone walking between you and the game console. It works with lots of existing controllers including PS3 (though pairing is a pain), PS4, Wii remote, Wii U Pro controller, etc.
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
I'll check to see if I still have the files...
[edit]
Yes. I believe I misinterpreted the Engrish in the readme file.
"Change button map" was followed by an ascii table/grid.
The entry should have said: "Changed button mapping."
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
I'll check to see if I still have the files...
[edit]
Yes. I believe I misinterpreted the Engrish in the readme file.
"Change button map" was followed by an ascii table/grid.
The entry should have said: "Changed button mapping."
While I was editing my reply to include a long rant about how I believe the receiver firmware enables turbo on NES, a couple extra posts were made.
There is a .dat file that you flash the receiver firmware with. It's 36kb, not a binary file size so probably compressed. Either way I'm sure there's no way to properly edit any controller mappings in notepad. Firmware updates are not normally stored as plain text.
I have thus far neglected to sign up for the 8bitdo forums, primarily because those noseless unisex avatars that everyone is assigned are also IMO extremely creepy. Not a single user has changed or updated their avatar so I assume it is disallowed.
Anyway the older and beta firmwares are uploaded to the support forums as attachments to forum posts and only registered users can download them.
Kinda stupid, but I really don't want to register their crappy forum just so I can get a download to rollback the firmware. If I buy a second NES receiver, I should want to run the pre-SNES firmware on it which used my preferred "VC style" button mappings.
I need you guys help to download NES retro receiver firmware 1.10 beta 4.
I ordered a spare NES retro receiver from eBay and it came with firmware 1.20 installed. It's got the B/Y input with A/X turbo which I absolutely loathe. My old retro receiver with original firmware maps to A/B. Anyway I desperately need to revert the firmware on this NES receiver so that it matches my other NES receiver which was IMO perfect out of the box. Just like NES Dogbone, GB, GBA, GBA on DS, and all Virtual Console titles which I am accustomed to the A/B button layout for NES.
Unfortunately I have attempted to register their crappy little forum at least four times tonight using both my Yahoo email accounts but cannot get in because I never recieved the confirmation email, and their older and beta firmwares are stupidly begind a login wall.
I need someone with account there to goto this page and send or link me to the firmware 1.10 beta 4. Any help would be appreciated, thanks...
Comments
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
I would hot-plug a receiver for all the same reasons I might hot-plug a regular controller.
I signed up for 8bitdo forums and downloaded it.
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
The same reasons you would plug in or unplug a wired controller:
Switch controllers
Add a player
Switch players
Why would being wireless change that?
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
The firmware needs to be worked on and i would suggest forwarding this to them, but i would assume this adaptor is drawing more power then a normal controller.
why would you put in a wireless unit while it is powered on to begin with? I have not tried the beta update since they have not sent me a email so i can sign up to download it yet.
I would hot-plug a receiver for all the same reasons I might hot-plug a regular controller.
I signed up for 8bitdo forums and downloaded it.
So I have to sign up somewhere to get the firmware update? Booo...
because it draws power from your super nintendo. same reason i do not hot plug my PSIO.
...and so does a standard controller. It's supposed to work within the specifications of a standard controller. My NES Advantage doesn't crash the system just because it has LEDs on it. Also, the NES Retro Receiver doesn't crash an NES. Unplugging a USB WiFi dongle doesn't crash my PC.
NES Satellite, Acclaim wireless controllers for SNES, Camerica Freedom Stick, and so many more draw their power from the console without issue.
+1. Even my custom made arcade controllers do not crash the system when I plug them.
The firmware needs to be worked on and i would suggest forwarding this to them, but i would assume this adaptor is drawing more power then a normal controller.
If it's drawing too much current, then a firmware upgrade won't fix it. But the NES 8bitdo never crashed my NES or AV Famicom. The datasheet in the manual claims 5V, 100mA, but that may just be what it reports over USB. I hope it's less than that. Four recievers in a four score or multitap would pull 400mA; that's half the power rating of the console right there.
I guess I could wire an ammeter in line with the VCC of the 8bitdo using a scrap USB, but I ain't that motivated to find out.
"Disappointed about the apparent lack of 4-player support from these NES and SNES receivers. What doe ...
I'm sorry, this's our mistake!
We have removed the mention of 4-players feature from the official website.
We'll test and fix it as soon as possible, if it could be.
If it is determined that 4-players are supported, at that time we'll add up."
http://forum.8bitdo.com/thread-1402-5-1.html
Edit: I can forsee a danger if you use the mutli tap with 3 units to play secret of mana on a SD2snes while using hd retrovision cables since all of those draw power from the power supply.
There is a bit of wiggle room when using these wireless units but you have to take into account that it draws more power then a normal controller and did not have to go through the standards that nintendo did for their add ons and licensed controllers from third parties.
http://download.8bitdo.com/Tools/Receiver/8Bitdo_RR_Firmware_V1.21.zip
I wonder how difficult it would be to mod a multitap with a separate power source to power them all.
Traditional wireless receivers are receive-only and draw very little power because there is no transmitter. That's the real reason the Wavebird has no force feedback: adding it means adding another transmitter/receiver. Bluetooth, OTOH, has to exchange two-way pairing data and receive acknowledgements and such but at least it's a modern standard with a focus on energy efficiency, so I'd expect it to be fine. Too bad it doesn't use BT LE. If they got rid of the LED lights when not pairing I wonder if that would cumulatively lower their power draw enough to enable another player or two.
I'll probably do some testing in an NES Satellite soon since it does not draw power from the console.
Edit: OK, I see now that it likely isn't a power problem contributing to lack of 4p support, it was the initial problem with the shift registers not responding correctly to bits over 12, since the multitaps and such likely use these bits, but I would still be concerned if we had an extra 500mA+ running off the controller ports. Even if they really do use up to 100mA, I doubt they use the full 100mA unless they are pairing an making themselves discoverable. As long as you pair one at a time they are probably good to go. Hopefully syncing doesn't use just as much. It seems that this may be another reason to hot-plug: to stagger controller syncs. Yes, you can stagger when each syncs, but all adapters will be scanning for them simultaneously at boot if you can't hot plug to insert them one at a time.
New non beta firmware out that fixes DKC and others.
The link I posted above (from the homepage) is still broken.
EDIT: Nevermind, they fixed it:
http://8bitdo.com/retro-receiver-snes/support.html
EDIT2: Went to the movies with the fiance and saw Sausage Party. I updated my firmware in my SNES reciever but have not tested it yet. I'm keeping the original firmware in my NES reciever though because I'm one of those "weirdos" who prefer to use A+B on the diamond instead of B+Y. Still good to know the 16-bit reciever should also work with a patch cable on my NES with B+Y if backwards compatability is maintained.
Well, there you have it, folks. He's been forced to play with a wired controller for three days now despite owning a Retro Receiver purely because of a problem that shouldn't be there. Hot-plugging should be possible! I'm very tempted to wire up an external PSU to see if it solves the problem.
http://www.ebay.com/itm/Konami-Hyperbeam-Wireless-Controller-Nintendo-Super-Famicom-Japan-/331774753607?hash=item4d3f50fb47:g:vtQAAOSwB4NWuwRY
Do those not work well?
New non beta firmware out that fixes DKC and others.
The link I posted above (from the homepage) is still broken.
EDIT: Nevermind, they fixed it:
http://8bitdo.com/retro-receiver-...
EDIT2: Went to the movies with the fiance and saw Sausage Party. I updated my firmware in my SNES reciever but have not tested it yet. I'm keeping the original firmware in my NES reciever though because I'm one of those "weirdos" who prefer to use A+B on the diamond instead of B+Y. Still good to know the 16-bit reciever should also work with a patch cable on my NES with B+Y if backwards compatability is maintained.
You can do custom mapping.
Didn't Konami release a Wireless controller option for the SNES/Super Famicom back in the 90's?
http://www.ebay.com/itm/Konami-Hy...
Do those not work well?
Infrared controllers are the problem with the later Atari Flashbacks and AtGames Sega Genesis consoles and a big reason why they should be avoided like the plague.
You can do custom mapping.
How?
FTR, I am perfectly happy with the original firmware of the NES receiver. Short of custom firmware, I'm not sure how you would remap the controllers as there doesn't appear to be a configuration utility.
Plugging the receiver into USB boots it as a HID gamepad. Plugging the receiver into USB with the sync button held down boots it into firmware mode.
The current firmware flashes to both retro receivers. I have reason to suspect that both retro recievers are identical from a hardware perspective, aside from form factor of the plugs. NES and SNES share the same mapping and byte order (A + B NES = B + Y SNES) for the first 8 bits. The extra two buttons function as turbo mode on an NES, but A + Y on SNES. This works because the firmware can count the number of bits requested by the console to detect 8-bit or 16-bit modes of operation. If the console requests 16 or more bits, it responds like an SNES controller. If the console requests 8 bits, A + Y become turbo buttons.
The only downside to enabling NES mode Turbo through firmware is said turbo functions will not work on a minority of Four Score enabled NES games which send 24 clock pulses per controller poll whether four people are playing or not. Pressing A, Y, LT, or RT on such games won't affect input anyway since the Four Score key for bits 17-24 will be incorrect, thus the game only processes the first 8 bits. "Turbo" buttons in SNES mode won't register as input in such circumstances.
I think there were a few 2-in-1 NES/SNES clones that used SNES clone controllers with firmware that detected 8-bit mode to use the additional buttons as turbo.
Infrared controllers are the problem with the later Atari Flashbacks and AtGames Sega Genesis consoles and a big reason why they should be avoided like the plague.
IR sucks donkey balls.
Didn't Konami release a Wireless controller option for the SNES/Super Famicom back in the 90's?
http://www.ebay.com/itm/Konami-Hy...
Do those not work well?
There were several options for infrared wireless. Akklaim had one too. Heck, even Nintendo had IR for the NES Satellite receiver. Infrared requires direct line-of-sight, like a TV remote. No. it does not work well.
We're talking about a Bluetooth receiver that works with practically any Bluetooth game controller you might already own. That's radio frequency and does not require you to keep the remote pointed straight at it. The signals won't be disrupted by someone walking between you and the game console. It works with lots of existing controllers including PS3 (though pairing is a pain), PS4, Wii remote, Wii U Pro controller, etc.
You can do custom mapping.
How?
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
I'll check to see if I still have the files...
[edit]
Yes. I believe I misinterpreted the Engrish in the readme file.
"Change button map" was followed by an ascii table/grid.
The entry should have said: "Changed button mapping."
You can do custom mapping.
How?
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
I'll check to see if I still have the files...
I thought you were going to sleep?
You can do custom mapping.
How?
At least, that's how I interpreted some of the Engrish I saw when I originally updated my NES receivers months ago. Something to do with editing files using a text editor. Either it was in the beta firmware thread or it was in the readme of the file I downloaded.
I'll check to see if I still have the files...
[edit]
Yes. I believe I misinterpreted the Engrish in the readme file.
"Change button map" was followed by an ascii table/grid.
The entry should have said: "Changed button mapping."
While I was editing my reply to include a long rant about how I believe the receiver firmware enables turbo on NES, a couple extra posts were made.
There is a .dat file that you flash the receiver firmware with. It's 36kb, not a binary file size so probably compressed. Either way I'm sure there's no way to properly edit any controller mappings in notepad. Firmware updates are not normally stored as plain text.
I have thus far neglected to sign up for the 8bitdo forums, primarily because those noseless unisex avatars that everyone is assigned are also IMO extremely creepy. Not a single user has changed or updated their avatar so I assume it is disallowed.
Anyway the older and beta firmwares are uploaded to the support forums as attachments to forum posts and only registered users can download them.
Kinda stupid, but I really don't want to register their crappy forum just so I can get a download to rollback the firmware. If I buy a second NES receiver, I should want to run the pre-SNES firmware on it which used my preferred "VC style" button mappings.
#firstworldproblems
I ordered a spare NES retro receiver from eBay and it came with firmware 1.20 installed. It's got the B/Y input with A/X turbo which I absolutely loathe. My old retro receiver with original firmware maps to A/B. Anyway I desperately need to revert the firmware on this NES receiver so that it matches my other NES receiver which was IMO perfect out of the box. Just like NES Dogbone, GB, GBA, GBA on DS, and all Virtual Console titles which I am accustomed to the A/B button layout for NES.
Unfortunately I have attempted to register their crappy little forum at least four times tonight using both my Yahoo email accounts but cannot get in because I never recieved the confirmation email, and their older and beta firmwares are stupidly begind a login wall.
I need someone with account there to goto this page and send or link me to the firmware 1.10 beta 4. Any help would be appreciated, thanks...
http://forum.8bitdo.com/thread-1404-1-1.html
"Date: 2016-05-11 V1.10beta4