Jump to content
LaunchBox Community Forums

Indrid_Cold

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Indrid_Cold's Achievements

1-Bit Wonder

1-Bit Wonder (1/7)

2

Reputation

  1. I was just bemoaning the fact that I was going to have to do this 100 times. Then came across the link below. Of course JoeViking already solved that too! 💪
  2. I need help getting LaunchBox to close an .EXE it did not launch. To be specific, I want LaunchBox to close PhoenixEmuProject.exe when I press the ESC key even though LB did not launch the Phoenix emu. I have LaunchBox launching LBPhoenixLauncher.exe (LB gives that .EXE the full path to the .IMG). LBPhoenixLauncher.exe launches PhoenixEmuProject.exe ,passing along the full path to the .IMG and then makes the EMU full screen. I got LBPhoenixLauncher.exe from here: https://forums.launchbox-app.com/topic/61999-another-phoenix-launcher-without-the-preloading-games-requirement-lbphoenixlauncher/ But now I am hoping to close PhoenixEmuProject.exe by using the ESC key instead of having to use CTRL-Q (the built in shortcut within the emu and the emu does not provide an option for setting up a different exit hot key) Nothing I put in the Running AutoHotkey Script will ever be effective since what LB called (LBPhoenixLauncher.exe) is already closed (i even get a quick flash of the exit screen right before the Phoenix EMU launches the .IMG). Before I realized that LB is no longer using the Running AutoHotkey Script (since what it launched has closed), i tried all kinds of things like below. $Esc:: { WinClose, ahk_exe PhoenixEmuProject.exe } But like I said, NOTHING in Running AutoHotkey Script will ever be effective because as far as LB is concerned, the .EXE it launched (LBPhoenixLauncher.exe) already exited (its not running). Maybe LB can launch 2 .EXEs (LBPhoenixLauncher.exe and something else like Notepad minimized) and then the Running Script will still be effective since that 2nd EXE is still running? Among the other Phoenix emu launchers (some of which specify they included the ESC = exit hotkey ) I want to use LBPhoenixLauncher.exe because it prepopulates the 3DO meta data for you, without having to do all the 3DO games before hand within PhoenixEmuProject.exe If nothing else I can always fall back onto using one of the other Phoenix emu launchers but I am hoping to keep my existing setup if possible. Any help is appreciated, thanks!
  3. Getting screen tearing when in full screen with latest version of PCSX2? Is the screen tearing gone when you run in a maximized window instead of running full screen? Then you may want to try "borderless windowed". For those that don't know, borderless windowed looks like full screen, but it is just a maximized window but hides the taskbar and the window title bar. LaunchBox already hides the taskbar by default. So it's really just a matter of hiding the title bar of the maximized window. Now I have PCSX2 set to start a game in a window, have LB launch PCSX2 with the default command -nogui to hide all of the bars (except the title bar of course) then have the AHK script below in the Running Script to take care of the rest. Below is the AHK script that I pieced together from examples in the LB forums, perhaps someone else will find it useful. ; the script below maximizes the window then switches it to Borderless Windowed #NoEnv Sleep, 2000 ;wait 2 seconds WinActive("A") ;grab the currently active window WinMaximize ;maximize the currently active window WinSet, Style, -0xC40000 ;change the window style to "borderless windowed" Return ; the script below kills PCSX2 when you press the ESC key $Esc:: { Process, Close, {{{StartupEXE}}} } Background story, for the curious: When I upgraded my year-old version of PCSX2 (from Aug 2021) to the latest version (Oct 2022) I started having very noticeable screen tearing in Devil May Cry during the FMV intro and even during gameplay. A lil Googling found a post revealing that starting with PCSX2 v1.7.2187, it disables the windows DWM when in full screen mode. For some users with a Variable Refresh Rate (VRR) monitor, that could mean screen tearing. And I'm one of those lucky guys. Turning on Vsync fixes that, but turning that on also makes the game run slowly for me. I tried a bazillion combos of audio / graphics / renderer settings, even disabled VRR on the HDMI port on my TV that my PC is plugged into and also changed the setting in Nvidia control panel from G Sync to "fixed refresh rate". Yet still no matter what combo of settings I enabled/disabled I was always left with either screen tearing without Vsync or horrible performance with Vsync. Running in a maximized window, it runs fine with no screen tearing. So "borderless windowed" was my best option. So now I have PSCX2 launching in a window, LaunchBox using the default command -nogui (to remove the "settings bar" from window) and added that AHK script to the Running Script. Thus ending a couple days of pain and frustration trying every combo of settings imaginable! My Setup: Monitor - 75" Vizio P Series Quantum X P75QX-H1 CPU - i5 10600kf (6 core / 12 thread @ 4.9GHz liquid cooled with AIO) RAM - 32GB 2666MHz GPU - GTX 1660 Super DISK - NVMe M.2
×
×
  • Create New...