Ralf

Forum Replies Created

Viewing 15 posts - 4,111 through 4,125 (of 10,003 total)
  • Author
    Posts
  • in reply to: Virus Heads Up #190296
    Ralf
    Keymaster

    As always:

    This is a false positive. Please report the issue to your AV vendor so they can fix the problem with their software, and/or exclude the vorpX program folder from your AV scanner to avoid future problems with the failing guesswork of your AV program.

    Alternatively consider switching to Windows Defender, which is less invasive than some other scanners. And in the worst case Microsoft at least reacts fast when they are made aware of a false positive. Windows Defender kicks in automatically when you uninstall redundant third party AV software.

    in reply to: A couple quick questions and observations #190260
    Ralf
    Keymaster

    Just for clarification: vorpX does change the .ini, but not that particular seting. What vorpX does is setting the resolution and disabling motion blur and DOF, which both look bad in VR.

    in reply to: A couple quick questions and observations #190256
    Ralf
    Keymaster

    Config app: you should be able to solve that by using by one of the High DPI compatibility options Windows provides. Right click the .exe > Properties > Compatibility.

    vorpX does not change the bLoadFaceGenHeadEGTFiles option in Fallout 3. Some mod managers or similar tools may also change .ini files. So if you are using something like that, that’s a potential candidate. The .vpxbak file is not used unless you restore settings in the vorpX config app.

    PipBoy: IIRC shaders in the game are used in multiple places, so enhancing/scaling the PipBoy breaks other things. EdgePeek is you best friend here. The save an extra mouse click you can bind the EdgePeek key to your PipBoy key.

    in reply to: Fallout 4 VATS issue #190254
    Ralf
    Keymaster

    It’s either VATS or DirectVR, sorry. Personally I don’t think VATS makes much sense in VR, but if you have to use it, DirectVR has to be disabled. IIRC the memory scanner FOV causes the issue, not 100% sure though, might also be the memory scanner head tracking.

    in reply to: Flickering on the screen of Red dead redemption 2. #190225
    Ralf
    Keymaster

    There will be an update sometime next week that is safer in regard to potential judder issues. I was a bit too optimistic with some related code in the DX12 implementation.

    in reply to: The Outer World #190176
    Ralf
    Keymaster

    You have to restart the game after switching to G3D. There should be a message recommending that directly below the option in the menu. Guess I have to make these red again, blue doesn‘t seem to cut it… Make sure to save the settings before you restart the game.

    in reply to: DX12 and Vulkan API support when? #190165
    Ralf
    Keymaster

    @ dborosev: vorpX automatically sets the renderer to DX12.

    in reply to: The Outer World #190142
    Ralf
    Keymaster

    That’s what vorpX’s DirectVR does. During my tests everything above 120 was ignored by the game though. I’ll check that again just to be sure.

    in reply to: Red Dead Redemption hooking problem #190138
    Ralf
    Keymaster

    There is nothing to share in this regard at this point. If that changes in future, I’ll let you know.

    in reply to: Far Cry 5 not hoking anymore…. #190134
    Ralf
    Keymaster

    The game is not supported by vorpX, so I can’t really say anything specific.

    Unless that has changed recently the game uses Easy Anti Cheat, which prevents vorpX from hooking into it. If you are using a tool to circumvent EAC or a “version” of the game that doesn’t come with EAC, you are on your own. Might or might not work. Hard to tell and for obvious reasons can’t be tested here unfortunately.

    in reply to: Red Dead Redemption hooking problem #190132
    Ralf
    Keymaster

    Z3D games per se only have positional tracking if it is handled via DirectVR, which is not the case here. Hope that answers your many questions for now, I’m somewhat out of answers. :)

    in reply to: Red Dead Redemption hooking problem #190129
    Ralf
    Keymaster

    Please first try with a lowered resolution, ideally something common, just in case 3200×2880 is too high for the game with vorpX running on your machine. Apart from that please also check for potential hooking conflicts. I wouldn’t rule out that some other app (e.g. some overlay) that hooks the same routines as vorpX could potentially cause an infinite loop whith vorpX hooked into the game.

    in reply to: The Outer World #190118
    Ralf
    Keymaster

    I can’t make an elobarate discussion out of everything. Sorry and thanks for your understanding. If you want me to continue to explain each and every detail to you, at some point you have to accept the answer you get. It really doesn’t make sense to set the zoom higher in this game because that would break the FOV, which is capped by the game as explained above. Hence vorpX automatically caps the zoom accordingly, which is a good thing. Unfortunately there is no other answer to your question/wish than this one.

    in reply to: Red Dead Redemption hooking problem #190116
    Ralf
    Keymaster

    If it still does not work after checking the above, please do a full factory reset in the vorpX config app (trouble shooting page).

    If you continue to have the issue after the factory reset, please check your PC for programs that might interfere with vorpX hooking the game. You can find more detailed information on the matter either in the vorpX help or in the trouble shooting post here on the forum.

    in reply to: Red Dead Redemption hooking problem #190112
    Ralf
    Keymaster

    Normally yes, but can’t hurt to try without.

Viewing 15 posts - 4,111 through 4,125 (of 10,003 total)

Spread the word. Share this post!