Jump to content
LaunchBox Community Forums

arcademode

Members
  • Posts

    51
  • Joined

  • Last visited

Posts posted by arcademode

  1. Hmm ok.  Well what can I do now? I have many Terminator console game marquees in different folders (like 10 or 15 of them) all assigned to Terminator Salvation.  Is there a good way out of this situation that doesn't involve the deletion of all those files? If it were just the one game it's not such a big deal but this has occurred on many arcade games that have home ports so it would be good if there was a way to manage this.  I think my folder structure mirrors the nomenclature convention that LB uses, not sure why this happened.

  2. My marquee images aren't in the LB folders, I have them elsewhere.  But in that folder each system has it's own dedicated folder.  For example "marquee images\Sega CD\Terminator, The (usa).jpg" and "marquee images\Super Nintendo Entertainment System\Terminator 2 - Judgment Day (USA).jpg" and several others. They're in different folders with different names, but the similarity pulled them into Terminator Salvation (arcade).  Same thing happened with my Killer Instinct, the marquee pulled in the SNES and Gameboy ports from their different folders.  If I hit "remove" in LB doesn't LB also attempt to delete the file or does it leave it in place?

  3. So when I added Terminator Salvation LB decided that all the terminator games on home consoles shared a marquee with this arcade game.  So it's like Sega CD, SNES, Genesis etc all those home console marquees are now assigned to Terminator Salvation.  If I click "remove" in LB it attempts to delete the files, so how can I keep the files yet remove them from being assigned to that game?

  4. Switched to WMP from VLC and that helped my newly developed freeze issue with this version.  I run RL in the background for most games but I'll test a couple that I launch directly with LB. Using VLC froze the ever living bejeezus out of BB for me, so it's nice that WMP seems stable for now.

    • Like 1
  5. On 11/15/2024 at 7:49 PM, vrocco said:

    Any progress on this issue. I found this thread as I am new to BigBox and have noticed after being in attract mode, the videos first start to lag behind (I.e. The video won’t match the game selected or the graphics on the screen) and then eventually just freezes altogether. I must then restart BigBox.
     

    Running the latest version with the CoinOps Redux theme. Tried all suggestions (no flv videos, using VLC, image quality medium, no transitions) to make it run better but nothing seems to help. 

    I love the ease of the program. After transitioning from HyperSpin, I was set up and running in no time. Bought the lifetime subscription to support development. I really hope I don’t need to find a new front end again. Thanks in advance. 

    Just emailed back and forth a bit with Brian again, my crash has returned - kind of?  I updated to the newest version, then experienced the Attract crash, then reverted to my last stable install but the crash remains. The weird thing is I have an older PC upstairs and when I put my BB drive in there it will still run for days.  So there's some hardware conflict of some kind happening somewhere.  For now I'm just leaving attract off when I want to run it for long periods.  Sucks that you don't get the attract mode but it's much better than having no front end active when you want to walk up and play. 

  6. On 7/1/2024 at 1:40 AM, paddyG said:

    If it might be of any help, is there a way I could actually send my entire PC to the LaunchBox dev team so they can see first hand what is going on when it freezes in attract mode?  I don't mind parting with it for a few months.  It's just a small HP EliteDesk 805 G6.  I would pay for shipping both ways as long as it is in the US.  Getting desperate to fix this. 

    Check out my comment a few posts up - I recommend getting in touch with the devs directly via email. You can exchange your Windows Logs to help them diagnose exactly what's going on.  They're certainly improving the issue but without knowing any specifics from your logs there's only so much that can be done.

  7. On 6/4/2024 at 9:23 AM, MrSco said:

    After I kill launchbox and big box, I can just start them again and it works without having to restart the computer

    Prior to the fix I was unable to reopen Big Big without a computer restart after a Big Box crash - something to do with the .NET framework getting screwed up. I had a very long back and forth with LB dev Brian via email where I provided tons of logs and tests to him and he was able to make the latest patch with that. He mentioned the following;

    "...it's more likely a page filing crash of some kind that's all controlled by .NET. The way .NET is supposed to work is that it's supposed to take care of this stuff automatically. It's one of the benefits of using a framework like this. This indicates there's something inherently wrong with what it's doing here, and we'll have to see what we can do to patch this up."

    I recommend reaching out to the dev team directly so they can investigate your logs and (hopefully) get to the bottom of the issue. I think I may get a slightly sluggish issue people are talking about, but it's only after running for a VERY long time and there seems to be no crash for me anymore. 

     

     

  8. On 8/4/2023 at 10:22 PM, The Papaw said:

    @JoeViking245 @C-Beats @y2guru @jayjayI love this app, but need a little help. I have created a badge for "partial gamepad support". I works in LB, but it shows both the regular gamepad badge along with my partial badge I created. I can't figure out how to get LB to show only the partial one. Having simliar issues in Bigbox themes I create, I have found a work around in BB using a custom field, but not the best solution. Any pointers guys?

     

    On 8/5/2023 at 6:21 AM, C-Beats said:

    You'd just turn off the built in badge and only use the partial. If going that route with badges I'd make a "fully gamepad support" badge along side the one you made and then just turn those both on and a game should only have one or the other and display the way you are wanting.

    I had some success implementing custom badges inside LB, but I can't get a grasp on the BigBox integration.  The custom gamepad options aren't showing up in the theme creator, not sure where to go from here or what kind of workaround to try. Thanks in advance! 

  9. Hey gang, thought I'd chime in with some positive notes here on this somewhat bleak thread;  Brain over on the LB dev team has been emailing with me back and forth trying to sort this out.  He's narrowed it down a good bit and digging deep, so kudos to him and his efforts.  I'll update here when I know more.

     

     

    • Thanks 1
  10. Quick interjection, at least 4 times in the last two weeks I've had a NEW crash source in libvlc.dll. The error dll is the one included with Launchbox.  Anyone else having this issue?

    I was chatting with Brian a bit on email about the attract crash. He seemed to think it might be related to some plugins or CTC themes or custom themes or whatever, but it was still crashing with a fresh installation.

    So to recap the only long-term stable installation had the following characteristics;

    • A completely fresh installation
    • VERY small game list (29 games)
    • No art assets added of any kind (no images or videos at all)
    • All transitions set to NONE

    Adding some art caused a crash, adding more games caused a crash, having transitions on caused a crash.  Not sure if this is helpful or leading to any progress but I figure it's useful to have more test scenarios and data.  I'll keep trying stuff, different combos of setups. In the meantime I hope Brian comes through with a discovery!

  11. Man is there like a Discord for Flycast or something? I can launch the game from a batch file sometimes but when I try to launch it from Launchbox (pointed to said batch file) I swear it just never boots.  The green Naomi boot screen comes up but hangs.  When it works its really cool.

    I was able to get F355 booting in Deluxe mode and got my 6 gear shifter working with it via emulated controller. Here's the video that game me the clues on how to set it up. This video is for Demul but the principal is the same: 

     

  12. On 3/7/2024 at 6:52 PM, JimV said:

    See my post from yesterday.  I think it might be the Fade Quick screen transition that is causing this problem.  Try hard coding the screen transition to something  else and see if it fixes your problem.  I went through all of the ideas in this thread including what you tried to no avail.  Good luck!

    Actually yeah, no dice. I set all my transitions to NONE and it still crashed. I should have known this would have no effect actually since running the ahk automated browsing with default transitions (various fade and slides or whatever) was stable. 

    EDIT: Wait a dang minute - actually on my other PC with a perfectly fresh installation zero transition mode might be working. Previously this freshie installation was also crashing. 

    2nd EDIT: This merits further testing. The fresh install is done on my desktop with 48gb ram, so memory wasn't really a bottleneck and there was still crashing before with lots of testing variables - last of which included a fresh installation with only 29 games on the list and ZERO media added of any kind, so no logos, no videos etc.  It was still crashing despite these restrictions! Turning off all transitions was stable for 12 hours with Default theme, and just now another 12 hours with Slipstream.  I'm going to keep testing, running it for longer and with other themes, then test on my full installation to see what happens.  Very interesting find @JimV! I'm curious if we can get some other users to test this out!

    3rd EDIT: So far Default is the only stable theme. Tested with a couple others, both crashed. Also Default crashed when I added in more games and some art, so something isn't happy. Still testing...

  13. Ok so I deleted my Launchbox installation on the other Win10 machine (which has 48gb ram, so there's not ram bottleneck here) and did a completely fresh installation. Setting attract mode to the fastest settings (10 sec wait, 5 sec between) to force the fastest crash and bigbox crashed in <2 hours. Ntdll.dll error, same as before.  (EDIT: important detail excluded. This installation pulled my 30 windows games into the database and I didn't grab any additional media. So no videos, some gameplay screenshots, and maybe 20% of the list had a clear logo. So the issue doesn't seem to be media related)

    So what are the odds of it being a Windows problem? In my estimation, low. Testing with my other Win10 machine (which has all the ram headroom and an up-to-date windows install) against the not-so-up-to-date original PC and experiencing the same error seems more like a bigbox problem, right?

    Happy to provide any additional information to assist in getting this fixed.  I was able to replicate the bug at random on my only other Windows 10 machine, so the devs should be able to replicate this issue. Is there any hope of this getting fixed, seeing as how similar issues seem to have been plaguing bigbox for years in attract mode?

     

    Another edit so I can stop blowing up this thread:

    Testing a couple more things now;

    1.) AHK script to manually scroll down a list. I'm curious if it's related to the Attract Mode programming, or if simply scrolling through the list causes a crash. Obviously if it's the latter that's a big problem because the crash could occur during normal browsing if you look at enough games

    2.) Way back in page 2 or 3 of this thread Jason suggested upgrading to Desktop Runtime 3.1.8. and a user said that helped. I had a slightly older version installed (and 6.0 which I think was installed by a game? not sure but I'm checking into it). So after the AHK test (which seems to be going OK so far) I'll test with Runtime 3.1.8.

     

    LATER THE SAME DAY (EDIT)...

    So the AHK script successfully navigated my MAME list for way longer than Attract Mode would have worked, around 4 hours. The thinking behind testing in this manner was to rule out any memory errors in loading media. I can test it longer but after scrolling through about 1800 MAME titles (all with video, png, screenshots - the works) everything was smooth sailing.  This seems to indicate an error in the Attract Mode feature itself, no?

    I then tested the system with Runtime 3.1.8 and Attract Mode enabled and we're back to crash city.

  14. Did more things, still crashing:

    - Ran BB and LB as Admin
    - Compatibility mode for BB and LB, Win8 and Win7
    - Fresh installation
    - .net framework repair tool
    - manually doubled the default windows paging size
    - sfc repair in command prompt

    Googled up the dll error which brought the net framework repair and sfc scan ideas, didn't help of course.

     

    EDIT: Here's a kicker - tried a fresh installation on a different Windows 10 computer using the default theme. Still throws the ntdll.dll error as before. I'm going to try a full delete and reinstall on this other Win10 machine, just to make sure I'm not missing something.

  15. On 11/27/2023 at 4:13 PM, drewjbx said:

    So I just wanted to chime in... this issue has been plaguing BigBox for a number a users for years at this point as I have seen old threads from here add reddit as far back as 2017.

    I have attract mode set to default speeds, switch between platforms on, 10sec time in between movements. I have tried HyperMax, Colorful, and Critical Zone themes. I have deleted all BB image cache and force populated, then defragged the HDD as well. Attract mode works fine for about 30min then it starts to lag a little bit, then gradually gets worse. An hour in it is almost locked up and unresponsive to input but task manager shows BigBox is using the same amount of cpu/ram (no issues with maxing out resources).

    So to exit I just press windows key to show the taskbar and close the BB icon and it shuts down just fine (no unresponsive error dialog box). The next step I tried is to remove the video folder, attract mode plays with absolutely no videos. The exact same thing happens... slows down gradually then locks up. I am on the latest build 13.8. I have tried this on 4 different HDD's (seagate and wd clones) so I know it is not a hardware issue. Very disappointing to say the least. So for me it has nothing to do with video playback. At this point I would hope a screensaver option can be added with user defined videos (Batocera does this)

    This way we can at least just play some pre-set gaming/arcade videos because Attract mode is broken for me, and it seems, quite a few other people. 

     

    Come join the fun! Here's a thread with more users having this same problem and there's no solution. Scroll up a few posts where I linked a thread dating back to 2019 where users are having the same issue:

     

     

  16. On 2/17/2024 at 6:06 AM, Retro808 said:

    I highly doubt Jason or the team are not interested. Last I spoke to them about this he was not able to replicate it to be able to track down what might be an issue. This was something that plagued me for quite a few years. Between 6 total cabs/builds running BigBox it would affect each them differently or not at all. On 2 of my cabs it ended up being corrupt video files (took some testing but eventually I found which platforms had the culprit files). On one other it just stopped being an issue. Two of them never even experienced the issue. I have not had a single crash in any cabinet in well over a year. 

    Have any of you tried removing your video folder and running BB to see if you get any crashes? Not saying this is the true issue, but it is one known to cause this for some users?

    Just tried removing the video folder, still crashes in the same way. Are all of your various PCs running the same version of Windows? Sidebar I also tried updating net framework. Crashes with and without video folders, so no change basically.

    @MrSco is the OP on the older thread which was started over 4 years ago now. It seems crazy to me that in 4 years none of the devs could replicate or remedy this fatal problem.

×
×
  • Create New...