LaunchBox 13.28 Beta Thread

[JoeViking245]

7 hours ago, crusadeRGP said:

I'm not explaining myself correctly to ask what I"m trying to accomplish. I have a Magazine platform category within LaunchBox that includes various gaming literature in PDF format. How can I use the new LaunchBox reader to open these files to view in fullscreen?

One means of doing that is to create a new "emulator" that points to the reader executable.  e.g. "D:\LaunchBox\System\Software\LaunchBox Reader\LaunchBox.Reader.exe".  The make that "emulator" default for that platform.

You can get possible command-line parameters by running at the Windows Command prompt "LaunchBox.Reader.exe --help".

e.g.
Basic usage:
  LaunchBox.Reader.exe --path "C:\Docs\Manual.pdf"
  LaunchBox.Reader.exe open --path "C:\Docs\Manual.pdf" --theme black --fullscreen

I suspect that 2nd set of parameters can be rewritten to "--theme black --fullscreen --path".  Then when launched with the "game", LB will append the path at the end. Just like you see with regular emulators.

 

EDIT:

Found this in the LaunchBox Strategy Guide.    

Using LaunchBox Reader as a standalone app

Edited 6 hours ago by JoeViking245
new discovery

[Rlad]

Regarding the issue i had with the D-input controller overriding the x-input in the reader, it seems to be a windows issue not specifically LB as i had the same problem testing ShadPS4.

[MysterNybble]

18 hours ago, Jabb3rJaw said:

Sorry I realize I copied the WMP file. Here are all the files requested with the most recent crash using VLC about an hour ago.  Here’s what’s confusing me, I normally get a crash within the first hour  if it goes longer without a crash it doesn’t crash at all and can run for hours  

Debug 2026-08-04 04-42-18 PM.log 395 kB · 1 download MediaEngine 2026-08-04 04-42-19 PM.worker.log 3.4 MB · 1 download MediaEngine Client 2026-08-04 04-42-19 PM.log 1.26 MB · 1 download native-v1-BigBox-20260804T211439836Z-p5200-t12296-C0000374-17b60245-34e8-4bb9-9b53-2a71cc2c.dmp 33.15 MB · 1 download native-v1-BigBox-20260804T211439836Z-p5200-t12296-C0000374-17b60245-34e8-4bb9-9b53-2a71cc2c.json 759 B · 1 download Report.wer 112.15 kB · 1 download

Thanks! While not conclusive (crashes never really are!), this strongly points to some input/controller-related issue. I'll have to scour our DirectX/DirectInput code to see if we're doing anything unsafe. This would explain the 'randomness'; it could be 'not every time but sometimes' while a controller powers up or down or loses connection to Windows itself.