Can we expect an lr-package for dosbox some day?
-
@edmaul69 So I started the mapper in dosbox and that works. But I get a dark blue keyboard with none of the options you are describing. There is no player 1 or 2 or hot key buttons. I'm guessing here that if you access the mapper in game, it looks more individualized for the game, but pressing f1 and ctrl in game causes weird lines and video loss. Here is a picture of the mapper launched from dosbox. Sorry it is so blurry. But it will give you the idea. Thanks for your help on this, by the way.
-
@kevinshope mod 1 mod 2 and mod 3 are the hotkeys. In the middle of the blue screen you see joystick 1 and 2. Click on 1 of the buttons there. Then at the bottom press add. Then press whatever direction or button i said. Then choose the keyboard keys i mentioned and click add at the bottom. Then press what controller button i said to add to those keys. Next click on mod 3. Then choose add. Then press select on your controller. Then in the middle of the screen is shutdown. Click on that then click on add at the bottom. Press start Then in the bottom left corner click on mod 3. Now click on save and exit.
-
@kevinshope made an edit. Forgot to mention to press start. Accidently said select
-
I compiled and tested the lr-dosbox core yesterday. There was supposedly a major bug in which inputs would repeat when pressing a key, thus making the core unusable, but that wasn't happening for me, so I assume this was fixed at some point.
The core works OK, but the speed is quite slow compared to the standard dosbox. It's possible to adjust the CPU cycles in the core's RetroArch settings to speed things up, and get a simpler game such as Wolf3D to run fullspeed, but more complex games like Descent run as a slideshow. I also tested Commander Keen (working fine), but I couldn't get Doom working - the shareware version exits with the "game mode indeterminate" error.
Keyboard and mouse support seems to work fine, but my joypad wasn't being detected; though perhaps it's a configuration issue per-game. The core does seem to let you map keyboard inputs to RetroArch's joypad buttons, but that also didn't seem to be working for me.
@BuZz, if you want me to send a PR to add lr-dosbox to the script (taking into account the issues above), let me know. I haven't submitted due to the port being inferior particularly for more complex games, so it probably would need discussing first.
-
@psyke83 I already have a module for it so no need to do a PR. I'll retest it.
-
@psyke83 yeah if they got it working at normal speed it would be cool. I heard it was really slow. One issue i am curious about? I use .sh files to boot directly into games. If it ever does get fixed for speed, is it even possible with the lr-dosbox to mount disc drives and boot directly into games? I am pretty happy with standalone dosbox and im not sure how the libretro version would have any advantages since i assume it would need individual emulators.cfg or individual .sh files to run the games seperately. That then seems to make it about the same effort to get the games running.
-
@edmaul69 said in Can we expect an lr-package for dosbox some day?:
@psyke83 yeah if they got it working at normal speed it would be cool. I heard it was really slow. One issue i am curious about? I use .sh files to boot directly into games. If it ever does get fixed for speed, is it even possible with the lr-dosbox to mount disc drives and boot directly into games? I am pretty happy with standalone dosbox and im not sure how the libretro version would have any advantages since i assume it would need individual emulators.cfg or individual .sh files to run the games seperately. That then seems to make it about the same effort to get the games running.
It's possible to boot directly into a game by choosing the exe. So for example, if you have wolf3d unpacked into roms/pc/wolf3d, in EmulationStation, you can navigate into wolf3d folder and then choose the wolf3d(.exe) entry, which will launch lr-dosbox with C mounted to the current directory (roms/pc/wolf3d) and automatically launch wolf3d.exe.
-
@psyke83 Regarding performance - did you enable the dynamic recompilation ?
BTW see this branch for lr-dosbox - https://github.com/joolswills/RetroPie-Setup/tree/exp_modules
-
I didn't. I'll re-test tonight when I have access to my Pi, using the same build configuration from your script. Perhaps that's the cause of the input bug, so it may not be fixed at all. Will let you know soon if I jumped the gun in that regard.
-
@psyke83 does it have a way of assigning a disk drive/cd drive? Both real and iso/img?
-
@buzz I do not see the Lr-dosbox package under experimental or optional packages. Where is it listed at for instillation?
-
@kevinshope it's not yet.
-
@buzz said in Can we expect an lr-package for dosbox some day?:
@psyke83 Regarding performance - did you enable the dynamic recompilation ?
BTW see this branch for lr-dosbox - https://github.com/joolswills/RetroPie-Setup/tree/exp_modules
Your script doesn't enable dynarec for rpi3:
isPlatform "armv6" && params+="WITH_DYNAREC=oldarm" isPlatform "armv7" && params+="WITH_DYNAREC=arm"It will compile correctly when the following line is added:
isPlatform "armv8" && params+="WITH_DYNAREC=arm"Dynarec improves things. Before I could only manage 4 x 1000 cycles before audio dropouts, but now it can manage a bit under 2 x 10000 total cycles. Descent becomes playable - much much better, but probably still not at the level of the native port.
It's probably still inferior, but now I'd recommend adding this to experimental for those that want to tinker. It's definitely usable when dynarec is enabled and I haven't noticed any repeating key input issues.
I've experienced several hard crashes with the native dosbox port that I haven't seen with the libretro core, so that's one plus, at least.
-
@buzz Being a new user to linux in general, I will eagerly wait for it to be added.
-
@edmaul69 said in Can we expect an lr-package for dosbox some day?:
@psyke83 does it have a way of assigning a disk drive/cd drive? Both real and iso/img?
"imgmount" is a recognized command in lr-dosbox, so I'm assuming it will work for mounting ISOs or hard disk images.
-
@psyke83 ok. Thanks.
-
Update on Doom:
It seems that Doom & Doom 2 were failing on lr-dosbox due to case sensitivity (!). Even though DOS is supposed to be limited to 8.3 filenames and case insensitive, when the wad files are named DOOM.WAD and DOOM2.WAD on the actual ext4 root filesystem (in roms/pc/doom/), the Doom executable can't find the files, but only if running via lr-dosbox (the native port is fine). Manually renaming the files to lowercase outside of the emulator fixed the issue.
Performance is acceptable in lr-dosbox with dynarec enabled, but it's definitely a bit choppier than the native dosbox version, and certainly not reaching the 35fps engine limit at all times (whereas I suspect the native dosbox version does).
-
@psyke83 is the 35fps the limit setting with pentium_slow with the cpu at "max" (95%) or setting it at "max 110%" (full speed)
-
@edmaul69 said in Can we expect an lr-package for dosbox some day?:
@psyke83 is the 35fps the limit setting with pentium_slow with the cpu at "max" (95%) or setting it at "max 110%" (full speed)
The original Doom had an engine cap of 35fps - that's what I'm talking about. The speed difference I'm seeing may be due to lr-dosbox not supporting auto cycle rate detection, so whatever arbitrary CPU cycle speed you select will not be optimal compared to the native port automatically adjusting speed by default.
-
@psyke83 gotcha.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.