Skip to main content
opamp
Up and Coming
July 8, 2015

Is timewarp working correctly in 4.8?

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.

    17 replies

    opampAuthor
    Up and Coming
    July 9, 2015
    Anybody?
    DK2. Phenom 2 x4 4.2GHz,Asrock Extreme 3 970,8GB DDR3 1600, R9 270x 1180/1400.
    cybereality
    Inspiring
    July 9, 2015
    I just tried it, and I'm also getting a black screen on UE4.8. Let me see if this is still supposed to work.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    opampAuthor
    Up and Coming
    July 9, 2015
    "cybereality" wrote:
    I just tried it, and I'm also getting a black screen on UE4.8. Let me see if this is still supposed to work.


    Cheers Cyber,

    Maybe im missing something as I know the SDK/Plugin has changed significantly.

    *edit ive just realised that the reason the tw latency is so low in the video is that qahead defaults to on in the runtime.
    But that still doesnt explain the apparent lack of timewarp.
    DK2. Phenom 2 x4 4.2GHz,Asrock Extreme 3 970,8GB DDR3 1600, R9 270x 1180/1400.
    artyom17
    Up and Coming
    July 9, 2015
    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.

    As to inability to see timewarped image with 'show rendering': I'll look into this, seems like it stopped working after we switched to the compositor. But timewarp works correctly.
    opampAuthor
    Up and Coming
    July 9, 2015
    "artyom17" wrote:

    As to inability to see timewarped image with 'show rendering': I'll look into this, seems like it stopped working after we switched to the compositor.


    Cheers artyomy17,

    Just to be clear, Im not too concerned about being able to test timewarp anymore.
    But more about the fact that the test now seems to imply that it doesnt appear to be working during normal use.
    At least im assuming thats what its implying?
    DK2. Phenom 2 x4 4.2GHz,Asrock Extreme 3 970,8GB DDR3 1600, R9 270x 1180/1400.
    artyom17
    Up and Coming
    July 9, 2015
    I've fixed the issue with the 'show rendering' black screen. Currently available via https://github.com/Oculus-VR/UnrealEngine
    cybereality
    Inspiring
    July 9, 2015
    Very nice, artyom17.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    opampAuthor
    Up and Coming
    July 9, 2015
    "artyom17" wrote:
    But timewarp works correctly.


    Doh, I missed that the other day.

    Many thank guys.
    DK2. Phenom 2 x4 4.2GHz,Asrock Extreme 3 970,8GB DDR3 1600, R9 270x 1180/1400.
    spyro
    Up and Coming
    July 9, 2015
    "artyom17" wrote:
    I've fixed the issue with the 'show rendering' black screen. Currently available via https://github.com/Oculus-VR/UnrealEngine


    Thank you. Will this be automatically part of the next UE4 update?

    spyro
    artyom17
    Up and Coming
    July 9, 2015
    "spyro" wrote:
    "artyom17" wrote:
    I've fixed the issue with the 'show rendering' black screen. Currently available via https://github.com/Oculus-VR/UnrealEngine


    Thank you. Will this be automatically part of the next UE4 update?

    spyro


    Most likely not the part of 4.8.2 but should be a part of 4.9. As to 4.8.2 - complain to Epic, they have their own policies and we can't force them to take all the fixes.
    Show more replies
    Terms & ConditionsAccessibility statement