Jump to content
LaunchBox Community Forums

oblivioncth

Members
 View Profile  See their activity

  • Posts

    163

  • Joined

  • Last visited

 Content Type 

Everything posted by oblivioncth

  1. oblivioncth
    More information about ""
    Ok yea I figured as much... The format of this file in particular is really annoying. I'll work on a fix.
  2. oblivioncth
    More information about ""
    @dsnyd22 Do me a favor and upload that file in question so I can examine it. I don't use the parenting feature extensively and so it's possible there's some fields that I didn't account for in some user's installs. The file should be at <Launch Box Directory>\Data\Parents.xml Also, just out of curiosity are you using "Selected Platforms Only" or "Force All" for the Playlist Game Mode?
  3. oblivioncth
    Huh they did put the page back. Well it's still a stretch but I'll keep it in mind if I come up with any ideas. As for FP itself, yea Ultimate 12 is a bit behind and I'm not quite sure when it's supposed to be coming. I don't think it will be super long, but if for some reason it gets delayed severely I might try to backport the features to an old build so that it can be used with 11.1, but currently it won't work with it as too much changed between the releases.
  4. oblivioncth
    @SiriusVI Just pushed the update for FP12. I did move a bit of a faster pace than usual and make a large number of behind the scenes changes. so it's possible there's some uncaught bugs, but everything seems pretty good as far as I can tell. Ironically, not long after you mentioned the page on the Flashpoint website that went over each platform in detail the Flashpoint Archive team removed that page because they felt it wasn't being maintained well enough. So using content from that in LB went from pretty much unfeasible (for me, in a reasonable amount of time), to outright impossible XD. The good news is that I did make the change such that all platforms are now automatically grouped under a "Flashpoint" Platform Category, and those platforms (as well as the category itself) will use their corresponding icons.
  5. oblivioncth
    Not at this time. It's something I might look into at some point but it's far down the bucket list at the moment. 1) I originally didn't bother doing this because it is another file I need to start parsing that isn't being parsed currently and at the time there was already a lot of different files I had to write readers/writers for. While it isn't too hard to do it manually, it certainly does get annoying having to redo it every time you update. I'm a bit busy with other things, but I'll certainly add this when I can since it makes total sense. 2) I'll double check to see if these are included somewhere in the distributions and if so sure, but if it comes down to needing to scrape them off the site then while I'd keep it in mind, it would be pretty far out in terms of hitting the trifecta of interest, time, and ability. Also would depend on the degree to which the page elements change when they update the list. I have enough fun dealing with the constant breaking changes of FP itself XD.
  6. oblivioncth
    There were no functional changes in that update. I was overhauling all of my CMake based projects to allow for building libraries and executables that are linked to their dependencies via shared libraries in addition to static ones. Essentially, the shared version just has DLLs along side the executable while the static version is standalone and doesn't need them. The latter is the form the releases had been taking before I started building both, so while it doesn't matter which you use in the futute, the static build matches the releases from the past. But in the end they're functionally identical. For now it doesn't even matter for me either and getting shared builds working was more of a formality. I'll probably note somewhere in the README that you can use either. EDIT: I guess there is technically the difference that the target version of FP changed to the latest in that release, so it is "better" in that it avoids the warning message of a mismatched version during import.
  7. oblivioncth
    Oh OK. You should be able to just import over your current setup without issue.
  8. oblivioncth
    Technically I've never asked the team about doing this, but from my familiarity with it I would imagine trying to just overwrite everything would have a high chance of breaking stuff. What I would do is remove the old copy of 10 and then put the copy of 11 in the same exact place with the same folder name so that the paths are the same. Then, if you don't want to mess with updating your imports, just download the latest version of CLIFp manually and drop it into the new FP folder. If you use the favorites system within Flashpoint then you'll need to export your favorites so that you can import them into the new version: https://bluemaxima.org/flashpoint/datahub/Extended_FAQ#TransferPlaylists
  9. oblivioncth
    @Vippy_man @SiriusVI Don't mean to spam, but I figured I'd ping you guys, just in case you were relying on an email or whatever to be notified.
  10. oblivioncth
    Ok the new version is up, give it a roll, and don't hesitate to let me know if you run into other issues.
  11. oblivioncth
    Haven't had time yet to look into the cause, but I can replicate the crash.
  12. oblivioncth
    Gotchya. Just trying to get at your exact intentions, as well as what you did. So originally you just wanted to import everything on the Flashpoint "Favorites" playlist (hence selecting that playlist, along with "Force All" of Playlist Game Mode) and that exhibited the issue? If your intention was to do exactly this (importing only the games from that playlist, regarddless of platform), then no you don't also have to select the Flash platform and are using the tool correctly. If you want to import ALL Flash games, regardless of whether or not they're on the Favorites playlist, then you will need to select the Flash platform.
  13. oblivioncth
    Sorry you're having this problem. I'll try to reproduce it as soon as I can. To clarify, you say you're trying to add Flash games but I can't see that platform option in your picture since it's too low in the list. So are you import options as shown in the picture, plus the "Flash" platform selected? It already has been, though now I need to fix this new issue. EDIT: Sorry, didn't realize I forgot to upload the past few releases here ><.
  14. oblivioncth
    Sure. Right now the only intentional handling is to do things the way Flashpoint does natively, so there is no force full screen switch or anything like that. I didn't consider it much given the games in FP tend to me more desktop oriented, and less "couch gaming" (not to say you can't do it anyway). I'll keep in mind trying to implement such a thing, but it would likely be challenging given how there are numerous different sub-programs that Flashpoint uses behind the scenes, some of which keep getting changed, that all may or may not support fullscreen or at the very least require different methods to make them go fullscreen. There is a more universal approach I can attempt, but that comes with its own challenges. For now at least, your best bet would be to try to use an AHK script or the like, as you mentioned.
  15. oblivioncth
    To clarify, is this something extra you're asking for? Or is the game full screen when started from the FL launcher? Also try hitting Alt+Enter while the window is active.
  16. oblivioncth
    Sorry I missed this. Right now I'm in the middle of overhauling the tool internally, but for the time being it should work fine with the latest Flashpoint. What you want to do is add all of the games you want to a playlist like you said, then in the tool make sure no Platforms are selected, select the Playlist you made, and then set the Playlist Game mode to Force All. This will cause the tool to only import portions of each playlist as required so that the game's in the playlist are available without anything else being grabbed.
  17. oblivioncth
    Exactly, the playlist is literally your FP favorites that starts empty by default and is there for you to fill in. It sounds like all is well then. Thanks for testing it.
  18. oblivioncth
    Fixed. The problem was those playlists both have leading spaces (annoyingly, and likely an accident) in Flashpoint. This isn't allowed for filenames on Windows, and so what would happen is that my tool was configured to save the name with the space, but the OS would automatically remove it. Then later when it checks for existing playlists it makes the comparison expecting the space to be there, because it knows nothing about the removal, and so it doesn't see it as the same given the small, but significant difference. I changed my filename handling so that it considers filenames with leading/trailing spaces to be invalid and therefore accounts for their removal during comparison (as well as removing them itself when saving the playlists for the first time). I also got lucky and happened to discover a bug that can cause a crash if you input the wrong Flashpoint folder so that was a nice catch to fix. To be a little less lazy, and not flood my repo with slightly different releases, try this one out before I christen it officially: https://www.mediafire.com/file/7nfh203dgwg21ec/OFILb_0.4.1.3_test.zip/file Also for the favorite playlist, make sure you actually have favorites set within Flashpoint or else it won't import anything regardless XD.
  19. oblivioncth
    Alright, give it a roll.
  20. oblivioncth
    It's likely due to two reasons. 1) 10.1 was updated three times (the third was rescinded) after release, with the most current available being 10.1.0.3. On the site right below the torrent link is a statement and link to the patch you need to update Ultimate to that version. The statement makes it sound like that if you downloaded the torrent more recently that you're already fine as the torrent was updated to include the patch; however, this isn't actually the case and I have notified the team that the torrent is still the original release and that the statement is misleading (plus it turns out someone else there already noticed the issue and they're just waiting for it to travel down the pipeline to be fixed). So tl;dr make sure you apply that patch. 2) This is the first version where the checksum (in this case, used as an identifier) for the FP launcher has differed between Ultimate and Infinity. Because I wasn't aware of this right away the checksum that both are checked against is only Infinity's, which of course will make Ultimate 10.1.0.3 always be seen as a "mismatch". I have rectified this for the next build. There is now another issue where it seems like a recent release of LaunchBox may have changed how images are handled, or something weird is just going on, because LB is ignoring the imported images now for me. Otherwise though the original issue has been totally fixed. Edit: Nvm, starting with a fresh LB installed fixed the issue. Must have just accidentally broke something (which is likely with some of how I do some testing).
  21. oblivioncth
    Yea, that is roughly what I was planning on doing (though nice call on the "and others"), but I decided to just make the whole thing a Custom Field. My concerns about it from the past only were an issue with a much older version of the code base and don't really pose a problem (other than a little bit for a future idea I have, but whatver I'll cross that bridge then) currently. Haven't had much time to do it but it will work and is partially complete.
  22. oblivioncth
    This is my ideal plan, but it's a tad annoying because if I remember correctly Custom Fields are stored in a separate file and are not part of the platform XML itself. In the end it's not a huge deal but it does require a little more work, though I glanced at using them before and thought I remembered another reason I decided to avoid using them, which is why I was mentioning just truncating the field. Either way I'll check them first before resorting to just cutting the field off.
  23. oblivioncth
    I sort of knew this already when you posted, but wanted to do some preliminary investigation just to make sure I wasn't being dumb, but the root of the issue is that one (or more) games in 10.1 have a ridiculously long Language field (which becomes Region for LB) and for whatever reason LB feels the need to create sub-folders in the Image directory that cover all regions you have games for within a given platform, even if there are no images that need to go in those sub-folders yet. The tool doesn't use those folders at all, they get generated on start of LB after an import, which then causes this path length issue. Ultimately it would be nice for Jason to enable long-path support with LB, though since it requires enabling a specific setting within Windows for the end-user it isn't the most user friendly anyway. As far as I can tell there is no way to disable this behavior, and even if you could it would probably be global and not per-platform. Since the languages a game covers isn't the most critical information, I will likely just set an arbitrary limit to how long the Region field can be and truncate it at that point. That or do something else with the original language field. I prefer to leave as much metadata untouched as possible since that's more proper, but obviously I can't just leave it as is.
  24. oblivioncth
    More information about ""
    It's because there was an issue with the initial release and so they pushed a sma update to the site. It's still marked as 10.1 but the checksum of the launcher is different. I didn't really think about updating it since it will still work, but whatver I mind as well to avoid confusion. The issue with the playlists is that the tool only knows for sure that one of your LaunchBox playlists came from Flashpoint if it sees that Flashpoint has the same playlist. When they change the playlist name, in a pure vacuum with no further content, there's technically no way to tell if the old playlist was a past Flashpoint playlist, or a completely unrelated playlist you made yourself. I could do something like including a list of all playlist names that FP has ever had within the tool and have it remove any on that list that it sees are no longer in the current version; however, this isn't perfect. While not the most likely, it's still conceivable that they could remove a more generically named playlist like "Daily Distractions", which would get added to the list, and then a new user who happens to have a playlist already named that goes to import FP and has that playlist deleted. Perhaps there could be a confirmation dialogue or something like that, but basically I had left this issue alone until I found a solution I felt was effect, but also had no risk of unintentionally deleting user content, since that would be well... bad. It is still something I do wish to improve. EDIT: The update taking into account the small change in version number due to the FP patches (again no functional differences so your import is fine) is live.
  25. oblivioncth
    I'm glad you figured it out, though I'm slightly confused by the exact order of events (just trying to make sure my tool isn't somehow responsible). Are you saying you did an initial test with the importer with only a small selection, removed the modified files, and then tried to import again with the whole thing and it failed? Then it worked again after you moved the files created by the test back? Just trying to ascertain the steps you took.
×
×
  • Create New...