Ralf

Forum Replies Created

Viewing 15 posts - 6,136 through 6,150 (of 10,066 total)
  • Author
    Posts
  • in reply to: Screen flashing when using SLI #169143
    Ralf
    Keymaster

    There is no SLI support, sorry. Disabling it is the right thing to do if it doesn’t happen to work for a game by pure chance. I think that’s also true for most native VR apps unless they explitely support VR-SLI, but that information may be outdated.

    in reply to: The Witcher 3 crash with Vorpx 17.3 #169142
    Ralf
    Keymaster

    G3D:

    Main pro: more natural 3D (2 ‘cameras’ like native VR apps).
    Main con: slow due to having to render everything twice.

    Z3D:

    Main pro: fast since the scene is only rendered once.
    Main con: 3D effect not as natural.

    Personally I think Z3D is OK for Witcher 3, open spaces usually work quite well this way, especially in cinema mode. Some however always prefer G3D regardless of performance. If that isn’t true for you, you can safely stick to Z3D.

    in reply to: The Witcher 3 crash with Vorpx 17.3 #169138
    Ralf
    Keymaster

    Witcher 3 hotfix is up. Please reinstall vorpX using your web installer. The version number has not been raised, so no auto-update.

    The hotfix addresses the grass/clutter rendered at wrong depth issue, but due to the really weird nature of this bug there is a certain chance that it also affects your menu problem.

    in reply to: Menu mouse speed / cinema screen options #169134
    Ralf
    Keymaster

    Yes, the left ALT key is blocked since this release on purpose. It is used for almost all default vorpX keyboard shortcuts, which could cause issues in several games.

    in reply to: Menu mouse speed / cinema screen options #169120
    Ralf
    Keymaster

    if the curvature option is not there per default (can’t remember), enabling “Expert Settings” in the config app should enable it. I’m 98% certain that there is no major difference between the two screens technically.

    in reply to: Menu mouse speed / cinema screen options #169117
    Ralf
    Keymaster

    OK, can’t really say anything profound in regard to what might cause that TBH, but I’ll add the speed slider mentioned above to the config app for the next official version (not todays hotfix though).

    BTW: you can also use the menu with the cursor keys and [ENTER] or a gamepad.

    Background:

    The ‘Immersive Screen Mode’ UI is kept to a minimum on purpose. You can however setup the normal cinema mode pretty much the same way if you want to customize, including switching the backgound to black.

    in reply to: Rift core 2.0 and VorpX #169113
    Ralf
    Keymaster

    What exactly is the issue you have? The new Oculus Home .exe is excluded per default in the latest version, so no need to do anything. Also no other reports of any new issues with the new Home software that I’m aware of so far.

    in reply to: Menu mouse speed / cinema screen options #169112
    Ralf
    Keymaster

    Odd, I’ll add a menu mouse speed option for the next vorpX version early next year.

    If you play Witcher 3, you will love the hotfix that will come in half an hour even more, I guess. It fixes a Geometry 3D glitch with grass and other objects being rendered at the wrong depth.

    Check the forum for an announcement thread.

    in reply to: Menu mouse speed / cinema screen options #169109
    Ralf
    Keymaster

    The menu mouse speed is hardwired, no way to change it, sorry.

    I’m curious though whether this only applies to one game, or do you have this in every game? Also are you maybe just using a rather fast mouse speed normally so that it just seems slow in comparison to what you are used to?

    I’m not suggesting anything, just wondering since noone ever mentioned that so far and I also use the menu quite often myself.

    in reply to: Trojan:Win32/Fuerboos.B!cl #169107
    Ralf
    Keymaster

    Add the C:\Program Files (x86)\Animation Labs\vorpX\ folder to the exclusion list and see whether that helps.

    The better contact in such a case is your AV vendor. They should have some procedure in place to report false positives for their users.

    Brief update: no issue with the latest Windows Defender definitions (1.259.764.0) here. If you don’t have that yet, try to update manually, that will probably suffice to solve the issue.

    in reply to: Trojan:Win32/Fuerboos.B!cl #169103
    Ralf
    Keymaster

    Yes, trojan/virus messages with vorpX always are a false positive.

    Probably due to vorpX injecting other program some AV-programs notoriously flag each new version as malicious when they do their apparently less than perfect guesswork.

    Ideally please report the issue to your AV vendor as false positive so they can address the problem.

    In the meantime please exclude the vorpX program folder from scanning if it allows you to do so.

    If you use anything else than Windows Defender, consider to switch. While that isn’t a 100% guarantee for avoiding false vorpX positives (happened once there too so far), it’s a lot less likely than experiencing this with some of the more invasive AV programs like BitDefender, Kaspersky etc.

    in reply to: vorpX 17.3.2 Available Now #169100
    Ralf
    Keymaster

    Unfortunately not. While a profile for the game exists internally, there is a severe judder-issue that makes it unusable, so it is not included in the release version.

    If this issue solvable, the profile will be included in the next maintenance release.

    Keep the “if” in mind though. It’s not clear at all currently whether there can be a solution to this judder issue.

    in reply to: The Witcher 3 crash with Vorpx 17.3 #169096
    Ralf
    Keymaster

    Just a short heads-up that the terrain/grass glitch is confirmed and will be looked into as soon as possible. I don’t recall to have seen that before so it’s probably (or at least hopefully) some last minute bug that can be found quickly.

    in reply to: World of Warcraft vorpX 17.3.0 ? #169093
    Ralf
    Keymaster

    Is there any start area where the water glitch occurs? The profile was mostly done in the human start area and as far as I can remember there wasn’t such an issue with a small creek in that area.

    It’s impossible to check any later game content unfortunately, so I would need to know about a start area where the glitch occurs to be able to check it.

    in reply to: determination of terms used #169092
    Ralf
    Keymaster

    I don’t recall to have written ‘geo3d’ ever anywhere, but if someone else used it, I would assume that it’s simply short for ‘Geometry 3D’.

    What has changed terminology wise is the introduction of “Immersive Screen Mode”, which sits between full VR and cinema mode immersion wise, for a slightly more detailed explanation please check the 17.3.0 release blog post.

    The other change is that the old “Game Optimizer” in the config app is gone and now part of “Direct VR” as everything the old optimizer did now happens automatically – and a lot better – when a game starts. Since optimizer and memory scanner both adjust games to work better in VR, it makes more sense to simply use the same term for both, although technically they are completely different things.

    So technically there is a “Direct VR Memory Scanner” and a “Direct VR Settings Optimizer”. From a user’s perspective however they both serve the same purpose, so both together are “Direct VR”.

Viewing 15 posts - 6,136 through 6,150 (of 10,066 total)

Spread the word. Share this post!