/vr/ - Retro Games

good luck, but half of /vr/ has a panic attack looking at the retroarch main menu so you probably won't get much help here

>>7330385
You don't need to use RA to use dosbox.

>>7330385
>r*troarch

>>7330354
Just use fucking eXoDOS

>>7330385
>using RetroAss to play games in DB

>>7330398
>ironic censorship

The S3 Trio64 isn't a particular system, it's a graphics card. It's fine for practically any DOS game, though obviously it won't run Glide for the few DOS games that support it.
Here's a quick rundown:
2750 cycles is roughly equivalent to a 286 12.5 MHz
7800 is a 386 33 MHz
26800 is a 486 66 MHz
77000 is a Pentium 100, which you shouldn't really need for much, mostly stuff like Quake, Blood, maybe Duke. But in that case you should just set it to core=dynamic and cycles=max.

>>7330354
There's no way to configure cycles to "just work" on all games since some older games only run properly with a low value and some newer games only run properly with a high value.
What game are you trying to run?

Sounds like you are shit out of luck. How unfortunate.

>RA is ba-

>>7330698
-sed since it makes /vr/gins SEETHE

>>7330354
It really depends on the game, exodos comes preconfigured

>>7330698
i hate it really i always thought shit like the monitor graphic around the screen was stupid

>>7330385
I have not ever and will not ever use that crap

>>7330416
Seconding this. Look in to ExoDos.

>>7330354
Just use PCem

>>7330354
>Westwood
based and Klepackipilled

>>7330354
Can you name some games that you have trouble with?

Btw using cycles is easier than people think at first sight, when i started using Dosbox i thought a slow host computer needed more cycles than a fast host computer to reach the equivalent speed, however this isn't true. A 2008 quadcore and a 2020 quadcore should roughly give you the same results when using the same cycles.

Only if you use a pc slower than the 2008 pc you will start to notice lags more so you'll need to add more, or use max cycles.

Some cycles i frequently use : 10 000 for the oldest games (if still too fast, use auto = 3000), for medium games 40k to 60k, for some specific games like Magic Carpet use 120k, many others can use max cycles if they have their own limiter, for example Wacky Wheels can just run on max cycles and it won't freak out.

You can try my custom made (dosbox based) dospack, it has 100+ games preconfigured (sounds, speeds, controls and resolutions):

https://mega.nz/folder/CldGAahb#yn_8LkRHraywPgKJMp5pqA

P.S. it's best to always use core=dynamic

>>7330354
PCEm is far more accurate if that's what you want. It'll emulate individual PC parts accurately. It's more like bsnes whereas DOSBox is like zsnes.

>>7330354
You can always just set-up PCem.
>>7330698
This looks awful.

>>7330354
>begs for help
>gets replies
>doesn't bother to reply back

>>7330698
reminder that CRT's don't actually look like this and scanlines aren't visible from more than a foot away

>>7334228
zoom zoom

>>7330385
>retroarch menus aren't bad

>>7330698
>>7334640
retroarch users are fucking stupid

Do you want DOSBox to accurately match a specific CPU speed? Or do you want it to actually run each game at the correct speed?

Because you can't have both. Which is exactly how it was on real PC hardware.

I'd really recommend Retro Arch for DOSBox. Most brainlets here can't use it, but it's easier to use and set up with individual games because you can easily save DOSBox game profiles, and do things like quickly fuck around with the CPU cycles speed while the game is still running. It's easier/quicker.


This is what i do:

1. Start a game in Retro Arch with a DOSBox core (I typically use the 'DOSBox SVN' core). If you don't know how to use Retro Arch and install cores then check out JewTube tutorials.
2. Get in to the actual game and press F1.
3. Go to Options.
4. Click on 'Save Game Options File' to save DOSBox settings for the game that's currently running.
5. Now simply fuck around with the four CPU Cycles settings shown in the bottom of the pic.
6. The two 'Coarse CPU cycles' options will make more obvious large changes to game speed. Increase/decrease these numbers and then press F1 to unpause the game and see how it is now running. If it's running too slow for example, press F1 again, go back to Options and increase these numbers. Repeat this until it's looking good.
7. The two 'Fine CPU cycles' options will make smaller less noticeable changes, but it's important to use these to get the game speed perfect (higher numbers = increased speed). Again, change these numbers, then press F1 to see how things are running. Repeat this the same as above.
8. Go back and forth doing this until the game is running at a nice speed/frame rate, and that's it. You don't have to do anything else. The settings will already be saved for that game.
9. Now repeat these steps for each DOS game, making sure you always click on 'Save Game Options File'.


By doing this i have around 60 DOS games running great. I can just click on a game and it will JUST. FUCKING. WORK.

>>7330354
if the game is on GOG it already has a working dosbox config.