SiriusVI
-
Posts
570 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by SiriusVI
-
-
23 hours ago, Kmetz7547 said:
Hi.
I dont understand much of the crazy script talk up there, but have an AMD card that seems to have a similar issue with Windowcast and RA.
when I start a game i see RA crashes, yet the emu ahk script continues to play fine but in windowed.
I was going to try the turning of G-Sync I read in a post above but Im unsure how to open RA/Windowcast to try this.
Anyone help a noob out?
Thanks
I'm not sure I'll be able to help you with this problem, since I have an Nvidia card. But with the recent release of "ShaderGlass" on steam, I think WindowCast might be basically obsolete. Will have to try to integrate it into my setup though.
EDIT: so basically, what you could do is the following:
1. Download ShaderGlass for steam
2. Load the shader you want (external shaders work, too)
3. Save your configuration as a profile within ShaderGlass
4. Within Launchbox, create an ahk script that starts when launching a specific emulator, such as Xemu, such as:Run, C:\Program Files (x86)\Steam\steamapps\common\ShaderGlass\ShaderGlass.exe -f M:\TestProfile.sgpThis works for me. It's much easier to set up than WindowCast and also there is not noticeable input lag.
-
2 hours ago, skizzosjt said:
d00d! do0o0o0o0o0o0o0o0d! having an eureka moment!
Started thinking about the fact you're using the AHK version included with LaunchBox. One of the very first scripts I wrote years ago had an issue when I first started using LB. It was the other way around though, I wrote a script on a really old version of V1 and it worked fine with that version.....but LB had a newer version and it impacted the scripts behavior negatively. I had to change syntax since they changed it between those versions.
this time around I'm using a more recent release of V1
I just tried running the script with LB's AHK file, which is v1.1.24.03 and is pretty darn old relatively speaking in AHK world. Also is the 32bit version and I always use the 64bit version
THERE IS DIFFERENT BEHAVIOR BETWEEN AHK VERSIONS!
I'm betting on THAT is the root cause here! I can recreate same error that being the file is read, but I cannot get the qty of entries in the array due to it seems the count method isn't working! As I wondered with the above troubleshooting version, I can even read the array, but something not working right with the Count() method (I called it a function in other posts but it's really a "method"). I get a null value and infinite loop just like you do when trying to use it to determine number of values in the array!
Value is null using the AHK exe included with LB
yet here I am running a much more recent version of AHK V1 and it works fine!
lets check if 32bit matters at all......NOPE!
Get your hands on the latest version of AHK V1. Even I am not on the latest but should be. The last release for V1 was like a year ago. V2 was in limbo for many years and they finally pulled the trigger on making it the official release version at that time about a year ago. So V1 is actually deprecated now but it's been around for so long that most basic users aren't going to make the switch.
so for ex I have this working fine when using v1.1.36.02
I just downloaded the last official release of V1 which is v1.1.37.02 and also works fine!
Each time I try and run it with the one included with LB is the only time the script doesn't work correctly!
You will need to download a newer version from their site. You can then replace the exe included with LB with the one you downloaded
Showing this so you don't think I'm just linking you to some rando website
Got to autohotkey.com and Click the green download button
Click other versions
Click AHK V1.1
Sort by date and pick the circled zip version of the latest release. The zip version is a portable version. You can simply unpack this archive anywhere and AHK is set to jet right away. Go into that folder and copy AutoHotkeyU64.exe to where LB stores its AHK exe. (\LaunchBox\ThirdParty\AutoHotkey) Be sure to rename the file to the same name inside the LaunchBox folder. ie rename the exe you just pasted in there from AutoHotkeyU64.exe to AutoHotkey.exe
I also pointed to the exe version should you want that. this one goes through the typical setup wizard process if that is more to your liking. Adding it to start menu and Windows Programs and App list, right click context menu and the like, etc etc official program stuff.
I think I'll advocate to the dev team to not be several years behind on their AHK version lmao! They are using a version released in 2017 that's before I even started using LB let alone AHK! 🤦♂️ Gotta get with the times!
I went digging in their change log and it all makes so much sense now! this method didn't even EXIST until a later version! Of course it won't work in some version from 2017, gotta have this version from 2018 or newer to use .Count()
I assumed I was going to find some bug fix report in here for the count method rather than it wasn't even introduced until a later version, but boy I'm glad I found this info here! I go nuts not knowing the "why" of things! The dots are now fully connected!
Oh wow, that is a great find! I downloaded the version you specified and the script works now. I also tried the newest version of Auto Hotkey, just to test and it does not work.
I'll say that I don't understand why AutoHotkey releases newer versions of its software that break previously written scripts. I sure hope that all the other scripts I have set up in Launchbox over the past years still work. I usually just copy scripts that other people wrote and I don't think I have the skill to update all of these scripts so that they work with different versions of Auto Hotkey.
Anyway, thank you so so much for guiding me through this! Have a great day! 😃 (If I encounter any more problems with the script, I'll make sure to tell you all about it here, haha) -
Wow thx so much for your hard work helping me. Truly appreciate it! Alright, here we go:
1. box
2. box:
3. box
4. box
5.box
6. box
7. box
8. box
So this is empty, it does not = 3 ...
AKH window looks the same:
-
6 minutes ago, skizzosjt said:
Thanks. This confirms the script is stuck in an infinite loop that is skipping over the body of a loop due to not reading your WindowCast.txt file appropriately. Further confirmed you never get the timeout message since it never reaches that line. As far as I can tell the root problem is the script not reading/parsing anything from your WindowCast.txt file otherwise it wouldn't be doing this loop body skipping. I was able to recreate the same issue with the infinite loop so I can prevent it, but need to confirm you did the same or something similar to get into an infinite loop too. I should be able to connect the dots after reviewing and trying out your WindowCast.txt file
You forgot to upload the WindowCast.txt file. I need the file you are using located at M:\WindowCast\WindowCast.txt
I did improve the script to throw a different error when this happens as well as prevent the infinite loop.
No redflags in the .ahk file! And that clarifies which version you were using so I know I'm testing with the same.
Attach that WindowCast.txt file and I'll check it out and get back to ya
Ah, yeah I forgot sorry. Anyway, it's just the file that came with the core. I just renamed it to "WindowCast.txt". Did nothing else to it.
Thank you so much for helping me out 😃 -
2 hours ago, Retro808 said:
@SiriusVI Are you on the most recent version of LB and have you used the Media Packs feature it now offers? Look and see if you have >Media Packs>Platform Icons>Legacy Conversion Icon Pack> folder. This may be the reason placing the images in the traditional folder is no longer working. Images would need to go in the Media Pack folder now. Custom images located in a \LBTheme folder override normal image folders, this may have the same affect on the Media Packs images as well. I have not messed with the new Media Packs feature so I could be wrong, but I would say check for that folder and test there and see if it works.
Oh yeah, that's probably it!
So the "old" platform Icon folder is not needed anymore, right? Can you telle me what other folders are also not needed anymore? I'd like to clean up evrything to avoid confusion in the future. -
On 1/16/2024 at 2:53 PM, C-Beats said:
Are those actual Platforms or Playlists you have displaying in the Platform list?
I'm also having a really annoying problem with platform icons lately. A while ago I added Steam, EA Games and GOG as separate platforms and I could easily add custom platform icons. It just worked, So I thought I knew what I was doing.
Now (a few years later) I added Epic Games, Ubisoft and Microsoft to the mix (as platforms, not playlists), and also copied custom icons in the correct folder, named correctly after the specific platforms. However, as you can see, the icons show up as the default "windows"platform, instead of the custom store front icons.
Can anyone help me fix this?
EDIT:
As a test, I just tried replacing the Super Nintendo Entertainment System.png and see if the platform icon changes, but it does not. Is there some kind of platform icon cache that needs to be updated / cleared in order for this to work?
I'm really confused, since it used to work so easily in the past.
Edit 2:
A new test: I switched to a different theme, called "Default Plus" which has custom Platform icons. So I copied the Epic games icon into the corresponding folder for this theme and that worked:
So I guess this behavior is a bug in the default Theme?
EDIT 3:
I found a workaround, but I believe this is definitely a bug of the Default Theme. So basically, if I copy the Platform Icons folder from this (default) location: "M:\Launchbox\Images" to this location: "M:\Launchbox\LBThemes\Default\Images", it works.
-
OK got it, so this is how it starts:
Once I scroll down to the end, it looks like this:
Again for reference, I use this script now:
SetWorkingDir, % A_ScriptDir SetTitleMatchMode, RegEx ; seems to work like mode 2 (partial match) but allows for use of expressions RetroarchWinTitle := "ahk_exe retroarch.exe" RetroarchEXE := "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe" WindowCastFile := "M:\WindowCast\WindowCast.txt" WindowCastListArray := [] TimeOutDelay := 10000 ; close script if game/emulator window is not found in X seconds RunRetroarchDelay := 1500 ; delay between finding game/emulator window and then opening Retroarch FocusHotkeyDelay := 2000 ; delay between launching Retroarch and sending hotkey to grab focus of game/emulator window. *HDR/Fullscreen method ONLY* ; Read WindowCast window list file and parse into array FileRead, WindowCastList, %WindowCastFile% Loop, Parse, WindowCastList, `r, `r`n { If (InStr(A_LoopField, "#")) Continue WindowCastListArray.Push(A_LoopField) } ; Loop through list to check which window exists InitialTime := A_TickCount WindowCheck: Loop, % WindowCastListArray.Count() { ; Check if entry is an exe If (InStr(WindowCastListArray[A_Index], ".exe")) { If (WinExist("ahk_exe " . "i)" . WindowCastListArray[A_Index])) { ExistingWindow := WindowCastListArray[A_Index] Break } } ; If entry is not an exe, it is a window title Else If (WinExist("i)" . WindowCastListArray[A_Index])) { ExistingWindow := WindowCastListArray[A_Index] Break } DurationTime := A_TickCount - InitialTime If (DurationTime >= TimeOutDelay) { MsgBox, 4096, Window Check Timeout, Couldn't find existing window. Exiting script! ExitApp } } If (ExistingWindow = "") Goto, WindowCheck Sleep, RunRetroarchDelay Run, %RetroarchEXE% -L wgc_libretro.dll %WindowCastFile% -f WinWait, % RetroarchWinTitle Sleep, % FocusHotkeyDelay ; Sends hotkey to give focus to game window so inputs are detected Send {LCtrl down}{LAlt down}{t down}{t up}{LAlt up}{LCtrl up} If (InStr(ExistingWindow, ".exe")) WinWaitClose, % "ahk_exe" . "i)" . ExistingWindow Else WinWaitClose, % "i)" . ExistingWindow WinClose, % RetroarchWinTitle ExitApp ; Hotkey to exit Retroarch and terminate script $Esc:: ; keyboard modifier ($) is needed so input isn't "eaten" by the game WinClose, % RetroarchWinTitle ExitApp
I'll attach the file here as well.
I do not get the message box you mentionied. It's just that nothing happens when I double click the script. Except that AutoHotKey appears in my task bar with the contents that I uploaded above. -
12 hours ago, skizzosjt said:
Ahh ok so that's good news, and bad news lol
Good news is the script "works", it is finding the emulator window, it is launching Retroarch. So good so far
Bad news is the core is buggy and finicky.
For ex, I am now launching Ninja Gaiden Black again and.....it works perfectly. Every. Single. Time. didn't change a damn thing from this morning lol. The window is getting focused appropriately via the script making it all automated as intended. I guess I'd rather be lucky than good because I have no idea why it wasn't working earlier, and why it is now
I'm on an AMD GPU but I had found many scenarios of weird with this core. No windows with "windowcast" in its title can exist.....I find that out from testing with this thread open. If minimized it can capture Firefox's minimized window and makes it look like Retroarch launched but froze before a window even appears. In reality what happened is it literally captured a minimized window lol. I then restore the Firefox window and that gets captured in Retroarch🤦♂️. Doesn't make much sense given there is nothing in the WindowCast.txt file that would make that window get captured hence why I think it is some bug with the core.
There is some discussion about GPU settings scattered in that link in the first post. There might be some hidden hints in there for you.
Alternatively, if you are using that very first version of the script I posted, you might be having challenges like I did for some scenarios where launching Retroarch into fullscreen was the issue. If you're using the first one, try the 2nd version instead, the "SDR" version. It will make Retroarch more of less a borderless fullscreen window and I found this as a workaround. It is always consistent unlike directly launching into fullscreen. YMMV though
So overall sounds like the script is doing what it was set out to do but something specific is causing a challenge on your system. And sounds like you found the potential culprit as Gsync. I'd believe it, there have been weirder things impacting my experience with this core!
Well it's not working , yet sadly. This ahk script now works, as in it launches WindowCast and successfully captures Xemu:
Run, "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe" -L wgc_libretro.dll "M:\WindowCast\WindowCast.txt"
However, the rest of the script does not work. In fact it does nothing, when I try to launch it. Retroarch doesn't even launch =/
EDIT:
I tried some stuff and shortening the script to just this now also works:
SetWorkingDir, % A_ScriptDir
SetTitleMatchMode, RegEx ; seems to work like mode 2 (partial match) but allows for use of expressions
RetroarchWinTitle := "ahk_exe retroarch.exe"
RetroarchEXE := "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe"
WindowCastFile := "M:\WindowCast\WindowCast.txt"
WindowCastListArray := []
Run, %RetroarchEXE% -L wgc_libretro.dll %WindowCastFile%
However, this does of course not send CTRL + ALT + T which is needed for the inputs to work.
I'm at a loss as to why the whole script won't work for me. -
4 hours ago, skizzosjt said:
sure thing mang
Xemu might be some funny business here. I didn't previously test it. I did get it to work right now but it wasn't very automated. I had to use keyboard/mouse to ALT+TAB to the actual emulator window, mouse click into the emulator window, and then ALT+TAB back to the Retroarch window, and THEN use the CTRL+ALT+T hotkey (the WindowCast specific hotkey to change window/control focus) to get the darn window to focus for controls to work. Also seems how this emulator renders affects how a shader would be applied. for ex, I'm not sure why the heck there are black bars on the side here. It's effectively cropping the image used for the shader as this image is 16:9 ratio so should cover edge to edge. aspect ratio is correct, but it's getting cropped. First emulator I've seen do this to me.
*further testing proves the keyboard is not sufficient to get proper window and controls focus. for ex, I can launch the game/emulator and then the script and I get no controls in game. I can still see the mouse cursor so I do a normal left mouse click where I know the actually emulator window is and now I have controls. so, seems like Xemu doesn't give controls unless it is first put into focus that way.....would require different methods to make this wholly automated
Doesn't sound like you did any redflag wrong moves. for the AHK question that is what Windows calls file extension association. You must have never opened an .ahk straight from Windows Explorer so it didn't know what program to use to open it. It needed to be directed to the main AutoHotkey.exe file in order to run .ahk files. You got that right. Doesn't matter if you use the exe included with LB or if you setup AHK yourself and placed it wherever you wanted. It will remember that going forward so should be a set it and forget it thing
clarify for me, this works for you if you launch an Xemu game manually, and then launch Retroarch manually and load the WindowCast core manually? if so, we at least know you got the WindowCast.txt file with proper name in there
Note the game/emulator window should be a window rather than fullscreen. Actual window, not a borderless fullscreen window. I do not have the full screen command used for Xemu here.
Running the script should be first line in the running script field to make sure it executes. if you put it below something like a hotkey or a WinWait command it may never make it to the Run command line. I wonder if this is the issue for you?
further testing if you're still getting stuck.....
launch Xemu manually. from what I can tell the last loaded game should boot up automatically. so at this point you should be running Xemu and booted into a game and it should be in a window mode
next, manually run the WindowCast.ahk script from Windows Explorer. it should work fine like this. if it doesn't it could be something is not configured right in the script for you
if it's not working at this point you should check the AHK tray icon and review the lines of code that have been executed. I would suspect either the script is exiting too soon for some currently unknown reason or some configuration or typo kinda issue. reviewing the lines executed will let us know what ran and where it's stuck if it is stuck. post an image of that window if needed
come back with how you make out and we'll go from there!
Hey thx for replying. Did some further testing:
Manually starting Xemu and then manually launching WindowCast works.
Launching this ahk script also launches retroarch: Run, "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe"This ahk script just freezes retroarch and I have to terminate the process: Run, "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe" -L wgc_libretro.dll "M:\WindowCast\WindowCast.txt"
I also get the freeze when just trying to launch this via CMD. I can see that WindowCast is trying to capture the Xemu window (yellow outlines aroundthe game window), but Retroarch crashes. Same behavior with Dolphin.
Again, running windowcast manually works perfectly.
EDIT:
I think I got it. It's Gsync. If Gsync is enabled in RetroArch, CMD and AHK crash Retroarch during the window capture. If it's disabled it works.
But again, when manaully starting WindowCast, it works fine, even wuth Gsync enabled.-
1
-
-
Hey man,
I'm trying to get this ahk working in Launchbox. I copied your script in a txt document and saved it as WindowCast.ahk. I added my paths like so:RetroarchEXE := "M:\Launchbox\Emulators\RetroArch - WindowCast\retroarch.exe"
WindowCastFile := "M:\WindowCast\WindowCast.txt"I put the file in M:\Launchbox\Utilities\Scripts\WindowCast and in Manage Emulators for Xemu I added in the running script section: Run, M:\Launchbox\Utilities\Scripts\WindowCast\WindowCast.ahk
However when I launch a game, Xemu starts like normal, but Retroarch never launches. So Am I doing something wrong here? (I of course tried WindowCast before from Retroarch and it works fine there.)
Can you help me?
EDIT: When first trying this, Windows asked me which program I wanted to use for .ahk files. I chose M:\Launchbox\ThirdParty\AutoHotkey\AutoHotkey.exe
I assume this was correct? -
20 minutes ago, Jammy said:
And not just the settings, but i dove so deep into bezels for example.
There are great ways to automate this as well.
If it's just bezels / overlays that you want, then you should take a look at the bezel project. It's a fully automated installer that will automatically set up bezels for all of your games:
https://github.com/thebezelproject/BezelProject-Windows
If you want something even fancier, I suggest looking into HSM shaders with included bezels. I recommend Duimon's shader presets:
https://forums.libretro.com/t/duimon-hsm-mega-bezel-graphics-and-presets-feedback-and-updates/28146
https://github.com/Duimon/Duimon-Mega-Bezel
Here is an example of what they loo like:
-
2
-
-
23 hours ago, Jammy said:
only the ones mentioned in the post.
- snes
- mega drive
- gameboy advance
- sega saturn
- sony playstation
sadly not. it was all on my ssd and i did not have any backups. 😭
Sucks that you lost your whole setup, but trust me, it's not actually that hard and it won't take that long to build it up again if it's just those 5 platforms.
What you wanna do is:
1. Download Launchbox
2. Setup Retroarch as an emulator (Launchbox can do that for you). Retroarch will be able to emulate all of these platforms, no need for standalone emulators.)
3. Get your games back (depending on how you want to go about it, this can take a bit longer. Did you have a hand-picked collection, a 1g1r set or a complete set with all available games for each system?)
4. Import all the games into Launchox and download all the metadata and media.
5. Aaaaand you're done --> Don't forget to make a backup this time 😃
If you have no experience with Launchbox, it may take a bit longer, and of course getting your game collections together might take a while. But if I had the games ready, JUST the setup within Launchbox & Retroarch would probably take me half an hour.
Good luck and don't forget to have fun.-
1
-
20 hours ago, Gosunkugi said:
Edit*
I have figured out how to successfully run ODYEMU, the Magnavox 1 emulator from within Launchbox, and it was absurdly simple.
Set DosBox as the chosen platform emulator, then it's a matter of creating a .bat for each game. Inside each one write ODYEMU tennis.mo1 for example, and that's all you need, the games will boot right up. Can't believe I was stumped on that. Hope this helps anyone who wants the Odyssey working, (it's totally not worth it :p)
Also the games are nothing but dots on a screen without the corresponding overlays. The game collection I have only includes one overlay, though there is a way to make your own with a utility named BMPTORLE.
Some time it would like to set this up as well. Getting the overlays to work seems like a bit of a challenge, especially when combined with complex shaders with bezels, such as Duimon's HSM shader presets. Will have to try.
-
Very nice setup. It's always great to see how different users set up their collections differently to get some new ideas =).
-
1
-
-
4 hours ago, McMeekan said:
I am able to get a number of high-resolution texture packs to work within Retroarch (Mupen64plue core with GLideN64) - all those are *.HTS compression files but the Wave Racer one uses an *.HTC compressed file and it does not seem to work. I have made sure the "Use High-Re textures" is on along with Cache Compression, Full Alpha Channel, enhanced texture storage, and enhanced Hi-Res Storage but it still does not use the High-Resolution textures. I had it working previously but had to do a full re-install of RetroArch and now it's the only High-Resolution pack that is not working. Any ideas?
Interesting ... as long as they are all in the "cache" folder, they should work regardless whether they are .hts or.htc files. If the texture pack worked before, then it's probably a settings issue. Do you have per chance a per game profile for Mupen64 for Wave Race?
-
On 2/18/2025 at 3:04 PM, Visuals said:
Hallo zusammen
Hallo zusammen!
Ich moechte euch meinen neuen YouTube-Kanal GameProphets vorstellen, der sich auf Tutorials rund um Emulatoren und Launchbox konzentriert – und das alles auf Deutsch! 🎮
Es gibt zwar viele englische Tutorials zu diesen Themen, aber oft ist es einfach viel leichter, alles in der eigenen Muttersprache zu verstehen, besonders wenn man mit der Technik noch nicht so vertraut ist. Deshalb habe ich den Kanal ins Leben gerufen, um deutschsprachigen Anfaengern und auch fortgeschrittenen Nutzern zu helfen, das Beste aus Launchbox und Emulatoren herauszuholen.
Auf GameProphets findet ihr derzeit Tutorials, die Schritt fuer Schritt erklaeren, wie man Emulatoren in Launchbox integriert, damit ihr eure Retro-Spiele problemlos geniessen koennt. In Zukunft plane ich, auch weitere Themen wie den Bau von Arcade Cabinets zu behandeln.
Der Kanal ist noch ganz frisch, aber ich lade regelmaessig neue Videos hoch. Schaut gerne mal rein und abonniert, wenn euch das Thema interessiert!
Hier geht's zum Kanal: GameProphets auf YouTube
Ich freue mich ueber euer Feedback und hoffe, dass ich euch bei euren Projekten unterstuetzen kann!
Beste Gruesse,
[Dein Name oder Nickname]Message brought to you by ChatGPT 😅. But could be pretty useful for German users. 😃
-
15 hours ago, skizzosjt said:
it is possible to have arcade CATEGORY and arcade PLATFORM use their intended videos (light blue with set of cabs "A" for category, and purple with set of cabs "B" for platform) along with their proper hardware device image. I certainly made it work at least. you're gonna have to make some edits whether that is renaming files and/or changing names or conditions in LaunchBox or the theme.
It's kind of a shame. COLORFUL is probably the cleanest and most consistent Theme out there. However, there are so many color mismatches that in its current state it's unusable for me. It also doesn't seem that fixing this this is a priority.
-
On 1/31/2025 at 8:52 PM, kmoney said:
I have determined that my freezing/locking up issues while in attract mode is VLC. I know VLC is the recommended one to use but I have been using WMP for over 24 hours without any issues where as while using VLC BigBox would freeze within a couple of hours.
5 hours ago, Raw64life said:I switched from VLC to WMP a year or two ago due to this issue which AFAIK was never resolved, and it honestly works great. I've had no issues with WMP at all.
I have also switched to WMP years ago, because VLC causes weird graphical issues for the first few seconds a video is playsing on three different PCs I tried. Have had no problems with WMP whatsoever and never went back to VLC to this day.
-
There is a third party plugin that can import PS3 games. I imported my rpcs3 games with it before Launchbox could do it on its own and it imported all games, even PS1 classics, PSP Minis and so on. Or do you mean something different?
-
7 minutes ago, C-Beats said:
This. You have 3D box art in your Box - Front image priorities. Either that or that image is tagged incorrectly and isn't marked as a 3D Box image.
That was it. Removed 3D Boxes from the Box Front Priorities and it works. Thank you!
-
1
-
-
Hey everyone,
if I use 3D-Boxes as an image group in Launchbox, on the right hand side I get this weird result that the 3D image is placed inside the 3D Jewel Case. Shouldn't this only happen with 2D art?
Here is a close up.
Is this a bug or have I messed up my settings somehow?
-
I just updated and downloaded some metadata / media after auto-updating the store-fronts (first time I tried it) and I got this error. Don't know if this is related to the update or not:
Full error here:SpoilerThe calling thread cannot access this object because a different thread owns it.
App: LaunchBox
Version: 13.18
Theme: Default
Type: System.InvalidOperationException
Site: Void VerifyAccess()
Source: WindowsBaseat System.Windows.Threading.Dispatcher.VerifyAccess()
at System.Windows.Window.get_CriticalHandle()
at System.Windows.Interop.WindowInteropHelper.get_CriticalHandle()
at Unbroken.LaunchBox.Windows.Desktop.MessageBoxEx.Show(Window ownerWindow, String text, String caption, MessageBoxButton buttons, MessageBoxImage icon, MessageBoxResult defResult)
at DescriptorUtils.ReflectAspectPolicy(Window ownerWindow, String text, String caption, MessageBoxButton buttons, MessageBoxImage icon, MessageBoxResult defResult, DescriptorUtils )
at Unbroken.LaunchBox.Windows.Desktop.MessageBoxManager.ShowError(String error)
at ReaderAlgo.ReflectAspectPolicy(String error, ReaderAlgo )
at Unbroken.LaunchBox.Windows.Desktop.MenuActions.DownloadMetadataAndMediaMenuAction.OnSelect(Boolean skipWizard)
at FactoryComparator.ReflectAspectPolicy(Object , Boolean skipWizard, FactoryComparator )
at Unbroken.LaunchBox.Windows.Desktop.ViewModels.MainViewModel.ExcludeInvalidIterator()
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ChangeAwareVisitor(Object )
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.PopSessionProcessor()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()Recent Log:
18:43:40 Exception
-
On 8/1/2024 at 3:17 PM, znam said:
the same problem with the G axis not working
were you able to solve the problem?Late replay, but still: unfortunately I haven't been able to figure out why some controllers don't work and some do. I also don't know how to distinguish between the working models and the non-working models.
What I did / had to do is just buy a ton of Dual Shock 3s and hope to get lucky. Soo far, I've bought 7 controllers and there are 3 working ones among them. I'd like to have a set of 4 working controllers, so I guess I'll have to buy a few more to get the last working one. -
I really absolutely love Launchbox for all the features and tweakability it offers. I have sunk countless hours setting it up to my specific liking. I couldn't do that with any other frontend. It's become a really fun hobby of mine.
So I hope people don't take it the wrong way, when I say that the performance and the user experience in Launchbox and BigBox is very bad. My collection is huge and I know LaunchBox struggles with that, but I also have a very high end PC, capable of running just about anything. I've tried all the optimizations suggested, I have read every thread, I have tried it on three different systems over the years. It's safe to say, the problem is not on my end (if you don't count having a huge collection as a problem, that is).
Navigating the GUI in Launchbox, every click, every edit, everything is sluggish. It takes forever (3 seconds when trying to edit one game up to over a minute for some bulk edits) for Launchbox to respond to anything I do. BigBox also has issues, such as the very slow booting process.
I believe this is not what most people expect from software nowadays. It should respond instantly to what the user does. Ideally, it should open instantly, and every click should have an immediate response.I can tolerate a bit of laggyness and I'm at an age where I have learned to be patient. But still, LaunchBox drives me crazy sometimes.
To make a long story short. I really love Launchbox and BigBox, but please oh please try to fix ther performance. This should be your top priority.
Anyway, I hope you didn't take this the wrong way. I'm still glad I paid for Launchbox/BigBox and I'd gladly do so again.-
2
-
Issue with Launchbox Conroller Hotkeys
in Troubleshooting
Posted · Edited by SiriusVI
Hey evryone,
I'm having an issue with Launchbox Conroller Hotkeys that I didn't have before. I don't know since when this problem started, since I haven't tried it in quite a while. The "Exit" hotkey does not work anymore. I have set it to "Start + B" on my Xbox Series conroller. It used to work perfectly, but now, it does not exit retroarch anymore.
Any help is appreciated.