Ralf

Forum Replies Created

Viewing 15 posts - 4,036 through 4,050 (of 10,045 total)
  • Author
    Posts
  • Ralf
    Keymaster

    EdgePeek:

    Can’t replicate. Please provide some details. Which game is this? Also FullVR or Immersive Screen?

    Please first try to reset the game profile to default, if that doesn’t help, try a full factory reset. You can find both options in the config app (trouble shooting page).

    Joy2Key:

    Either make sure that vorpX’s internal gamepad mapper is disabled (‘X-Box Gamepad Override’) or use that instead of Joy2Key. If you don’t need any special features Joy2Key provides, using the internal mapper should always be your preference.

    Ralf
    Keymaster

    Did you try to reset the view with ALT+SPACE? The screen is centered to the camera normally.

    However, if that’s not what you want, you can change the perceived height with a little trick: move up or down your head, then recenter with ALT+SPACE and move back to your preferred position.

    Ralf
    Keymaster

    Not really. For vorpX any gamepad is just an X-Box gamepad and with that it works as it always did. Not sure what to recommend to you, sorry. Can’t really imagine any change that could possibly make your PS4 gamepad fail suddenly, there is not a single line of code that treats it differently than an X-Box gamepad.

    Ralf
    Keymaster

    OK, did some more testing. vorpX uses a new frame sync mechanism for DX11 on Oculus, which enhances FPS a little (~10%), but with very low frame rates below 30fps like in your case the old method seems to feel smoother in Monster Hunter World.

    I would suggest to adjust the game settings to reach 40fps and then maybe enable FluidSync. Overall that will yield a better experience than playing with a super low frame rate.

    If instead you rather want to go back to the old sync method, you can do so with an .ini tweak:

    1. Navigate to C:\ProgramData\Animation Labs\vorpX\Devices\Display
    2. Open Oculus.ini with a text editor
    3. Change iDmBufferGrabberSyncDX11 (near the bottom of the file) from 1 to 0

    Only change the DX11 value, DO NOT change the value for DX12, DX12 is untested with the old method and may fail entirely with it.

    If you can’t see the C:\ProgramData folder, you have to enable ‘Show hidden files’ in Windows Explorer.

    Ralf
    Keymaster

    For me the game seems to work as good as before even with the GPU clocked down to run the game at ~30fps, at least in a (very) brief test. Maybe even better since with 20.1.0 the Oculus runtime is less likely to throttle down to half the headset refresh rate.

    There is a confirmed isssue with the latest Oculus software though that seems to cause frame drops for some. Maybe your issue is related to that. They have a hotfix in their public test channel (PTC). You can subscribe to the Oculus PTC in the Oculus Home desktop app.

    Also try to enable ‘FluidSync’ on the ‘Display’ page of the vorpX menu. If you had that on before the vorpX update, it probably got switched off. FluidSync caps the FPS, but can make things feel more, well, fluid since the frame rate is more constant.

    Let me know if you still encounter this issue with the Oculus hotfix.

    More info on the Oculus issue here:
    https://forums.oculusvr.com/community/discussion/83277/newest-update-12-0-0-191-268-introduced-unplayable-frame-drops-in-hmd

    in reply to: How to create new profiles? #191126
    Ralf
    Keymaster

    You can import Descent 1 levels into D2X-XL (http://www.descent2.de). It’s not necessary to make a custom profile to play Descent 1.

    Apart from that: the vorpX help has a short introduction regarding user profiles. Easiest way to access it is probably from the ‘Local Profiles’ page of the config app.

    Fun fact: wanting to play Descent on my DIY headset almost eight years ago was pretty much what sparked vorpX.

    in reply to: vorpX 20.1.0 Preliminary Changelog #191125
    Ralf
    Keymaster

    @ all: Thanks for the kind words. Fingers crossed that nothing else broke while fixing stuff. In a few hours we’ll know more…

    @ Ticklywizard: Still DX11 only, I ran out of time. It’s not forgotten though, will check it shortly.

    @ Flandy: Y-axis: that’s what it’s for. It’s on per default for ‘FullVR’ play style and off per default for ‘Immersive Screen’ and ‘Cinema’. You can adjust it on the ‘Input’ page of the vorpX menu.

    in reply to: Subnautica Below Zero #191124
    Ralf
    Keymaster

    Without having checked the profile: if it’s set to ‘Immersive Screen’, then that’s what the profile author had in mind.

    The ‘Immersive Screen’ play style was introduced about a year or so ago to sit somewhat between ‘FullVR’ and ‘Cinema’ mode, i.e. it allows to create a reasonably immersive setup without having to care about precise head tracking/FOV calibration.

    Judging from the PC Gaming Wiki the game has an adjustable FOV though within a rather large range, so if you don’t mind the tweaking, creating a FullVR setup should be fairly easy. The ‘1-2-3 Game Setup’ guide in the help explains how to do that in three steps. Way easier than you might think.

    Might also be worth to check first whether maybe another user profile for the game exists in the cloud that already implements FullVR.

    in reply to: Nier Automata crashing #191113
    Ralf
    Keymaster

    Interesting find. Works indeed perfectly fine with other headsets, so it has to be the Oculus software that somehow interferes. Odd that that also happens without vorpX, that’s not something one would expect.

    in reply to: How to ‘detach’ the HUD #191112
    Ralf
    Keymaster

    That’s not posssible, sorry. You can scale the HUD and (in G3D mode) change its depth, but it can’t be disconnected from the game window.

    in reply to: vorpX 20.1.0 Preliminary Changelog #191105
    Ralf
    Keymaster

    You can apply a sharpening filter to the final image in the vorpX menu, which in Oculus/SteamVR mode accidentally was also applied to the depth buffer used for Z3D stereo creation. Now the sharpening only gets applied to the final image as it is supposed to.

    in reply to: McAfee – Some Advice Welcomed #191099
    Ralf
    Keymaster

    If you are on Windows 10, you can simply uninstall it. Doing so will enable Windows Defender, which in recent tests is as good, if not better, as the best third party AV programs without being as invasive as some others.

    With Windows Defender there is less risk of false positive detections in regard to vorpX, and in case it does still happen Microsoft at least reacts reasonably fast and reliable when they are made aware of it.

    in reply to: Asking for a G3D list if possible. #191085
    Ralf
    Keymaster

    It’s planned to show this info on the ‘Local Pofiles’ page of the config app alongside with any comments that might have been added whwn a profile was uploaded. One of those things that have been pushed back a few times already because there always seems to be something more inportant. Won’t make into the next release, but I promise to do it early next year.

    in reply to: Is Monster Hunter World really G3D? #191084
    Ralf
    Keymaster

    No problem, glad this is solved.

    Ralf
    Keymaster

    If you aren’t opposed to using the Epic Store, my personal top recommendation as far as new profiles for the next vorpX are concerned is Control (G3D/Z3D). Great game.

    There will also be an official Star Wars Jedi: Fallen Order profile (G3D/Z3D), Remnants from the Ashes (Z3D) will be added, and and if you like racing games, F1 2019 (G3D/Z3D) is worth a look.

    And if by any chance 4X strategy with vorpX sounds appealing to you, get Civilization V (sic!). After only about five years or so on my internal ‘I-should-really-do-this-sometime’-list I finally implemented some DX9 compatibility improvements that allow G3D for the game. Looks absolutely awesome on the cinema screen.

    vorpX 20.1.0 will be out either tomorrow or on Chrsitmas Eve, there still is a bit of profile fine tuning work to do.

Viewing 15 posts - 4,036 through 4,050 (of 10,045 total)

Spread the word. Share this post!