I had to come give further props to Ralph and vorpX. I’ve used it for a long time, ever since I got my DK2 when those first shipped. It’s always worked, and been a great tool to enjoy non VR games in VR. I got a Vive now and am going over all my favorites to see how they play now. I tried the direct VR in a few games and it worked great as an easy solution to just tweaking settings like the old days. But when I ran it in Fallout 3 I about fainted.
I have to say vorpX has really, really knocked my socks off yet again. After running the direct scan in Fallout 3, it just feels like your actually transported into the wasteland. The FOV gets set, the position locates you and bam your there… Its damn near perfect 1 to 1. Crystal clear image, the best image quality in an injected game I have ever seen. The vanilla textures even look good in VR! They’re muddy up close but the clarity of the image and the fact that parallax textures now work in 3D and you got a feast for the eyes.
The room scale works so good I’m actually stunned. You can use cover, peek around corners, walk around and browse and loot. Its unreal how good they got it working for this game. This feels as close to a native game as your going to get. Sure there are some issues with UI and CTDs but that’s more a Fallout issue then vorpx. Really need to patch the memory and get some other UI mods to see if I cant solve these few issues..
I was so floored by how amazing it worked that I ended up playing until 5am two nights in a row. I haven’t even tested out mods because I cant resist popping back in to Fallout 3 VR. Its just so damn good, its freaky…. Really guys, if your half a Fallout fan you must try It in Direct VR. Even if you think you’ve played it with older vorpx versions, try it now, you wont be disappointed.
Outlast for some time was a fairly popular vorpX title, there certainly is no general performance issue with it, should run at steady 45fps using a decent resolution (1600×1200) with a much slower GPU than yours.
What I would recommend is resetting your graphics driver settings in the nVidia control panel to default and make sure that antialising is disabled in the game if it has such an option. Some Unreal Engine 3 games suffer a severe FPS loss with vorpX when AA is enabled. I don’t recall Outlast to be among them, but I wouldn’t rule it out either.
More general: although that shouldn’t be necessary for Outlast on your machine, it’s always worth to consider Z3D in games that don’t perform well with G3D. Doesn’t look as natural, but is a lot faster.
Halo 2 reminds me strongly on Unreal 1, escpecially the creatures.
http://www.moddb.com/games/unreal/downloads/s3tc-highend-texture-package
The above is an easier all-in-one download for the textures. It’s over 1gb.
If that is down or slow more choices at:
http://www.oldunreal.com/textures.html
You might find this page helpful:
https://steamcommunity.com/sharedfiles/filedetails/?id=129368243
I had originally set up Unreal for triple monitors so my FOV and other settings were already altered, I just copied the folder from my old computer to my current one – I didn’t really alter the Vorpx settings or make a profile. Just getting a nice FOV for the weapon
I may revisit this, since I would like to play Klingon Honour Guard and DS9 The Fallen. They are also unreal engine games. When I do I’ll upload a profile.
By the way you may still be crazy, but not as far as Unreal on Vorpx goes…
Demosthenes, thank you for proving I’m not crazy!
>Perhaps it is because I use the GOG version and had applied the patch.
Yes! My version is the GOG version, too!
>By the way, you should also apply the high resolution packs to improve visuals:
Yes, I had a look at that website, but was overwhelmed by all the textures. Which ones exactly should I download to make the game faithful to the original but higher resolution? All the ones found on the page you mentioned?
Also, I’d like to know what parameters you changed exactly. Would you mind sharing your profile on the vorpx online profiles? In another post about Unreal, Ralf said “If it would work in 3D, there would be an actual profile for the game.”
Finally, it’s really troublesome to have to use the keyboard every time I die, or when browsing the Unreal menu. Any way to get the xbox controller work there too?
Thank you!
Are you shure this works with Vorpx ?
…uh, yes I’m sure! Why would I lie about this?
Again, what I did is:
1. Update the game to the .227 patch (DirectX 9, not 10 or 11).
2. Create a profile using the DeuxEx profile
3. Copy and rename unreal.exe to unreal_vorpx.exe (or any name you want)
4. Assign unreal_vorpx.exe to the new profile
Good luck, and please post your results here, so Ralf can “un-ban” the game!
p.s. I’m using the non-Steam version of Unreal Gold
Are you shure this works with Vorpx ?
So far i tried the DX10 Renderer for Unreal 1, but VorpX doesnt allow any DX-Dlls in game folders.
BTW: This DX Renderer also supports Deus EX and Rune.
http://kentie.net/article/d3d10drv/page1.htm
Anyhow , it works great with 3D Vision though.
Good news everyone! The original, the one and only Unreal Gold! The action, the music, the atmosphere, the thrills! All of it work pretty well in VR. Just be sure to install the 277 patch here to get the game to work with DirectX 9, and just create a profile based on DeusEx. Oh, and you will need to copy and rename Unreal.exe to Unreal_vorpx.exe or something, since Unreal.exe is already assigned to a hidden profile. Hopefully, Ralf can delete that hidden profile now that the game is officially working!
Oh, and other adjustments you might want to consider: mouse sensitivity to 1, widescreen view (that seems to be what they call FOV) to 120. I’m still a n00b, so if someone could be kind enough to make a better profile, that would be greatly appreciated!
There can be various reasons for hidden profiles. In case of Unreal 1 the reason is that the game only ‘works’ in a very limited way, if at all. I just checked the profile, it’s restricted to OpenGL only, so you can launch the game with the OpenGL renderer. You will need to set the 3D-Strength to 0.0 though. 3D does not work correctly.
If you want to experiment with DX9+ renderers, rename the .exe to anything else and then try to create a custom profile, but I’m quite certain there is no way to make it work in 3D. The engine is so old that the only option for 3D would have been OpenGL, and that doesn’t really work.
If it would work in 3D, there would be an actual profile for the game.
I tried Unreal 1 a long time ago and would have loved to include an official profile. One of my absolute all time favorites. Couldn’t really make it work in 3D myself unfortunately. Since the game isn’t too popular anymore these days I didn’t invest too much time for research though.
You definitely would need a DX9+ or OpenGL renderer. The original DX renderer won’t work for sure.
What I tried was the OpenGL renderer from the last official patch (worked halfway, but 3D was borked) and the Kentie DX10/11 renderer, which worked only in 2D IIRC.
What also should work (but also 2D only) is using the nGlide Glide wrapper. The Glide renderer was the best looking Unreal renderer back in the day. Much nicer skies.
I’ll check the .227 fan patch on occasion, don’t think I tried that one.
Hopefully find the form or some method to actually get this.
With the arrival of new future announced VR versions for Fallout 4 and Skyrim, VR support by using Alien isolation mod, Doom3 mod and bfg edition, silent update for native Dying Light support with Cv1, and the currently developing mod For Half Life 2 VR …
The current situation makes Elder Scrolls Online now, among a few others, one of the new best candidates to play in VR using Vorpx.
The inclusion of 3D Geometry for games based on Unreal Engine 4 and Frostbite engine, would also be an improvement that Vorpx and users, shout out in this times.
Hi,
I’ve just bought VorpX specifically to try Unreal 1 in VR, as I have read several reports that people got it working in VorpX with Patch 227.
After I ran the game, VorpX would not attach to the executable. I have tried to create specific profile for the game, but it said that the executable is already used in a different profile – Unreal.
I have searched for profile called Unreal, but have not found any. After some digging, I’ve found out VorpX contains many hidden profiles to intentionally prevent people from playing certain games.
I am completely perplexed by this decision, as:
A, There are reports from people that actually had the game running in VorpX, before it was actively disabled by hidden profile.
B, There are other games running on the exact same engine, which are supported – Deus Ex for example.
Therefore I am feeling blatantly cheated, as I’ve just thrown out money for VorpX out of the window, to not only find out that game I want to play does not work, but that it does not work because it was made so on purpose.
Is there any way I could get a refund at least? My order at the point of writing this message is about half an hour old.
Thank you
I can’t really say much re Pimax specifically, sorry. vorpX supports Steam VR, how good that works on a given headset mostly depends on how well Steam VR is implemented for that headset. One issue with the Pimax in the beginning was that it doesn’t have a proximity sensor, which lead to the screen going black after a while in vorpX. That has been addressed, otherwise I can’t say whether there maybe are other glitches in their Steam VR support. Haven’t heard anything in a while yet though, so I guess it’s OK now. Maybe someone with a Pimax can chime in.
Games are very, very different regarding how they render graphics, so there is no simple answer to your profile related questions. In some cases it’s enough to copy an existing profile of a game based on the same engine. Works fairly well for Unreal Engine 3 games for example. In other cases that is not possible at all. Completely unsupported games are shown in 2D.
The performance impact varies heavily, mainly depending on the 3D mode that is used by vorpX. There is a mode that renders everything twice like native apps (called G3D), which costs about 50% +/- 10%, and there is a post fx 3D mode (called Z3D), which is a lot faster, but doesn’t look as good. On top of that there is an additional VR-specific performance impact compared to monitor 3D since in a final step the image has to be rendered to the headset.
The first thing you should do whenever a Direvt VR scan does not work as expected is restarting the game. As said before, Unreal engine games have the habit of changing the memory locations for rotation/position/fov, which also may vary from PC to PC. Restarting the game ensures that the memory layout is as close as possible to what the Direct VR profile for the game in question expects.
Apart from that:
If you use anything else than Windows Defender as your antivirus, get rid of it. Some AV programs may prevent Direct VR from working correctly.
The same may be true for recording software that hooks into games. So if you do your recoding via software, check whether maybe starting the game with/without recording software makes a difference.
Same for anything else that can hook into games (CPU/GPU utilities of any kind, messengers etc.).
In general: the most important aspect of Direct VR is the 1:1 head tracking. If the FOV scan fails for you, you can almost always compensate that with one of the other methods that vorpX provides to address FOV. For all three Bioshock games for example it can be done quite easily with the Game Settings Optimizer in the config app.
There probably isn’t much that can be enhanced in regard to the Dishonored scan profile, sorry – it’s pretty much optimized to death.
Like the message during the scan says the scan process is not 100% reliable by nature, there always is a chance of failure and it may even be the case that Direct VR doesn’t work at all for a specific configuration.
Unreal Engine games (like Dishonored) are a prime example of that since the memory locations used for FOV/rotation/position change on various occasions, making the whole thing even more difficult than for other games. I will check whether it is maybe possible to reproduce your issue here, but can’t promise anything. The warning message during each scan is there for a reason. :)