Puukko
Arcane
In all fairness RDR was released right in the middle of that ugly brown period, my screenshot is with Reshade as well. You definitely want to touch up games from that period if you can.
And following scalers:fullresolution=original
windowresolution=original
output=surface
joysticktype=4axis_2
So, all 16 buttons and 4 axes used. Can you beat that, joystick-fags?left analog stick: analog joystick (ship's direction) [DosBox input]
triangle: x (firing settings)
square: w (weapon settings)
circle: (roll) [DosBox input]
cross: (fire) [DosBox input]
L1: r (target nearest enemy)
L2: y (previous target)
L3: i (toggle target boxes)
R1: s (shield settings)
R2: t (next target)
R3: enter (match speed of target)
Select: shift+a (assign target to wingmen)
Start: p (pause)
d-pad up: ' (select next component)
d-pad down: . (cockpit on/off)
d-pad left: f9 (laser recharge rate)
d-pad right: f10 (shield recharge rate)
right a-stick up: ; (shield energy to lasers)
right a-stick down: ' (laser energy to shields)
right a-stick left: - (decrease throttle)
right a-stick right: + (increase throttle)
You mean DOSBox SVN Daum 20140125?Daum's DOSBox (adds quicksaves, MT-32 emulation, Direct3D output, Glide support and more - go with the build from 26.01.2014
Yup. As always.Out of curiosity, did the game already detect the controller originally?
If you're talking about the same joystick, then maybe DosBox hates it for some reason. Maybe try some other setting in dosbox.conf, like "fcs" or "ch":I've had this weird issue over the years where I want to use my joystick with a flight or space sim, and while it connects to the computer fine, it makes DOSbox lose its damn mind some way or another. Its been consistent across every system I've used for some bizarre reason.
# 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.
I've had a couple over the years, but the last time I tried the one I currently have, it was always moving, like it had no deadzone. Curiously, I checked just now and its solved...I just need to manually have DOSbox register each axis as a joystick one. Weird. Did it always have that functionality and I've just now noticed it or is it new?If you're talking about the same joystick, then maybe DosBox hates it for some reason. Maybe try some other setting in dosbox.conf, like "fcs" or "ch":
fullresolution=original
windowresolution=original
output=surface
aspect=false
scaler=none
scalers work fine, at least when using Nvidia GPU.Scaling is not performed for output=surface.
Sadly, you can call me a graphicswhore, but I can't enjoy my DOS games when they look like shit (wrong aspect ratio, pixelation, shitty filters). And unfortunately that's exactly how DosBox-X operates.Started as a fork of the DOSBox project, it retains compatibility with the wide base of DOS games and DOS gaming DOSBox was designed for. But it is also a platform for running DOS applications, including emulating the environments to run Windows 3.x, 9x and ME and software written for those versions of Windows.
fullresolution = desktop
output = surface
fullresolution = desktop
output = default (it uses direct3d)
fullresolution = desktop
output = openglpp
fullresolution = desktop
output = default
aspect = false
fullresolution = desktop
output = default
aspect = true