-
Posts
1,054 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by cleverest
-
Actually it's not really...it's a core i5 3.4ghz (not the old generation one), 8GB DDR3 memory...SSD OS drive...mid level Nvidia cart (GT 740), it is custom built...I always custom build my PCs...maybe I'll try a different motherboard next time...but I don't thik it's the core that's the issue because I was using Launchbox for months before with this same MB/CPU/RAM/HDD without issues... I'll probably boot to safe mode and strip everything off of it I can, to see if/when it happens. Really appreciate you sticking it out and trying to help ckp (and everyone)
-
The only exception is some games I have that are ISO, but they are also labeled (TGX) (PSN), turb-graphix ports I guess...they don't load in PPSSPP, they just saying LOADING GAME... on bottom right corner and stick there...but I'm okay with that, most work fine...apparently most of these isos were PSN games for the PSP, so it worked out :-)
-
Retroarch is fine for me, using BIN and CUE's at least... for ISO's, PPSSPP is working just fine. Thanks anyways.
-
I did that...it opens, it just loads all games with no video (black)...I've tried all the open GL plugins, reduced resolution to 800x600, even tried to DL a d3D plugin, same issue... some games (most?) when they load give the controller config on the top right (showing the PS1 controller graphic), but that is it...tried all compatibility modes, tried running as admin, tried resetting it up, etc..
-
Yes it fails on everything I try it on....I've used it in the past before, just not with this computer....I tried removing teamviewer which was said to cause some issues with it, and nothing works...no biggie, all these games work in PPSSSPP, I play my regular PSX games through Retroarch. (they are all bin/cude games). Thanks,
-
I just realized that these ISO's load fine in PPSSPP, I guess they are intended for the PSP...silly me!
-
I'm using Retroarch / Beetle PSX, and it plays my bin/cue (loading cue) files fine...but loads black on these ISO games...I tried creating a cue file using isobuster, but it just crashes the emulator when I load them... Is there way to batch create all the cue files I need for these ISO games? for that matter how do I create one that works with my emulator? EPSXE won't work with windows 81, I've tried all fixes I could find to no avail. Thanks for any help!
-
After Updating The Cache Has To Be Repopulated
cleverest replied to Robin55's topic in Troubleshooting
Possibly... my collection is compressed but only playable formats when so, takes up 8TB...notices excessive caching too, but dealing with a bigger crash error for now. -
After Updating The Cache Has To Be Repopulated
cleverest replied to Robin55's topic in Troubleshooting
Interested in this too.... how big is your collection? -
So I played around with my 8 TB drive LB collection on my laptop last night, it was slower than my desktop....normal....but also had moments of some interesting lag/hourglasses that occurred. (thought it was going to crash a few times) and one time it may have closed without any error, just suddenly not open, but that was a bit ambiguous what happened there...overall it was still going on strong, it never crashed...so my portable LB collection appears to be (mostly) fine at least... Damn desktop...
-
Jason, you've had no other reports of this crash exactly?... or you have? I hate this CLR file now...worst DLL on my computer, LOL Faulting application name: LaunchBox.exe, version: 7.12.0.1, time stamp: 0x59cd55b8 Faulting module name: clr.dll, version: 4.7.2114.0, time stamp: 0x59a63e48 Exception code: 0xc0000005 Fault offset: 0x000000000019a5c1 Faulting process id: 0x1a8c Faulting application start time: 0x01d3389e843a61be Faulting application path: L:\LaunchBox\LaunchBox.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 40293700-a495-11e7-8268-d050990cbf7b Faulting package full name: Faulting package-relative application ID:
-
Thank you for the response on this Jason...it really bums me out, I want to upgrade my LB license to a lifetime from a 1yr premium, but I have to wait until this issue is no longer occurring of course. it gets so frustrating I just stop using it after 1-2 times... I'm going to try to run my 8 TB collection (external hard drive) tonight on my laptop tonight and see what it does...but given the crash happens on a flash drive with almost no roms on it on my desktop only...it seems obvious it is one of the things you mentioned...I guess I need to take this thing apart piece by piece to fix it until I can replace my computer...I love launchbox so much, this really sucks, but of course, I know it's not your software!
-
Good summary! Just to clarify though, I haven't tried my main 8 TB collection on another computer yet...that test will be tonight....curious if it will crash or not...I hope not, would rather not have the collection/rive me the issue come to think of it...thanks so much for the help, I'll post my results... :-)
-
So to confirm, the nearly bare flash drive solution DOES still crash on the main PC, even after clearing cache...I left it sitting, went to work, and remote connected, and I see it's crashed... I'm running 8.1 now, but it was happening with Win 10 and 8.1 the same...for awhile 8.1 seemed more stable but now it's just as bad....new 8 TB hard drive too... Great advice, I will try the new account, thanks.
-
Deleted my comment above, I'm tired and not thinking straight....my flash drive version crashes, but only on my main PC, NOT my laptop...LOL, I need to sleep, I'll catch up with this tomorrow...I deleted the CACHE and will let it load up on the trouble PC (desktop) and see if it crashed in the morning...thanks so much for the help!
-
BTW all the crashing, from the flash drive and main 8 TB drive, the smaller errors pictured recently, and the one that closes LB are totally random from what I can tell...not for any game or platform or button clicked, etc...I've had it happened in the EDIT window, main view...while importing stuff (mid progress bar, after import), etc...it's never happened inside of bigbox, but I rarely use bigbox...and the crash dumps reference launchbox.exe, not bigbox.exe anyways...
-
BTW no anti-virus or auto backup stuff, I just use the built-in defender with 8.1 - I'm very good at avoiding anything nefarious online and cleaning stuff if I do get anything..nothing like that has happened with this PC....I'm very tech savvy (I repair computers for a living), at least savvy for everything except this apparently, LOL
-
Thanks CKP, I may end up sending you may main LB folder, minus the license, games, images, media, etc...maybe you can figure something out, LOL...no pressure though...I'm at a loss.,,but actually the stripped down flash drive version I've been using and posting images on tonight, does NOT crash on my laptop...at least not yet...if it does I'll post an update.... ....so it may not be anything in the LB collection...tomorrow I'm gonna try to connect my main 8TB collection to my laptop...just a pain in the arse cause I gotta move stuff around (being a desktop drive), and that will tell us for sure if my main issue is somewhere on the drive or god knows...
-
So I fresh installed LB on my flash drive to test this, seems to be working, had one issue though besides the glitch above however, as pictured...this is all I did: 1. I only moved my nestopia folder over from my other launchbox (emulators folder), and 2. the NES images, videos and manuals.... 3. Set up emumovies login in options. 3. then I imported the games from the other collection I have (copied them through the import wizard, unchecking images/assets to download).... I set my theme to TOMATO, enabled VLC as default player in options, and that's it... All good and fast....but as I was going through and editing the games to rename some that wasn't showing front covers/info for them to fix them, (I probably did about 10), I get to start tropics II and this error pops up....I submitted a ticket as it requested and CLOSED IT...LB didn't crash though, which was a relief...not the same error, LB stayed open and seems to be fine...still using it....not sure if that helps figure this out...