Jump to content
LaunchBox Community Forums

PadeMoNiuM Prods

Members
  • Posts

    324
  • Joined

  • Last visited

  • Days Won

    2

PadeMoNiuM Prods last won the day on June 2

PadeMoNiuM Prods had the most liked content!

Recent Profile Visitors

13485 profile views

PadeMoNiuM Prods's Achievements

32-Bit GPU

32-Bit GPU (5/7)

294

Reputation

  1. Version 2.0.0

    27 downloads

    The Legend of Zelda Ocarina of Time.mp4
  2. Good to know, thanks Donell! Anyway, I wasn't planning on seriously playing these games just yet. It's mostly my daughters who play them, so I'll wait until they're properly emulated. But honestly, the progress they've made in just one week is absolutely insane! It's almost scary how fast things are moving! So I've already started working on my Switch 2 system I've got my intro ready, a few icons done, and now I'm going to start creating the views. It's not easy coming up with a good visual direction for the Switch 2, but hey, it's always exciting to add a new platform to the collection!
  3. You’ve probably already seen it in the news, but a new Nintendo Switch 2 emulator called Eglantine has just been released. I tested it last night, and to my great surprise, it actually runs incredibly well! Of course, it's not perfect yet. We're not hitting 120 FPS, some graphical elements are still disappearing, and there are a few bugs left to fix. But the crazy part is that it actually runs, and pretty damn well! Honestly, seeing this much progress in such a short time is absolutely mind-blowing. And it looks like this is only the beginning! I wouldn't be surprised if Zelda is next on the list, and sooner rather than later. These guys are absolute barbarian! Things are moving fast!
  4. Version 1.0.0

    21 downloads

    Onimusha Way of The Sword.mp4 All my content Here : https://forums.launchbox-app.com/profile/244237-pademonium-prods/content/?type=downloads_file
  5. Ah yeah, I see what you mean if you prefer to choose which version to use. But personally, I think the recompiled versions will often be the best ones. Just look at how God of War runs. It's absolutely insane! I've never seen it run so smoothly. And we're still in the early days of recompilation. Technically, it's already incredibly impressive. Just imagine what things will look like in a few years! Apart from some particularly well-optimized PC ports, I think it'll be pretty hard to beat.But hey, everyone has their own preferences! For me, it's mainly about consistency and keeping things simple. If you start creating specific icons for recompiled games, you'll also need to create the corresponding playlists: PS2 Recompiled, PS4 Recompiled, Xbox Recompiled, etc. And since recompilation is starting to expand across more and more platforms, you might eventually end up duplicating a huge part of your library!That means new playlists, new icons, more media... And if we take that logic even further, why not create separate icons for every emulator too? It never ends! ^^ By the way, when it comes to launching games, you should normally be able to create desktop shortcuts directly from Quiver, just like with Yuzu. If I remember correctly, you just right-click on the game's icon and there should be an option to create a shortcut. I'm not 100% sure about the exact steps, though, so you'll have to check. That way, you can launch your recompiled games directly without having to go through the Quiver interface every time.
    I love it! It's great to see you working on platforms other than PC and Switch! Your themes are always so consistent and polished. The choice of images, the tabs, the little intro sequence, the references to the original box art, the official logo… Everything is there! Seriously, nothing to complain about. You can really see the amount of work and attention to detail that goes into these themes. Awesome job, man! And of course, I already stole them from you! ^^
  6. Personally, I decided not to create a specific icon for recompilations. If you follow that logic, you'd also need an icon for every emulator, like Yuzu, RPCS3, etc. And honestly, with the crazy number of PS4 recompilation projects popping up lately, you might end up with a massive second PS4 playlist that basically duplicates your existing one. At this rate, I wonder if it's really worth it. That's a lot of extra work for very little benefit.I prefer to integrate games directly into their original platforms. A recompiled PS4 game stays in my PS4 category. Everything is seamless: you select your game, launch it, and don't have to worry about the technology running behind the scenes. That said, it's a really good idea! Just keep in mind that if you want to stay consistent with everything else, you might end up creating a lot more work for yourselves down the road.
  7. Version 1.0.0

    14 downloads

    Since I was in the neighborhood, I'm dropping off a little Game theme for you. Gears of War Eday-1.mp4
  8. I love your playlist ! 😉
  9. ZE UL.mp4 Sorry about last night, but I was absolutely wiped out.😴 I made a new comparison video to definitively clarify the behavior of Box - Full. Small clarification regarding the comparison videos, because my previous wording was ambiguous: My first test was done entirely on the NES platform. This new test is different. I am comparing the standalone Zelda Ultima version running on LaunchBox 13.19 with the current Zelda Ultima version integrated into my up-to-date Nostalgic Bedroom custom theme running on the current LaunchBox version. (14.00) So the purpose of this new comparison is not to compare two different collections, but to compare the same Zelda Ultima content across two very different LaunchBox generations and two different stages of my theme setup. The important point is that the Box - Full workflow itself is being compared between an older LaunchBox version where it worked correctly and the current version where the 3D result is different. At this point, one thing is now established: Box - Full is indeed an existing LaunchBox feature designed to build a 3D box from a single complete unfolded cover image when separate Front, Spine and Back images are not being used. That is exactly why I have been using this feature for years across NES, Switch, PlayStation 2, PlayStation 3 and several other systems. A single image already contains the front, spine and back. Instead of preparing three separate media files for every game, you prepare one image and LaunchBox builds the 3D box from it. I completely understand that using three separate images is technically easier for the 3D engine, since LaunchBox does not need to calculate where the front, spine and back begin and end within the full image. But if the Box - Full → 3D box system exists, worked correctly before, and now produces a different result with the same media, it is still worth understanding what changed. And this also raises a broader question: why not promote this feature more? The potential time savings are considerable, not only for me but for the whole community. Today, Front, Spine and Back media are often prepared and published separately. Yet when a good-quality Full scan already exists, all of that information is already contained in a single file. If Box - Full could become a reliable and more widely used source for 3D boxes, it could greatly reduce redundant work: fewer files to prepare, fewer separate media assets to publish and maintain, fewer Front/Spine/Back posts, and a lot of time saved for contributors as well as the team. In the future, LaunchBox could even use the Full image as the main source media and automatically derive the individual faces whenever they are needed elsewhere. That is why I would find it unfortunate for this feature to become secondary simply because it appears to be rarely used. In my opinion, it is actually one of the most useful features of the 3D system. And above all, it could greatly simplify the way box artwork is organized. Today, there can be separate POSTS for Front, Spine and Back, even though in practice some contributors already publish several of them together. But if a single Box - Full image already contains everything required to reconstruct the 3D box, that immediately reduces the number of media assets that need to be managed. Instead of maintaining three files or three separate categories for the same physical cover, you can have one complete source. That simplifies contributions, reduces duplication, makes media organization easier, and saves a huge amount of time for both contributors and users. Even without completely removing separate Front, Spine and Back images, making Box - Full a more central source could already optimize the workflow considerably. There may be an existing feature here that actually deserves to be used much more.
  10. Sorry, I’m going to get some sleep now. It’s late here in France and I’m exhausted after a long day. If you want to test it on your side, the important thing is to temporarily remove the separate Box - Front, Box - Back and Box - Spine images for the test game, and leave only the Box - Full image. If LaunchBox then builds a proper 3D box from that single Full image, then the feature is working correctly on your setup. If you have access to a 13.26 installation, you can also run exactly the same test there. On 13.26, that single Box - Full image should wrap correctly around the 3D model. **One important detail for the test: please temporarily remove the separate Box - Front, Box - Back and Box - Spine images for that game and leave only the Box - Full image. In my setup I was using the image priority settings, so simply changing the priority can still leave some ambiguity about which artwork LaunchBox is actually using. The cleanest test is therefore to give LaunchBox no alternative: one game, one Box - Full image, and no separate Front, Back or Spine. If that single Full image produces a correctly wrapped 3D box, then it works on your setup. If you can repeat the exact same test on 13.26, it should also show the old working behaviour. I’ll check back tomorrow. Thanks for testing it.
  11. Don't hesitate if needed.I can do you a demo of the Launch Box /Big Box on the 13.26 compared to today to show you the difference.
  12. @MysterNybble Front image priorities = Image in win explorer = image in the media of the game=
  13. @MysterNybbleOf course ! Thx.
  14. @MysterNybble Hi, Just to clarify one important point: this was really the whole advantage of using Box - Full images in the first place. Up to version 13.26, you could take a single unfolded full cover containing the back, spine and front, place it in the appropriate Box - Full folder, and LaunchBox would automatically wrap that image around the 3D box model. That saved a huge amount of time because there was no need to manually create and separate three different images for Front, Spine and Back. In fact, I assume this was one of the main reasons the Box -😅Full image type was introduced in the first place. Otherwise, there is very little practical benefit to having a complete unfolded cover if LaunchBox cannot use it directly to construct the 3D box. Someone originally implemented this behaviour so that a Full Box image could be mapped automatically onto the 3D model, and it worked perfectly for years.Since 13.27, that behaviour appears to have been lost. The same Full Box image is still recognised, but instead of being wrapped correctly around the model, it is rendered as a long rectangular block. Using separate Front, Spine and Back images still works, but that defeats the entire purpose and convenience of the Box - Full workflow. So this is not really a request for a new feature. It is a regression of an existing feature that worked correctly up to 13.26. I’m also attaching a video of the 3D thumbnail directly from LaunchBox. vlc-record-2026-08-24-21h24m27s-Desktop 2026.08.24 - 20.48.55.01.mp4-.mp4 As you can see, it is rendered exactly the same way as it is in Big Box, with the same incorrect rectangular shape. And this is not an isolated game: it happens across the entire set. My NES collection, for example, was built using Box - Full / Full DVD images, so every game that relies on this method now shows the same problem. This also confirms that the issue is not specific to one Big Box theme or one particular view. The incorrect rendering is already present in LaunchBox’s own 3D preview.I was wondering why I hadn't received any feedback on my post, but it turns out I might be one of the few people using that optio👀😮—which actually saves a huge amount of time, because otherwise you have to set up the front, spine, and back every single time.-_- It would be a real shame to miss out on a feature that saves you so much time.
×
×
  • Create New...