-
AuthorSearch Results
-
Jan 16, 2016 at 10:50pm #96359
Topic: OutLast Not Working
in forum Technical Support
vrgamegirl1984ParticipantI just bought VorpX so I could play Outlast, but when I try and start outlast it just starts on the PC, not on the DK2. I got Crysis 3 working, (It looked like crap, all zoomed in made me cross eyes on G3D. But anyway, I thought I would try Outlast. Please help! I Have the latest Oculus run-time and the newest vorpx because I just bought it.
Jan 8, 2016 at 6:30pm #96197In reply to: Crysis 2 does not work
GrumdarkParticipantCrysis 1:Yes, I have made the right step to run under DX9, and reconstruction geometry is represented in the game, the problem is that it presents hight graphics problems.
z-modes seems to work properly.
Previously,I did not happen this problem in the past versions(g3d).Crysis 2:Yes,actually only z-buffer, but the problem is that it does not perform the injection, vorpx has a bug, and collects and sends information to Microsoft dialog automatically.
PD:Just to clarify:
I’m used to perform these steps usually for games that only support DX9 geometry. Apart administrator modes also check soil and other potential problems in case troubleshooting before reporting.
In this case, almost certainly I think there is a problem with the latest version vorpx.
CheersJan 8, 2016 at 4:25pm #96191In reply to: Crysis 2 does not work
RalfKeymasterCrysis 1 has to be run in DX9 mode for Geometry 3D like indicated in the vorpX start message and the Game Optimizer. You have to add “-dx9” (without the quotes) to the start options in Steam, DX10 is Z3D only. For Crysis 2 please try to change between the different DirectX version that the game offers. Can’t remember ATM, but not unlikely that only one of them works, the game is Z3D only.
Jan 8, 2016 at 4:21pm #96190Topic: Crysis 2 does not work
in forum Technical Support
GrumdarkParticipantI bought and downloaded crysis 2 version steam, to play it with vorpx, after seeing that is in the list of supported games, however, the game does not work at all for me.Any help with this?
On the other hand crysis 1 (steam version)has broken my reconstruction 3D geometry in this latest Vorpx version, with important graphical quite a while problems with several games from the list of supported vorpx.
Any idea how to fix this?Nov 1, 2015 at 5:11pm #90901In reply to: The zoomed-in problem
feathers632Participant@Ralf:
Although Vorpx hadn’t been sandboxed I think some windows files had and that seems to be the cause. It’s stopped corrupting now.
Still don’t know why vorpx isn’t setting the FOV on games using the optimiser. It’s saying it has but not reflected in the game. I’m setting FOV manually at the moment.
IPD really made a difference with Metro LL but I didn’t realise the FOV wasn’t being set in other games like Arma 3 and Crysis 3. Can only go so far using the vorpx FOV/image zoom so I have to manually edit the FOV for these games. Arma 3 looks correct since manually editing FOV to 120.
My IPD of 67 I got via my Oculus rift profile (after doing the calibration.
Serious Sam 3 looks great on vorpx.
Nov 1, 2015 at 1:49am #90879In reply to: The zoomed-in problem
feathers632ParticipantI’ve been spending time with Crysis 3, Arma III and other games and all have this zoomed in view that makes them unplayable. Adjusting FOV to 120 doesn’t help here and IPD also doesn’t make any difference.
So it seems like the only way I can play these games is with cinema mode which isn’t as immersive and I can’t look all around me.
I’m really starting to feel like I’m wasting my time with it. Trying to reduce the zoomed in view on every game. I use the game optimisations and in some cases manually edit the game’s FOV but the games still don’t look right.
Does it make a difference which Nvidia graphics driver? I’m using an older one: 350.12
The whole thing is starting to really annoy me because it’s so far removed from the visuals I get with native oculus games.
Oct 30, 2015 at 2:19pm #90833In reply to: The zoomed-in problem
feathers632ParticipantOne very important thing regarding the “zoomed in” effect, that almost everyone misses, including me, is calibrating IPD in vorpX’s ingame menu. So do calibrate your IPD following the on-screen instructions, trust me…it does wonders to the resulting image both for FOV and 3D depth and presence feeling.
I tried a few games like Crysis, Fallout 3, BF3, BF4 etc and no matter what methods I used for improving FOV, including FOV enhancement tools and vorpX’s FOV options and zoom, it still felt a bit “zoomed in”, especially on close range objects.
So after finishing the whole BF3 campaign using Flawless Widescreen set to max FOV, Letterbox 1 aspect ratio, 2D FOV-Enhancement and 85 % image zoom, I started BF4 (same settings) which had better 3D definition but after playing for a while, the “zoomed in” feeling became kind of annoying and broke the immersion. Besides that I also got some blurry vision for half an hour after playing, until my eyes readjusted.Then I started messing with Calibrate IPD option from page 2 (display) and found that 64.00 which is the default average for most males was wrong, so I re-calibrated using the on-screen instructions and ended up at 60.75 where the cross was perfectly visible and most clear (I do not suffer from any vision issues, I see very sharp, near and far).I was stunned by the result as the “zoomed-in” issue was completely gone, the FOV was just like as in an Oculus native supported game like Alien Isolation or HL2. I was stunned even more when I instantly noticed a huge improvement to 3D depth, the distance from my face to every object in the 3D environment was very clear which is a huge boost for presence feeling. And after playing for a couple of hours without any pause, when I exited, the blurry vision was greatly diminished and it completely disappeared in 1-2 minutes.
So this is the most important thing to do besides setting the FOV. You might end up higher than me, closer to 62-63…in my case, might be the VR Cover cloth which I applied over the DK2 and puts a bit of higher distance between the lens and the eyes, although the VR native games didn’t gave me any problems with the 64 IPD default setting in Oculus profile. I’m not sure how that is possible, maybe it differs from one game to the next, but the result is amazing.
Looks like you’re right! Every game has been massively zoomed-in and even after I spent hours last night following the advice to change FOV in game, in vorpx or by modding game ini, it made absolutely no difference. So after finding your advice here I went in to metro ll and adjusted the IPD (haven’t used the in-game calibrate yet – i simply increased the IPD and now the game doesn’t look zoomed in anymore. Also changed the z-buffer mode and increased 3d effect. So many people are posting here about zoomed-in problems and the standard advice to mod FOV isn’t working. Well done for sorting it out!
Oct 25, 2015 at 3:18pm #90597Topic: vorpX restart loop
in forum Technical Support
titi974ParticipantHello :)
I’ve just bought the driver and installed it. I’m running win10 x64, using latest nvidia beta drivers (358.78) and latest oculus runtime (0.8) and whenever I try to use vorpX well, it keeps restarting.
I mean, for example if I run the desktop viewer or a game like crysis 3, 10 seconds after I run the program, it restarts and I have to click again on the window for the image to update on the DK2’s screen ! It’s pretty annoying … any ideas ?Oct 25, 2015 at 12:16pm #90582In reply to: vorpX 0.9.0 Available Now
RalfKeymaster@ Karlor : Not sure if I understand the question. What do you mean by ‘spectator other screen display thing’? If that means the mirror window, you should be able to use it with just a little performance impact. Normally there should be no need to adjust settings to use it.
@ Nikolay : In general the raw FPS are about 10-20% lower than before due to the far more complicated rendering pipeline that was necessary for the Direct Mode. but that’s countered by the async timewarp, which makes things still look smoother. Can’t really imagine Mirror’s Edge at 120fps in G3D on your 960. With a GTX970 it always ran around 60 before in the start area. Crysis 3 didn’t have G3D before, 15-20 still sounds quite low even for a GTX960 in Crysis 3. With a GTX970 the game runs at about 35-40fps in the start area (ship in rain) when using Geometry 3D. Low settings IIRC. From testing various GPUs I would say a GTX970 is a reasonable recommendation, it’s also what Oculus suggests for the Rift in general.
You could also take a look at the Reddit thread linked below for advanced tweaking, a similar advanced tweaking sticky will follow here shortly:
vorpX 0.9 performance tip: custom 8:9 resolution
byu/eVRydayVR inoculus@ Cy : That sounds odd, especially since it happens in games that run perfectly fine at 75fps. Anything special about your setup (SLI, Optimus or uncommon in any other way)? Can you make a video of this? A frame by frame analysis might be helpful to at least understand what’s happening. I could provide you with an FTP account to upload it.
Oct 25, 2015 at 10:52am #90576In reply to: vorpX 0.9.0 Available Now
NikolayParticipantIt’s strange… Everyone says about performance improvements since update, while I have severe performance impact. I have GTX960, 8GB DRAM. For example, Crysis 3 runs up to 100 fps on High settings without VorpX, and I had just about 20-30% performance impact while using VorpX 0.8.0.1 with Oculus Runtime 0.6.0.1 (Extended Mode). But after update the game runs just on ~15-20 FPS, and even lowering graphics settings to lowest doesn’t help at all! It seems that main problem is Geometry 3D mode: after I’ve switched it off to Z-buffer, performance got up to 30FPS on high settings and started to react to changing graphic settings adequately. What’s worse, same issue remains even with pretty old games with Geometry-3D support, like Mirror’s Edge: prior to 0.9.0 update the game used to run extremely fast: 120 FPS and higher with Geometry-3D activated, but now it runs 20-30 FPS only. Async Rendering set on “half” helps though, but it still doesn’t give even 75 FPS except disabling Geometry-3D which bumps it to 150+ FPS. I’ve tried Oculus Runtime 0.6.0, 0.7.0 and 0.8.0.0, updated NVidia driver to 358.78, tried to recover it back to official stable 358.50 – and I can confidently say that’s not the cause.
Oct 24, 2015 at 12:12pm #90502In reply to: like a big Monitor
ClayParticipantThat is not true!
Crysis 3, Elder Scrolls Skyrim is on the list… and it works only in 2D!Jun 5, 2015 at 9:06pm #87962In reply to: The zoomed-in problem
adisplinterParticipantOne very important thing regarding the “zoomed in” effect, that almost everyone misses, including me, is calibrating IPD in vorpX’s ingame menu. So do calibrate your IPD following the on-screen instructions, trust me…it does wonders to the resulting image both for FOV and 3D depth and presence feeling.
I tried a few games like Crysis, Fallout 3, BF3, BF4 etc and no matter what methods I used for improving FOV, including FOV enhancement tools and vorpX’s FOV options and zoom, it still felt a bit “zoomed in”, especially on close range objects.
So after finishing the whole BF3 campaign using Flawless Widescreen set to max FOV, Letterbox 1 aspect ratio, 2D FOV-Enhancement and 85 % image zoom, I started BF4 (same settings) which had better 3D definition but after playing for a while, the “zoomed in” feeling became kind of annoying and broke the immersion. Besides that I also got some blurry vision for half an hour after playing, until my eyes readjusted.Then I started messing with Calibrate IPD option from page 2 (display) and found that 64.00 which is the default average for most males was wrong, so I re-calibrated using the on-screen instructions and ended up at 60.75 where the cross was perfectly visible and most clear (I do not suffer from any vision issues, I see very sharp, near and far).I was stunned by the result as the “zoomed-in” issue was completely gone, the FOV was just like as in an Oculus native supported game like Alien Isolation or HL2. I was stunned even more when I instantly noticed a huge improvement to 3D depth, the distance from my face to every object in the 3D environment was very clear which is a huge boost for presence feeling. And after playing for a couple of hours without any pause, when I exited, the blurry vision was greatly diminished and it completely disappeared in 1-2 minutes.
So this is the most important thing to do besides setting the FOV. You might end up higher than me, closer to 62-63…in my case, might be the VR Cover cloth which I applied over the DK2 and puts a bit of higher distance between the lens and the eyes, although the VR native games didn’t gave me any problems with the 64 IPD default setting in Oculus profile. I’m not sure how that is possible, maybe it differs from one game to the next, but the result is amazing ;)
May 12, 2015 at 7:15pm #87630In reply to: Outlast – Everythings way to big
GrumdarkParticipantThis is my configuration,It could serve as a possible help.
English is not my native language, sorry.Crysis 1:
Crysis 1,uses a different model for hands/weapon and you can not scale its size for now.In some games, weapon fov(or similar)can help to be(scalable with separation 3d) after,in menu vorpx, but it is not the case of crysis.I use this setting to crysis:
Apply optimizer vorpx entry.
Force dx9.
Make 1920×1080 resolution, window mode off, motion blur off
Low shadows and any other possible graphic options(recommend for better performance)Open console ingame(push key º)and enter:
con_restricted = 0
cl_fov 90
You can enter more fov from play,but not recommended for my,cause fisheye effect.
However,we introduce a little more in the ingame menu fov vorpx,(3d fov enhancement)for several reasons.vorpx ingame menu,page 1:
Cinema virtual mode:Off
3d reconstruction:Geometry (required force dx9 in this game for now)
3d fov enhancement: 0.45 (help with more fov,and better fov support in the interior vehicles)
Separation (3d strength):1.30 (this changed world scale,I always prefer to do so after the fov adjustment,and zoom)
Camera height modifier:1.90 to me (change camera height,help with aiming,height depending player,useful with positional tracking on)
Focal offsett:0.03page 2:
Fix chromatic aberration:On
Fix black smear:ON
Game ui / scale:0.42 (scale and resize HUD and menus in geometry)
Game ui / depth:0.85
Aspect ratio correction:Pixel 1:1
Image zoom:0.85
2d fov enhancement:0.00
vignette scale:1.00page 3:
optional positional tracking:On/off
Save changes.Possible issues: large hands and arms.
Only possible “help” at the moment,
console, r_DrawNearFov 50 or less, notably hides the length of the weapon,in normal aiming.
weapon not correct scale, but more hidden inside the camera.
Sorry my english.
Regards.
LaserParticipantOk so I was trying to use the Crysis64.exe instead of Crysis.exe, after changing to 32bit version it hooked up correctly.
The funny thing is that as I suspected the fps isn’t great but for some reason it still runs much smoother than most games I played. Others usually require that 75fps to get smooth headtracking but this one is still playable with much less.
Anyway thanks for the help, Crysis looks really nice with geometry 3d and I recommend anyone who has this game and vorpx to try it out. No major glitches found during brief testing, only some black bars(?) during cut scene but while player controlled looked really nice. :)
OculusRiftRocksParticipantif SBS support was offered would that make crysis 3’s official 3D support would work, because currently when i select it in the in game menus i saw 2 pictures per eye.
also i think human revolution has official 3D support, and would likey do SBS, i think in that scase the guns would be fixed, as currently when you do 3D with vorpx there is a double gun issue making 3D less enjoyable than 2D.
-
AuthorSearch Results
-
Search Results
-
Topic: OutLast Not Working
I just bought VorpX so I could play Outlast, but when I try and start outlast it just starts on the PC, not on the DK2. I got Crysis 3 working, (It looked like crap, all zoomed in made me cross eyes on G3D. But anyway, I thought I would try Outlast. Please help! I Have the latest Oculus run-time and the newest vorpx because I just bought it.
Topic: Crysis 2 does not work
I bought and downloaded crysis 2 version steam, to play it with vorpx, after seeing that is in the list of supported games, however, the game does not work at all for me.Any help with this?
On the other hand crysis 1 (steam version)has broken my reconstruction 3D geometry in this latest Vorpx version, with important graphical quite a while problems with several games from the list of supported vorpx.
Any idea how to fix this?Topic: vorpX restart loop
Hello :)
I’ve just bought the driver and installed it. I’m running win10 x64, using latest nvidia beta drivers (358.78) and latest oculus runtime (0.8) and whenever I try to use vorpX well, it keeps restarting.
I mean, for example if I run the desktop viewer or a game like crysis 3, 10 seconds after I run the program, it restarts and I have to click again on the window for the image to update on the DK2’s screen ! It’s pretty annoying … any ideas ?
