Forum Discussion
[Rift] A suggestion about Adaptive PD
Hello,
first of all, its nice to see my biggest concern (interlock between ASW and APD) is being resolved.
I'm preparing to submit mi app to Store, so doing a lot of perfomance testing and noticed APD can cause frame drops as well - likely caused by the 2seconds delay between changes
- In low GPU intensity section, the PD goes up to 1.25 (cap)
- When settings starts to change, PD goes down to 1.21
- fps drops to 70-80 as GPU can't handle the resolution
- after 2 reconds, PD is changed to 1.02 and fps goes back up to 90.
I understand the concern of having a delay between changes, but please ask yourself a question:
What's better - rapid resolution changes or framedrops?
My suggestion would be to allow APD to readjust PD even during the 2sec delay if the fps is still low (get some limit for that - like 85fps is ok, below is change), and keep the 2sec rule for going up.
Jan Horsky aka ENiKS
first of all, its nice to see my biggest concern (interlock between ASW and APD) is being resolved.
I'm preparing to submit mi app to Store, so doing a lot of perfomance testing and noticed APD can cause frame drops as well - likely caused by the 2seconds delay between changes
- In low GPU intensity section, the PD goes up to 1.25 (cap)
- When settings starts to change, PD goes down to 1.21
- fps drops to 70-80 as GPU can't handle the resolution
- after 2 reconds, PD is changed to 1.02 and fps goes back up to 90.
I understand the concern of having a delay between changes, but please ask yourself a question:
What's better - rapid resolution changes or framedrops?
My suggestion would be to allow APD to readjust PD even during the 2sec delay if the fps is still low (get some limit for that - like 85fps is ok, below is change), and keep the 2sec rule for going up.
Jan Horsky aka ENiKS
3 Replies
Replies have been turned off for this discussion
- Why would you want adaptive PD if pupils don't move? That is usually configured when you start using the rift and should stay the same setting for that user forever.
- PD is for Pixel Density, sorry for confusion :)
- Thanks for the reply, I've checked the source code of OculusRift plugin and see quite clearly on how the policy can be changed. Unfortunately, it would mean changing the OculusRift plugin itself, which is something I'd like to avoid for future compatibility. Would it be too much to ask for this to be exposed as public? Or if i change the plugin to expose the functionality, for my code to be added back to the codebase? (I assume the Oculus* plugins are maintained by Oculus, so pull request to UE4 master would not change much)
