Up and Coming

Is timewarp working correctly in 4.8?

17 replies
3965 views

I just tried testing timewarp in both the 4.8 binary release from EPic along with Oculus's 4.7-06 branch and im not see'ing
what i expect to see.

In previous releases you could test timewarp by setting 'showflag.rendering' to 0.
Like so,

But with 4.8/ 4.7.6-06 I only get a black screen.

Additionally the tw latency within hmd stats is very high on 4.8/4.7-06 compared to the video.
16 odd ms compared to 4ms.

This topic has been closed for replies.

Show previous replies

S

spyro

Up and Coming

"artyom17" wrote:
As to 4.8.2 - complain to Epic, they have their own policies and we can't force them to take all the fixes.

I did, I do and I will do. ;)

Holding back working bug fixes for more than a month is just not acceptable. Often I am getting crazy about something for hours just to discover that this bug was internally fixed many weeks ago but wasn't published.

A

artyom17

Up and Coming

"spyro" wrote:
"artyom17" wrote:
As to 4.8.2 - complain to Epic, they have their own policies and we can't force them to take all the fixes.

I did, I do and I will do. ;)

Holding back working bug fixes for more than a month is just not acceptable. Often I am getting crazy about something for hours just to discover that this bug was internally fixed many weeks ago but wasn't published.

This is why you should build your own version using our github branch :)

M

muchcharles

New Participant

"artyom17" wrote:
The latency is a known bug in 0.6.0.1 Runtime. You should either to switch back to 0.6.0.0 or try the following trick, enter the following console command: 'hmd qahead on'. This should reduce the latency (but still not to the 0.6.0.0 level). This bug will be fixed in the next version of Runtime.

How about throughput? I would like to use the one that gives me the most headroom on frames-per-second/throughput: is that 0.6.0.0, which doesn't have queue-ahead but doesn't have this known bug (what is the known bug? Is there a thread on it elsewhere in the forum?), or am I better off with 0.6.0.1 with queue ahead turned on from the console? Would 0.6.0.1 give me a higher FPS in spite of the latency bug?

A

artyom17

Up and Coming

"muchcharles" wrote:
"artyom17" wrote:
The latency is a known bug in 0.6.0.1 Runtime. You should either to switch back to 0.6.0.0 or try the following trick, enter the following console command: 'hmd qahead on'. This should reduce the latency (but still not to the 0.6.0.0 level). This bug will be fixed in the next version of Runtime.

How about throughput? I would like to use the one that gives me the most headroom on frames-per-second/throughput: is that 0.6.0.0, which doesn't have queue-ahead but doesn't have this known bug (what is the known bug? Is there a thread on it elsewhere in the forum?), or am I better off with 0.6.0.1 with queue ahead turned on from the console? Would 0.6.0.1 give me a higher FPS in spite of the latency bug?

Yes, 0.6.0.1 with Queue Ahead should give you better results.

I

ipas

Participant

How do I enable Timewarp in UE4 ( 4.8.3 ) ?
"hmd timewarp on" gives 'command not recognized' ..

C

cybereality

Inspiring

Timewarp is on by default, and can't be turned off.

C

cjwidd

Up and Coming