Archives

Homepage Forums Search Search Results for 'fallout'

Viewing 15 results - 1 through 15 (of 1,137 total)
  • Author
    Search Results
  • #223253
    Ralf
    Keymaster

    The gamepad override affects actual gamepads as well as emulated gamepad input.

    Its main purpose is to ensure mouse based head tracking can work while using a gamepad in games that can’t handle simultaneous mouse and gamepad input. This issue exists for both actual and emulated gamepad input in affected games.

    In case of Fallout 3 simply leave everything at default (Really!). After running the memory scanner vorpX does not use mouse emulation head tracking anymore in these games, so that gamepads works natively and motion controllers work in gamepad mode.

    There is no need to tweak anything at all in this respect for Fallout 3/4/NV. Reset the profile to default, run the memory scan and you are good.

    #223251
    pschimpf
    Participant

    Thanks Ralf. Couple of things:

    1) I switched to Gamepad input mode and things ran pretty well (outside of Fallout 3’s occasional confusion in not recognizing there is a gamepad attached). In that mode I noticed that the scanner always fails rotation unless I set Override XBox controller to Full or Partial, which is no big deal (but see item 3). However, when running outside of VorpX Fallout 3 adds options to the Pipboy when a gamepad is in use. The most important, to me, is (X) to drop an item. When gamepad input is disabled, those options are not displayed and an item is dropped using RMB. With VorpX I never see these options whether I am using Gamepad or Keyboard/Mouse input. As a result, I recently switched back to Keyboard/Mouse input and mapped (Shft-Rclick) to RMB so that I could drop items.

    2) The downside in keyboard mode is navigating the pipboy screen and dialogs with NPCs. I’d rather not use head tracking and right joystick to navigate those, although it is tolerable if I turn the right joystick sensitivity way down. This is why I wanted to map something to up, down, left, right. Shft-Rstick was logical, but didn’t work (Rstick would be even more logical for me if we were allowed to map that). I thought maybe this was the not-allowed mapping of Rstick extending to broken mapping of Shft-Rstick, so I tried mapping Shft-A and Shft-B to up/down and that didn’t work either. So I’m unable to map anything to those keys. When running outside of VorpX I have to make sure the cursor is pointed away from anything for those to work, so when I’m in VorpX I make sure to gaze away or use RStick to get the pointer out of the way. Meta Link does not filter any controller functions. It’s hard to see how it could be a Fallout problem because it doesn’t know where key codes come from. My best guess would be that Vorpx is generating keycodes that are different than what the keyboard generates for those. Can you verify that you are able to map something to the cursor keys?

    3) This is not particularly relevant, but I think I’m confused about the difference between setting gamepad override to full and setting input mode to keyboard/mouse. I thought the former would only apply to using an actual gamepad, which I’m not using. But then why does my scanner always fail unless turn that on, or set input mode to keyboard/mouse? Does it also apply when controllers are set to gamepad mode?

    #223113
    Ralf
    Keymaster

    Different list. When geometry gets drawn both a vertex and pixel shader are active (actually to be precise often more than that, but those are the only ones we care about here), so both can be utilized do define special stuff.

    Usually it’s best to start with vertex shaders, especially for HUD or shadow. Try pixel shaders if that doesn’t work, e.g. because it catches too much. Effects like unwanted DOF, motion blur etc. on the other hand are often better manageable via pixel shaders. Very different from game to game though. The only useful universal rule is: try vertex first.

    In case of Fallout 76: if nothing has changed in a recent update, all HUD elements – at least those I am aware of – should be definable via vertex shaders.

    #223109
    takatori
    Participant

    Fallout 76 has the same issue. Yes a profile update was downloaded by VorpX yesterday and used the “import” function in VorpX to revert to default but the problem persists in Fallout 76.

    I had used the shader editor before due to some issues with shadows and water (hid what wasn’t showing correctly) and tried to delete all my settings but is there a way to get those to revert to default as well?

    pschimpf
    Participant

    I’m trying to program the shift functions of either joystick to be the up, down, left, right keyboard keys. The in-game menu accepts them, but they do not work on either joystick. I’ve tested in places where the keyboard keys work, such as looting a body and talking to an NPC. I’m playing Fallout 3, where you can’t exit an NPC conversation without scrolling down and selecting a particular response. This is very tedious because the down arrow on the dialog selections is tiny, and difficult to land on with a joystick-controlled cursor. It’s bad enough that I have to revert to an XBox controller to play effectively. I am a newbie here, so apologies if this has been answered. I searched the forums but did not find anything. Headset and controllers are quest 2.

    #222852

    In reply to: Metro Exodus dx11 G3D

    J0hnnieW4lker
    Participant

    Hi, I would really like to play **Metro Exodus** using the G3D DX11 profile, but it’s not working. I’ve tried reinstalling it, but that didn’t help. Can someone please assist?

    This is a great title, and since it’s listed as working with the default G3D profile, it would be nice to get it running properly.

    I am using a generic 3D display config, and I tested it with another game, Fallout: New Vegas, which worked fine. BTW Metro Exodus Enhanced Edition has the same problem.

    #222830
    rbturcott
    Participant

    Hi,

    Using PC with Valve Index, no VR controllers or Xbox type controller. So trying to use keyboard and mouse.
    On starting Fallout NV, things seem to start and hook in. Steam VR starts and the game boots to the start menu but is displayed in a window to the left. In the centre is a panel with a couple of hints and to the right is some more help in another panel.
    Only Vorpx functions appear to respond to any keystrokes or mouse in the headset.
    Mouse disappears outside of any Vorpex function or panel.
    There is no way to do anything outside of Vorpx fuctions at this point. Game is displayed on my regular monitors, partially across two monitors. Alt-Tab works, sort of, to get out of VR, but mouse is gone, keyboard sort of works outside of VR. I have to log out or reboot to get mouse functionality back.

    Plugged in an Xbox controller to see if that would make a difference, but no luck.

    Note, I do not know if this is specific to the game, as this is the only game I’m using it for. It used to work years ago and I’m only just revistiing this game after quite some time.

    Any help would be appreciated.

    Thanks.

    #222806
    Boblekobold
    Participant

    There is already a topic with a lot of them :

    Geometry VR Game List.

    You can check engines&games here :
    https://rjkole.com/gamestuff/engines/index.php

    Or looking for the game on the forum.

    Or just trying it (the only way to be sure).

    From my personnal experience, best profiles are :
    Originals Bioshock 1&2&Infinite
    Originals Metro (I tried 2033 it has perfect G3D and 6dof) and Redux versions (I tried Last Light Redux and it was perfect but I recommand a top end graphic card with this Redux version, without even knowing if it’s better than standard)
    The ascent (and some others Unreal Engine 4 games) works well.
    Black Mesa (&Xen), probably Portal and Dark Messiah.
    People say Dishonored, Titanfall 2, F.E.A.R, Mirror’s Edge, Fallout 3, etc. works well.
    Probably Clive Barker’s Jericho & Undying too.
    Originals Stalker works with good G3D but without adavanced lighting (DX9 only).

    Kingdom Come Deliverance, Metro Exodus and Farcry Primal works well enough (and so probably Cry Engine games like Prey 2017 / Crysis 1-3, and Snowdrop Engine games like Facry 2-5)

    Even if concerning Metro Exodus, I prefer Z3D during most of the game (except bunkers&spiders which are great in G3D) in order to have raytracing, at least on Reverb G2 (no compression, so it’s stunning).

    Some Z3D profiles are very close to G3D (Atomic Heart, Frontier Of Pandora, Unreal Engine 5 games seems to work great from my experience).

    I may be wrong, but I think most DX9 games probably have perfect G3D, and some DX11 games too.

    #222719
    Ralf
    Keymaster

    26/01/13 | vorpX 25.1.5 has been released

    Another maintenance update. Addresses a couple of input glitches, comes with a rewritten host-exit that better handles exit crashes with Meta’s OpenXR since a recent Meta Link update, makes alternative hooking usable for more games, fixes a rare DX9 issue, has a bunch of profile fixes/updates and more.

    Click here for a list of noteworthy changes

    • vorpX: keys wrongly blocked in some DirectInput games (e.g. Fallout 3/NV).
    • vorpX: the tracking center hotkey also ensures foreground and input focus.
    • vorpX: ALT+TAB and back could occasionally confuse key state tracking.
    • vorpX: fixed cursor clipping in some older games (e.g. Metro 2033).
    • vorpX: headset audio device switching did not work anymore.
    • vorpX: D3D9: better unhooked surfaces handling, e.g. Venetica ALT+TAB crash.
    • vorpX: improved host exit, cleaner in various games and with Meta OpenXR.
    • vorpControl: folder exclude handles symlinks (e.g. latest EA Desktop).
    • vorpControl: minimize runtime windows option supports latest Quest Link.
    • vorpControl: alternative hooking working for more games.
    • Cyberpunk 2077: improved sync between mod-portion and vorpX.
    • Tron 2.0: .ini changes weren’t applied anymore since a while.
    • Dishonored 2: scalable HUD added.
    • Dragon Age Origins: deal with GOG version 2-core lock.
    • Dragon Age II: deal with GOG version 2-core lock.
    • Farming Simulator 25: Fixed a Z3D issue related to vehicle mirror count.
    #222674
    pokkla
    Participant

    I recently got back to playing Fallout New Vegas (last played Feb ’24). However, it appears that vorpX now disables the “E” and the “ESC” keys. No other keys seem to be affected. I can run the game without vorpX and all the keys work fine. I can also run other games with vorpX, like Skyrim SE and Fallout 4, and all the keys work fine. I use MO2, so I tried FONV native (no MO2 and no mods) and I got the same results as running with MO2. That is, the keys work fine without vorpX. But, those two keys are disable with vorpX running. I have done all the noob fixes too, like rebooting the computer, etc.

    In FONV, I can remap the action key “E” to something else (like “P”) and the action key works as planned. However, I can’t remap the ESC (menu) key and it is critical to game play. vorpX works fine itself displaying great VR once up and running. It’s just that I can’t use the E or ESC keys.

    I have had vorpX for many, many years and used it with many, many games, and this issue is a head scratcher. Is there a different hook/method I should try? Any suggestions would be appreciated.

    #222610

    In reply to: Linux support?

    ryanshedy
    Participant

    I personally feel he’s missing a big opportunity here.

    People are crying to move away from windows and now bazzite has took off a bit people are experimenting. I’ve been running my VR setup on my steam deck with amazing results. I get better performance on steamOS VR than I do on windows 11/10.

    I really think Ralf should look into porting into linux or even just giving us a way to run it via proton. There are a lot of people attempting it but they can’t get it to hook. I haven’t tried but I’m using ALVR with steamVR and id love to play fallout New Vegas in VR. It just doesn’t seem worth it to have to partition my drive and install an entirely new OS just for 1 game. Plus performance also takes a hit.

    I don’t think he’d even have to do that much considering everything is in place, we just need help on getting it to hook correctly with proton

    #222566
    Ralf
    Keymaster

    25/12/20 | vorpX 25.1.4 has been released

    This maintenance update mainly focuses on an annoyance affecting mouse/keyboard players in some games that upscale the image to the monitor size. Under certain circumstances that can lead to vorpX’s stereo cursor being shown at a wrong position, making it difficult to hit buttons in menus etc. Various reasons for this super annoying glitch are now covered. The remaining will follow later.

    Apart from that there have been a few more fixes and a new profile for Farming Simulator 2025 with automatic FOV and a scalable HUD.

    Click here for a list of noteworthy changes

    • vorpX: Improved stereo cursor rendering in games that upscale their output.
    • vorpX: Z3D could break in some games after taking off the headset.
    • vorpX: some games could crash with Windows display scaling set to 150/175.
    • vorpX: some games could crash on audio device change (25.1.3 regression)
    • Farming Simulator 2025: new profile with HUD scaling and DirectVR FOV.
    • Farming Simulator 2022: DirectVR FOV update.
    • Fallout 4: DirectVR FOV scan was broken after a game update.
    vrenjoyer1
    Participant

    Hello,

    I’m trying to get vorpx to run games on a HP Reverb G2. At first I tried to play Half-Life 2 using SteamVR but it didn’t work very well. The actual game screen appeared small in the distance, although it rendered there in stereo 3d. Once the game started it glitched out and frame rate dropped so bad I could barely move the mouse. Then I read that SteamVR is not advised for WMR headsets. But how does everything work now in the Oasis era? Will OpenXR, which I found out is the recommended method work still? Do I need to download it from somewhere, or is it included in windows?

    I tried to change settings in vorpx to openxr and launch Fallout 3, but the headset doesn’t even turn on. Has anyone tried to get the Reverb G2 to work with vorpx with the Oasis driver?

    Thanks for the help!

    Demu
    Participant

    OS: Windows 10 latest with ESU
    AMD driver: 25.10.3 – 25.12.1
    GPU: XFX RX 6900XT (Both OC and non OC tested)
    CPU: 9800X3D
    RAM: 32GB DDR5-6000
    Module: SteamVR – OpenXR
    Headset: PS/VR2 with PC adapter – Displayport connection.
    VorpX: 25.1.2

    I’ve noticed that the app is constantly crashing when using VorpX on any game. Tested Fallout 4, Cyberpunk, Stalker Anomaly, Left 4 Dead 2, Ghost Recon Wildlands, Factorio, 15+ others.

    The Virtual desktop starts fine and works fine(usually, sometimes VorPX will attempt to hook vorpDesktop and timeout), until the moment I try to actually play a game. Game will usually start, but inevitably crash after less than 5 minutes. SteamVR reports ‘ IPC Namespace Unavailable ‘ and AMD driver reports that the driver has crashed. Notably, the driver crashes to the Virtual Desktop and in rare cases, crashes out of the VR experience outright.

    This happens only with VorpX. SteamVR home works fine, mods for Cyberpunk like RealVR work great, so it’s a very specific VorpX problem with the headset.

    Effectively this appears to make the software completely unusable under Windows 10 at this moment.

    Hope this helps you ascertain the issue Ralf. I can provide additional info and tests if you need them, to hopefully help you get some more customers for the software.

    antoineplu
    Participant

    I have the following hardware: RTX 3080, Windows 11, Meta Quest 3, and a 5 GHz router, but I’m not sure it supports Wi-Fi 6.

    I’m connected to three monitors; that might be a lot, but even when I disable them, I don’t really notice any change.

    I can connect Meta’s Air Link without much trouble, though I sometimes get an error because the 2.4 GHz band seems to be missing — yet the connection still works.

    I try to launch Kingdom Come Deliverance 2, but I get lost in the settings. I can start the game on the PC, but it never launches the display in the VR headset.

    I’ve tried many things, and it’s quite confusing for me to sum up all the (likely) wrong manipulations causing bugs. The whole setup feels rather erratic. I even noticed that the game’s settings (in 4/5 resolution) would reset when I launched it.

    I tested with Fallout 3 to see if I could at least make another game run through VorpX, and that worked quite well.

    Could you share any feedback, general advice, or essential steps to make this game work properly?

    —————– (version original de mon post en français)—————-

    Je possède le hardware suivant : rtx3080 Windows 11 Meta Quest 3 Un routeur en 5 GHz, mais je ne suis pas convaincu qu’il est Wi-Fi 6
    Je suis connecté à 3 écrans, c’est peut-être beaucoup, mais même quand je les désactive, je n’ai pas vraiment l’impression d’un changement.
    Je parviens sans trop de problème à connecter Air Link de Meta, j’ai parfois une erreur car la bande 2.4 GHz semble être absente, mais la connexion se fait.
    Je tente de lancer Kingdom Come Deliverance 2, mais je m’y perds dans les réglages. Je parviens à lancer le jeu sur le PC, mais jamais à lancer l’affichage dans le casque VR.
    J’ai essayé beaucoup de choses et c’est assez confus pour moi de récapituler toutes les (probables) mauvaises manipulations sources de bugs. L’ensemble me paraît assez erratique. J’ai même constaté que le paramétrage du jeu (en résolution 4/5) sautait quand je le lançais.
    J’ai testé avec Fallout 3 pour voir si j’arrivais quand même à faire tourner un autre jeu avec VorpX, et cela a été un succès sans trop de problème.
    Pourriez-vous me donner des retours d’expériences ou des conseils généraux, ou des impératifs absolus pour réussir à utiliser ce jeu ?

Viewing 15 results - 1 through 15 (of 1,137 total)

Spread the word. Share this post!