DOSBox-Optionals icon indicating copy to clipboard operation
DOSBox-Optionals copied to clipboard

Weird game launch problem

Open olliraa opened this issue 4 years ago • 10 comments

I just tried this for the first time and I really love DOSBox-Optionals :) I have a DOSBox launcher Launchbox in use and there is a weird issue with starting a game. When I click on the game, the actual game won't start loading, it only opens the DOSBox screen with the standard prompt "z:". If I use the default Dosbox version 0.74, the game goes past the prompt and actually starts loading. Game starts normally also with e.g. DOSBox ECE.

It seems that for some reason the DOSBox optionals does not automagically mount the game directory as the other versions seems to do?

This also happens with other DOSBox frontends, so there's definitely something different related to DOSBox versions and launching a game.

What could be the difference, that causes this?

Win10 Launchbox 11.2 (latest) DOSBox Optionals r4338

olliraa avatar Aug 26 '20 08:08 olliraa

Hello & Thanks :+1:

I actually changed something there. Just to stay portable. So start Dosbox and everything happens in its own directory without specifying a config. However, I have checked the Config Commandos and arguments from the standard GOG or Steam installation to make sure everything is running. There are no problems in that regard. I don't know Launchbox. I've heard of it but never worked with it myself.

What does the standard argument look like. So the command line how Launchbox starts the game?

regards

MartyShepard avatar Aug 29 '20 17:08 MartyShepard

Hi, thanks for the reply :) I'm really not sure what the standard arguments for Launchbox are. How could I try to find those?

This is what it says in a guide page:

image

Thanks,

-Olli

olliraa avatar Aug 30 '20 11:08 olliraa

Hello,

-noconsole is changed to -console . Dosbox Optionals Win32 doenst show anymore on default the console window.

Normal it should works. example my Shadowwarrior setup from GOG Dosbox.exe -conf ".\GAME\dosbox_swarrior.conf" -conf .\GAME\dosbox_swarrior_settingsTD.conf -c exit works

If ihave more time i try to test Launchbox

grüsse

MartyShepard avatar Sep 01 '20 12:09 MartyShepard

Hi.

Ok, sounds logical :) Would it be easy for me to test the Launchbox? I mean I could try to help to save your time. Of course if it's really complicated then the time would guiding me :/

olliraa avatar Sep 01 '20 18:09 olliraa

You are Welcome :+1:

MartyShepard avatar Sep 02 '20 14:09 MartyShepard

THis is a repeatable issue. I cannot launch games from the command line using Dosbox-optionals; dosbox is ignoring the provided commandline executable and just opens a DOSBOX session with an interactive shell (at the Z: prompt).

Example: dosbox "c:\gamedir\game.exe" -fullscreen

just opens a DOSbox command shell window. The game.exe is never executed, and no reference to the game is mentioned.

The exact same command line with DOSbox 0.74 works perfectly and launches game.exe.

aaciii avatar Mar 08 '21 00:03 aaciii

Fixed, Comes with the next version.

MartyShepard avatar Mar 10 '21 11:03 MartyShepard

I can't do it anymore today. Got to work long hours. But the days come. promised.

MartyShepard avatar Mar 14 '21 17:03 MartyShepard

I just want to thank you for all the work you've put in so far. Main reason I'd like to switch to DOSBox Optionals is for all of the patches & updates that have been added over stock DOSBox, as well as being able to use various shaders. No rush, but am wondering if we might be getting the update that fixes this issue as well as others. Thank you and keep up the good work. :)

KojiKenshiro avatar Aug 27 '21 15:08 KojiKenshiro

Do you know when a new version will be released?

I'd love to see a "stretch to fill screen" option.

Jkapp76 avatar Aug 29 '21 17:08 Jkapp76