Skip to content
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

Significant input lag in all Project Diva games #10195

Closed
ghost opened this issue Nov 26, 2017 · 12 comments
Closed

Significant input lag in all Project Diva games #10195

ghost opened this issue Nov 26, 2017 · 12 comments

Comments

@ghost
Copy link

ghost commented Nov 26, 2017

I assume the input lag is present in every game, but it''s a major problem in the Project Diva series, for obvious reasons.

Even with the 60 FPS cheat, a wired controller, Aero turned off in Windows 7, the games are basically unplayable on any difficulty other than easy in my opinion. I've tried the Retroarch core, and the difference between it and standalone PPSSPP in terms of input lag is like night and day.

My question is can anything be done to fix or reduce it? I'm using Windows 7, GTX 970, i5. Not that I think those things make any difference.

@hrydgard hrydgard added this to the v1.6.0 milestone Nov 26, 2017
@hrydgard
Copy link
Owner

I'm not quite sure why it's better in retroarch, so this should be looked into.

@Dotty
Copy link

Dotty commented Dec 6, 2017

RetroArch has display options to prevent excessive buffering. Including a pretty neat GL swap trick labelled hard sync.
https://github.com/libretro/docs/blob/master/docs/guides/optimal-vsync.md#input-latency
There's even quite a sizeable thread on their forums dedicated to getting input latency as low as possible.
https://forums.libretro.com/t/an-input-lag-investigation/4407

@unknownbrackets
Copy link
Collaborator

So basically using this to sync against the GPU:
https://www.khronos.org/opengl/wiki/Sync_Object

We could also do this in Vulkan.

-[Unknown]

@hrydgard hrydgard modified the milestones: v1.6.0, v1.7.0 Mar 24, 2018
@Leopard20
Copy link
Contributor

Leopard20 commented Apr 2, 2018

PD Extend has almost zero input lag on my device (Android), and I use touch controls. But PD 2nd has a noticeable input lag (~10-30 ms)

@unknownbrackets
Copy link
Collaborator

As noted in #4020, enabling real clock sync helps.

@hrydgard, I wonder if it makes sense to reduce the max frames rendered ahead of display when this setting is on. It's already basically a clear choice that input/network should be realtime as possible, so it seems logical to extend to display as well.

-[Unknown]

@hrydgard
Copy link
Owner

Yeah, that's not a bad idea. I'm not gonna go poking in the frame timing until well after 1.8.0 though :)

@unknownbrackets
Copy link
Collaborator

Yeah, agreed. For 1.8.0, we should probably remember to add to the release notes that if you get a drop in performance, it's because lag sync works correctly now... or maybe we should just flip it off automatically, it mostly didn't work before anyway.

-[Unknown]

@AkiraJkr
Copy link

I think it's best to keep it turned off automatically. It's best to not have people complaining about a drop in performance soo suddenly.

@hrydgard
Copy link
Owner

I'm gonna change the name of the ini parameter so it gets reset for everybody.

@Leopard20
Copy link
Contributor

Leopard20 commented Feb 25, 2019

Just a reminder: PD Extend works great already so make sure you don't break it in 1.9.0! ;)

@hrydgard
Copy link
Owner

I don't plan to break anything, and if I do let me know :)

@hrydgard hrydgard modified the milestones: v1.9.0, v1.10.0 Jun 27, 2019
@hrydgard hrydgard modified the milestones: v1.10.0, v1.11.0 May 10, 2020
@hrydgard hrydgard modified the milestones: v1.11.0, v1.12.0 Nov 11, 2020
@hrydgard hrydgard modified the milestones: v1.12.0, v1.13.0 Jul 10, 2021
@hrydgard
Copy link
Owner

hrydgard commented Sep 6, 2023

Closnig this in favor of #17685

@hrydgard hrydgard closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2023
@hrydgard hrydgard removed this from the Future-Prio milestone Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants