Hello! Please let our support team know at info@retro-bit.com. They will be able to send the replacement part and help you do a quick repair.RaykOscuro wrote:@Retro-Bit: I bought one of your Bluetooth Sega Saturn Gamepads (EU version) less than 2 weeks ago. Today I used it for the first time for a longer period of time and the D-Pad broke... it's pretty much the same problem that's described and documented in this review on Amazon: https://www.amazon.de/gp/customer-revie ... LC7I1MFTL/
So this seems to be a recurring problem... I'm really disappointed since you wrote on this forum that you would make sure that problems like those with the first wired controllers wouldn't occur again. Seems like the D-Pad is once again a very weak part in this controller.
Press Start once to let it "search" and then Start again for it to force pair. Sometimes, you only need to press Start once to connect. This is due to the receiver signal still being paired. Extended time powered off on the receiver will set it back to search for a new controller.mario64 wrote:Finally got one of the 2.4ghz Saturn controllers and have a question. I read the manual but oddly it doesn’t cover this. How do you wake it up? I power on my Saturn then press the Start button and it takes 5-10 seconds and sometimes fails to connect. Is this a defect? All of my 8bitdo 2.4ghz controllers connect instantly when you press Start
Do you have to press it twice or something? Thanks
So you're saying if I press Start twice it will instantly connect even if the receiver has been powered off for an extended period?Retro-Bit wrote:Press Start once to let it "search" and then Start again for it to force pair. Sometimes, you only need to press Start once to connect. This is due to the receiver signal still being paired. Extended time powered off on the receiver will set it back to search for a new controller.mario64 wrote:Finally got one of the 2.4ghz Saturn controllers and have a question. I read the manual but oddly it doesn’t cover this. How do you wake it up? I power on my Saturn then press the Start button and it takes 5-10 seconds and sometimes fails to connect. Is this a defect? All of my 8bitdo 2.4ghz controllers connect instantly when you press Start
Do you have to press it twice or something? Thanks
We're sorry to hear about that. Please email our support team at info@retro-bit.com.atohmdiy wrote:Same problem, bought a saturn pad maybe a month ago, use it very lightly. Today i take it, press the down button of the dpad and i feel a crack. I open the controller and the dpad plastic cross was broken...
This seems to be the case. Some folks stored it away for an extended period of time or they purchased it from an independant retailer that we were unable to get recalled inventory from. It's tough to enforce the fact that we've made changes when these cases pop up but we stand by what we said and will continue to support future issues should any arise.Austin wrote:I thought they said they had addressed that issue? If so, might have gotten one from the old stock.
This brings up a pet peeve of mine. It is in no way a deal breaker because I love my Saturn pad, but it is annoying.Retro-Bit wrote:Press Start once to let it "search" and then Start again for it to force pair. Sometimes, you only need to press Start once to connect. This is due to the receiver signal still being paired. Extended time powered off on the receiver will set it back to search for a new controller.
I agree. This is a very bad design. 8bitdo has a much better one. You press ONCE and have an instant connection. Actually if you change to the BT version the Retrobit controller works that way. They just screwed up the 2.4ghz connectionmatt wrote:This brings up a pet peeve of mine. It is in no way a deal breaker because I love my Saturn pad, but it is annoying.Retro-Bit wrote:Press Start once to let it "search" and then Start again for it to force pair. Sometimes, you only need to press Start once to connect. This is due to the receiver signal still being paired. Extended time powered off on the receiver will set it back to search for a new controller.
The problem I have is that pressing "start" the second time to pair the controller actually activates it on the system, which sucks if the Saturn is already running and the cursor is somewhere I don't want it to be. I have a Phoebe installed, and what usually happens is that unless I have the controller in hand already and am able to press start before the boot screen is over, there's no way to pair the controller without booting the first game on the Rmenu list. Then I'm forced to turn the system off and on again just to select the game I want to play.
If there's a way to change this in a future firmware update, it would be much appreciated.
Oh I understood everything he said - my answer is the same regardless. If you're referring to my response to Austin, I was talking about in general when it comes to these issues.bigbadboaz wrote:RB, Mr. Oscuro was quite clear he was talking about one of the new Bluetooth pads and not an original wired one. This was not something that could have slipped through that old recall or be attributed to "new old stock".
You really haven't addressed his concern.
I beleive this is programmed into the boards used on the receivers. That said, we do want to streamline our 2.4 GHz wireless offering as we go forward with upcoming wireless controllers. I can't reveal too much but we are looking at the feedback we've received to see where we can improve in the future.matt wrote:If there's a way to change this in a future firmware update, it would be much appreciated.
Well, as I stated, we're looking at feedback and working to improve on this and other things users have pointed out. We definitely want to look at streamlining firmware updates, pairing, and more.mario64 wrote:I agree. This is a very bad design. 8bitdo has a much better one. You press ONCE and have an instant connection. Actually if you change to the BT version the Retrobit controller works that way. They just screwed up the 2.4ghz connection
That's great to hear. Thank you. Looking forward to itRetro-Bit wrote:Oh I understood everything he said - my answer is the same regardless. If you're referring to my response to Austin, I was talking about in general when it comes to these issues.bigbadboaz wrote:RB, Mr. Oscuro was quite clear he was talking about one of the new Bluetooth pads and not an original wired one. This was not something that could have slipped through that old recall or be attributed to "new old stock".
You really haven't addressed his concern.
I beleive this is programmed into the boards used on the receivers. That said, we do want to streamline our 2.4 GHz wireless offering as we go forward with upcoming wireless controllers. I can't reveal too much but we are looking at the feedback we've received to see where we can improve in the future.matt wrote:If there's a way to change this in a future firmware update, it would be much appreciated.
Well, as I stated, we're looking at feedback and working to improve on this and other things users have pointed out. We definitely want to look at streamlining firmware updates, pairing, and more.mario64 wrote:I agree. This is a very bad design. 8bitdo has a much better one. You press ONCE and have an instant connection. Actually if you change to the BT version the Retrobit controller works that way. They just screwed up the 2.4ghz connection
Heya,atohmdiy wrote:I really hope your team will give me an answer, no news from them after my email...
Oh, please contact our support team at info@retro-bit.com. They should be able to replace it if it turns out to be faulty.Taco_Human wrote:Is my controller messed up? Got it new in the mail yesterday, just testing it now. I have to wait til later to test it on an actual genesis mini, but why wouldn't it work on my Switch? The input switching doesn't seem to work.
I'm not speaking on behalf of our development team, but the PC Engine/TurboGrafx 16 has always been an odd one for me. I do hope we get a good look at the console but there are some limiting factors to it, especially in terms of demand and cost. I think in terms of the Playstation consoles, that's another area that is on our list but we have much to work through to get there.RetroSnow wrote:Now how about a wireless PC Engine controller that works on actual hardware (pleeeeeease)? The only way around it now is to use an adapter and a Bluetooth controller. All my other systems have their own dedicated wireless pads.
Very nice! We do love seeing people get fancy with their controllers.BONKERS wrote:These controllers are super easy to disassemble.
I opened my Smoke Black one and painted it on the inside with Tamiya Transparent Red and then a layer of Tamiya Gloss top coat.
Gives it a nice deep red color
Ok, that is absolutely a weird problem! I'll be honest - I don't think we test for screensaver issues like that. But it seems you're using an older version of Windows? In which case, I'm unfortunately not the best candidate for knowledge on that. Please let me know what version of Windows you're running and I will relay the information.BazookaBen wrote:Retrobit, is there anything I can do about my Saturn USB pad blocking the screensaver in Windows?
Like, as long as my Saturn pad is plugged in, the screensaver will never come on. I'm trying to not to burn in my CRT! And I'm sure OLED owners want to avoid that too.
I don't remember this being an issue when I first got the pad, it seems like it may have started after the 2004 Windows update, but I may have just not noticed it before.
Heya,mario64 wrote:@Retro-Bit
I've been trying for a week to get a response from your support line. Anything you can do to help?
Also, when are you going to fix the incompatibility with Saturn games such as Bug! and MK II? You have to disconnect then re-connect the wireless receiver in order to play these games.
EDIT: they just got back to me
The shells are unique for 2.4 GHz and Bluetooth, they are not interchangeable. We can offer an exchange for a working one. The issue stems from the shell as the factory made a mistake on some of them (literally less than a millimeter).mario64 wrote:Anyone know if there is anything we can do to fix the sticky C button on the 2.4ghz Saturn wireless controller? Is it a problem with the button itself or the shell? I was thinking maybe you could swap the top shell and/or button from the BT version. No response from Retro-bit as yet. Thanks
I'm on Windows 10 version 2004, which is the most up to date version. "2004" Just means the year 2020 (20) and the month of April (04). You guys using Macs over there or something?Retro-Bit wrote: Ok, that is absolutely a weird problem! I'll be honest - I don't think we test for screensaver issues like that. But it seems you're using an older version of Windows? In which case, I'm unfortunately not the best candidate for knowledge on that. Please let me know what version of Windows you're running and I will relay the information.
Thank you for the responses. So glad to hear you’re working on the 2.4ghz issue. Support is going to replace my sticky C button controllers. All good now. Really appreciate itRetro-Bit wrote:Ok, that is absolutely a weird problem! I'll be honest - I don't think we test for screensaver issues like that. But it seems you're using an older version of Windows? In which case, I'm unfortunately not the best candidate for knowledge on that. Please let me know what version of Windows you're running and I will relay the information.BazookaBen wrote:Retrobit, is there anything I can do about my Saturn USB pad blocking the screensaver in Windows?
Like, as long as my Saturn pad is plugged in, the screensaver will never come on. I'm trying to not to burn in my CRT! And I'm sure OLED owners want to avoid that too.
I don't remember this being an issue when I first got the pad, it seems like it may have started after the 2004 Windows update, but I may have just not noticed it before.
Heya,mario64 wrote:@Retro-Bit
I've been trying for a week to get a response from your support line. Anything you can do to help?
Also, when are you going to fix the incompatibility with Saturn games such as Bug! and MK II? You have to disconnect then re-connect the wireless receiver in order to play these games.
EDIT: they just got back to me
Apologies to you and everyone waiting for a reply. We get TONS of emails around this time especially with new stuff coming out (people asking for info, samples, recommendations, ideas, Scott Pilgrim, etc). Plus all the new stuff we got going on has us a bit distracted BUT we will get to them!
As for the issues on the Saturn for the 2.4 GHz. YES! We are aware that Bug!, Lemmings, Mortal Kombat II, and some versions of World Heroes Perfect have a desyncing issue. Yes, we are working on a fix but we will not have it ready just yet. As to what causes it... there seems to be some sort of desyncing forced on the controller (or in this case, the receiver) - this is just my knowledge from testing our stuff on various consoles. We hope to have a fix set up soon.
The shells are unique for 2.4 GHz and Bluetooth, they are not interchangeable. We can offer an exchange for a working one. The issue stems from the shell as the factory made a mistake on some of them (literally less than a millimeter).mario64 wrote:Anyone know if there is anything we can do to fix the sticky C button on the 2.4ghz Saturn wireless controller? Is it a problem with the button itself or the shell? I was thinking maybe you could swap the top shell and/or button from the BT version. No response from Retro-bit as yet. Thanks
We have a variety of Mac and Windows machines (and a couple Linux PCs) here. I've asked our team to check it out and see if there's anything we can do about it or if there's a Windows setting we can do to prevent it.BazookaBen wrote:I'm on Windows 10 version 2004, which is the most up to date version. "2004" Just means the year 2020 (20) and the month of April (04). You guys using Macs over there or something?
I think my Saturn controller was in the first wave of Switch-compatible USB pads last year. And it prevents the screen saver whether I have it in Dinput or Xinput mode.
