Jump to content
LaunchBox Community Forums

Hamburglin

Members
  • Posts

    203
  • Joined

  • Last visited

Posts posted by Hamburglin

  1. I honestly can't even remember how I got the bezels but I thought it was through the media download in launchbox. What doesn't make sense to me is why deleting and reinstalling retroarch would make those bezels disappear.

    Anyone know how I get the bezels back? For some reason LB has been stuck on clearing image cache for like 15 minutes after I tried downloading the bezels per the video out there. Is it stuck?

  2. Ok, I found one way to trigger the fps tug of war.

    1. Alt tab to any window besides LB to get the frame rate back up to the intended 119hz

    2. Go back into LB. It should still be at 119hz

    3. Click tools -> manage -> emulators to bring up a menu window. 

    4. OR, just launch big box and it happens immediately.

    Boom, fps is all over the place. It sometimes triggers JUST by clicking on the tools drop down menu and letting it sit there for a second.

  3. Ok, sounds like I'll need to flip through a few settings.

    I did just figure out what's causing the flickering (when it does occur).

    Something is fighting for the refresh rate in BB to be 61hz whereas the tv is trying to use 119hz:https://gfycat.com/badterrificant

    I flipped freesync off and on it got rid of the flickering. Im going to check if its a BB thing only or all around: https://ibb.co/KKk9Y2t

    Edit: only keeping premium free sync on and turning vrr + gsync off, I don't see the framerste fought over (and therefore flickering) anymore. For now...

    Strange how that only showed up in BB but maybe it's another WPF app thing.

    Edit 2: Nope, the 61 vs 119 fps fight continues on and ONLY when LB or BB are the focus window.

  4. 11 minutes ago, C-Beats said:

    Yeah, np. I get where you're coming from. Out of curiosity what card are you using, and does your system have an integrated card, a dedicated one, or both? I do know that intel integrated cards have known issues with WPF applications, so curious if something similar may be occurring on your machine.

    It's a weird one. It's an amd Vega laptop style gpu that comes physically attached onto a NUC Hades Canyon board from around 2018.

    Intel is in charge of the drivers now (even though it's red amd styled) and I think they used this relationship to start their own gpu business.

    My tv is a 77" LG C2 ran in 2560×1440 @ 120hz in its new fancy game mode with amd free sync premium (vrr) enabled.

  5. Just now, C-Beats said:

    LaunchBox doesn't have any custom code to handle rendering, it's all done by the WPF framework which is just using Direct X to do everything. A lot of what you're talking about is far too low level for the application to have any idea about it, let alone change behavior because of it.

    That's all fine and dandy. Not placing blame, just letting you guys know that ONLY big box had an issue after a driver update. Nothing else did, including retroarch, srand alone emulators, windows gui and pc games.

    I also getting flickering in big box's UI sometimes as well. The entire screen where it's black flickers really obviously a couple times a second and its a random rhythm. Not sure if it's a vudeo driver setting, resolution or framerate thing and I haven't tried to figure it out. Again, everything else works fine.

  6. 2 minutes ago, C-Beats said:

    I'd vet if you TV has a "game mode" in it that helps with response times. If the same program works on one TV but not the other it has to be because of the device of the OS settings for that device. The way LB works it really doesn't pay any attention to the monitor it's on other then to determine scaling values.

    Well, it works now on game mode with amd variable refresh rare at 120hz. It just took plugging it into another tv first.

    I imagine something changed between driver version and LB did not catch it or was defaulting to some weird mode since everything else worked fine.

  7. 2 minutes ago, moudrost said:

    Sorry I missed the fact you said this was in Big Box. So can I assume everything is fine when you play your games? This really sounds like a refresh rate issue. What does your graphics driver report when you check? When I had this issue, it was slow in Big Box and every emulator I tried. Everything showed 30 Hz

    image.thumb.png.f3d0f7559e84135af60005bfec042060.png

    Ok yeah I checked my refresh rate and resolutions and stuff already and they are correct (60hz or 120hz)

  8. It's almost like it decided to start using my CPU or onboard GPU for its graphics or something. Is there a setting for this somewhere?

    I've tried changing resolutions, hz and image scaling.

    When I go to the unlock screen in big box, it takes a second to load even though I hear sounds and button presses. When I moved the arrow keys around to select my pin, it doesn't update the image for like 3 seconds even though I hear my button presses.

  9. 1 hour ago, neil9000 said:

    Launchbox does not touch your emulator configs in any way, it simply passes the rom to the emulator. It has zero to do with saving or loading in the emulators either, the only time it even knows that a config even exists is when you specifically specify loading one via the comand line section in the edit emulator screen. Launchbox is a launcher, it has zero direct control over a emulator unless you specifically give it those commands to do so.

    That's true but the way to trigger the issue is by using LB to start up retroarch. Not saying it's LB's fault but I can't figure out what else it is right now. My second guess is that it's a weird permissions issue within Windows but like we said, there's no admin password prompts.

     

    1 hour ago, vaderag said:

    Have you worked out which files store the overlays?

    I have the cfg's that tell the overlay what to do (in RA -> Config -> Core -> Game.cfg) 

    And they get used automatically, but outside of that I can only find the one set in Retroarch.cfg which seems to do everything

    Have you worked out how to set one for a specific system?

     

    We got sent down that path by a mod above... I would have assumed the same, but it works outside of LB and does not work when launched by LB

     

    I'm not sure about overlays. That reminds me, I turned them off for games that have two screens that are extra wide and I think THAT actually saved at some point through LB -> Retroarch. But maybe I opened retroarch separately for that config change too...

    But yeah, retroarch.cfg itself is failing to save for me.

×
×
  • Create New...