Jump to content
LaunchBox Community Forums

MadCoder

Members
  • Posts

    49
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by MadCoder

  1. Launchbox Database Restore

    View File
    As I'm sure most of us have experienced more than once, launch box can corrupt itself from time to time, but it's becoming less and less of an issue as versions progress. However, it does happen especially.  Considering the amount of data launch box processes it's to be expected. This makes restoring back to previous state one click simple.

     

  2. HOW TO SOLVE
    This assumes you've installed the latest  .NET core runtimes or fresh Launchbox install or update.

    First, ensure the .net core path is properly listed within your systems path variables. To add or check system paths: Press Windows Key + R and enter "SystemPropertiesAdvanced.exe" next select Environment Variables.

    There you should see the path listed. Any OS version prior to 8.1 should have an entry like so "C:\Program Files\dotnet" otherwise x32 systems will be listed as "C:\Program Files (x86)\dotnet"


    If you've installed the latest version .Net Core (6.0.9 as of this posting) you will see subset of versioning folders located within the "C:\Program Files\dotnet\host\fxr" folder. More than likely there will be no files within the 6.0.9 folder. Copy the "Hostfx.dll" file from the 6.0.6 folder and place it in the empty 6.0.9 folder and that will resolve the consistent "Install .net core ..." messagebox allowing Launchbox to properly load.

    Launch Launchbox and enjoy

     
  3. 40 minutes ago, neil9000 said:

    It can absolutely be a GPU or cable issue. If the actual device outputting the signal, be it a motherboard when using onboard graphics, or a dedicated GPU only has a HDMI 1,4 output port, you will be limited to 4K30. This is a hardware limit and not something you can just apply in the GPU control panel. As you can see in the below spec page from hdmi.org HDMI 1.4 can only support 3840x2160 at 24, 25 and 30hz. So if the user has a older GPU, which can be quite common in the emulation community as current high end GPU's are not required for most emulation then they simply may be hardware restricted.

    https://www.hdmi.org/spec/hdmi1_4b

    I'm very aware of HDMI's protocols and limitations. However...

    Hardware restrictions wasn't mentioned, or even considered seeing that the original post was about a 4K display which assumes the end user must, or should have,  decent hardware installed to get the intended performance. I ship about 5-10 custom builds a week and this is the most common issue I see once it arrives and the customer hooks up their build to a new 4k which will make make the GPU adjust. What's really nuts is when a $4k custom builds maxes out at 12FPS in mame because the customer has a $75,000 99" 16k QLED TV. 

     

×
×
  • Create New...