Search Results for 'Get Even'

[Ralf]

The hooking related wish doesn’t really make sense. vorpX already automatically inserts hooks on game start (and destroys them on exit). Otherwise it wouldn’t work (obviously). The only thing in that respect vorpX *may* do afterwards is that in case the normal hooking fails it displays a trouble shooting assistant that among other things offers to install hook helpers. That’s a good thing, otherwise there wouldn’t be an *additional* fallback hooking method.

As far as external docs in addition to the in-app tooltips and notifications are concerned: there are HTML help docs with additional information that can be accessed either from within the config app, a shortcut on the desktop or a shortcut in the start menu. I’ll consider adding even more documentation as soon as I get the impression that more than 0.05% of you guys actually read the already easily available information. ;)

[andreysneg]

24.1 is superb. 95% of games work fine ( Pico4 + Virtual Desktop ). FSR clarity – make me happy .

1) Please make normal PDF manual. Small hints don’t explain anything.

2) Please destroy startup welcome screen ( i must press E every time ) for every game. Where is Option for this ? Ingame GUI dont work for this. Tips still appear, even if you turn it off.

3) Please make normal move immersive screen and cinema – UP, DOWN, LEFT, RIGHT. Example – Virtual Desktop and all others VR programms. So simple move screen. ALT+SPACE Center screen – work only for horizontal center. And i have big emtpy space below. And i must show UP for show all screen . Eyes get tired after looking up for an hour. Virtual Desktop, OpenXR, Steam Vr – don’t help. It is not possible to lower the screen.

4) Please make Automaticaly insert Hooks or insert Hooks before start game. They need to be inserted always. And why does this happen after Launching and Exiting the game ? I think you can insert them immediately before launch. You can make settings in each profile – Automaticaly insert ( and destroy hooks ). And you will save a lot of time and problems.

Thank you.

[Laser]

Get the 7800x3d, on higher resolutions you are mostly gpu bottlenecked but for simulators 7800x3d blows others out of the water and gives a nice boost even on higher resolutions. I upgraded from 3900x to 7800x3d and haven´t regretted it a second.

[conman588]

So obviously moving the screen closer is not the same as making it bigger even though it will then fill up more of your FOV, but I would assume it also strains your eyes more. I do wonder what the screen size and distance in VR mode is, because at the end of the day if you take immersive screen mode, add headlock, add headtracking and you got yourself VR mode. @Ralph what distance and scale would one have to use in immersive screen to get the same properties of the screen as it would be in VR mode minus headlock and headtracking of course? I mean alternatively an option in VR mode to disable headlock and/or an option to customize the zoom for edge peek would be even better, then one could conveniently switch between the two without any distortion or warping.

[0li0li]

Seems like the Vorpx-forced change from <directx forcedx9=”false” /> to <directx forcedx9=”true” /> causes the issue. I have tried manually setting my ingame profile (ingame and via the file) with it being set to read only AND Vorpx set to not change game setting in the menu, and it is now much more stable. This variable is correlated with the game crashing with Vorpx – it’s fine otherwise, I used it before.

That said, even without this code change, it’s still completely broken as I do no get recentering, the vorpx menu, and G3D option is 100% gone for good regardeless of what I do. At least I found a (annoying) way to make something work, but it would not have been remotely as bad if we could simply ignore the local profile.

That’s actually the second time where those imposed local profiles lead to more problems. We really need a way to kill them, or at the very least remove the exe… Renaming is almost never an option (not with legit game copies anyways).

Anyways: Dirt 2 and 3 profiles need fixing or be removed until they actually work.

[Ralf]

The virtual display has all custom resolutions predefined that previously had to be added manually to the display driver to make vorpX work as best as possible, so you don#t have to do that anymore. That’s the original purpose of the virtual display.

I’d rather have left it at that without any further configuration options, but in the end succumbed to various extra wishes. :) What I can’t do however is entirely taking away your own responsibility that comes with the greater than originally planned freedom to tinker. If you don’t want to let vorpX handle things automatically, you should be fully aware that tinkering with the Windows display configuration may get you into trouble if one of the displays is a potentially invisible one.

That said, knowing my audience, A LOT of time has been spent to cover all sorts of potential fatal tinkering scenarios, mishaps and error conditions. So even if you managed to disable your actual monitor while auto switching is disabled (which is not really a good idea) and for some reason also don’t see anything in the headset anymore, on next boot at the latest a working condition will be restored. Sounds like this last resort failsafe mechanism saved your day as intended.

[Cer]

Hi Ralf,
thank you for the answer, but I wasn’t complaining about auto-disabling of the real monitor. I just wanted to point out there can be a situation leaving you without any monitor.
Maybe you can read my post again and check every point as I think they are all valid, but maybe misunderstood. Don’t get me wrong, I just want to help make this great pice of software even better.

For example “hooking while the desktop viewer is active are intended” is sure a good feature if you are going to play games “made” for vorpx, but it doesn’t work for games that should run natively in SBS or just flat on a big screen. Since the desktop viewer supports both, it should work. Well, it does work but not as comfortable as I would like. Why not supporting this by having a profile that tells the hooker not to hook? And going further this way, why not have a profile that switches on the desktop viewer and activates the virtual monitor for me?

What I cannot agree with (or maybe just don’t understand) is, that there is “No need to fiddle with custom resolutions ever again”. How can the virtual monitor know what resolution I want to look at? Even in vorpx supported games I manually choose the resolution depending on the performance of the game, how good the game supports wide screens and if I am playing in imersive or not. I already missed a possibility to define a resolution per game (e.g. as local extended profile setting) before I discovered the virtual monitor.

About the “head tracking issue”: I found 2 settings. One to switch it on and one for sensitivity. I tried for quite some time but couldn’t make it work.

[MarcDwonn]

Please report if the nVidia Ambient Occlusion works in stereo mode. I’ve never been tempted to add AO to The Witcher 1, because it already uses baked lighting. On the other hand i tried out the Far Cry VR mod the other day, and that one really needs some AO because it looks super flat. I briefly thought about nVidia AO, but dismissed the idea as “not compatible” with stereo view.

So yeah, looking forward to hear about your experience.

About modding: i played TW1 fully modded with texture mods and other stuff, and the engine gets a bit more unstable, but it works great in G3D, S3D is perfect, even the particles have proper depth. It was my first vorpexed game i played and i was mighty impressed.

[SavaDude]

Good evening –

Whatever help I could get would be greatly appreciated. I am running a heavily modded Fallout 4: FROST build with the latest and greatest version of VORPX. There are several issues.

1. VORPX hooks into Fallout 4 just fine
2. The Edge Peek does not work – I have assigned it to multiple keys, mouse buttons – no dice.
3. The VORPX In game menu does not work – I have assigned it to multiple keys, mouse buttons – no dice.
4. The right eye on my Oculus 3 does not work. I have run it with Oculus air link as well as set it for a generic headset, a STEAM configuration with Virtual Desktop – no dice.
5. The left eye works fine
6. Even with the FOV set in the INI file to 100, 110, 112, 120, 125 – nothing changes. It is zoomed in so far that it is unplayable
7. In troubleshooting I have:
a. Removed the Fallout4 Upscaler
b. Removed Shadow Boost
C. Turned of all NVIDIA upscaling, sharpening, etc.
d. Set the resolution options to all manner of different things – it makes no difference.

Any ideas you may have would be great!

THanks

[Ralf]

When automatic resolution is available there really is no reason not to use it. The auto computation is a fairly complex algorithm that factors in various vorpX/game settings that may impact the best possible aspect ratio/resolution. Disabling it will often result in less optimal performance.

Even more important are other automatic settings changes, which whenever available for a game typically make sure you get a perfectly matching FOV and/or less graphical glitches. Often these even include things required to get games working at all like choosing the right graphics API or a working AA mode.

You are of course free to dismiss all of that, but please don’t recommend doing so to newcomers. In the best case that makes things harder for no good reason, in the worst case it makes games unplayable with vorpX for average users entirely.

[Altered_Cabron]

Hi Ralf, thanks for the reply. You do a tremendous job replying to everyone here and given the million different ways to get this thing running, this is commendable.

The only way I could get meta quest 2 controllers to be detected was to disable the XBOX controller default option. Then regardless of KB/Mouse or XBOX controllers I have access to the mapped controls, which are great. The place I’m coming up short is knowing which buttons to press to gain access to the less-frequently used controls (ie T for picking up a voice call, or X for using items from the inventory shortcuts, and also tagging with mousewheel when Im in stealth wheel). It’s not obvious to me what those alternate mappings are – even when I cycle between the shift mode and look at the controllers, they don’t seem to exist.

Can I just open this up more generally to ask other users who are running via steamlink and using meta quest controllers what button they press for the inventory items or tagging in stealth. Thanks in advance/

[Altered_Cabron]

Hi Ralf – thanks for the speedy reply, and thanks also for making an incredible mod!
I have read all the documentation and looked far and wide, but couldn’t see this specifically addressed (apologies if its there and I missed it).

I do have my head around using the shift functioning on the second controller to get sprint/escape/d-pad for weapon switching but I’m just stumped about how to use this or what the default mappings are to get to using quick-slot items like the health packs, or even tagging enemies in stealth mode.

As a second question I wanted to ask about the default mapping during stealth mode of hitting ‘F’ which is the upper button on the left quest controller (you have to hold the menu button just below it, to get into stealth mode and from what I can tell drop the other controller and press ‘F’/Y with your other hand to perform hacks). Any thoughts on this, or have I missed something?

[TaunHawk]

I am a determined soul.. must have my Farming Simulator 22 in VR…. After my fourth re-install of vorpX, I finally got everything to work again. Had to setup a new profile and set up all new settings. Took a few hours, but it appears we are back in business for now. I really dislike the “optimize game settings” that vorpX does when the checkmark is not marked in the config options, but there appears to be no way to get things rolling as far as getting “3D Reconstruction: Geometry” to activate in the profile until this is optimized by vorpX a few game start ups. All my in-game keybindings also got reset by vorpX to default, which was really annoying. Eventually I was able to turn off the optimization and setup the graphics exactly how I want it and get vorpX to stop messing with it. Such a fiddly program, but if its what we have to put up with when dealing with non-native vr games, well.. its really the only option for now.

Lesson learned, dont update vorpX to new versions unless you are about to start playing a new game and are no longer using it for another game that is already running perfectly fine as is. Never touch a running system… I always forget this…

[headsetvr]

Since I’ve had a Quest 3 headset recently, i Found that i can not get anything to hook. Even games that I’ve got running myself in the past and games ive seen other people get working. I just tried a reinstall of the beta 23.1 to see if that helps and all i got was getting asked to re-register again again. I’ve even tried using OpenXR instead of the Quest option and no joy there either. It’s bound to be some setting that i’m unaware of but i’m not technically minded so wouldn’t know where to look. Can you help please?

[Boblekobold]

Just tried Metro Last Light Redux (2 euro on Steam this week). It’s impressive. G3D seems perfect so far (First Level). I think the game is far less optimized than Metro Exodus, because it ask a lot to my RTX 4090 (even the best card possible is not enough to get the perfect resolution and framerate on Reverb G2). But it’s enough to be really good.
I played in 2880×2160 ultra (I think I can still raise it a little bit more). I tried 3200*2400, it was visually perfect, but framerate was a bit low ‘^^