11/9/2023 0 Comments Magic dosbox svn core![]() Thank for your amazing work on this core. I don't use the retroarch features mentioned (rewind, slow motion.) Using Dosbox pure, framerate stay fixed to 144Hz (the native monitor refresh rate, meaning VRR does not work) Eg, launching "Cadaver" for example makes the framerate approching 70Hz. In the monitor menu i can see the framerate adapt to content. Sync to Exact Content Framerate (G-Sync, FreeSync): ON I'm on Linux (ArchLinux) with a VRR setup. RetroArch settings under Video -> Synchronization.Īs most of the trouble I have is related to other RetroArch features like rewinding, slow motion, gpu sync while using the automatic performance cycle mode, I'm also curious if anyone here uses these features.Įdit: As most of the trouble I have is related to other RetroArch features like rewinding, slow motion, gpu sync while using the automatic performance cycle mode, I'm also curious if anyone here uses these have the same issue like others here and stay with Dosbox-Core until this one will be fixed. But Variable Refresh Rate currently doesn't work with DBP because of the way it renders frames, as described here. Maybe call it 'Classic' lol.Īnd if you implement some equivalent to 'external' mode, will VRR/FreeSync/G-Sync work with it? This is the only way to get full speed and truly stutter-free DOS games, even better than a 70Hz monitor because it always perfectly matches the refresh rate and compensate for fluctuations in frame rates (like slowdown). Although at 60Hz DOSBox-Pure occasionally looks slightly smoother than any of those modes in DOSBox Core/SVN, depending on the game, which is one of the reasons i hope you keep your current implementation as a separate option. ![]() But none of these are ideal on a 60Hz display, there's still practically always stutter to some degree. I just try out 'internal' 'internal (fixed 60fps)' and 'external' and use whatever is best. You can only go lower if you have a strong enough CPU or you'll get crackling audio.įor me it entirely depends on the game. As for input latency, I choose a lower number on the audio latency setting under audio output of retroarch to give me quicker input commands. As far as video synchronization settings I leave them at default. I don't know if Little big adventure 2 is a 70 Hertz game but it seems to be enjoyable on a 60 hertz screen.not too slow. And besides I don't see any other way around this since most people don't have 70 Hertz monitors. I'm interested in both the core settings (timing mode) and RetroArch settings under Video -> Synchronization.Įdit: As most of the trouble I have is related to other RetroArch features like rewinding, slow motion, gpu sync while using the automatic performance cycle mode, I'm also curious if anyone here uses these features.Īs far as core timing mode, I use external because it syncs dos content to retroarch's front end timing of 60 hertz no matter the refresh rate of the dos content. Wondering if the people subscribed to this issue could report what settings they find ideal when using either of the other DOSBox cores (dosbox-svn or dosbox-core). I can't promise anything at this point just yet because getting that automated scaling right at stable framerates without (noticeable) stuttering is very tricky. To counter the performance loss either the "Threaded Video" option of the front-end or maybe a core option that brings back some form of asynchronous processing could work. Adding input latency on the other hand is definitely a no-no. I'm willing to sacrifice a bit of overall performance for this. It should actually result in lower input latency because the DOS emulation and the frontend won't run asynchronous anymore. If this works out, it should be a "best-of-both-worlds" thing and would end up being the way forward for DOSBox Pure. So I'm currently trying to get something like the external timing mode working but with something similar the cycle scaling feature of regular DOSBox. AUTO is the default mode in DBP and I think it's a big part of what makes DOSBox fun to use. This issue was opened just in time when I started trying out some things to improve this.Ī huge problem in my opinion with the 'external timing mode' in the other cores is that it doesn't support AUTO/MAX cycle scaling. ![]() Thanks for linking the other related issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |