-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(D3D) It takes screenshots of the menu, not the game. #5928
Comments
Is there a reason you're using the d3d driver? It is very incomplete. |
SDL2 and D3D runs a TON smoother than all of the other video drivers. I made an topic on the Libretro forums specifically for this but... no-one was able to help and no-one believed me. Quotes:
-SigmaVirus on https://forums.libretro.com/t/libretro-cores-are-choppy-while-their-standalone-versions-are-not/12052/38 or
-radius ( yes, fr500 ) from https://forums.libretro.com/t/add-fast-forward-to-the-sdl2-video-driver/12252 or #5628 -orbea I mean, I don't want to seem "disrespectful" ( sorry fr500 I guess )
but just claiming that I don't appreciate the work of the devs and ignoring these big issues just saddens me. I might've said something wrong here and there but... goes to sleep |
I do agree we should try to fix this, the D3D driver should become important at a certain point, especially for Xbox/UWP purposes. |
What about the SDL2 driver? Is it going to keep being left out? I thought D3D wasn't for Linux? Lakka is a Linux distro. Lakka is choppy on PC. |
@hyarsan I read through your threads and it seems you never mentioned your GPU. What do you have? Have you tried the gdi video driver? If that driver still shows performance issues with cores, then I have to admit it's highly likely there's some gremlin in your system, either hardware or software. Can you also post a screenshot of the first page of "Information -> System Information" from the latest nightly please? |
I don't see how the melonDS issue is related to this at all. Quoting it seems to stir drama for no reason whatsoever. I agree it would be cool if all the drivers were mature and fully featured but as of today, they are not. Not even Vulkan is usable for me for various technical reasons. That said. You shouldn't have any perf issues with GL. But without being able to see it for ourselves it's hard to understand what choppiness is. Maybe take a video? I have a PC running an i5-760 and a GTX760i and it's perfectly smooth. (I use the MMX3 intro to check for "choppyness" since it has a fast scrolling scene) You should try the usual suspects, clean driver installation, remove any overlays (steam / discord / reshade / GFE) |
I tried to set the performance profile to max performance and recorded it but the result is not accurate at all. The recording functionality in RetroArch seems be producing perfectly smooth video, which doesn't demonstrate the point I'm trying to show. I guess the choppyness is more like lagspikes. I used ShareX, anyone recommend other video recording software that are accurate? Oh and the melonDS thing? Just pretend like nothing happened :D |
A phone with a camera
…On Tue, Dec 19, 2017, 7:18 AM hyarsan ***@***.***> wrote:
I tried to set the performance profile to max performance and recorded it
but the result is not accurate at all. I used ShareX, anyone recommend
other video recording software?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5928 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpC0OASrf9skG3zjTy7kAHRF00IdjoJks5tB6mZgaJpZM4REsyn>
.
|
I second the phone camera, not really an easier way to get something semi-accurate. Since GDI doesn't work right either, I'm 90% certain it's something not related to RA. I would look into possible DPC issues http://www.resplendence.com/latencymon. |
@fr500 Would you rather he start a new issue? I'm fine with that as long as nobody brings any drama into it. I just want to help the guy... I'd be pretty frustrated too if I had this issue across different hardware when nobody else did. You know how I seem to be cursed as well. |
No it's fine imho to keep going here |
Nah, I didn't mean to start drama. I just wanted to make clear that I respect you and the other's work :D ❤️ |
Also @hyarsan since you are on the Fall Creators Update, there is a good chance this is the biggest cause of your problems. That version in particular seems highly broken across the board for a lot of people. See here: |
But then how come Lakka was really choppy for me ( On another laptop ) ? And why was it choppy before the update too? ( On another laptop... ) And I thought I said it was 60 fps? ( Full speed ) I guess that #5607 is the issue here! No weird choppyness when I use full screen! :) Is #5607 talking about the frame rate? If not, then that's the real issue! I dunno, first that needs to be fixed. That core i7 laptop has really bad frame rates ( Probably because it has a ton of shiz installed ) Not sure about Lakka though. But why is D3D and sdl2 smooth in windowed mode? I'll keep playing in Fullscreen GL for the time being and if I see something go wrong, I'll tell you. |
I have no idea. But we do need some video proof to understand just what "choppy" means. We're all scratching our heads over here. |
I feel like #5607 is more important first. So far full screen seems to work perfect, at least on this device. And if you really want inaccurate video for some reason, here you go: |
https://forums.libretro.com/t/libretro-cores-are-choppy-while-their-standalone-versions-are-not/12052
The same guy?
…On Wed, Dec 20, 2017 at 7:03 AM, hyarsan ***@***.***> wrote:
I feel like #5607 <#5607> is
more important first. So far it seems to have fixed it, at least on this
device... in full screen of course.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5928 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWPDto9XYyrDFuC9ntNJvIsZoiBerw0Jks5tCEC8gaJpZM4REsyn>
.
|
Yeah, Flooder is me. |
Closing since it does not seem to be happening anymore. |
First and foremost consider this:
Description
When you take screenshots using the Direct3D video driver, it takes a screenshot of the menu. It most likely happens because of the fact that it shows the game for a frame which is not long enough.
Expected behavior
It take a screenshot of the game.
Actual behavior
It takes a screenshot of the menu.
Steps to reproduce the bug
Bisect Results
I don't remember when it did work, actually.
Version/Commit
You can find this information under Information/System Information
Environment information
The text was updated successfully, but these errors were encountered: