shadowfire36

I’ve been troubleshooting an ongoing video transition/loading issue in the Unified Refried theme in Big Box, specifically with Steam. All other platform wheels appear to work fine; Steam is the only platform giving me this issue. Steam wheel videos appear to have a bad loading or transition behavior that does not happen the same way on other platforms. I chose Nintendo 64 as my comparison platform because its wheel behaves correctly and gives me a known-good reference to compare against. Known-good reference set The Nintendo 64 video set has been my reference point because those videos do not show the same loading/transition issue. When I checked them with ffmpeg/ffprobe, the N64 files were typically closer to: H.264 / AVC 640x480 4:3 59.94 fps AAC 48 kHz stereo That became the benchmark I was comparing the Steam set against. First Steam rebuild method used The first rebuild method I used for the Steam videos was a yt-dlp + ffmpeg workflow that downloaded gameplay clips from YouTube-based search results and cut out a section from each video. The workflow was: search by game title + gameplay/no commentary use yt-dlp primary format selector: best[ext=mp4]/best fallback format selector: bv*+ba/b merge output as MP4 cut only a section of the source video instead of downloading the whole thing output to a separate ready-for-LaunchBox folder first The clip timing logic I used in that workflow was: if the source video was under 5 minutes, clip from 00:02:00 to 00:02:30 if the source video was 5 minutes or longer, clip from 00:05:00 to 00:05:30 So the first rebuilt Steam set was being made from: yt-dlp search/download YouTube-based source matching section cutting MP4 merge Even after that first rebuild, many of the Steam files still did not match the Nintendo 64 set closely. Steam files in that set were commonly things like: 640x360 around 30 fps mixed H.264 profiles/levels mixed container metadata mixed audio/sample rate behavior So although I rebuilt the videos, the first rebuilt Steam set was still inconsistent compared to the N64 reference set and was still a likely cause of the glitching/loading issue. Second pass / second method used After that, I moved the original Steam videos out to: C:\Program Files\LaunchBox\Videos\Steam_Originals The second pass was focused on rebuilding/retesting the Steam set against the N64 reference and checking whether the files themselves were the problem. On this pass, I was no longer just treating the issue as missing videos. I was specifically comparing the Steam outputs to the N64 outputs and checking: encoding differences frame rate differences aspect ratio differences possible corrupt/glitch behavior whether the first few seconds of the Steam clips were part of the issue I also tested the idea that the front of the Steam clips might be the problem, because some of the Steam videos appeared to have bad startup behavior before they displayed correctly. That led to the idea of making a third set by trimming the first 10 seconds off the originals. I also tested ARRM as a replacement workflow, but it only reliably pulled images, not videos, so it was not a valid solution for the Steam video snap issue. So in practical terms, the methods I’ve used on the video side were: Method 1 yt-dlp + section-cut workflow yt-dlp search download gameplay/no commentary source best[ext=mp4]/best first bv*+ba/b fallback merge to MP4 clip from either 2:00 or 5:00 depending on total duration Method 2 rebuilt/retested Steam set against N64 reference moved originals to Steam_Originals compared outputs with ffmpeg/ffprobe checked whether the files themselves were causing the problem investigated trimming the first 10 seconds from the front of each original as another test path Media-side findings The media-side findings so far are: the original Steam set was inconsistent the first rebuilt Steam set created with yt-dlp section-cut logic was also inconsistent relative to the N64 set the N64 set remained the known-good reference some Steam videos may also have startup/glitch issues in the first several seconds So on the media side alone, I still have reason to believe the Steam files themselves are at least part of the problem. What I checked in the Unified Refried theme On the theme side, I searched the relevant XAML files for transition and animation behavior, including: ImageVideoTransitionSelector TransitionPresenter Storyboard BeginTime Duration FlowControl DiscImage Blackscreen VideoBlackScreenImage StretchVideo Panel.ZIndex I compared these files between Nintendo 64 and Steam: WheelGamesView\Nintendo 64.xaml vs WheelGamesView\Steam.xaml Wheel2GamesView\Nintendo 64.xaml vs Wheel2GamesView\Steam.xaml Wheel3GamesView\Nintendo 64.xaml vs Wheel3GamesView\Steam.xaml Wheel4GamesView\Nintendo 64.xaml vs Wheel4GamesView\Steam.xaml XAML comparison results WheelGamesView Steam and Nintendo 64 were effectively the same except for art paths. I did not find any meaningful transition difference there. Wheel4GamesView Steam and Nintendo 64 were also effectively the same. I did not find any meaningful transition difference there either. Wheel2GamesView Steam had extra DiscImage rotation animation lines that Nintendo 64 did not have. Wheel3GamesView Steam also had extra DiscImage rotation animation lines that Nintendo 64 did not have. Those extra Steam-only lines were: <DoubleAnimation Storyboard.TargetName="DiscImage" Storyboard.TargetProperty="(UIElement.RenderTransform).(TransformGroup.Children)[1].(RotateTransform.Angle)" From="0" To="0" BeginTime="00:00:0" Duration="00:00:00.001" /> <DoubleAnimation Storyboard.TargetName="DiscImage" Storyboard.TargetProperty="(UIElement.RenderTransform).(TransformGroup.Children)[1].(RotateTransform.Angle)" From="0" To="360" BeginTime="00:00:2" Duration="00:00:5.000" RepeatBehavior="Forever" /> At this point, the only actual behavior difference I found between the working Nintendo 64 setup and the problematic Steam setup inside Unified Refried was the extra DiscImage rotation animation in: Wheel2GamesView\Steam.xaml Wheel3GamesView\Steam.xaml That makes those two Steam XAML files the strongest suspects on the theme side. I also created PowerShell commands to back up the Steam wheel files and remove the DiscImage rotation lines automatically from those two files. I also verified that WheelGamesView and Wheel4GamesView did not show meaningful transition differences versus Nintendo 64. Best summary After checking both the media files and the XAML theme files, the strongest theme-side issue I found so far is that Steam has extra DiscImage rotation animations in Wheel2GamesView and Wheel3GamesView that Nintendo 64 does not have. At the same time, the Steam video set itself has also been inconsistent. My first rebuild method used a yt-dlp section-cut workflow with MP4 merging and 2:00 / 5:00 start logic depending on source duration, but that rebuilt set still did not naturally match the N64 reference style. On the second pass, I moved the originals out, compared the Steam outputs directly against the N64 outputs, and started investigating whether the startup section of the Steam clips themselves was part of the issue. So at this point, the issue may be a combination of: inconsistent Steam video files and encoding/output behavior Steam-specific Wheel2GamesView / Wheel3GamesView theme behavior in Unified Refried Environment / device This is being tested on LaunchBox 13.26 on an ROG Ally X (Xbox version). Because this is a handheld setup and not a desktop PC, I’m also trying to determine whether the issue is being influenced by the device itself, video decoding behavior, or performance differences when Steam videos load compared to Nintendo 64.

I used Emusync its a lot easier to do it manually EmuMovies Sync - EmuMovies

UPDATE: This is a complete modernization of a guide I originally wrote 10 years ago. With VMware Workstation Pro now being free for personal use and VirtualBox being more robust, we can use advanced virtualization features to seamlessly integrate broken legacy games (Gingerbread/Lollipop era) into a modern LaunchBox setup. This guide will show you how to use a "Time Capsule" Virtual Machine to play games that crash on modern emulators (like Zenonia 1-3) and launch them with a single click from LaunchBox. The Core Concept We are creating a "Russian Nesting Doll" to bypass modern compatibility issues: Host PC (LaunchBox) -> VM (Windows 7 Guest) -> BlueStacks 0.8 -> Game By using Unity Mode (VMware) or Seamless Mode (VirtualBox), the Guest Windows OS disappears, and the Android emulator window floats on your real desktop. LaunchBox treats it like a standard Windows game, but inside, it is running a perfect Android 2.3 environment. Part 1: Prerequisites Software (Choose One Virtualization Platform): Option A: VMware Workstation Pro (Free for personal use from Broadcom). Option B: Oracle VirtualBox (Free Open Source). Required Files: Windows ISO: A copy of Windows 7 is recommended (lower RAM usage), but Windows 10 works. BlueStacks 0.8.0: The specific "Gingerbread" era installer. Search for BlueStacks_App_Player_0.8.0.2997.msi or "BlueStacks 0.8.0 XDA". LaunchBox: Your front-end on your main PC. Hardware: At least 8GB RAM on the Host PC. 30GB Free Hard Drive space. Part 2: Building the VM 📝 NOTE: This guide assumes you have a basic understanding of how to set up a Virtual Machine and install Windows. I will not go into extreme detail on the OS installation process as there are countless tutorials on YouTube. If you are brand new to virtualization, please search YouTube for "How to install Windows 7 in VMware" (or VirtualBox) before proceeding. Option A: VMware Workstation Pro (Recommended) Create VM: Open VMware -> Create a New Virtual Machine -> Select your Windows ISO. Specs: Click "Customize Hardware". Memory: Assign 4GB. Processors: Assign 2 cores. Display: Check "Accelerate 3D Graphics". Install: Finish the wizard and install Windows. Install VMware Tools (CRITICAL): Once Windows boots: Menu VM -> Install VMware Tools. Run the installer inside the Guest VM and Reboot. Unity Mode will NOT work without this. Option B: Oracle VirtualBox Create VM: Open VBox -> New -> Type: Windows 7 -> Select ISO. Specs: Base Memory: 4096 MB (4GB). Display: Check "Enable 3D Acceleration" and max out Video Memory (128MB or 256MB). Install: Finish the wizard and install Windows. Install Guest Additions (CRITICAL): Once Windows boots: Menu Devices -> Insert Guest Additions CD image. Run the installer inside the Guest VM and Reboot. Seamless Mode will NOT work without this. Part 3: Setting Up the "Time Capsule" (Identical for Both) Perform these steps inside your new Windows Virtual Machine. Install BlueStacks: Drag the 0.8.0 installer from your PC into the VM window and install it. Disable Auto-Update (VITAL): Inside the VM, press Win + R, type services.msc. Find BlueStacks Updater Service. Right-click -> Properties -> Startup type: Disabled. Click Stop. Install Games: Drag your .apk files into the VM and install them. Create Shortcuts: Ensure your game shortcuts (e.g., Zenonia icon) are visible on the Guest Windows Desktop inside the VM. Part 4: The Integration Strategy Here is where the two methods differ. Follow the section for your software. Option A: VMware Integration (Batch Script Method) 1. Gather Your Paths: Copy these paths to a Notepad file to prepare them: Path to vmrun: "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" Path to your VM file (.vmx): "C:\Users\YOUR_NAME\Documents\Virtual Machines\Gingerbread\Gingerbread.vmx" Path to Game Shortcut: Enter Unity Mode (Ctrl+Shift+U). Right-click your game in the VMware menu -> "Create Shortcut on Desktop". You will need the path to this specific .lnk file for the script below. 2. Create the Script (Template): Create a new text file (e.g., Launch-GameName.bat) and paste the code below. ⚠️ IMPORTANT: You must create a separate batch file for each game you want to add to LaunchBox (e.g., Launch-Zenonia1.bat, Launch-Zenonia2.bat). You must edit the GAME_SHORTCUT line in each file to point to that specific game's shortcut. batch @echo off :: CONFIGURATION :: Set the path to the vmrun.exe tool (Standard location below) SET VMRUN="C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" :: Set the path to your Virtual Machine file (.vmx) SET VM_PATH="C:\Users\YOUR_USERNAME\Documents\Virtual Machines\Gingerbread\Gingerbread.vmx" :: !!! CHANGE THIS FOR EACH GAME !!! :: Set the path to the specific Game Shortcut (.lnk) you created on your desktop SET GAME_SHORTCUT="C:\Users\YOUR_USERNAME\Desktop\NAME_OF_GAME.lnk" :: EXECUTION :: Ensure VM is running (starts it silently if off) %VMRUN% -T workstation start %VM_PATH% nogui :: Wait 5 seconds for VM to be ready timeout /t 5 /nobreak >nul :: Launch the specific game shortcut start "" %GAME_SHORTCUT% exit Option B: VirtualBox Integration (Shared Folder Method) VirtualBox does not export shortcuts easily, so we use a Shared Folder workaround. 1. Create a Shared Folder: Create a folder on your Real PC (Host) named C:\RetroShortcuts. In VirtualBox Settings -> Shared Folders -> Add C:\RetroShortcuts. Check Auto-mount and Make Permanent. 2. Move the Shortcut: Inside the VM, drag the Game Shortcut from the Guest Desktop into that Shared Folder (Drive Z: or similar). Result: The .lnk file is now visible on your Real PC in C:\RetroShortcuts. 3. Enter Seamless Mode: Press Host Key + L (Default Host Key is Right Ctrl). The Guest desktop vanishes, leaving only the BlueStacks window floating. Leave the VM running like this. Part 5: Adding to LaunchBox Open LaunchBox. Import: Drag and drop your file: VMware Users: Drag your Launch-Zenonia.bat. VirtualBox Users: Drag the shortcut .lnk file from C:\RetroShortcuts. Select "None of the above" (Import as a standard application). Platform: Select Windows. Metadata: Manually search for "Zenonia" (or your game name) to get the correct box art. Clean Up: Right-click the game in LaunchBox -> Edit -> Launching tab -> Check "Hide Console" (for Batch files). Part 6: Controller Support & Troubleshooting Controller Support: BlueStacks 0.8.0 has no native gamepad support. You must use a key-mapper. Recommended Tools: AntiMicroX (Free/Open Source - Highly Recommended) JoyToKey (Free Shareware) Pinnacle Game Profiler (Legacy favorite) Setup: Install one of these tools. (You can install it on your Host PC for easier management, or inside the Guest VM if you want the controller profile to travel with the VM). Run the software as Administrator (Required to send commands into a VM). Mapping: Map your controller buttons to the keyboard keys the game uses (e.g., D-Pad to Arrow Keys, A Button to Z Key). Zenonia Note: The Backspace key often acts as the "Menu" button in old Android games. Map a spare controller button (like Select/Back) to Backspace to access inventory and save menus. Troubleshooting: Black Screen: If the Unity/Seamless window is black, go to BlueStacks Settings (inside the VM) and change the Graphics Mode (OpenGL vs DirectX) or increase Video Memory in the VM settings. VM Freezing: For faster launches, never "Shut Down" the VM. Just "Suspend" (VMware) or "Save State" (VirtualBox). The script/shortcut will wake it up instantly.

i updated to the latest Retroarch 1.20 and LB 13.18. I'm not sure what changed but i cant seem to launch my NEO-GEO set with final burn alpha 2012 core . I went to the retroarch settings and double checked the settings they still look correct SNK NEO GEO MVS core= fbalpha2012_libretro, default emulator checked , extract roms = unchecked SNK NEO GEO AES core= fbalpha2012_libretro, default emulator checked , extract roms = unchecked I went and installed a separate retroarch with only the fbalpha2012_libreto.dll core and it works , but i didnt want to have 2 separate emulators t runnning . If any one has the time i could use some advise on what to check to get this corrected

thank you kind sirs appreciate the help

I have had this software since like 2016.. give me a little credit on i know how to use and not as a noob I know how to import roms , im telling i went through the wizard and that how it came out i didnt import one rom , these are things that have JUST started since my last update .. thats why i posted things have been a little unusual minor things happening I have never imported to all .. these has been a weird update fellas

no i cant right click there are no options to make changes , i added a dreamcast rom last night and the all Icon changed to dreamcast

i didnt have an .xml in there with "all"that was the 1st thing i checked , which i thought was weird

its greyed out , i cant make any changes to either categories, there are not any options to edit or delete

it removed one if i uncheck it , if i re-enable its adds one back

Not sure why this update did this, but i now have two categories for under platform "All" ... anyone know how to remove this double entry ? I looked the .xml flies cant seem to find anything to remove

that did it ty

its a specially modded version that allows naruto ninja 4 to be played in English it does not have a version build number

I recently updated my Launchbox to 13.16 . Now that i have I am getting an error message from dolphin emulator stating "Unknown long option 'version'" Im not sure what changed but I cant seem to get rid of this error message from opening on launch box

I have been trying to write a .bat to convert .7z files to .CHD.. it sort of works i can get the zip files to drop the .7z files into .ISO's , but thats it.. it doesnt seem to convert the other part of the .bat which is to change them to a .CHD can anyone take a look and see what im doing wrong in this ?? ------------------------------------------------------------------------------------------------- @echo off setlocal enabledelayedexpansion for %%i in (*.zip *.7z *.rar) do ( "C:\Program Files\7-Zip\7z.exe" x "%%i" if errorlevel 1 goto fail del "%%i" ) for %%f in (*.cue *.gdi *.iso) do ( chdman createcd -f "%%i" -o "%%~nf.chd" if errorlevel 1 goto fail del "%%f" del *.bin del *.cue ) echo Done! goto :end :fail echo Error! Stopped :end -----------------------------------------------------------------------------------------------------

I got them from " The internet archive " search there. then go in the system folder for retroarch and place it there

wouldnt it make more sense to be able to copy over an already built setup from a windows machine to copy it over with the dll's?

@Jason Carr so i was wondering would it be possible to run big box using photon ? I have seen tutorials where people are running the windows install for PSN the steam by adding some .dll to the directory. I was thinking is it possible to possibly to the same for launchbox ?

bump

I have my big box setup to run thru steam-link , but when ever i run standards Windows pc games The controls do not seem to work for that game. So for example I have Samurai Shodown i can use the XB1 controllers to navigate through Big box menu and select the game , once it switches to the game it looks like it defaults to keyboard input only ..there a way to change this so i can keep my xb1 controllers on the remote machine ? ?

this is my setup hope it helps, i have switched to flycast works a lot better these in the retroarch than demul

since i updated last week , i keep getting this error when i try to scroll thru my tools>manage>platforms this is the message i get and its reboots my pc, any suggestions Dispatcher processing has been suspended, but messages are still being processed. App: LaunchBox Version: 12.13 Type: System.InvalidOperationException Site: IntPtr WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) Source: WindowsBase at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 11:06:21 PM Exception

Thanks ,, that did it !

do you know how i can get this core ? i cant find an older core release anywhere .. i have never installed the core until recently