LukeRoss

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 31 total)
  • Author
    Posts
  • in reply to: Assassin's Creed Origins #171050
    LukeRoss
    Participant

    Is anyone else playing AC:Origins with vorpX at the moment? Have you guys been able to squeeze more than 20-ish fps from it while in the streets of Alexandria?

    in reply to: Tron 2.0/Thief 2014 #171043
    LukeRoss
    Participant

    Also, instead of hiding the weapons completely, you might want to experiment with +PVModelFOV <n> (the default value is +PVModelFOV 75). Unfortunately the console is disabled in Tron 2.0, or at least it is in my copy, so you cannot tweak the weapon FOV value in realtime during play.

    in reply to: Tron 2.0/Thief 2014 #171042
    LukeRoss
    Participant

    @Stryker_66 Try this one: from the Tron.exe launcher, select Options, write +DrawGuns 0 in the Command Line, make sure that “Always pass command line arguments to the game” is checked, and confirm with OK.

    LukeRoss
    Participant

    OMG OMG OMG, Tron 2.0 with Geometry 3D and DirectVR!!! You are DA MAN!!! Now I just have to find a way to teleport myself three days into the future, can’t wait ;-)

    in reply to: Assassin's Creed Origins #170785
    LukeRoss
    Participant

    Well, it would be good to know if Ralf is seeing the same frame rate halving on his test machines. If he can repro, perhaps we can still hope for a fix

    in reply to: Assassin's Creed Origins #170757
    LukeRoss
    Participant

    The higher FOV that vorpX sets might be the reason

    Thanks for the reply, Ralf. It’s not that. I don’t change the FOV in the .ini when I play the game in 2D without vorpX. To double check, I took two screenshots in the exact same location, one with vorpX disabled and the other after reloading the game with vorpX enabled. The two screenshots matched perfectly, so the FOV doesn’t change (but the frame rate drops to half).

    It’s always a good idea to reduce graphics details when playing a newer (and thus more demanding) game with vorpX

    That might be true in general, but as I said in my previous post, I have tried putting graphic detail all the way down to minimum and the frame rate doesn’t change. It’s exactly as if vorpX was causing everything in the game to render exactly twice, which would be expected in G3D mode, but not in Z3D mode (and anyway as I wrote it also happens if I disable 3D in the vorpX overlay menu).

    in reply to: Assassin's Creed Origins #170754
    LukeRoss
    Participant

    In 3D using Pimax 4K and Z-normal I only get 18 FPS, is this a normal penalty ?

    I can confirm there is something odd going on with Assassin’s Creed: Origins and vorpX. In Alexandria, walking around in the streets, I get 18 fps average on my GTX 1080 Ti, just like Sune Jorgensen. I have the Oculus Rift though, so it’s not specific to the Pimax.

    I have tried: a. tweaking various game-specific options in the NVIDIA control panel; b. turning Z3D off and on; c. lowering the game graphics options all the way down to minimum; d. changing the pixel density; and e. everything else that I could think of. Nothing makes any tangible difference.

    That would seem to imply that the game is CPU-bound; however, the exact same location gives me 36-37 fps average when vorpX is disabled.

    in reply to: NFS Most Wanted (2005) Geometry 3D support #170678
    LukeRoss
    Participant

    This might be a symptom of the same underlying issue as reported here for Assassin’s Creed 2. I have an NVIDIA card by the way, so probably not card-related.

    Do you see any errors or warning in the vorpX log for the game?

    in reply to: Seeking for Oculus Rift Core 2.0 beta feedback #170677
    LukeRoss
    Participant

    Hi Ralf,

    no problems here with fullscreen DX9 games while Oculus Home 2 is running. I also just tried with the samples from the old June 2010 DirectX SDK and they go in and out of fullscreen with no issues. If you want I can try specific options (I don’t know, 64-bit exe, backbuffer formats, whatever).

    I am on the Public Test Channel, Rift Core 2.0 beta enabled, Oculus App version 1.23.0.527813 (1.23.0.528114), GeForce GTX 1080 Ti, driver version 388.31. Perhaps it’s driver dependent? I heard of a lot of issues with Oculus and NVIDIA more recent drivers.

    LukeRoss
    Participant

    Thanks for the suggestion (I assumed you meant checking the “Never change any game settings” box), however I just tried and it made no difference whatsoever. In any case, vorpX doesn’t seem to have custom settings for Assassin’s Creed II: the “Restore Game Settings” list doesn’t even include the game. Out of curiosity, was yours a generic recommendation or did you find instances where leaving the automatic settings enabled would kill Geometry 3D?

    BTW, of course I also tried resetting the profile to factory default, both in the “Local Profiles” page and from the “Trouble Shooting” page (not sure whether there’s any difference between the two restoring methods), and Geometry 3D is still unavailable. For the sake of completeness, I also tried toggling the “Try to block known game overlays” and “Run vorpX Control as administrator”. Nope.

    LukeRoss
    Participant

    Should I give up all hope for this great game? :’-(

    BTW, Z3D is also not working for me in AC2: Normal has zero depth regardless of the settings, and Adaptive has uniform depth (toying with the settings I can manage to push the whole world more or less “inside” the virtual screen, but there is no convergence whatsoever). It’s as if vorpX were unable to read the depth buffer.

    LukeRoss
    Participant

    If it’s any help, there is a suspicious entry in the vorpX log for the game:

    WRN: Loading pre 17.3.0 G3D settings (0.0.0)

    Other lines that contain the term G3D appear normal to me:

    INF: ProgSetting User: Head Tracking G3D Latency Enhancement: 0.000000
    INF: ProgSetting User: G3D Max Separation: 1.000000
    INF: ProgSetting User: G3D Focal Offset: 0.000000
    INF: ProgSetting User: G3D FOV Multiplier: 0.000000
    INF: ProgSetting User: G3D Camera Height Mod.: 0.000000
    INF: ProgSetting User: G3D Shadow Treatment: 4
    LukeRoss
    Participant

    Same problem here with AC2 (original DVD version, so Steam is not the culprit). The vorpX popup says right at the beginning that the game has Geometry 3D, but then the option isn’t available: only Z3D.

    I am a sad panda, because to me Geometry 3D makes all the difference…

    Ralf, when you have some time could you check on this? If G3D was implemented for the game, is there a trick for making the option available?

    in reply to: vorpX Desktop Viewer for Oculus Home 2.0 beta #170252
    LukeRoss
    Participant

    Wonderful Ralf, thanks!!!

    LukeRoss
    Participant

    Add: I saw that disabling “Positional VR” gets rid of my weapon glitches, and it appears to make no difference otherwise. I thought that it also would disable position tracking, but apparently it doesn’t. So basically everything now just works!!!

Viewing 15 posts - 16 through 30 (of 31 total)

Spread the word. Share this post!