Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    3,942
  • Joined

  • Last visited

  • Days Won

    13

C-Beats last won the day on January 30

C-Beats had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

C-Beats's Achievements

128-Bit Self Aware

128-Bit Self Aware (7/7)

1.2k

Reputation

  1. Hmm, you're right. I may be remembering things wrong then, I was thinking that tool would move files as well.
  2. The tool has an option that MOVES the file, not COPIES and so the only thing left would be the orphan files. Then you can do what you wanted with them and move the other files back. Agree it's a bit long-winded but gets you where you're wanting.
  3. If you have a premium license (required to use custom themes) you can use the Omni theme. When you hide the sidebar in the you still have a combo box at the top of the theme that lets you change sidebar filter. Should allow you to do what you're asking to do.
  4. @Fursphere Folders are added for you so that users know where to put the files. Otherwise they'd have to know our naming convention and potentially stop and think what we use. It also is a good way to show which systems that feature works on since it doesn't work on all the platforms in our DB. As @Alfie Wilmott stated, if you turn off the feature we delete those folders for you. You can still use the manual Scan for Added games tools from that point on if you need to sync a folder like the new system does. It's just more manual/granular.
  5. Alternatively you could use the menu option in the Tools > File Management menu that moves files for you. Select all the games in that platform, and then use the tool to move those rom files to a different folder, games left over are your orphan files. Though it IS possible those files WERE imported, but were combined into additional apps. I'd run an audit of the platform and then sort by the Additional apps column and see if any of the files got placed under a parent game.
  6. I use x360ce personally on my cab to help with this. Pretty easy to set up and can set up per app configurations. That being said I've not verified lately how nasty it is to use keyboard inputs with it, I was thinking it could but it's been a long while since I've tried.
  7. Where are you seeing this error? Steam website or in LB somewhere?
  8. I know it sounds like I'm being facetious but the following is always a good starting point? Have you verified the monitor is plugged in? Is it on? Can you press the monitor buttons to open and see the menu? If not the monitor is broken (assuming the answer to the two above is yes). Can you try a different port on your computer? Can you try a different chord?
  9. Can you look in \\LaunchBox\Logs and see if there is a file in there from when you experienced the issue that could be used to help assess the situation?
  10. How? What I'm referring to is the actual WPF functionality that processes mouse input. Even a mouse virtualized via RDP or apps calling Win32 still go through that same call stack. Best way to confirm it's not that is attempting to rotate the box with an attached controller. LB Options set to only accept input from that specific controller (not the "All Controllers" option) and then use that controller to rotate the box. If the box doesn't stutter during that test it's likely caused by the input code or some interaction with it.
  11. Feature is using WPF's built in 3D modeling solutions which (when possible) leverages DirectX. CEF isn't used at all in this process. I'd imagine the issue is from how the mouse interacts with the control on the device and one of the mouse events isn't making it through do to a priority call in the CPU/UI events. Would also explain why using the controller doesn't have the same issue since at that point the WPF input processing is removed from the equation entirely. Unfortunately because of that there may not be a ton we can do. We can't change how WPF operates and potentially culls events.
  12. Issue you're going to run into is that simply rotating everything just doesn't really work. To make that horizontal gameplay fill the screen you'd either need to stretch the window (would look horrible) OR zoom in on the playfield (and lose sight on a LOT of the left/right play field. My use case rotating worked because the video was just a virtual pinball playfield where the entire playfield was in the 16:9 frame, so I just had to rotate it 90deg. You can't really do that with most videos/gameplay.
  13. Glad you got it. What wound up to be the issue? Letting people know could potentially help some one in the future if they run into the same thing.
  14. If you disable the auto-rom import feature those empty folders are removed and won't be created on startup (if you're referring to the folders for platforms you haven't actually imported).
  15. It's been quite some time since I built the theme, but as I recall FauxVert DOES play video. That being said you're right in that the video's need prepped. I had a script I ran via a video editor and did all mine in bulk, it wasn't a manual process at all. I didn't ultimately use that theme and just use portrait mode on my vert cab. I don't have any Steam games that don't play in TATE mode on that cab and so haven't really ran into too many issues. Most emulated titles that aren't vertical just use a bezel I found online to fill the dead space in the screen.
×
×
  • Create New...