Jump to content
LaunchBox Community Forums

igotdvds

Members
  • Posts

    194
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by igotdvds

  1. I want to fill my 4:3 screen with the game video. If I enable background videos, a 4:3 video will fill the screen. If I dont and use an "IMAGEVIDEO" object, it wont, and leaves a small black bar at the top and bottom.

    Code I'm using for imagevideo window.

     <transitions:TransitionPresenter TransitionSelector="{Binding BackgroundTransitionSelector}" Content="{Binding ImageVideoView}" Height="{Binding ElementName=Canvas, Path=ActualHeight}" Width="{Binding ElementName=Canvas, Path=ActualWidth}" IsContentVideo="true" />

     

  2. 1 hour ago, prophecy0 said:

    I have trouble with Big Box stuttering when I navigate through my game lists. I have less than 30 games total in Launchbox at the moment. My computer specs are as follows:

    CPU: i7 4790k @ 4+GHz
    RAM: 16GB DDR3 
    GPU: GTX 980 Ti

    Launchbox is installled on a Samsung EVO SSD. 

     

    Here is a video of what the stuttering looks like. When navigating the platforms everything runs completely smooth, but when I navigate the game lists there is slowdown. It appears that the slowdown occurs when Launchbox is trying to load the background art. Is there any way to disable background art completely? I'm about to try deleting all but one piece of fanart for each game to see if that helps at all. 

     

    edit: Deleting all but a single piece of fanart didn't help.

    Are your images cached? (meaning) have you scrolled through that library multiple times. If you hover on one and then com back to it, does the stutter reoccur?

  3. 5 hours ago, Crush said:

    %1% is the first command line parameter, %2% the second, e.t.c

    When running a game, LB usually sends the romname (including path) after the emu executable so if you run Archon.g64 with Hoxs64.exe, the command line will be something like:

    D:/emu/c64/hoxs64/Hoxs64.exe D:/emu/c64/games/archon.g64

    So %1% will hold "D:/emu/c64/games/archon.g64"

    So how would I use the new %gameid% feature?   I added a new exe and left no parameters defined. It output the rom path as %1% but nothing for %2% or %3%. How can I get %platform%, etc. to work?

  4. 1 hour ago, Crush said:

    You send all command line parameters through the ahk script. Here's my Hoxs64 ahk script - modified with markmon's suggestion so i can read the rom name outside LB - it maps various joystick buttons to Save State, Load State, Wrap on/off, e.t.c and uses the romname to save/load game states.

    I compiled the script to .exe and use it as the emu executable instead of hoxs64.exe (so i don't have to setup any ahk scripts or command line parameters in LB)

    #SingleInstance force
    #WinActivateForce

    SetWorkingDir, D:\Emu\C64\hoxs64

    GameName = %1%
    SplitPath, GameName, rom_name
    rom_name := SubStr(rom_name, 1, -4)

    RunWait, "hoxs64.exe" -fullscreen -autoload "%GameName%"

    ; Exit emu
    esc::
       Send !{F4}
       ExitApp
    Return
    4Joy17::
       Send !{F4}
       ExitApp
    Return

    ; Change Disc
    4Joy2::
       Send !{enter}
       Sendinput {Alt Down}
       Sendinput {D}
       Sendinput {I}
       Sendinput {E}
       Sendinput {Alt Up}
       WinWait, Choose a disk image file
       WinWaitClose
       Send !{enter}
    Return

    ; Switch Joysticks
    4Joy7::
       Send !{j}
    Return

    ; Warp mode On/Off
    4Joy15::
       Send !{q}
    Return

    ; Load State
    4Joy18::
       IfExist D:\Emu\C64\hoxs64\States\%rom_name%.64s
          Send !{enter}
          Sendinput {Alt Down}
          Sendinput {F}
          Sendinput {Alt Up}
          Send {Down 5}
          Send {Enter}
          WinWait, Load
          Send %rom_name%.64s
          Send {Enter}
          Send !{enter}
    Return

    ; Save State
    4Joy19::
       Send !{enter}
       Sendinput {Alt Down}
       Sendinput {F}
       Sendinput {Alt Up}
       Send {Down 6}
       Send {Enter}
       WinWait, Save
       Send %rom_name%
       Send {Enter}
       IfExist D:\Emu\C64\hoxs64\States\%rom_name%.64s
            Send {Alt Down}{Y}{Alt Up}
       Send !{enter}
    Return

    ; Pause
    4Joy20::
       Send !{p}
    Return

     

     

    What dictates what %1% returns? What does %2% return? Is there a %3%? How is markmons script calling %platform%?

  5. 12 hours ago, markmon said:

    Ok here is an example of how I do this exact thing using an AHK script for pscx2. I have a set up that determines which game config to use based on the game that is being requested by the front end. In this case, the front end passes full path and rom name. I extract the full path and rom, use AHK function SplitPath which extracts just the romname, then substr to grab the name of the rom without the extension (.iso or such). From there, I am running my own script that knows the rom passed in.  In my case, I then check for whether or not a config with that rom name exists and if so I launch pscx2 with config. Otherwise we use default config.  I call this launchboxstartps2.exe and I told launchbox that pcsx2.exe is actually launchboxstartps2.exe.

    Here is my script:


    #SingleInstance force      ;Prevent multiple instances
    #WinActivateForce          ;Hopefully makes pinball fx window activate.
    exitEmulatorKey = Esc 
    SetWorkingDir, H:\Game Launcher\Theater\pcsx2

    GameName = %1%
    SplitPath, GameName, ConfigGame   
    ConfigName := SubStr(ConfigGame, 1, -4)

    ConfigBase = H:\Game Launcher\Theater\pcsx2\gamesettings
    ConfigPath = %ConfigBase%\default

    Hotkey, $%exitEmulatorKey%, ClosePcsx2  

    ifExist, %ConfigBase%\%ConfigName%
        ConfigPath = %ConfigBase%\%ConfigName%

    RunWait, "pcsx2.exe" "%GameName%" --cfgpath="%ConfigPath%" --fullscreen,,UseErrorLevel

    ExitApp

    ClosePcsx2:
    Hotkey, %exitEmulatorKey%, Off
    Process, Close, pcsx2.exe

    I completely understand this but how is your LB configured? What command line parameters allow you to read them here?

  6. 3 minutes ago, markmon said:

    You will get the exact command line that the emulator receives in this case. You can tell by launching a game,  load task manager while it's running,  poke around to select columns and enable command line and you can see the exact command line sent to the emulator. It'll most likely be the executable for the emulator as arg 1 and the path to the Rom and rom file as arg 2. 

    I have launcher scripts already i place for other purposes but I cant find any documentation regarding how to structure the command line arguments to pass variables. is it as simple as %1% and %2%? Do you have a screenshot or perhaps documentation I haven't seen?

  7. 41 minutes ago, markmon said:

    This is super easy to handle via an ahk script that launched the game emulator executable (and I'd argue that anyone that knows how to write an ahk script to do anything with the Rom name would also know how to write an ahk script that also replaces the emulator executable) . Happy to provide an example here. Basically,  create an ahk like starthosx64.ahk and have it parse the incoming command line,  runwait the actual emulator and then it can handle events as well in the script. Edit the emulator set up inside launch box to run starthosx64.exe instead and you're done. 

    What items are available to pass in this way? %gameid% is a new one..what are the others?

  8. On 1/25/2017 at 5:37 PM, Jason Carr said:

    - Improvement: A new %gameid% variable can be used when launching emulators to help with game identification

    Please elaborate..Is this is response to the ticket i opened regarding passing variables to AHK when launching a game? How can I use this?

     

  9. Anyone see this or can reproduce?

    Problem: Exiting Future Pinball causes BigBox marquees to move almost entirely off screen

    Here are the steps to reproduce this problem:

    1. Enable secondary backbox display for Future Pinball

    2. Enable marquees for BigBox (same screen as backbox display)

    3. Open Future Pinball in BigBox

    4. Exit Future Pinball

    5. Do marquees stay visible for you???

  10. 4 hours ago, jaythompson said:

    Sweet! I love the marquee. That must have been a challenge getting all the art in place for that.

    I learned Imagemagick. Pointed it to the folders with boxes and logos and ran a script. Did all of one console in less than an hour.

    Edit: Also, most of them are already available in the DOWNLOAD section.

     

    • Like 1
  11. 38 minutes ago, ckp said:

    maybe you can try creating a test emulator in LB that is just a batch file and try launching it with some game or fake game to see what gets passed. i'm pretty sure system and rom gets passed. the batch file could be like:

      echo %1 >> c:\temp\test.txt

      echo %2 >> c:\temp\test.txt

      echo %3 >> c:\temp\test.txt

    and then look at c:\temp\test.txt to see what was passed.

     

    I dont want to modify the existing configuration. I want the user to use LB to configure their emulators as they do today but allow my app the ability to know what system and other information so it can hook in to LB and give them additional options during gameplay across all emulators. Think universal pause capability and access to image directories.

  12. 3 hours ago, markmon said:

    There are always alternative ways to do things. The ahk script here may not be needed at all. On my set up,  for example,  I point launchbox  the emulator exe which is actually an ahk script that runs the emulator and does some other stuff. You'd handle that outside of launch box and you get passed the full path and filename of the Rom. You would know the name of the emulator at that point as well. Not sure what you're trying to do but the launch box ahk only runs when a game is launched anyway 

     

    Please elaborate....

    My goal is to have the user run anything in LB or BB and have it pass system name, rom path, emulator path, etc. to another application so it can interact back and forth.

×
×
  • Create New...