Jason Carr

It's coming, slowly but surely. I can get you a beta version soon probably.

Well, looking at the settings, it looks like Dark Forces only supports the X axis and the Y axis. The right analogue stick uses additional axes so unfortunately the only way you could make it work is with a mapper program like XPadder.

Lol...thanks. I've got my hands plenty full already though.

Ah, doesn't look like it. It doesn't look like that engine has any controller support. You could try using a gamepad to keyboard converter of some sort, though I've never really tried. You could try using something like XPadder: http://www.xpadder.com/.

So you point the graphics engine to the CD files? If that's all you do then you can probably just copy the files off the CD to your hard drive somewhere. Then you can just uncheck Use DOSBox in the LaunchBox game settings and point the Application Path to the XLengine_Launcher.exe file. That should work I think.

Ha, well no kidding. I was able to get it working by right-clicking on XLengine_Launcher.exe and selecting Run as administrator. Let me know if that works for you.

Hmm, interesting. Having some trouble getting it running. I downloaded the latest package here: http://xlengine.com/downloads/ I downloaded the "XL Engine Release R2" and extracted it. Then when I ran it, it told me I was missing OpenAL32.dll. So then I went and downloaded the OpenAL setup from here: http://www.mediafire.com/download/nwt3ilty2mo/oalinst.exe Then I was able to run XLengine_Launcher.exe from the package and it worked properly (was able to see the interface). Clicked on Dark Forces, and then pointed the Game Data Folder to my Dark Forces install directory. Unfortunately though when I click Play the application crashes. I'm running Windows 8.1. Maybe you can try that and see if it works for you. The error it gives me is an access violation, which could be 10,000 different things, unfortunately. The site does say it's an alpha release, so it's still very much in development. Let me know if you get it running though.

Lol...shoot.

It is, but of course the games are stretched (there's no way to change the perspective in-game to make it widescreen for DOS games). Probably the easiest way to do it is to change the output resolution. Try setting the fullresolution setting in the DOSBox configuration file to 640x480. The line should look like this: fullresolution=640x480 It's under the [sdl] section. I thought the aspect setting would do it, but it apparently doesn't. So fullresolution is your best bet, probably. You can either change it for all your games under Tools > Edit Default DOSBox Configuration, or edit it for specific games in the DOSBox tab.

Just to update this forum post, with dreams' (and others') help I believe I've fixed the issue, should hopefully be putting out a new release tonight.

nmc, I think I've finally got this fixed; if you can, send me an email (just use feedback on the site) and I'll send you a test version so you can confirm that it works. I'll put out the new release tonight if we can get it confirmed. Thanks much for your help. Jason

Thanks nmc, I've narrowed the issue down to the new DirectX controller input. Still haven't figured out why it's erroring for everyone else and not me, but at least I have a lead. Can you tell me if you have SharpDX.dll and SharpDX.DirectInput.dll files in your LaunchBox folder?

Thanks, can you check your Windows Event Log to see if you have any errors in it that might be related? Go to Control Panel > Administrative Tools > Event Viewer > Windows Logs > Application and take a look at the list. It's a bit complicated but I'd really appreciate if you could see if you could find anything; I'm at a loss why everyone is experiencing errors at this point.

So I hear. Can you screenshot me or give me any more details? Don't understand what's going on at this point.

Bah, you're not the only one. I don't understand yet what's going on; I haven't been able to get it to crash myself. Can you screenshot me or give me any kind of details that you have? For now, I've reverted the downloads on the site back to 2.14. To fix it for now, you can download the setup and install over top.

Also, does it happen on a new installation? You can go download version 2.14 from the site and install it over top and things should work properly again.

Bah, I've reverted the downloads back to 2.14. Can you send me screenshots of what's going on? I'm confused because it's not crashing for me.

I've implemented the "cancel and keep your games" option in version 2.15.

Hey dreams, I just put out version 2.15 with DirectX controller input. Let me know if Vjoy is working for you now.

jtrain, FYI, I just put out version 2.15 and I've switched the controllers over to use DirectX instead. I would expect that the controller issues you were seeing should be fixed now. Let me know if they're not.

OzzieMonkey, FYI, I just put out version 2.15 with that new Sort Title field.

Thanks, dreams. At some point here I plan on replacing the joystick implementation with a DirectX version (instead of native Win32 joystick calls), which should resolve this and any related joystick issues. For now, disabling joystick input in the Options will at least allow you to keep using LaunchBox.

Dreams, hit me up at jasondavidcarr@gmail.com so we can talk offline.

Ah, yes. Makes sense. Hopefully I can get it into the next version.

Hi dreams, I see the advantage of allowing you to stop half way through and keep your games, but there are also situations where you want to cancel and you don't want your games affected (in theory, "cancel" should really mean to cancel and nothing should be done). Maybe another "Stop" option is in order though, as with long imports, it would probably be nice to stop and not lose your progress. Thanks for the note, I'll add it to the list.