pjburnhill

@polymorph77Doh, just came back to say that as I realised that was the case! Thanks.

Hi, Is there a document somewhere which details the specifics of creating a Big Box custom theme and what the limitations are? I come from a design point of view with fair amount coding background but can't seem to find any concise information on this. Is there just a page I haven't seen? I tried searching the forums but maybe used wrong terms.. What I'm specifically after at the moment is the limitations of XAML in regards to Big Box - how far can I deviate from the Big Box default theme, in terms of design, before it can't be done in the Big Box UI.. Thanks! PJ

Bedwyr said I'm still trying to figure out the status of the Steam Controller and what, exactly, it does when Steam is either running or not running. Valve refers to the not-running mode as "Lizard mode" referring to the rudimentary emotional human brain ("lizard brain"). A number of redditors and Steam fans suggest that Lizard Mode is a combination mouse-and-keyboard in HID rather than Xinput... but maaybe it runs through Xinput when Steam is running?? I dunno. It's hard to get answers and you know how Valve is. I have found that if you launch an Emu/Game through Big Picture, the controller is treated as an Xinput device, but if you close/minimize Big Picture (returning to Desktop), it turns into that 'Lizard' mode with keyboard&mouse emulation.. So, BB works great if you run it from the Desktop in the 'Lizard' mode (using it as Keyboard & Mouse), but the problem raises as you launch any game that requires controller support - it doesn't find a controller as the controller is still treated as Keyboard & Mouse. The only way to get the controller working through Steam Link as an Xinput controller is to run Emu/Game through Big Picture, the problem there is of course that BB doesn't currently support Xinput so you need a physical keyboard/mouse to bridge from Big Picture -> BB -> Emu/Game. Eagerly looking forward to the Xinput support in BB! Cheers, PJ

Hi Jason, Sorry to pester on this but have you had any luck with implementing xinput controller inputs to BB? I'm trying to get it to work with x360ce but still no luck... x360ce recognises the 'Steamified' x360 controller but I just cant get it to work in BB at all.... How does BB use DirectX to search for the controller?

no way to delete post.

Just a follow-up: Indeed, if you use -userconf, the first -conf to follow is the 'master' conf (i.e. dosbox.conf) and any consequent ones override any parameters that are different (apart from [autoexec] which is 'stacked' with the master [autoexec]). So, if LaunchBox had 'Additional DosBox Command-Line Parameters' in the game-specific DosBox tab, the user would have to make sure, if using -userconf, to point to the main dosbox.conf before any game-specific '-conf game.conf'. Or alternatively, Launchbox's default Dosbox command line should have this built-in so any '-conf game.conf' in the game-specific 'Additional DosBox Command-Line Parameters' would always be the 2nd conf without the user having to add the main dosbox.conf manually. Sorry to ramble on this, just would really like to see this implemented

Hmmm.. I'm trying to get this working with using -userconf in the command line parameters, but it doesn't seem to do anything.. When running Dosbox games, what is the actual command that Launchbox/BB uses under the hood? And where are the command line parameters added in that command. I.e. if I add -noconsole in the 'Application Command-Line Parameters', how is that passed on to Dosbox, or is it? Are they added as parameters for the game exe, i.e. DosBox.exe -dosboxparameters "c:\Path\Game.exe -noconsole -conf gameconf.conf" which wouldn't work.. Could we just add 'Additional DosBox Command-Line Parameters' in the DosBox tab in the game options.. ? That way you can load both your custom .conf and in that .conf define your per-game .map.. Unless the first .conf AFTER -userconf has to be the main dosbox.conf before any additional '-conf gameconf.conf'. If that is so, then I guess the 'Edit Default DosBox Config' should have 'Additional per-game .conf' check-box or something.. At the moment, after xbox controller not working in Big Box through Steam Link (xinput), this is the reason why I'm hesitant to use Big Box through Steam Link as my launcher...

Hey, Sorry if I'm being daft but is there detailed changelog anywhere online? I got the new beta update available notice and would preferably know what the changes are before updating.. Cheers, PJ

Jason: You are absolutely right, I hadn't read the update dialog properly! There must've been a LaunchBox update just as I swapped to Daum so I just assumed it was notifying about that!

SentaiBrad: Unfortunately DOSBox doesn't allow defining the mapper file in command line, only it's erasing or mapper editor starting at launch.. If it did, that would solve the whole issue! Annoying that it's not possible... http://www.dosbox.com/wiki/Usage Not sure what the screen grab is meant to show?

Thanks Jason, As you've probably noticed, I've created a feedback post at BitBucket (https://bitbucket.org/jasondavidcarr/launchbox/issues/359/per-game-dosbox-map-implementation) for this. As mentioned in the feedback, one way to do this would be to use dosbox's -userconf to have game-specific .conf which stacks with the default dosbox.conf. See: http://www.vogons.org/viewtopic.php?f=31&t=38724#p349443 Cheers! PJ

Also, is there any way to add dosbox executable parameters into the dosbox launch? Using Daum, you get a menu at the top of the Dosbox window, which I'd like to disable at launch with 'dosbox.com -nomenu' but I see no way to do that?

I agree that what Launchbox is doing now regarding DOSBox versions is probably enough for what it should do.. Yes, it would be great to have support for SVN builds with in-Launchbox settings edit, but that's really not that big of a deal.. What I do find a little annoying is, as I use Daum myself, is that if I have 'Check updated on launch' option enabled in Settings, it also checks for official DOSBox version against the one in .\DOSBox and notifies about a new official version.. So either you turn off update check on launch for everything or live with the repeated notifications of DOSBox update..

Thanks Jason, that would be massively helpful. At the moment RetroArch, DOSBox, Snes9x, xinput Games etc all work through xbox controller -> Steam Link -> Big Picture -> Emu/Game And even this: xbox controller -> Steam Link -> Big Picture -> LaunchBox/Big Box -> Emu/Game But I have to use keyboard/mouse for LaunchBox/Big Box in the middle of the chain. I would be eternally grateful if I could play my collection of old Dos game from my sofa with just a controller!

Hi, I'm trying to figure out the best way to create and use Dosbox mapper files (.map) per-game basis (to use my xbox controller). My current workflow is to create a new .conf file for each game and in the settings, point to a .map file I've previously created for that game. Is there a way to point Dosbox to a mapper file without creating a whole new config for the game? Command line command or something? Am I missing some simple trick here? Thanks, PJ

Right, continuing with some controller issues. I have no idea why this happens but I'm running Big Box through Steam Link -> Big Picture -> Big Box. As per previous post, the controller works if plugged directly to host computer (as long as I run in Win 7 Aero theme, not basic) but when running Big Box via Steam Link, it doesn't work at all (and not recognised in the Controller Setup in Big Box). The controller works fine this way in all xinput apps through Steam Link, including RetroArch and all games... Just not in Big Box.. I assume Steam uses some sort of xinput emulator for the controller when plugged into Steam Link, which doesn't seem to talk to DirectX... Is there way for the DirectX to hook into Xinput or something? Would a 3rd party app help here? Thanks in advance, PJ

Hi, I've just imported a stackload of old Dos games and going through them, trouble-shooting issues (installations, configurations, cd-rom issues etc.). The problem is most of the time, when there is an issue, Dosbox runs and quits straight away, so I have no idea what the error was during launch. I have to open Dosbox manually, mount each game folder and run in there just to see what the issue was. Is there any way to temporarily disable Dosbox window auto-close after application run in Launchbox? Thanks, PJ EDIT: Doh! Just found this under Launchbox settings!..

Hey Jason, That's where I checked the settings for controllers - in Big Box. I've ticked both tick boxes ('Enable Game Controllers' & 'Use All Controllers'). Nothing's showing under 'Device:'. I've got an official Xbox 360 Wireless controller and official wireless receiver. As I said in the previous post, the controller works fine in Steam Big Picture and any games which support xinput natively. What system info would you need to figure out what the issue could be? Cheers, PJ EDIT!: After some heavy uninstalling, removing, installing and opening joy.cpl (didn't show there before) and selecting as preferred device, NOW it's working!...

Hey, I'm trying to get my Xbox 360 controller to work with Big Box and having no luck. I've ticked both boxes in Options under Controller and the controller doesn't show up under controllers.. It works fine and as it should under Steam Big Picture mode... no idea why it wouldn't work in BB! I'm using latest 64bit drivers from: https://www.microsoft.com/hardware/en-gb/d/xbox-360-controller-for-windows Windows 7 Ultimate on a MacBook Pro Retina 15" Thanks, PJ

Right, I just bought the Premium licence and I'm having the same issue not being able to check the checkboxes in settings. I'm using Windows 7 classic theme to keep things bare-bone and I'm having to switch back between that and the default theme to change the settings in Big Box. Secondary issue is that I can't get my Xbox 360 wireless controller to work with Big Box, doesn't show up in the Contollers section, but will post a separate post about it..