Sorry for dumping guy but damn you live for the fight still, that's for sure. If something gets fixed now or down the road I will call it a blessing and if it's broke forever, honestly I'll be ok with that too, it makes no difference to me at this point. So, I am going to just let you do whatever you want and dance with other folks for a while. I can use this stuff, how it is, broke and all and probably still be happy. It's just not worth it to me to get the run around in circles for every issue posted. Why not do some speed testing or fill in default values or whatever to improve things. Anyway for the immediate future TAB and RA need to co-exist, we still need access to it, so why not fix up a few things. They've had a few more years to work on it. for 1000s of games TAB is capable of doing. TAB input is still important until Retroarch/Libretro is ready to overhaul that interface to handle all the current input methods, dials, pedals, etc. It would be another 25 posts of meaningless sidebar about how the controller works fine instead of addressing the keyboard not working.ĭon't get me wrong sidebar is my favorite part of any post but addressing the OP during is preferable. I hate to call any response 'circular redundancy' to the tune of a foregone conclusion but, well, it is, you are. I have no idea how to share this information more clearly with you if you didn't anyway. I know you're intelligent and I know you know what I am trying to communicate so I have no idea why you run this kind of shit in a senseless circle. I was all for making this the best emulator possible, but honestly, you're not easy to work with. You guys do incredible, impeccable work and I was more on the testing side, which is still important, as I do believe because it is obvious you don't use Libretro cores much. It seems sensible and makes sense to continue to add spit and polish but maybe not.Īnyway I have tried working with you to improve Plus as best as I can. So basically, I still have no idea what you're trying to say here or you have tried entering values for all fields and you get errors or maybe you're just guessing, again? The only thing I was trying to suggest is filling in default Retroarch Retropad values vs. I am not saying I have a game that uses 10 buttons to test but nothing faults or gives me an error during setup or while playing. I am not sure what the "Median 101 Limitation" means mentioned above but I have Retropad values (also keyboard values in addition to Retropad values-6 buttons for Player 1 & 2-4 buttons for players 3 & 4) set for all 4 players, all 10 buttons, start and select, credits, etc. You will need to confirm this with mark but as far as i can see its a number of keys you have which is median 101. I didnt address your issue on the other keys being set. Again, you can't set a field to NONE in Plus when you make a mistake entering values you have delete your default.cfg and start from scratch. When using Plus and pressing Escape twice quickly in the TAB screen it just adds the escape key as an input selection value. The issue I was trying to address is with Plus. What you're saying is when you press escape twice in the TAB screen with lr-mame2003 it exits the emulator? You must be using an old version or something is broken, hotkeys are disabled? I have no idea why we have to widely different outcomes when pressing escape twice in the TAB screen while entering data in an input field in lr-mame2003. I was hoping Plus would work similar as that's how MAME has always done it, as long as I can remember when using an arcade cabinet type setup. When I hit escape twice (quickly) in the TAB input screen in lr-mame2003 it sets the field to NONE, which I thought was the proper expected behavior. If a 360 controllers works as you mentioned above that's good news that controllers are coded properly but again it still doesn't address the keyboard issue. I havent tested this on a keyboard but with the xbox360 controller and my zeroday encoder i just select the button like im going to select a button then press left twice and it sets to none.ĭamn dude, I don't understand why you tested a controller? The testing and issue I posted was with a keyboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |