Jump to content
LaunchBox Community Forums

We1Dont7Die

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by We1Dont7Die

  1. Fixed! Just changed the frequency setting in the cfg to 140 (ive read for gsync its best to cap 4-5 frames down so it doesn't go out of range) Thanks! Now that I think about it, I had to disable Gsync and set to fixed refresh in Nvidia Control panel for Starcraft 2 because that game is capped at 60fps and it wreaks havok with gsync I also had to disable Gsync and set fixed refresh for BigBox mode because of the weird stuttering transitions. Seems to be down to the way gsync enables and disables when fluttering around the 60fps range. My monitor has gsync range of 30-144hz so why there are problems around the 60 fps range is a battle for another day Gsync is great but it isnt perfect
  2. You must select Set up G-sync (like I see you have there) then go to the top menu and select "Display" then you will see "g sync indicator" It's hidden pretty well I thought that retroarch's frequency settings could be a culprit but i didn't mess with the setting in the frontend because it just seemed odd having to adjust by such small increments. But you're saying do it in the cfg instead....I'll give that a try. I run 144hz as well
  3. Thanks for the reply I just did some testing and enabled the G-Sync overlay in the Nvidia Control panel. With d3d12 selected as Video Driver I see the familiar G-sync overlay as shown here in Retroarch and here in game When i use gl as the Video driver, there is a different looking overlay and here in game And I can assure you that even though it shows G sync is on with gl mode, I am getting an incredible amount of tearing while d3d12 looks amazing. Do I need to do something with my drivers? Is there anything I should look for settings wise? Nothing weird about my setup...just a very clean win 10 install. I don't really fiddle with graphics settings. LaunchBox is set to use gl by default and I had to change that almost immediately because of the tearing.
  4. I am having the same problem. platforms on the left were sorted properly (alphabetically) before update to beta
  5. So basically i get screen tearing when using OpenGL in Retroarch. Using d3d12 all of my emulators work fine, even my gsync works. Retroarch cores which require OpenGL have been eliminated from my system due to there being d3d compatible alternatives. The only reason this is an issue is because there arent any alternate cores for Dreamcast which don't use OpenGL, so I'm stuck with the tearing for that core. Has anyone experienced this? Windows 10 64 gtx980 i7-6700k
×
×
  • Create New...