dov_EL
-
Posts
665 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by dov_EL
-
-
40 minutes ago, Lordmonkus said:
Well it looks like they finally added the non fast core. For the longest time it was only the fast version of the emulator which used hacks to improve speed so the difference is one is fast with hacks while the other is slower but more accurate. Kind of like how there's different versions of the bsnes cores for speed and accuracy.
Thank you very much. So we can say that this is a core that uses accurate emulation even for PC Engine. I had not noticed that he had been released, he had escaped me
-
Mednafen : PceFast va Mednafen Pce in RA.
I can't find information on the differences between the two cores. Does anyone among you have information on this?
-
On 11/8/2019 at 2:55 AM, sundogak said:
There was another thread, although more related to controller and may be unrelated to this issue. Have you tried changing the RA Input to "Raw"
WORK PERFECT !!! THANK YOU !!!!
-
1
-
1
-
-
3 hours ago, Jason Carr said:
@dov_EL I did some additional testing over the weekend, and my initial thoughts that it was related to Retroarch's controller settings were wrong, as I couldn't replicate the issue without the keyboard being involved. But all LaunchBox should be doing is sending volume up and volume down keyboard presses, so I'm still lost here. What do the K and F9/F10 keys have to do with it?
F10 in retroarch SEND DIAGNOSTIC . Probably the system you used goes to touch a series of keys that goes into conflict with retroarch.
-
K is not the only key that creates conflicts, they also have F9 - F10 and other keys that I'm trying to understand.
-
99% the problem is this
-
-
Just now, DOS76 said:
In the input settings under hot key binds is the pause toggle set to the same key your bartop is using for LB volume?
Er not.
P is keyboard . Bartop have gamepad input .
However I tried to change this too, but I don't get any results. unbelievable -
the problem should be this, but I still don't get results even by turning off the function
-
-
Maybe I understood the problem. I could not visualize everything because I deactivated the "MENU WIDGET" function.
As soon as we try to increase or decrease the volume, the game pauses for the first time, then it works. The reararch PAUSE appears at the top right (last version) -
3 hours ago, Mr. RetroLust said:
OK https://forums.libretro.com/t/retroarch-and-launchbox-big-problem-windows-volume/24891
If I have described the problem incorrectly, can you help me with your English so that we can hear from developers?
-
15 hours ago, Jason Carr said:
Unfortunately not. It's a Retroarch glitch in that it doesn't obey the default settings.
we have some retroarch dev here? To whom can we report this problem which is very serious for those who use launchbox and retroarch in the bartop?
-
@Jason Carr this is retroarch default config setting.
Can it help you understand the cause of the problem?
-
Just now, Jason Carr said:
That's because the issue has nothing to do with any keyboards or keys. It's a glitch with controller button combos in Retroarch.
however, now that I have based the whole emulation of my bartop with retroarch and launchbox, I can adjust the volume only from a keyboard and no longer in Big Box. For this I preferred the volume which can only be adjusted from bigBox and not from InGame
-
I understood, but the fact is that if I use a keyboard that also has the volume control of Windows. If I increase or decrease the keyboard volume while I'm in GAME, I have no slowdown. Thus, keyboard manufacturers will have low-level access other than the APIs they offer to developers. Unfortunately they can no longer access this information today.
7 minutes ago, Jason Carr said:There are no keyboard drivers involved, other than the standard ones. This issue has nothing to do with the keyboard or the keyboard keys that we are sending. It has everything to do with the controllers. We already figured this out and we know exactly what's going on. Retroarch is interpreting button combinations incorrectly. Again, it has nothing to do with the keyboard.
-
15 minutes ago, Jason Carr said:
Yes, that's exactly what we use. We sound those volume down and volume up keys. That's what we've always done.
the STRONGNESS is that if the volume of Windows is adjusted through the keyboard, there is no slowing down in the retroarch. At this point I suspect that the keyboard drivers use APIs different from those that microsoft documents on the site.
-
https://docs.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes
Did you use the keyboard APIs in BigBox?
-
Just now, Jason Carr said:
Unfortunately I'm confused by what you mean. Can you explain?
Old System volume (big box)
-
19 minutes ago, Jason Carr said:
I'm pretty sure fixing it isn't even possible at this point. It was an issue with all previous releases, and as I've already stated, it's pretty clearly a bug in Retroarch. I don't think there's anything we can do to fix it.
But is it possible to ALSO have the volume as in previous versions of BigBox where it was not possible to select music in Game?
-
No fix for Volume ?
-
A solution could be:
Until retroarch.exe is started, bigbox must be frozen. Only when retroarch.exe is closed, launchbox.exe must resume its activity. -
3 minutes ago, Jason Carr said:
@dov_EL That can be fixed by adjusting the startup screen timing settings in the emulator settings.
I tried, the problem is not solved. Also because it is only the first start that causes this "problem", because thanks to the Windows superfetch, at the second start of the software the times are halved considerably and therefore the problem disappears.
-
3 minutes ago, Jason Carr said:
I haven't really come up with a solution yet. I still haven't figured out what on earth Retroarch is doing in that regard, or how it could be a new issue. I do plan to look into it soon.
probably the problem lies between retroarch and windows and video drivers. I am sure that MS also offers other ways for volume commands, you should look for a group of developers, they will certainly offer different solutions than those used.
Retroarch and Commoroe 64 : 3 new cores! 3rd one - VICE 3.0 (Commodore 64 emulator)
in Emulation
Posted
retro joy in not avaiable in VICE