It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
DosFreak: You can try the Linux version of DOSBox, according to the git webpage the person who worked on Chrome for DOSBox stopped working on it:

https://www.androidpolice.com/2018/08/19/install-linux-applications-chrome-os/

If the same issue then something is going wrong with your OS and/or keyboard.
Yeahhhh. I tried that. I could never quite get that to actually work. Meanwhile, the chrome app version does.
I know this is an ancient post but I feel like it could use a bit more data. I'm writing this from memory so apologies in advance if some details have gone muddled.
avatar
AmethystViper: set "joysticktype" to fcs and "timed" needs to be set to false.
analog sticks won't drift away (caused by "timed" being set to [true]).
The best setting for timed depends on the way that the game reads the joystick, and is therefore game-specific.
avatar
AmethystViper: thanks to [fcs] enabling the D-Pad/Hat swtiches
the horizontal axis on the right stick doesn't work for some reason
I can't sprint and shoot at the same time
You can't just enable the d-pad/hat, you need to trade for it. The gameport joystick connector had pins for only four axis and four buttons, no hat! Your choices are CH, which sacrifices the button combinations, and FCS which sacrifices one axis. The game must also support these sticks and be configured accordingly.

Basically choose ch if you need all four axis + hat for the game (but can then only press one button at a time), and fcs otherwise (only three axis + hat, but can press more than one button at the same time).

You may also want to look for an "improved" dosbox, as the stock one is a bit bone-headed here. Unfortunately I forgot the particulars, it's been years since I fiddled with this. But I seem to remember something about it applying the DOS restrictions to itself too, even though it could at least easily produce keypresses from excess controls.

I mean, there's no actual reason why you couldn't have four axis and four buttons with no limitations at all, mapped to a standard joystick that the game can see, and in addition to this have the d-pad send arrow key events. But I don't think you can do that with the mapper in stock dosbox. Not sure about daum or the others.
Post edited March 05, 2020 by Rixasha
I'm unable to play with two controllers in MK.
avatar
Qbix: start dosbox with the -startmapper commandline parameter
avatar
EspyLacopa: Sounds like a great idea.

How do I do that on a Chromebook using the Google Chrome app version of DosBox?
Look on the bright side, the normal dosbox won't even launch unless a physical mouse is attached.
avatar
AmethystViper: This is something that has been bugging me whenever I see a problem concerning DOSBox and being able to use a Xbox 360 or XInput controllers to play older DOS games. Usually when this problem crops up, the most common answer I see is "use programs like Xpadder or JoyToKey" to get around this. The thing is the answer is already within DOSBox, it just requires a few config edits.

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=false
avatar
AmethystViper: Here are the default settings DOSBox's joystick settings, but the glaring problem these settings for Xbox 360 or XInput controllers is not being able to use the D-Pad and the analog stick not working properly. After fiddling around the settings and looking up the solutions to these problems, these are the settings I use for some of the DOS games I play under DOSBox. You might also want to reset the mapper file (usually it's "mapper-0.74.map" by default for v0.74) or delete it before you change anything; you can save a new one once you made the appropriate changes. What you need to do is set "joysticktype" to fcs and "timed" needs to be set to false. By doing this, your D-Pad should work (thanks to [fcs] enabling the D-Pad/Hat swtiches) and the analog sticks won't drift away (caused by "timed" being set to [true]).

Now what if a particular game doesn't give you the ability to rebind the inputs for the controller or calibrate the analog sticks, either in-game or as a separate set-up program? This is where DOSBox's keymapper comes in (special thanks to F4LL0UT for this). By pressing Ctrl+F1, you'll get a screen like this: http://i.imgur.com/Ac83yEV.png

The keymapper is kinda like DOSBox's Xpadder though not as advanced but gets the job done for the most part. If you want to bind a certain key to a controller input, let's say binding the arrow keys to the Xbox 360's controller's D-Pad, first you click the key on the on-screen keyboard for the arrow keys, then click on "Add" on the menu where you will be prompt to add another input to the command (e.g. bind Arrow Key Up to D-Pad Up, Return/Enter Key to Start, Gamepad Button 1 on the Xbox 360 controller's A Button). The same can be done for keyboard inputs, like mapping WASD to the Arrow Keys for Abuse.

Unfortunately this isn't the "end-all-be-all" solution for rebinding inputs on a controller. So far this worked on some fighting games like One Must Fall 2097 or Super Street Fighter II: Turbo, shoot 'em ups like Tyrian 2000, and platformers Jill of the Jungle or Genocide 2: Master of the Dark Communion. Older first-person shooter games like Doom aren't to keen when it comes to rebindable inputs for a controller as the horizontal axis on the right stick doesn't work for some reason; the SVM Duam build does get around this but for some reason I can't sprint and shoot at the same time (it could be something I did with the config file though). There's also the inability to rebind mouse inputs such as the left or right click, mouse movement, and the scroll wheel on the original DOSBox's keymapper, so you're out of luck for point-and-click games or if you're planning to play Abuse on a controller unless you get Xpadder or similar programs.

I hope this can help some people out with playing games on DOSBox.
Have you tried Dosbox Staging at all?

https://dosbox-staging.github.io/

It supports joysticks with as many as 16 axises.
Post edited May 29, 2020 by TheBigCore
dosbox staging does not allow me to run shadow warrior complete in multiplayer, that have to be done through the included dosbox. one of the people i play with need to use a controller because he can not handle a keyboard for long. i tried the solution at the top of the page and nothing happens, the controller is simply not recognised by dosbox.
avatar
andreasaspenberg2: dosbox staging does not allow me to run shadow warrior complete in multiplayer, that have to be done through the included dosbox. one of the people i play with need to use a controller because he can not handle a keyboard for long. i tried the solution at the top of the page and nothing happens, the controller is simply not recognised by dosbox.
A: https://www.8bitdo.com/sn30-pro-plus/ A proper multimode controller will go a long way to fix most issues.

B: https://www.youtube.com/watch?v=0nVjB9hSoJI And here's a tutorial video by Pixelmusement.
i do not need that. my xbox 360 controller is good enough. i just need to set up dosbox correctly if someone is to use it there. how do i do that?
avatar
andreasaspenberg2: i do not need that. my xbox 360 controller is good enough. i just need to set up dosbox correctly if someone is to use it there. how do i do that?
I noticed you mentioned you had this problem with dosbox-staging; support for more axis (which makes modern controllers work correctly) is *not* available in stable 0.75.0; it IS available in unstable dosbox-staging 0.76.0-alpha builds; you can download latest alpha builds from here (but you need a GitHub account to access build artifacts hosted on GitHub).

I also uploaded recent builds here (no GitHub account required):
dosbox-staging-linux-v0.76.0-alpha-274-g35a4c.tar.xz
dosbox-staging-windows-x64-v0.76.0-alpha-274-g35a4c.zip
dosbox-staging-macOS-v0.76.0-alpha-274-g35a4c.dmg
Post edited July 06, 2020 by dreamertan