Jump to content
LaunchBox Community Forums

MazJohn [Mr Arcade]

Members
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

8 Neutral

About MazJohn [Mr Arcade]

  • Rank
    16-Bit Artificial Intelligence

Recent Profile Visitors

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

  1. 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?
  2. @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...
  3. 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.
  4. Thank you Jason, Will go with minimal script for the time being...
  5. 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
  6. using that script i get the above error on exit with xbox controller automation.
  7. 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)
  8. 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...
  9. 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....
  10. 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...
  11. 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,
  12. 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...
  13. 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
  14. 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...
×
×
  • Create New...