Jump to content
LaunchBox Community Forums

Xrc6

Members
  • Posts

    51
  • Joined

Posts posted by Xrc6

  1. 2 hours ago, Jason Carr said:

    Why do you continue to argue with us? It will work if you actually do what we're telling you to do in order to fix it. You're misunderstanding a number of things, so honestly, I'm doubting that that's what really happened in the past. Regardless, we gave you the solution.

    But I just explained your solution doesn't work? lol I'm not arguing. I'm explaining as simply as I can. Are you avoiding certain things I explained? Even adding TGCD and pointing to the same core under associated platforms doesn't work unless that command parameter is checked. It won't unless I make a new LB install which is what I did earlier as an example. It's exactly listed the same, imported as TG CD but only shows as TG 16 in Associated platforms and yet it works. How can it work in one LB folder and not another despite using same import platform and core?

    I also explained it worked fine previously. Then stopped. Nothing ever changed and no the solution didn't make it work. Once it loses it's ability to path to the core/emulator. It will never again work without that command parameter unless I do a new LB install folder. That happened before with C64 and before that with Gameboy and another platform. I have the threads history that proves it.

    I already found the solution that worked. hence the thread. I was just trying to help it get sorted to prevent it from losing it's ability to see the path. I get what you explained but you're not understanding that if it were the case, then it wouldn't have worked previously. All I do with it is import roms into a platform and play the games. They work then one day they won't launch and it appears random despite what information it shows.

    You may find me doubtful but you realize I made the thread finding my own solution and was just trying to get it sorted. I get that TG CD wasn't listed, adding doesn't effect it either. You mentioned LB doesn't know what platform goes to what core to which I then pointed out that if I import a platform and point it to a core then LB knows what platform it is. But manually adding it to the associated platforms didn't work but the command line does.

    I apologize for trying to help out in the community in case someone else has this issue. I found the solution that worked so if/when it happens to another platform, I'll just add that command but working around what I'm explaining doesn't make it go away.

     

     

  2. 30 minutes ago, neil9000 said:

    Correct, that core is for both. You do however need to tell Launchbox it is for both, Launchbox will never attempt to guess the platform or emulator to use for it, that is defined by the user. In your case you are using a core that supports the CD platform, but you have not told Launchbox to use that core for that platform. This is the reason for the associated platform tab in the first place, so that you can use the same emulator, or in this case the same emulator core for different platforms.

    While Launchbox does try to automate as much as possible some user input is still needed, it just cant be expected to know of every emulator ever made and for which platform it supports, thats just not possible. So the way it works is you add any emulator you want to use, but..... you need to tell Launchbox to use it for that specific platform.

    Also bear in mind you can use any name you like for a platform, so if you decided to call Nintendo 64 "ninty 64" for example Launchbox would have no idea what that platform is, or what to do with it, hence you "associate" a platform to that system and emulator.

    But if you import it as TG CD, then it should know that it's for that CD platform. shouldn't it list itself under associated platforms?  I just tested with a separate LB folder and found it does not even though it says TG CD platform under the edit game details menu. It created a new TG CD platform in my platform category. It scrapes all the media as CD...then how could it not know? Why would it launch after I import but at some seemingly random point, it won't? 

    But as in my previous thread. I had Commodore 64 in it and worked great for a while. Maybe 1 or 2 months later it stopped launching. That one is always shown in associated platforms list.

    See if it does the same for you. Create a new platform, select NEC TG-CD for Retroarch and for me everywhere else it lists as TG CD except for the associated platforms list. All LB has to do is create a new title under that list. However for me, just making one didn't change anything. I still had to use the command line.

    *Edit: Here's a pic of what I mean. This is from my test folder with just LB only installed in it and I created a new import. In one menu it shows the CD platform from which I imported it as. In associated list, it only shows the TG 16....why couldn't it create a CD version there as well? But either way, that alone didn't seem to be the source of what causes my issue with a random platform stop launching.

    f2vdhs.png

    *second edit: I just now noticed that Commodore 64 isn't listed by default. So importing C64, it must create one in associated platforms list then because it's shown on my regular LB install where I imported it. So does TG CD show up on your list if you import that platform? Because it's not for me.

  3. 4 hours ago, Jason Carr said:

    It looks like you're missing the NEC TurboGrafx-CD platform from the Associated Platforms list in the Retroarch emulator. That's what's causing it.

     

    2 minutes ago, Lordmonkus said:

    You are showing TurboGrafx CD games not working but in your associated platforms list you only show a TurboGrafx 16 platform, no CD platform. You need to have your Associated Platforms added and named correctly.

    Then why did it work before?  Same with previous times with C64, Gameboy and SMS. They would work fine then at some point stop. Didn't matter if I re-imported everything or not. I feel like I'm just repeating myself beating a dead horse. 

    I can change it to say CD. Doesn't make it work when I uncheck the command parameter though.

  4. 3 hours ago, neil9000 said:

    Yeah, just watched the video posted, in this specific issue you are launching a Turbografx-16 CD game, but when you go to the associated platform tab for Retroarch you only have a entry for Turbografx-16. You need to add another associated platform for the CD version, they are different systems in your Launchbox sidebar, so need separate entry's in the associated platform tab also.

    EDIT.

    This is why adding the commandline to the games works, Launchbox doesnt know which core to use for that platform as it is not in the associated platform list. Obviously adding it per game tells Launchbox which core to use, so it loads correctly then.

    That core is for both 16 and CD. That's the only core for NEC I have and it works perfectly in Retroarch itself. But that doesn't solve why a platform will work perfectly fine and then suddenly stop. Otherwise it would never work to begin with.

  5. 4 hours ago, Jason Carr said:

    @Xrc6 Thanks for the video explaining things. It's certainly odd, especially since I haven't heard about this being an issue from anyone else. Can you zip up and PM me your LaunchBox\Data folder (in a state where the issue is occurring)? Sorry if you already have; I should be able to walk through the code to figure out what's going on if I can replicate it here on my end with your data.

    I can but I added that custom parameter to all the roms effected since then so it's not in the exact same state that the issue occurred. Does that matter? 

    This is the other thread I found where a user seemed to have a similar issue to the one I keep having and there's a post there mentioning the command parameter which worked for me: 

     

  6. I'm posting this here hoping someone can take this (rare but common for me) issue to the author to get fixed because it's definitely an LB only issue.

    • Issue: All ROMS under a platform will suddenly stop launching Retroarch for no reason even though it worked fine when last used. Re-assigning everything does not work. Delete platform then Re-importing does not work.
    • Solution: Edit emulator details tab. Check "use custom command line parameters" Type: -L "cores\****"   (where **** is the name of the libretro core
    • Cause: I believe that something to do with the Associated Platforms stops working. Even though everything is properly assigned. Even re-assigned, it forever stops working unless you reinstall LaunchBox and start all over. However this problem eventually re-occurs with some other platform.

    My previous thread about the issue: 

     

    After that last thread where C64 Platform stopped launching retroarch. I was told no one else has this issue. So I took the drastic approach and reinstalled Windows and Launchbox. Just as I knew would happen, the issue occurred again but this time it was for the TG 16 CD platform. (it's always a random one) But I googled and found someone else did post the same issue, just worded it differently so I'm not crazy and it's the problem definitely isn't something I'm doing as everyone tells me it is.

    So I solved it by selecting "use custom Parameters" under the edit emulation menu and put this into it. -L "cores\mednafen_pce_fast_libretro.dll"  So even though this core is selected under Associated Platforms, it stops working for no reason and is not fixable without rei-installing LB.

    So the big question. Why would ROMS for a platform work fine one minute, then never again the next without any changes ever being made? It has to be a bug in the code where the core listed is no longer working in LB despite re-assigning it. But the command parameter bypasses it. So despite what anyone thinks, I really think the author should look into it or at least offer that command parameter to be selected rather than manually typing it in because I had no idea what -L means until I googled around and came across that parameter to type in. So mods can move this wherever but I just wanted the author to look into it because it's a weird issue even if it's rare for everyone else but me.

     

     

  7. 29 minutes ago, CDBlue said:

    Ok thx for reporting back.  Nothing there seems to point to a permissions issue that I can see (at least not as far as LB/BB or roms are concerned). Was just a thought I had when I was reading your issue, so worth asking to be sure :(  Another thought, are you experiencing any other weird glitches with any other software on that PC other than LB/BB?  Maybe it's a hardware issue that just seems to manifest itself more with LB/BB? Do you know how to run a Memtest and HD test just to see if things are fine there?

    Everything seems to work normal. Dell has their own hardware diagnostic software which also updates drivers and it checked fine last I used it. But the C64 roms suddenly not launching also happened on my previous laptop, Lenovo Yoga. With the videos not playing issue, they do play in Big Box...so that's something. It shows that the issue doesn't affect BB mode but only Desktop mode. That just about has to be something with LB or how it interacts with VLC and WMP media players.

  8. 8 hours ago, Jason Carr said:

    If it's still not showing the videos after that, then for some reason it's just not finding the video files. If you edit the game, does the video file show up in the Game Video Path field?

    Yes it shows, as you can see in one of my posted screenshots. You can see the video path is correct and the video file is there. In fact it plays fine in Big Box mode. But not at all in desktop mode, so yes it can't find the file in that mode. I don't know how LB is different between the 2 modes code wise...just like it suddenly could not find my emulator core to launch C64 games. Again these seem too similar, some kind of bug occurs that causes LB to lose it's link even though it's set or re-assigned, that link is permanently broken after that.  It's what I've been trying to say, now whether LB updating itself is somehow causing it, I'm not sure since I didn't pay enough attention at the exact moment but I only noticed all of these kinds of issues at some point soon after LB updates itself. Again I don't play all that often so it's not unusual for me to play a few times then not again for 2 months only to find LB wants to update.

  9. 6 hours ago, CDBlue said:

    Just out of curiosity, not sure if it's related to the issue or not. But do you have launchbox install on the local machine, or a NAS/External drive?  If it is a local install, where did you select to install LB?  Same question for your roms, local to the same machine that you're trying to launch them on or on a NAS/External drive?  I'm wondering if maybe there's a permission issue going on here?  Again, just taking a stab at some other possible answers to what you're seeing.

    It's installed at C:\Games\Launchbox. Roms were set to move to LB's Game folder. I keep a copy of that folder on an external HD in case anything happens.

    Although I've had this video not playing issues before on a number of roms, I could mess with them individually to get them working again, usually re-assign folder, switch to WMP and back or a few things like that. This is actually the first time that no video plays and nothing I do helps it and more than that, it happened immediately after I just reinstalled LB.  Even though my previous install had the issue of C64 games suddenly not playing, at least the videos did play....so what could have happened there?. However they play fine in Big Box mode...so I'm pretty sure this is some kind of bug and maybe it's related to how Windows OS or the media players function. VLC is the latest version and installed somewhat recently.

    I'm going to try reinstalling VLC. *edit: I reinstalled VLC, videos still don't play in desktop mode.

     

  10. 7 minutes ago, Retro808 said:

    Do you have videos checked to show in the game details pane?

    Edited as I see you said you have auto play set.

    do you mean the view details?  The game detail pain to the right only has 3 options. Favorite icon, Edit and Close. Videos always used to play fine by default right after I would download media. I've always used these same settings.

    2629wy1.jpg

  11. 22 hours ago, Lordmonkus said:

    I haven't been dismissive of you at all.

    If you want to provide more information such as screenshots of your emulators setup in Launchbox (if / when this issue occurs for you again) we will try and help you out. Screenshots of your edit emulator, edit platforms and associated platforms window would help out a lot, quite often when we dig into peoples setups we find a small but not so obvious error in the setup such as a path changed, platform name mismatch or the user changed the emulator and didn't transfer that change in Launchbox.

    Well right now after a new install of LB and just after importing arcade games, my videos will not play. However they will play if I use Big Box mode. But I don't prefer that mode. So here is a screenshot showing that my video's are properly linked and another shot that shows the video is not playing. I have the options set to VLC (also tried Windows media player but no luck) and set to auto play videos. So since this is my current annoying issue, we'll just start with that.

    I originally wanted to make a video showing me re-assigning Retroarch in the bulk editor and not launching but found I had no way to do that. So as you can see below, it's linked to video, but doesn't play. It's kinda similar to how C64 suddenly wouldn't play any of it's associated games. Whatever the source is, may be the same but there's nothing outside of LB that is interacting with it except me.

    Here you can see the screenshot shows, but no video like it usually does.

    e6925k.jpg

    It's linked directly to the file.

    dr6t7p.jpg

    setting. I already tried WMP but it didn't make it work either. But again plays fine in Big Box mode, so clearly this is an LB only issue. Also "autoplay videos" is set to on. iF you need any more pics, let me know.

    1zeks9x.jpg

     

     

     

  12. 21 hours ago, Drakkorcia said:

    I agree with LordMonkus and Scooter. This sounds like necessary files are being quarantined at first run. Afterwards, the application doesn't work anymore until you reinstall and start over. Then the cycle continues. Launchbox is a solid program that when configured properly, has never given me trouble. 

    If that was the case, then doesn't it seem likely that no other game for my other platforms would launch either? So since I use very few 3rd party apps that are popular, then that means one of those or the Windows 10 OS that many people also have, would have to  wait a few weeks and at some random point, remove a file that only causes C64 games not to launch? Or in previous cases, cause TG 16 and Gameboy roms to not launch? However as I stated, this has happened several times since last year when I first posted the issue. I had a completely different laptop. Different drivers. An older version of Windows 10 than what I have now and only a limited few 3rd party apps that I mentioned previously. I didn't even have a 3rd party antivirus until recently. So the only application that can quarantine a file by default is Windows Defender. So if your Defender doesn't remove LB files then why would mine? HOwever it doesn't show anything ever being quarantined. If WD ever removes a file, a pop up box will display asking me what to do with the file. THis has never happened, I don't do too much with my laptop.

    It doesn't make sense for any software to wait a few weeks then remove a super specific file for a 3rd party program like Launchbox. But since I have the same OS and very popular 3rd party software that everyone else has, then I would not be the only one.

     

  13. 14 hours ago, Kondorito said:

    Have you checked the quarantined/processed files and folders in webroot? 

    Seems that after first run, the AV is placing some stuff in quarantine. 

    Try adding the whole LB folder as well as the emus folders as exclusions. 

    There doesn't appear to be a quarantine folder but webroot report shows it has never found any threats and it's only going to quarantine those. Though I've had the issue before I had Webroot. Windows defender has nothing in quarantine.

  14. On 4/14/2019 at 12:37 PM, Lordmonkus said:

    Again, I am only guessing here but I am gonna say there is some other underlying cause of the issue here and it's not Launchbox itself. Like I said before, I have never experienced this is in the 3-4 years of using LB and I have never seen any other users have this issue.

    Simply deleting and re-installing Lb without find the actual cause of the issue is just going to end up in the same result again for you.

    But that's now how things typically work with computers, just because you never experienced something before doesn't mean it doesn't exist. There are tons of software out there where only a minority people will experience a bug due to too many hardware and software configurations between many hardware manufactures, driver code, bios's, etc. I've experienced this on Lenovo Yoga Laptop with Windows 10 and now Dell XPS with Windows 10. There's really nothing special or unique on my system and as far as 3rd party software goes, aside from updated drivers, I have Firefox, Webroot, VLC player, LB, Retroarch, MAME and Adobe Elements installed. On my Lenovo, it had some Lenovo software, Opera browser, VLC and various emulators. So I'm game for any theory on what kind of underlying issue could exist between two different laptops that otherwise work great. I don't think being dismissive is very helpful at all. If you don't know that's fine but blaming me when I literally mentioned exactly what I do with it causes more frustration and more willingness to look elsewhere for a launcher.

    I can't help it that the only way to fix it is to reinstall it all over. So how is it that reassigning the emulator, seeing that it has the proper path multiple times over doesn't work but reinstall does and yet it's not an issue with Launchbox? Nothing else is interacting with it so how is that possible? I only open LB once in a while, Run it's updates if it asks and making no other changes only to find some random day that a specific platform suddenly won't launch Retroarch anymore.

    Quote

    Simply deleting and re-installing Lb without find the actual cause of the issue is just going to end up in the same result again for you.

    Don't take this the wrong way because you must understand how frustrating it is to have people dismiss you just because they don't have the issue but don't you think finding the cause is why I"m here asking? I went as detailed as I could be and as you can see, there is nothing else but LB that could cause it's own problem. Then it magically works with a new install, seems obvious there's some kind of bug or issue caused when updating. Maybe some corrupt piece of code that suddenly prevents it from linking with Retroarch....I don't know how it launches games, that's why I'm on here asking.

    *Edit: I just noticed the other issue I've had before regarding videos and some artwork/flyers not showing. I just did the reinstall. Imported MAME games and downloaded media. And none of the videos will play in LB. They games link directly to the .mp4 file, The game title screen displays but the video doesn't. I have it set to auto play videos. And to use the recommended VLC. ...so is this a VLC problem? a LB issue? Or am I to blame, what? The videos usually work fine and like my retroarch launching issue, they would randomly stop playing. This time it occurred right off the bad. I manually linked the video for a couple of games and the video is there, it plays fine in VLC....but it's not displaying.  So I wonder if this inability to link to video despite it shows it is, happens to be a similar issue to why all the games for a specific platform suddenly won't launch when pressing play?

  15. 7 hours ago, Lordmonkus said:

    That is extremely strange, like I said, I have never seen that or seen anyone mention anything similar. Maybe you have an overly aggressive anti-virus or something but I am only guessing when I say that.

    I will tag @Jason Carr for him to have a look at this thread and maybe he has some more insight into what could cause this sort of problem.

    I bought Webroot about 4 months ago so only WIndows Defender has been the only consistent AV since I got into using LB with Retroarch. I figured this issue would go away after a few version updates but I think it's specifically related to how Launchbox handles retroarch to launch games. It's not like I really play all that often, I usually launch a few random games to play once in a while when in the mood.

    I have MAME for arcade games and never an issue launching that and before I started using Retroarch, I didn't have this issue. I even have the latest version of Retroarch and C64 games just stopped working recently under LB but again works fine in Retro directly. I didn't realize until I went to launch a game and the only thing that might have changed since my last play in C64 was Launchbox updating itself.

    Now one thing I have done that causes an issue with a few videos and box art loading properly is that whenever I reinstall Windows 10 using the refresh method, which I do on occasion just to keep it operating like new. I'll take the entire Launchbox folder and back it up to another drive and put it back after Windows is done. It works fine except that some videos won't load and some box art won't display until I go into the editor for each game that won't show video/art and make a change...any change like just deleting a word in the notes tab or reassigning where the files are located and then it'll work. Even though the link to the files still shows properly, just making any kind of change under that edit properties window seems to make it work again....it's weird but that one in particular seems to be related to moving LB folder back and forth even though I put it in the exact same file structure as before. But odd that many videos play fine but only some won't as a result of me doing that. It appears to me that LB can act as a portable application for the most part but maybe I shouldn't do it that way again.

    I went ahead and deleted LB and am going to start again for probably the 8th time since however many months ago this started. I'm going to uncheck updates this time and see if that helps.

     

  16. 8 minutes ago, Lordmonkus said:

    Not sure what to tell you, I have never had this happen to me in the 3-4 years I have been using Launchbox, nor have I seen anyone mention this happening to them.

    I would suggest though that if this happens again, instead of uninstalling and re-installing try selecting all the games in the platform causing issues and using the bulk edit tool to re-assing the emulator to the roms.

    I might try to make a video showing what it's doing.

    I've done that....many times in fact. Even if I completely delete C64 system and import from scratch. It will not run. But they launch perfectly in Launchbox so it's not Retorarch itself. I had this issue last year on a completely different computer.

  17. I use RetroArch for all of my platform systems. I don't know exactly what causes this issue or when exactly it occurs but usually on at least 1 platform (console system) Launchbox will not start any of it's games BUT they work just fine in Retroarch itself. So for example I installed Commodore 64 and some games in Launchbox. Press play, retroarch launches and game works fine. At some point in time, I'll start up Launchbox one day and suddenly none of the Commodore 64 games will do anything when I press play. If I open Retroarch and play from there, they work fine. If I check the edit menu in Retorarch, it still shows it as the emulator. The other console system platform will launch retroarch and the games play fine.

    So if I delete Commodore 64 from Launchbox and import it again. It still wont work. The only way I can get it to work again is to uninstall Launchbox completely and start all over from scratch. Then every platform will run just fine until some random day later on, I'll launch it and at least 1 platform system will have it's entire library of roms not able to launch. So I don't know if somehow upgrading Launchbox causes some kind of issue or what.

    As a secondary issue I also have is that eventually some of my video's that were downloaded won't play in the default menu. It's almost as if Launchbox will just lose it's ability to link to files despite proper settings. I don't use any kind of themes. Last time I had this issue, it was the TG-16 roms not launching. Another time it was Sega CD. So it seems to be unable to link to retroarch to launch the game but yet all the settings are set up perfectly. Nothing changes except whenever I let Launchbox update itself. Any idea what might cause this, it's so annoying to spend hours redownloading all of my videos and artwork, etc.

  18. 50 minutes ago, Lordmonkus said:

    No, I am reading but I am trying to make sense of what you are saying.

    I have tried to determine if it was just some games in a platform or all the games in a platform. I am also trying to narrow down the problem beyond "games don't work" because "games don't work" tells me nothing in trying to help troubleshoot

    This tells me you don't have an emulator associated with those games.

     

    If things worked and then just stopped working it is most likely either your roms changed location or your emulator changed location.

    It is possible that you have run into an extremely rare bug but it would be an extremely rare case because I have never seen anyone have this issue that you are describing it without being a case of user error. Also I have never had games just stop working (outside of my own user error) and I have been using Launchbox since version 5.

    ALL the ROMS for Gameboy, TG 16, PS1 do not work. I covered that well I think. I already mentioned I checked the links under the edit menu, all those ROMS and the emulator and Launchbox are in the same folder and nothing has changed or moved and under the edit menu, they are the correct file names and links directly to the ROMS and Emulator. I checked multiple times. As mentioned, I even reinstalled Retroarch, reassigned all the ROMS to retroarch. ALL ROMS are located in C:\Launchbox\Games\*folder for each console. I haven't even opened Lunchbox in almost a month in which case it updated to the latest version recently.

    Also this particular Windows laptop is only used for emulation. It doesn't get used outside of that, I use a MacBook for everything else. So nothing has moved or changed other than Windows updates and Launcbox update. The ROMS that don't run in Launchbox, run fine in Retroarch directly. I already audited all the ROMS, reassigned them....they are pointing to the correct locations so that's what I'm asking about. Since they used to work fine and nothing has changed, I can't user error that if I don't even open the laptop since they were last known to work fine.

    Quote

     Let me clarify further. Every single console in Launchbox are using the Retroarch emulator with their respective core. They all used to run fine in Launchbox, I tested them. Now some consoles such as Gameboy are not. Every single ROM for Gameboy is using the correct emulator and core. I checked multiple times, same issue for TG16 and Playstation. The bios files are still there, Launchbox doesn't show any missing cores.

    I can run those exact same ROMS under Retroarch just fine, they launch immediately. So I deleted Retroarch from Launchbox and added it again. I had to use the bulk editing tool to reassign all the ROMS and I checked that they are assigned to Retroarch. I even deleted Retroarch itself and reinstalled it using the latest version. I updated all the cores, assets from within Retroarch...still same issue. Not sure I can clarify that any better.

     

     

  19. 21 hours ago, Lordmonkus said:

    Which games aren't working ?

    I already mentioned that. I get the feeling you aren't really reading but ALL of the Gameboy ROMS, TG 16 Roms and PS ROMS don't run under lunchbox but do under Retroarch. Again they used to work just fine as in maybe a month or so ago. I haven't tried playing any of them until recently so not sure if the last update for Launchbox did something or what but they are correctly assigned. The ROMS for all the other systems run fine and again they all use Retroarch.

     

  20. 30 minutes ago, Lordmonkus said:

    If some games are working and some aren't and you are 100% positive that the rom files are fine then you have some games assigned to a different emulator.

    But I can right click on each ROM, select edit and see that the ROM is associated to Retroarch. Every ROM is assigned to Retroarch. Only the ROMS for Gameboy, TG16 and PS are not working through Launchbox, they are all assigned to Retroarch...there's only 1 emulator on here and I can select the same ROMS directly under Retroarch and they work fine. I bulk edited every Rom to assign to Retroarch twice now. There's no other emulator listed because I only have 1 installed.

×
×
  • Create New...