search

libretro / dosbox-libretro

Port of DOSBox (upstream) to the libretro API.
GNU General Public License v2.0
61 stars 40 forks source link

Slow #35

Open RobLoach opened 7 years ago

RobLoach commented 7 years ago

When running anything in the Archive.org MS-DOS Games Software Library, everything runs extremely slow and choppy. Know what is up?

Duke Nukem for instance...

retroarch -L path/to/dosbox_libretro.so DN1.exe
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36866061-slow?utm_campaign=plugin&utm_content=tracker%2F2175333&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2175333&utm_medium=issues&utm_source=github).
inactive123 commented 7 years ago

We'll need to see where we stand with the Dosbox core, whether we can make use of a dynarec that is available here, whether we can update from upstream, whether there are other Dosbox forks that have nice things which we should backport, etc.

I think so far only radius and meancoot tinkered with this core, so there's probably plenty to do here.

Unrelated - we should also be getting the PCem core ready as well.

andres-asm commented 7 years ago

Uhhh I can run even windows 98/pitfall just fine I only get choppiness when resolution is too high.

Did you increase CPU cycles in core options?

On Thu, Aug 11, 2016 at 2:54 PM, Twinaphex notifications@github.com wrote:

We'll need to see where we stand with the Dosbox core, whether we can make use of a dynarec that is available here, whether we can update from upstream, whether there are other Dosbox forks that have nice things which we should backport, etc.

I think so far only radius and meancoot tinkered with this core, so there's probably plenty to do here.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/libretro/dosbox-libretro/issues/35#issuecomment-239272559, or mute the thread https://github.com/notifications/unsubscribe-auth/ABpC0Hf5-YjaPvKu1fTNF0MSE5UYvPlSks5qe34EgaJpZM4Jieqx .

RobLoach commented 7 years ago

Did you increase CPU cycles in core options?

How do you go about doing that? Is that something we could enable by default?

andres-asm commented 7 years ago

It's set at 100, there is no perfect value. Press F1, go to options and raise, I usually use the x1000 value (1000, 2000, etc) then I tweak till I get good sound

On Thu, Aug 11, 2016 at 5:24 PM, Rob Loach notifications@github.com wrote:

Did you increase CPU cycles in core options?

How do you go about doing that? Is that something we could enable by default?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/libretro/dosbox-libretro/issues/35#issuecomment-239311990, or mute the thread https://github.com/notifications/unsubscribe-auth/ABpC0AAWoGsO2hurezJQ6c4DWOiVtAidks5qe6EYgaJpZM4Jieqx .

Schroedingers-Cat commented 7 years ago

But why does vanilla dosbox 0.74 (defaults "core=auto", "cputype=auto" and "cycles=auto") manage to run games like Jazz Jackrabbit at original speed while the default config of libretro-dosbox runs it at like 0.5fps?

andres-asm commented 7 years ago

because we don't have support for auto cycle rate detection?

Schroedingers-Cat commented 7 years ago

Now that is confusing. I thought this is a wrapper so when I feed it with my dosbox config file, the wrapped dosbox should behave the same, shouldn't it?

andres-asm commented 7 years ago

We don't support auto cycle rate detection. That's all.

jmfergeau commented 7 years ago

I have the same problem, but it doesn't happen all the time. The games runs fine, but there's random times where, for around 15 seconds or more, everything is unbearably slow.