Jump to content
LaunchBox Community Forums


  • Posts

  • Joined

Everything posted by Hifihedgehog

  1. Just wow. I have always been wanting a theme that meshed together the very clean and thoughtful look of Colorful with a mature, radical look of others here. There is zero clutter here and it looks stellar. Here is a thought: have you ever considered using the game clear logo in place of the game title in text? That is something I wish Colorful did. Granted, this is easily modifiable for us users thanks to the modularity of community theme builder. But I feel that using the game logo in the place of text for the game title would evoke the feeling of the game more.
  2. Respectfully, I disagree. Please refer to this article below that I shared earlier. I will take Geoffrey Morrison's advice over all the manufacturer spin and pseudoscience. As a computer engineering graduate, I can tell you that electronically, the HDMI cables themselves even during the early HDMI 1 years were already physically designed to such a high degree (shielding, conductivity, low capacitance) that they can easily cope high-speed electronic requirements of HDMI 2.0. Over the years, the differences in the HDMI specification itself have overwhelmingly occurred quite little in the cables (transmission) and far more from the HDMI interface (signal generation) in the ICs and circuit boards. Therefore, signal integrity on the cable end of the equation only really becomes an issue with long runs (~25 feet and above) or the cheap no-name Chinese manufacturers on Amazon/AliExpress who do not follow specification and cut corners.
  3. Right, but it is not good enough alone if your cable supports 4K at 60Hz. As I explained, any HDMI cable should just work unless there is an electronic issue with it. What I am asking is what your computer's video device is. Your computer may not support HDMI 2.0. That means it may not support 4K at 60Hz. That is what I am speaking about. Can you confirm what video device you have by following the steps from my last post on page 1? Thanks!
  4. Thanks. Can you run Device Manager by right clicking on the Windows' Start Menu icon? Then expand Display Adapters by hitting the plus sign. I would like to see what is in the red section there (see example). I am guessing you probably just have Intel integrated graphics (e.g. Intel UHD Graphics). The Core i7-8700 natively (that is, by default or what it comes with built into the processor) has just HDMI 1.4. That means unless your motherboard has a conversion chip, you are limited to just HDMI 1.4.
  5. A few things here. Point #1: In my experience, HDMI 2.0 works fine on lesser rated cables unless you are connecting over very long runs and it may be a problem, but even then, it shouldn't. Why? Most all HDMI 1.4 cables are already mechanically and compositionally the same as their HDMI 2.0 counterparts other than the certification testing they formally paid for. Does a cable suddenly change just because its manufacturer up and decided to pay $1000 for formalized certification? Of course, not! That means your cable should "just work" just the same an "official" HDMI 2.0 one would. Not convinced? Read the CNET article "4K HDMI cables (are nonsense)" by Geoffrey Morrison, an expert in the AV field. Don't fall for the snake oil lies that cable manufacturers spread, which is all a bunch of bunk to try to make you spend more money than you need to. That brings me to my next point. Point #2: Given point #1, we should still see a 60Hz option because the monitor and video card cannot actually detect if the cable is HDMI 2.0, 1.4, etc. The reason then the OP may not be seeing 4K at 60Hz as an available option may come down to something else in the signal chain. And if not the TV, the input device, which the OP claims supports 4K at 60Hz, then, by process of elimination, the computer, the output device. That brings me to my last point. Point #3: Before us going any further, have we confirmed that the OP's output device/graphics card actually supports 4K at 60Hz, namely that his or her computer's HDMI port is 2.0? They stated their TV supports 4K at 60Hz, meaning the TV has an HDMI 2.0 input. But the computer may not have an HDMI 2.0 output. Both the input (TV/monitor/projector) and output (computer/game console/smartphone/tablet) devices must support HDMI 2.0 for 4K at 60Hz to work. So... Out of curiosity, what graphics card are you using here? For example, your graphics card may support 4K at 60Hz but only on its DisplayPort (DP) output, not on its HDMI port.
  6. Just as a heads up, this could also end up being a problem at some point. If in doubt, try disabling Potentially unwanted app blocking in Windows Defender. Thanks, Microsoft, for enabling the new feature we did not ask for. Windows 10 begins blocking installation of "Potentially Unwanted Apps" by default this month - Liliputing
  7. I was just about to post this answer to the riddle of all this nonsense, but I am glad someone found it! In my misadventures of getting my cabinet up and running about a year ago, I encountered the same exact trouble as @Benjc did. There were two things I had to do: first, have the monitors side by side in their default positions, primary on left and secondary on right in Windows' display position; and second, both monitors had to be at the same scale factor, which in nearly all cases would be 100%. I had to have my monitors in the default position that Windows places them, meaning Display 1 (primary) has to be on the left and Display 2 (secondary) on the right with the top of Display 2 even with the top of Display 1. This defies intuition of course because ideally you would think you would want them placed top and bottom (marquee on top and main screen right below) as you would want your mouse to flow from the top of your main display to bottom of your secondary display, but nope, that's Microsoft for you. You also have to have the scale factor equal because Windows' display management is equally garbage in this regard. In my case, I have a high DPI 4K/UHD main display so just so I can keep my main display's text legible, I use a Visual Basic script to automatically toggle the scale factor to 100% until Big Box's process is closed. You might not be seeing it maybe because it is Windows 10 related or perhaps it is a new "feature" specific to later feature updates of Windows 10. I noticed it on Windows 10 May 2020 Update with either Intel (Intel Iris Xe on Microsoft Surface Pro 7+) or NVIDIA (GeForce GTX 3090) with both clean and updated installs of the operating system. Pure nonsense, I tell ya.
  8. I voted for better performance out of Big Box. Right now, it is hard getting 1080p with Colorful theme (with video backgrounds enabled) running fluidly on low-end integrated graphics like Vega 3 (like on a Ryzen R1505G) or Intel HD/UHD Graphics (with 24 EUs or less). I have to aim for 720p or even 480p in some cases just for fluid operation if I want to have video backgrounds. That is my current situation with performance enhancements from (1) Process Lasso, (2) highest performance levels in the BIOS and Windows power settings, and (3) disabling or demoting prioritization on any less critical system services.
  9. A lot has been confirmed already yesterday and contrary to some reports, most of the hardware is finalized and is not in a state of flux at this point. Valve has confirmed in multiple communications now at least two things that people are getting confused about. 1. This is--repeat--a full-fledged PC (meaning, for example, it can be installed with an alternative OS via bootable media), so you can install whatever OS and software you want. There is zip, zero, nada locked down here. So putting Linux and Windows petty rivalries aside for a brief moment, if you prefer the pure Windows experience, go ahead and install it. Or if you want a different Linux distro than the stock one from Valve, that's totally up to you too. Or stay pure with SteamOS 3.0 and add any additional software you want. 2. The SSD is 2230 M.2 NVMe slot that Valve claims is "not intended for end-user replacement" and is surrounded by an EMI and thermal shield. Let me dispel some fears here. Don't get tricked by semantics! They are saying it is not intended to be upgraded though it most certainly can with minimal effort. That way, you doubt the ease of upgrade and you jump for the highest model and they preserve the upsell. In fact, Microsoft used the same lingo to describe the Surface Pro X and Pro 7+'s serviceable SSD. In reality, on those two Surfaces, it is just ONE screw and a flex-metal housing away from removal, as you can see here. Lastly, don't let the EMI and thermal shield terminology scare you. It is in reality likely just a clam shell covering the SSD to reduce EMI radiation in order to pass FCC requirements. As seen in this video, it is probably just like the Surface Pro 7+'s EMI and thermal shield which is trivial to remove.
  10. I would also like to report that I get the same error rate as @ferretlegshad indicated on the order of 1% for a scraping session over 10,000 media items. I will add too that the error rate seems to be worse as the processing power gets less and less on the hardware. I have a Ryzen 9 5950X semi-dedicated arcade system that seems to get the least errors, followed by Surface Pro 7+ which gets a bit more, and finally my thin client portable arcade system (an HP T640, a passively cooled dual-core Ryzen R1505G mini PC) which gets the worst level of errors. Bear in mind that all these devices have a top-of-the-line Intel AX200 or AX201 wireless AX Wi-Fi cards and are connected to blazing fast 1.2 Gbps Comcast cable internet. The error rate was so bad on the T640 (on the order of greater than 90% for EmuMovies) that I tried everything to remedy the failed downloads. I tried using a VPN thinking it was an ISP issue (interestingly, though, the issue was nowhere as profound on the other two, higher powered devices) and I even tweaked resource allocation in Process Lasso to give LaunchBox and the browser subprocesses higher process and I/O priority. I got so frustrated that I finally tried the latest 11.13 beta and that finally seems to have mostly fixed the downloading issue on the T640. The caveat here is that I still get a small error rate, on the order of less than 10 errors for 10,000+ media items. My current scraping session is visible below. I am almost 2,000 media items in and only two errors have occurred so far. Contrast that with before loading the beta on the T640 where I was getting an error rate of >90%, where maybe a couple hundred media items would download and then all of the remaining items would fail repeatedly afterwards. I am glad to report that this latest beta seems to be the fix to this recent issue that popped up in the last few releases. Thanks for continuing to make me a proud and happy LaunchBox user with your ongoing support and amazing upgrades to this excellent piece of software. This is the best arcade software bar none!
  11. I'll throw out there that I am also seeing the same issues described in this thread. I'm a bit tied up this week so I won't be able to throw up a log file, but I'll try to send one over next week if it is not yet resolved.
  12. This. They are coming out August 5th. In my case, I have one already as I harvest it from a prebuilt system back in late April. As for performance, it is quite zippy. At a mere 65W, it outperforms a 125W 10700K. With that perspective, that's quite something, especially considering it also comes with a GT 1030-level integrated GPU. In the past, the 4750G that I had before already ran significantly cooler than the 2400G. The 5700G runs even cooler and faster than my 4700G. If you are doing emulation, though, I would recommend stepping up to a dedicated GPU and Ryzen 5000 series CPU. For most people, a 5800X is more than enough and will be even better than the 5700G APU, especially at Switch emulation. As for a GPU, that is currently a crapshoot unless you know how to set up a stock notifier bot. There is way too much latency with the Discord groups and the YouTube channels and you will be 15 seconds behind those who have notification bots running on their local machines. If you are up to doing some basic technical legwork, I recommend installing streetmerchant to notify you on stock changes. I was able to get an RTX 3000 series card that way from Best Buy.
  13. I will add that I have also experienced this, but I never was sure if this was a feature or a bug. This has occurred on all my LaunchBox builds since the beginning.
  14. Congratulations! I have been one of the many beneficiaries of your wide array of high-quality themes. It will be nice to see your expertise coming into play here now with an official twist.
  15. Thank you for the thorough explanation and kind clarification about the source author of this plugin. I am not personally involved in the development here, so I was operating on the assumption that theme author was implementing coding interfaces that are included in and maintained by LaunchBox. @faeran, since this is a third-party plugin and not one that LaunchBox themselves maintains, who is the author that would need to be contacted to patch this bug?
  16. Still getting the same bug with only one platform added. In this case, I only have ScummVM games added and it is giving me this madness:
  17. Will check soon. I had a similar bug when I had only one platform added.
  18. Ditto! Can you please add the latest version of ScummVM to LaunchBox? Thanks!
  19. Well, I was just adding some Freddi Fish and I stumbled on the same issue as you. You can add the following line in the [scummvm] section of the config file "epicfail_scummvm.ini" located under the relative directory "LaunchBox\ThirdParty\ScummVM".: joystick_num=0 ..., which is described here. It doesn't give you a full keyboard, but you can use your gamepad with the keyboard keys and mouse actions that does everything I need, at least. You can use the gamepad analog stick as a mouse, for example. It works well for me in testing Humungous Entertainment, but your mileage may vary.
  20. IPAC2 does not have LED outputs, so I am not quite certain why a IPAC2 is being mentioned here. You don't have to change your input method to augment your setup with dynamically lit LEDs. What you need is an LED controller and that is where something like the PacLED64 comes into play. LEDBlinky doesn't care so much about the protocol of your controls (when I say protocol, I am speaking of the language your controllers speak in), be it keyboard-based or DirectInput/XInput-based (two protocols for game controllers). What LEDBlinky needs is a compatible LED controller. Then, when you are assigning each of the numbered LED strands in LEDBlinky, you map them to either keyboard keys or the button numbers of each of your player controls. Then when it interfaces with BigBox/LaunchBox, it knows to light up LED 1 for button 1, LED 2 for button 2, and so on. Plus, you can convert any keyboard or DirectInput-based controller to XInput anyway with x360ce version 4.x in combination with WhiteKnight. That's pretty much the long and short of it.
  21. I am going off on a limb, but it sounds like the joystick was installed backwards which is why the axes are reversed. So up is down and right is left and so on. So I believe MAME lets you assign input for each direction, but RetroArch only detects input for the axe and doesn't let you reverse the direction it detects. So you have a number of options, assuming it is what I think it is: (1) reverse the joysticks by physically uninstalling them, turning them 180 degrees from their current orientation and reinstalling them; (2) switch around the leads between up and down and left and right (EDIT: I see you are using zero delay boards, so this method is preferred over method 2); or (3) passing through the inputs to virtually instantiated controllers in x360ce and fixing it all virtually. And as to method 3, see my response elsewhere to you in a different thread about x360ce as you would also need to set up WhiteKnight to hide the physical controllers to eliminate duplicate or ghost inputs from the source physical controllers. On the other hand, if it is not due to a backwards installed joystick, you might also try updating RetroArch since I see you are on a relatively old release, 1.7.7, and it may be an actual bug to blame.
  • Create New...