MazJohn [Mr Arcade]

I am also still experiencing the game videos re-sizing issue as well with Beta 15. In my previous description within this thread, I referred to it as video Glitches. Respectfully speaking, It honestly makes the front end UN useable for me at least in its current state. My scroll wheels are also experiencing artifacting, and the text inside my themes option menu keeps expanding , then de-spanding in size and the text garbles. Ive tried everything imaginable on my end to no avail. Only solution is to go back to 11.2 official release, then all the problems go away. @Jason Carr also asked if I was using any Plugins in a previous reply (thank you) .... to answer that, I am Not using any plugins. My plugins folder is empty. Does it come down to a fresh install of windows 10 for me? I really don't think it is the OS since reverting to Previous 11.1 and 11.2 builds work fine for me. Thanks-

Since I posted this above, I have tried the following on 11.3 BETA 13: 1- Un-Installed and then Re-installed all instances of .NET Core / .NET Framework. ( Note: I let Launch-Box add .NET core back upon updating the system afterwards) 2- Used the DDU tool to completely remove the Nvidia graphics driver from the system, Then did clean Re-Install of latest Nvidia graphics Driver 3- Re- Installed Direct X runtime for Windows 10 4- Deleted all themes. Reinstalled fresh Copy of Unified Redux, Unified, and Unified Refried (theses are my current 3 primary themes) 5- Went back to using default Startup theme 6- Swapped fresh copy of LBthemes folder, and Core folders from a different installation. 7- Switched From using VLC engine to alternate MS engine... no difference. The problems still persist. When I go back to using the V11.2 official release the issues are gone. It's obvious to me this only occurs when I upgrade to any 11.3 Beta XX Again, the problem is stuttering, glitching system videos, Glitching themes, and the system wheels are glitching and changing size randomly. I have tested 2 separate Launchbox instances, but have the exact same problem on both.... IS there anyone else having this issue? Anything else I can try? Are still these common issues that still need to be ironed out since Launch-box switched to the .NET Core update? Thanks.

Just constructive feedback... multiple themes are still glitching on beta 13, videos are sometimes missing, glitch and freeze, and big box keeps suddenly shutting down randomly. Going back to 11.2 official now seems to strangely have stability issues as well.... Not sure what to do next... Oh well... If an official release is coming, looks like based on my experiences with beta 13 'm out of luck. 2 separate independent builds on separate pc's both have same issues.

Thanks, double checked and did do that. Rebooted then re-installed launchbox update to 11.3 beta 2, and it worked.... However this beta seems to be causing artifacts and video glitches on all of my themes. Launchbox would also completely lock-up when trying to launch Cemu. For the first time in a long time I had to roll back....went down to 11.2 stable for now. Problems gone after rollback.

Since I updating to 11.3 beta 1 I can no longer start launchbox. I already installed the .NET core 3.1 which was told to be missing. I rebooted and sill get this error that i need to install .net core to use the application. When i re-run .net core install it tells me its already installed. Am i doing something wrong guys? thanks

As I had stated in an earlier post, I supported development by purchasing the android version even though I never used it. This being said, building off of what Pixelpiper said above, Has there been any community poll taken to vote on consideration to revisit/ develop a Linux desktop port of Launch box as an alternative (better second option) to windows? Unlike android, Linux is obviously open source and like windows, would also provide the developer total control over the platform. I would think that many emulators would be supported including Retro-Arch which already has cores for most systems. Linux is lean and mean and would be quite a stable platform as an alternative to Windows for many. I am even seeing Linux run many Windows Steam games these days.... Maybe I am in the great minority, but I would purchase a Linux version.

Thanks For this update Jason..... While the majority of your install base are currently Exclusively using Launch-box/Big-box on the windows platform and I do prefer/ agree development should be the primary focus here, I did purchase an android copy just to help support its development efforts. This being said, the Android announcement did get me thinking. My concerns for Launch-box longevity are more focused around the worry that in 5-10 years, ARM may takeover.... We might need a migration path or plan if this does ever occur... Launch-box has become a platform in itself for those who love and *rely* on emulation/gaming. These builds and all the hard work put into them can technically run for years and provide steady access to these gaming platforms, as long as the HOST OS platform and emulators are updated and supported.... yea... we cant predict the future and Windows likely isn't going anywhere for a long time..... but ARM might change things... hopefully if so there will be a migration path if needed to support whatever the future brings so that our beloved Launch-box builds can stay up to date.... \\

I'm suddenly having this same problem in launch box where the fonts became super small and almost impossible to read... doesn't seem to be a way to fix this- what i did temporarily was lower the windows default resolution from 4k back to 1080P .... its better but the fonts are still UN-proportionally small. I'm wondering what changed... I did upgrade to Widows 10 build 1903 recently... could this have anything to do with this? Anyone else have this problem? any ideas to fix this?

Same here

@jason-carr/, I know this is probably off topic, but regarding a next feature poll, I am wondering if there is the possibility for revisiting a global setting for default system bezels by platform... now that we have pause screens, startup and shutdown screen overlays on top of the emulators, would this now be more feasible for consideration to implement? Thanks for consideration...

I'm sorry to hear this to be the case. If I recall, Jays Arcade helped the community some time back with a Loader for Future Pinball. I personally had hoped for the most streamlined way possible to import (assuming they are free to use) .VPX (Visual Pinball) and .FPT (Future Pinball) files... I guess maybe there just isn't much more needed to do here that cant be accomplished already.

Thank you Jason, Will go with minimal script for the time being...

Regrettably, got a crash on beta 2 after 8 game exit attempts ... error dDebug 2019-06-06 05-43-50 PM.logump and log file attached. I do appreciate all you have aready done to try and help.... Cannot set Visibility to Visible or call Show, ShowDialog, Close, or WindowInteropHelper.EnsureHandle while a Window is closing. App: Big BoxDebug 2019-06-06 05-43-50 PM.log Version: 9.9-beta-2 Type: System.InvalidOperationException Site: Void VerifyNotClosing() Source: PresentationFramework at System.Windows.Window.VerifyNotClosing() at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel) at System.Windows.Application.DoShutdown() at System.Windows.Application.ShutdownImpl() at System.Windows.Application.ShutdownCallback(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 5:44:49 PM Music.StopAndResumeBackground Start 5:44:49 PM Music.Kill Start 5:44:49 PM Music.Kill Finished 5:44:50 PM Music.StopAndResumeBackground Start 5:44:50 PM Music.StopAndResumeBackground Start 5:44:51 PM Music.Pause Start 5:44:51 PM Music.Pause Start 5:44:52 PM Music.Pause Start 5:46:11 PM Music.Resume Start 5:46:13 PM Music.Kill Start 5:46:13 PM Music.Kill Finished 5:46:16 PM Music.StopAndResumeBackground Start 5:46:17 PM Music.StopAndResumeBackground Start 5:46:17 PM Music.StopAndResumeBackground Start 5:46:19 PM Music.StopAndResumeBackground Start 5:46:19 PM Music.StopAndResumeBackground Start 5:46:20 PM Music.StopAndResumeBackground Start 5:46:20 PM Music.Kill Start 5:46:20 PM Music.Kill Finished 5:46:21 PM Music.StopAndResumeBackground Start 5:46:21 PM Music.StopAndResumeBackground Start 5:46:23 PM Music.Pause Start 5:46:23 PM Music.Pause Start 5:46:23 PM Music.Pause Start 5:49:32 PM Music.Resume Start 5:49:35 PM Music.Kill Start 5:49:35 PM Music.Kill Finished 5:49:39 PM Music.StopAndResumeBackground Start 5:49:39 PM Music.StopAndResumeBackground Start 5:49:41 PM Music.StopAndResumeBackground Start 5:49:41 PM Music.Kill Start 5:49:41 PM Music.Kill Finished 5:49:42 PM Music.StopAndResumeBackground Start 5:49:42 PM Music.StopAndResumeBackground Start 5:49:43 PM Music.Pause Start 5:49:43 PM Music.Pause Start 5:49:44 PM Music.Pause Start 5:50:20 PM Music.Resume Start 5:50:22 PM Music.Kill Start 5:50:22 PM Music.Kill Finished 5:50:24 PM Music.StopAndResumeBackground Start 5:50:24 PM Music.StopAndResumeBackground Start 5:50:25 PM Music.StopAndResumeBackground Start 5:50:25 PM Music.Kill Start 5:50:25 PM Music.Kill Finished 5:50:31 PM Music.StopAndResumeBackground Start 5:50:31 PM Music.Kill Start 5:50:31 PM Music.Kill Finished 5:50:33 PM Music.StopAndResumeBackground Start 5:50:33 PM Music.StopAndResumeBackground Start 5:50:34 PM Music.StopAndResumeBackground Start 5:50:34 PM Music.Kill Start 5:50:34 PM Music.Kill Finished 5:50:34 PM Music.StopAndResumeBackground Start 5:50:34 PM Music.StopAndResumeBackground Start 5:50:35 PM Music.Pause Start 5:50:35 PM Music.Pause Start 5:50:36 PM Music.Pause Start 5:50:45 PM Music.Resume Start 5:50:47 PM Music.Kill Start 5:50:47 PM Music.Kill Finished 5:50:49 PM Music.StopAndResumeBackground Start 5:50:49 PM Music.StopAndResumeBackground Start 5:50:50 PM Music.StopAndResumeBackground Start 5:50:50 PM Music.Kill Start 5:50:50 PM Music.Kill Finished 5:50:51 PM Music.StopAndResumeBackground Start 5:50:51 PM Music.StopAndResumeBackground Start 5:50:53 PM Music.Pause Start 5:50:53 PM Music.Pause Start 5:50:53 PM Music.Pause Start 5:51:10 PM Music.Pause Start 5:51:10 PM Music.Kill Start 5:51:10 PM Music.Kill Finished 5:51:13 PM Exception

using that script i get the above error on exit with xbox controller automation.

Jason, Ok, so I tested with the above provided retroarch exit script. counted 30 game exit attempts made- and NO CRASHES occured so far.... I typically would think I would have gotten at least 1 crash by now.... ( using Xbox controller automation with hold button and close active window)

Interestingly, with default script, using the escape key to exit games from retroarch did not result in a crash in about 20 tries on exit.... I then i started exiting games again using the Xbox one controller, using the assigned "hold button" and "close active window" (shoulder buttons 5&6).... got 2 crashes straight to desktop again out of about 20 tries. No error dump provided, just sent directly back to the windows 10 desktop.... Hopefully this might help in some way to narrow it down.... If you still need more extensive testing to pinpoint root cause , let me know- i could continue over a longer time period to collect results. thanks...

Jason, OK, so when i changed the default script in retroarch to "sleep 50" and re-started big-box, I can now no longer exit a game using the defined "hold button" and "close active window" using my Xbox one controller.... I assume this is to be expected behavior since the default script is no longer running...... ? I then reset to use the default retroarch script again, and within 3 game exits, it crashed again on the third try. This time it didnt even come back with an error dump at all... it just exited Launchbox completely and I am returned immediately to the windows desktop. (running 9.8 official) Thank you....

updated back to 9.8 official then checked retroarch autohotkey exit as requested. reads as follows; ; No custom exit script is necessary for Retroarch ; since it already uses the Escape key by default This setting was never touched. my launchbox backup copy was also set the same way for retroarch. edit.. opps.. will change to sleep 50 as requested and report back...

Jason, Sorry for not being able to respond back sooner... The crash to desktop problem seems to be happening on all emulators... I can say for a fact, it happens on Retro-arch which covers a great deal of systems for me personally, but it also occurred on pcsx2 and Dolphin. I have seen it more on Retro-arch simply because more systems are using it..... Something important to say.... I mentioned it way back in my original post- When I revert back to Beta -16 the issue seems to stop occurring ... anything past beta 16 all the way up to current 9.8 release causes me to have this issue.... 9.8 was crashing almost every time on emulator exits the past few days... by the way, In my last post above from past Friday, none of those other things mentioned that i could try seemed to help.... *Disabling startup screen from Big-Box options menu seems to have prevented the crashing in 9.8 final... (unchecked) I stress tested my My CPU and memory running on z390 platform and the Windows 10 system is stable. No other applications are experiencing issues- its a dedicated Launchbox build, and alsways has been... Much do Appreciate you looking into this for the next release and taking some of your your Dev time to help. Regards,

Under controller buttons in BigBox, the exit button is set to none. Also worth noting; 1- I did have "use all controllers" enabled under controller automation , so i tried unchecking that but to be honest I never had a problem before in leaving that checked. 2- Under keyboard mappings, i un-assigned the default "x" button from the exit command just for the hell of it.... 3- Under keyboard automation, I unchecked "use keyboard automation" .... this is a new feature unless mistaken... wonder if that being enabled was causing any issues... this being said, I never changed any of the default keys while it was enabled. I just disabled it now so I will see if that helps in any way. Also, please note that the problem is intermittant (estimate 1 out of every 5 exits results in crash) - what I am getting at, is that this "double exit" crash (if i may call it that) is not consistant.... What i do find a little confusing is that under "controller buttons" and "controller automation" , the same joypad keys are permitted to be used in both sections... I'm throwing a needle at a hair here, but could there be some sort of conflict that causes it to crash from that? I removed all Joypad assignments from controller buttons anyways just to help further isolate... lol... To add more to my own punishment (just being sarcastically funny here) ... I removed all emulator entries for "auto hotkey script" inside launch-box itself. Another note; I've been updating launchbox since version 5 from each beta to the next over time ... never had any issues until now... been loving it. Thanks...

Jason, Attached is a debug log as requested. I collected it just after a crash. see the very bottom of the log. not sure what it means but it seems to be related to a shutdown.... by the way, I updated my GTX1060 Nvidia driver to latest release available dated 5/27/19, enabled debugging in launchbox options, the played some games and it crashed on exit within a few tries. Log immediately attached after the crash.... maybe this will help you if not me but it was worth a shot.... I have a backup of my Launchbox install. would there be any specific files that i could replace from my backup that are related to the shutdown issue? thanks anyways for taking your time ... i will have to do some testing on my build until i can isolate, or just keep startup screens disabled for now. regards, Debug 2019-05-30 05-02-01 PM.log

Hope the above info helps. Wondering if this is a system specific issue on my part or something else requiring more time... either way- Any updates? thank you...

Thanks Jason for taking the time to take a look into this... please see my answers to your questions below... 1- disabling pause screen alone from Big-Box options menu did not help ... same crash behavior occurred on BB exit. 2- *Disabling startup screen from Big-Box options menu seems to have prevented the crashing... (unchecked) Note: I have always used startup screens in the past without issue, so i do find this interesting. Again just to mention that this crash on exit issue seems to have begun just after Beta 16 and still occurs for me in the 9.8 final.... by the way, I am using "big logo" theme for startup screens... So in summary, with both pause screen and startup screen disabled the crashing seems to have stopped. 3- its actually controller automation enabled from the options menu which i am using to exit games launched from inside Big-Box. I am using Using Xbox one controllers with buttons 5 (as hold button) &6 used to exit active game (shoulder buttons)... nothing else used otherwise to make it work. In light of the above feedback, i appreciate your thoughts

I have updated .NET to latest version which was version 4.8 .... same crash error on game exits... the crash occurs about once out of evey 5 game exits from BigBox... hope someone here in the community has some ideas or can ping Jason for some feedback... thank you all.... If it helps to know, I am running on latest mainstream windows 10 build , which is version1809 with modern intel platform hardware ... I7 cpu, Nvidia gpu...ddr4 -16gb ram. latest crash after .NET 4.8 update is posted below.... Cannot set Visibility to Visible or call Show, ShowDialog, Close, or WindowInteropHelper.EnsureHandle while a Window is closing. App: Big Box Version: 9.8 Type: System.InvalidOperationException Site: Void VerifyNotClosing() Source: PresentationFramework at System.Windows.Window.VerifyNotClosing() at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel) at System.Windows.Application.DoShutdown() at System.Windows.Application.ShutdownImpl() at System.Windows.Application.ShutdownCallback(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 10:06:11 AM Music.Resume Start 10:06:11 AM Music.Pause Start 10:06:11 AM Music.Resume Start 10:06:13 AM Music.StopAndResumeBackground Start 10:06:15 AM Music.StopAndResumeBackground Start 10:06:15 AM Music.StopAndResumeBackground Start 10:06:16 AM Music.Initialize Start 10:06:16 AM Music.Kill Start 10:06:16 AM Music.Kill Finished 10:06:39 AM Music.StopAndResumeBackground Start 10:06:39 AM Music.StopAndResumeBackground Start 10:06:43 AM Music.StopAndResumeBackground Start 10:06:43 AM Music.StopAndResumeBackground Start 10:06:44 AM Music.StopAndResumeBackground Start 10:06:44 AM Music.StopAndResumeBackground Start 10:06:46 AM Music.StopAndResumeBackground Start 10:06:46 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.Kill Start 10:06:50 AM Music.Kill Finished 10:06:50 AM Music.StopAndResumeBackground Start 10:06:50 AM Music.StopAndResumeBackground Start 10:06:54 AM Music.Pause Start 10:06:54 AM Music.Pause Start 10:06:54 AM Music.Pause Start 10:07:22 AM Music.Pause Start 10:07:22 AM Music.Kill Start 10:07:22 AM Music.Kill Finished 10:07:25 AM Exception

Since anything beyond Beta 16 up to current release of 9.8, I have been receiving intermittent crashing when exiting games from Big Box.... I get sent back to the windows desktop with a crash report on game exit. It happens using hotkey button to exit and it occurs randomly from any emulator and any theme. My Windows 10 Launch box system has been running stable for the past 4 years until updating past beta 16.... If I go back to Beta 16 prior to the current release the crashing stops. I've tried re-installing Nvidia graphics driver, changing themes, and re-installing Launch box multiple times but issue still continues. I opened a ticket for this but it was suggested I post here instead for help.. I do Appreciate any help possible from the community to resolve, I'm not sure what else to try at this point. Below is the error received. Thanks, Cannot set Visibility to Visible or call Show, ShowDialog, Close, or WindowInteropHelper.EnsureHandle while a Window is closing. App: Big Box Version: 9.8 Type: System.InvalidOperationException Site: Void VerifyNotClosing() Source: PresentationFramework at System.Windows.Window.VerifyNotClosing() at System.Windows.Window.InternalClose(Boolean shutdown, Boolean ignoreCancel) at System.Windows.Application.DoShutdown() at System.Windows.Application.ShutdownImpl() at System.Windows.Application.ShutdownCallback(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 8:39:13 PM Music.Kill Finished 8:39:15 PM Music.StopAndResumeBackground Start 8:39:15 PM Music.StopAndResumeBackground Start 8:39:18 PM Music.StopAndResumeBackground Start 8:39:18 PM Music.Kill Start 8:39:18 PM Music.Kill Finished 8:39:20 PM Music.StopAndResumeBackground Start 8:39:20 PM Music.StopAndResumeBackground Start 8:39:23 PM Music.StopAndResumeBackground Start 8:39:23 PM Music.Kill Start 8:39:23 PM Music.Kill Finished 8:39:24 PM Music.StopAndResumeBackground Start 8:39:24 PM Music.StopAndResumeBackground Start 8:39:26 PM Music.StopAndResumeBackground Start 8:39:26 PM Music.Kill Start 8:39:26 PM Music.Kill Finished 8:39:27 PM Music.StopAndResumeBackground Start 8:39:27 PM Music.StopAndResumeBackground Start 8:39:28 PM Music.StopAndResumeBackground Start 8:39:28 PM Music.Kill Start 8:39:28 PM Music.Kill Finished 8:39:29 PM Music.StopAndResumeBackground Start 8:39:29 PM Music.StopAndResumeBackground Start 8:39:33 PM Music.StopAndResumeBackground Start 8:39:33 PM Music.StopAndResumeBackground Start 8:39:37 PM Music.StopAndResumeBackground Start 8:39:37 PM Music.Kill Start 8:39:37 PM Music.Kill Finished 8:39:38 PM Music.StopAndResumeBackground Start 8:39:38 PM Music.StopAndResumeBackground Start 8:39:42 PM Music.StopAndResumeBackground Start 8:39:42 PM Music.StopAndResumeBackground Start 8:39:46 PM Music.StopAndResumeBackground Start 8:39:46 PM Music.Kill Start 8:39:46 PM Music.Kill Finished 8:39:48 PM Music.StopAndResumeBackground Start 8:39:48 PM Music.Kill Start 8:39:48 PM Music.Kill Finished 8:39:57 PM Music.Kill Start 8:39:57 PM Music.Kill Finished 8:40:17 PM Music.Kill Start 8:40:17 PM Music.Kill Finished 8:40:18 PM Music.Kill Start 8:40:18 PM Music.Kill Finished 8:40:21 PM Music.StopAndResumeBackground Start 8:40:21 PM Music.Kill Start 8:40:21 PM Music.Kill Finished 8:40:22 PM Music.StopAndResumeBackground Start 8:40:22 PM Music.StopAndResumeBackground Start 8:40:24 PM Music.StopAndResumeBackground Start 8:40:24 PM Music.Kill Start 8:40:24 PM Music.Kill Finished 8:40:29 PM Music.StopAndResumeBackground Start 8:40:29 PM Music.Kill Start 8:40:29 PM Music.Kill Finished 8:40:30 PM Music.StopAndResumeBackground Start 8:40:30 PM Music.StopAndResumeBackground Start 8:40:32 PM Music.StopAndResumeBackground Start 8:40:32 PM Music.Kill Start 8:40:32 PM Music.Kill Finished 8:40:33 PM Music.StopAndResumeBackground Start 8:40:33 PM Music.StopAndResumeBackground Start 8:40:36 PM Music.Pause Start 8:40:36 PM Music.Pause Start 8:40:37 PM Music.Pause Start 8:52:50 PM Music.Resume Start 8:52:52 PM Music.Pause Start 8:52:52 PM Music.Pause Start 8:52:53 PM Music.Pause Start 8:54:43 PM Music.Pause Start 8:54:43 PM Music.Kill Start 8:54:43 PM Music.Kill Finished 8:54:47 PM Exception