Post by: Charly_2005 on January 28, 2020, 02:57:19 PM
With the games there is no problem, but with the interface I have the problem that everything is moving automatically after a joystick or button press.
For example: I scroll through the list of games and at one point a press makes it continue moving in that direction, being the only way to stop pressing that direction again.
With the buttons that change the letter the same thing happens, one press and have to press again to stop the automatic movement.
It does not always happen but it is annoying.
I have tried to modify the configuration files without success.
Post by: Pieter Hulshoff on January 29, 2020, 07:44:41 AM
Post by: Charly_2005 on January 29, 2020, 01:45:01 PM
Do you know if another encoder works?
For my part I can contribute that no button works correctly, the joystick quite well although sometimes it fails and that once pressed a button the joystick goes crazy. The only way to release the pulse is to press the same address or button again.
PD: In controls.conf second line of text (down) one parameter says joyAxis5+ and another says deadzone, but the documentation does not appear.
Post by: Pieter Hulshoff on January 29, 2020, 04:13:16 PM
I'm using the ipac2 board myself; no issues so far.
Post by: Charly_2005 on January 30, 2020, 01:33:15 PM
I expect a response from the community although I would not mind buying the ipac2. I'm probably better than my encoder.
Post by: johnm on January 30, 2020, 02:44:41 PM
Paste the line below into a text document and save it, rename the extension to .bat and run it. This will open up your game controller settings, click properties and note down what your joystick registers as and the buttons. You can then make your own controls.conf to what suits you
When copying the button numbers in windows you drop it by 1 in the controls.conf, example button 1 in the windows control panel you change to joy0Button0 for RetroFE
rundll32.exe shell32.dll,Control_RunDLL joy.cpl
Post by: Charly_2005 on January 31, 2020, 08:56:23 AM
The other question was to know if joyAxis5 exists, since nothing appears in the official documentation and it appears in my controls.conf (CoinOPS).
Post by: johnm on January 31, 2020, 01:09:14 PM
Some of those settings you will see in the controls.conf are to do with the likes of the xbox360/one controller and will have no relevance to you if you dont have your encoder wired up as such, hence why i recommended making a new controls.conf set up to how you wanted. You could choose your next playlist or whatever based on your buttons and not someone elses
joyAxis5+ and joyAxis2+ are for the shoulder triggers on an xbox controller, the + being because they are analog( i assume)
Post by: Charly_2005 on January 31, 2020, 04:33:11 PM
Post by: batodan1911 on February 03, 2020, 07:43:48 AM
Post by: Charly_2005 on February 03, 2020, 05:55:44 PM
But there has to be some way to be able to pass the controls as if it were an xbox controller and modify controls.conf
Post by: Pieter Hulshoff on February 03, 2020, 10:01:27 PM
Post by: Charly_2005 on February 06, 2020, 03:24:05 PM
Post by: Pieter Hulshoff on February 07, 2020, 08:20:55 AM
Sent from my SM-G950F using Tapatalk
Post by: Charly_2005 on February 08, 2020, 09:30:36 AM
I'm getting a controller based on a zero delay soon, so I'll have a look to see if I can reproduce the issue, and solve it.
He said when you get it. I would like to know if there is a delay or other difference. I don't mind investing in an ipac2.
Post by: batodan1911 on February 12, 2020, 09:40:16 AM
im still didnt find a way to fix my 0 delay to work normally
Post by: Pieter Hulshoff on February 12, 2020, 04:37:36 PM
Post by: procyon on February 12, 2020, 09:31:01 PM
ipac2 cost much more then the 0 delay kit
You get what you pay for. Zero delay encoder are junk.
Post by: Charly_2005 on February 19, 2020, 06:01:39 PM
Post by: batodan1911 on February 23, 2020, 05:59:39 AM
Post by: cmundy79 on February 27, 2020, 09:49:03 PM
Post by: Pieter Hulshoff on February 28, 2020, 08:12:56 AM
Post by: Charly_2005 on February 28, 2020, 09:13:17 AM
Post by: cmundy79 on February 28, 2020, 10:51:17 AM
Post by: Pieter Hulshoff on March 01, 2020, 12:21:53 PM
Post by: cmundy79 on March 02, 2020, 03:30:22 PM
Post by: batodan1911 on March 05, 2020, 01:01:22 PM
Ok, I have received the controller, and can reproduce the problem. I will have a look this week to see if I can fix the issue. It looks like the zero delay board doesn't always send the release control to the computer, and RetroFE only reacts to transactions, not status of the keys, so since it does not receive the key release it assumes the key is still pressed.man you are amazing everyone in coinop try to figure it out and you just did
Post by: cmundy79 on March 05, 2020, 03:29:19 PM
Ok, I have received the controller, and can reproduce the problem. I will have a look this week to see if I can fix the issue. It looks like the zero delay board doesn't always send the release control to the computer, and RetroFE only reacts to transactions, not status of the keys, so since it does not receive the key release it assumes the key is still pressed.man you are amazing everyone in coinop try to figure it out and you just did
I agree, yes he is :)
Post by: ger on March 06, 2020, 12:35:06 AM
Post by: BritneysPAIRS on March 06, 2020, 08:51:10 AM
Post by: batodan1911 on March 10, 2020, 08:52:18 AM
Post by: cmundy79 on March 10, 2020, 11:33:12 AM
in the discord of coinop i saw alot of ppl ask this question and all the support team says there is no solution for now
I'm sure a solution will be found shortly. :)
Post by: procyon on March 10, 2020, 03:50:36 PM
I'm sure a solution will be found shortly. :)
Why are you so sure? ZDE boards are made really cheaply, if a solution could be found it almost certainly would have been made available by now. More likely, you will see a hardware revision released, and you'll have to buy an upgraded board if you really want it fixed.
Post by: cmundy79 on March 10, 2020, 03:57:45 PM
I'm sure a solution will be found shortly. :)
Why are you so sure? ZDE boards are made really cheaply, if a solution could be found it almost certainly would have been made available by now. More likely, you will see a hardware revision released, and you'll have to buy an upgraded board if you really want it fixed.
Nice one, because I'm hoping that a software side solution can be implemented but I really appreciate your opinion.
Post by: Pieter Hulshoff on March 10, 2020, 10:01:05 PM
Post by: cmundy79 on March 11, 2020, 12:59:33 AM
Ok, make a copy of your current retrofe.exe file, and give this one a try. Let me know if it solves anything, and does not introduce too many new problems. :)
Pieter, amazing , thank you so much. I've been testing for a while now and it seems to be fixed. Thank you again for all your hard work on this!
Post by: Charly_2005 on March 14, 2020, 04:51:21 PM
Thank you very much Pieter, this will help a lot of people.
Post by: stef on March 15, 2020, 07:35:05 PM
Post by: Charly_2005 on March 24, 2020, 01:49:25 PM
Thanks.
Post by: Pieter Hulshoff on March 24, 2020, 09:05:05 PM
Post by: manu70 on April 28, 2022, 07:25:30 PM
I open the subject because i used your retrofe version. It'works very well. But it's an old version. I would like the parts of the code to compile a new version based on the last version.
Is it possible ?
Thanks.
Post by: Pieter Hulshoff on April 30, 2022, 06:17:17 AM
Post by: manu70 on May 05, 2022, 11:05:49 PM
I see that the last version is 0.10.31. But the bug that you have corrected in 2020 is not report in this version. Do you have the part of the code to apply in 0.10.31 ?
Thanks for your help.
Post by: Pieter Hulshoff on May 05, 2022, 11:22:31 PM