Search Results for 'Ice Age 2'

[Ralf]

Not sure if anyone is interested in this, so ignore if you already read enough CV1 first looks.

I’ll keep it brief. After playing around (better: working) with the CV1 for a few days now I think Oculus made the right decisions overall.

Most important thing in my book: yes, FOV is a bit smaller than DK2’s FOV, but you wouldn’t notice without having both side by side. My guess is they tried to find a compromise between maxed out FOV and minimized screen door effect. I think they pretty much hit the sweet spot. Obviously that’s a matter of personal preference, so your mileage may vary. For vorpX a slightly lower FOV is a good thing BTW.

Lenses: not much I can add to the lens disussion. Clearer image overall, but the fresnel lens flare is quite obvious, especially in dark scenes. So far I’m undecided whether the advantages outweigh the disadvantages for me. It’s probably something one can get accustomed to. On the other hand I had no real complaints regarding the DK2 lenses. Ask me in four weeks for a final opinion on this one.

Head phones: didn’t use them much so far, but unless you are a hardcore audiophile you probably will be satisfied. Also they are easily removable, so whether you want to use them or not, no reason to complain here. As far as I’m concerned not having to deal with another cable outweighs any potential quality concern (which I don’t have anyway).

Tracking: didn’t encounter any issues so far. Tracking volume seems to be a bit larger than before, which is obviously a good thing. Doesn’t matter too much in regard to vorpX though.

Comfort: Huge step compared to DK2, provided you use the headset mainly yourself. Once adjusted it just fits perfectly.

Overall: Not a revolution, but a very substantial evolutionary step compared to DK2. Certainly large enough that DK2 owners do have a reason to upgrade if the headset itself is all to consider.

[Ralf]

vorpX is mainly programmed in C++ (main application) and C# (config app and a few backend tools), also a bit of PHP on the server side.

The profile authoring is done via an ingame GUI that contains the most important/common options. Some things were left out to keep this GUI as comprehensible as possible.

So, no programming language involved. But to create a profile from scratch you still need a grasp of what matrices, buffers, shaders etc. technically mean in the context of Direct3D. So you should have at least a little insight into the inner workings of computer graphics.

Personally I programmed my first 3D-“engine” almost 20 years ago (getting old I guess, feels like yesterday…) in Macromedia Director, which really wasn’t meant for that at all back then, and without any of that fancy D3D/OpenGL stuff that does half the work. Every polygon carefully hand-transformed so to speak. ;) You don’t need to go that far though.

[VRISHERE80]

iankemp wrote:

Okay, I enjoyed G3D games with VorpX alot, so I look at Unreal 3 Engine FPS, which are not supported yet and try them with renamed game exe. Here are my results and begging to Ralf to make them supported because of problems with steam and FOV, when renaming.
My FOV recommendations with them: The official recommendation is 120 FOV at 1920×1080 Pixel 1:1 Distance Zoom 1.00
With that settings you have mostly a good perspective, but massive overhead to the sides and blurry image, because you can see only a third of the picture. So I try to “calibrate” it with 90 FOV and 1600×1200 / 4:3 resolution.
90 FOV: Distance Zoom 0.56
or
95 FOV: Distance Zoom 0.60
This looks the same than 120 FOV at 1.00 Zoom, but without overhead and a much clearer graphic (more ppi).
Renaming: There are a couple of UE3 Profiles with different features. I tested with BorderlandsPreSequel.exe and ADVGame-Win32-Shipping.exe (Deadfall)
Both offer positional headtracking.

Now the games:

Bulletstorm (ShippingPC-StormGame.exe)

Ingame graphic settings I set shadows and Post Processing to low.
Resolution to 1920×1080 (4:3 gives black bars)
To set FOV use this Tool, because of crypted inis:
http://community.pcgamingwiki.com/files/download/580-bulletstorm-ini-editor/
to edit the ini’s:
FOV
1. Go to %USERPROFILE%\Documents\My Games\Bulletstorm\StormGame\Config\ StormCamera.ini
2. Change to the desired FOV.

Framerate
1. Edit %USERPROFILE%\Documents\My Games\Bulletstorm\StormGame\Config\StormEngine.ini
2. Change MaxSmoothedFrameRate to a higher cap; alternately, remove the frame rate cap entirely by setting bSmoothFrameRate to false.

Mouse Smoothing (for proper Headtracking)
1. Edit %USERPROFILE%\Documents\My Games\Bulletstorm\StormGame\Config\StormInput.ini
2. Find bEnableMouseSmoothing and to ‘false’ to disable mouse smoothing.

You also need to calibrate Headtracking manually per VorpX Menu: Fokus something in “real life” and slowly shake your head left and right and notice how it stays in your view. Then do the same ingame and edit the HeadTracking value.

My G3D rating: 8/10

very little lightning issues, some auto head movement when walking and fast gameplay makes it a little nauseous. Iron Sight you need to aim between the dots, its playable. Great 3D-Effekt.

Nearly the same settings with Bulletstorm ini editor with:
Alien Rage Unlimited (ShippingPC-AFEARGame.exe)

This game has some strange light sources in G3D, so I only recommend Z3D.

Homefront (HOMEFRONT.exe)

The FOV settings ingame only works for Multiplayer, not the Campaign (only in first mission). There is a Homefront FOV Changer: http://community.pcgamingwiki.com/files/download/487-homefront-fov-changer/
But that only works with the HOMEFRONT.exe, so we need a profile for that.

G3D, positional-tracking works (turn of DX11 ingame, restart), but many issues especially with shadows. So turn down shadows ingame, Post Processing and turn off frame limit and mouse smoothing in the game menus. Weapon sights are good playable with red dot weapons. Easier for the eye with Z3D.

My G3D rating 6/10. Too many graphical problems with g3d, but playable. +1 with the FOV changer.

Medal of Honor (2010) (moh.exe)

The Campaign is UE3 Engine, so works great (Multiplayer is Frostbite). Documents\EA Games\Medal of Honor\Config\MOHAEngine.ini
bSmoothFrameRate=false
MOHAInput.ini
bEnableMouseSmoothing=false
The G3D looks amazing with very little lightning issues, but overall nearly perfect, but…
The FOV is 55. Again there is a FOV-Changer for the original.exe:
http://community.pcgamingwiki.com/files/download/389-medal-of-honor-2010-fov-changer/
So… VorpX specific profile needed.
G3D rating: 9.5/10 possible if getting FOV to a playable view

Santum 2 (SanctumGame-Win32-Shipping.exe)

Wow, that was a surprise. It’s a steam only game, so you can’t rename it so easily, but after I get it to work with the Deadfall profile (ADVGame-Win32-Shipping.exe), the game works flawlessly in G3D, with all graphic options maxed out, even shadows and lightning stuff and keeps a clean graphical image. Even FOV adjustable in the menus. Easy setup, looks great, very nice to play in VR.
\Documents\My Games\Sanctum2\SanctumGame\Config
SanctumEngine.ini
bSmoothFrameRate=false
SanctumInput.ini
bEnableMouseSmoothing=false

G3D-rating 10/10

Singularity (Singularity.exe)

Looks amazing in G3D, but yeah, bad FOV…
Needs Flawless Widescreen or Widescreen Fixer Tool to fix FOV. So not with renamed exe.
G3D-rating 10/10 (with better FOV)

Section 8 Prejudice (S9-Win32-F.exe)

Untested, because it has a launcher and can’t rename the game.exe
FOV settings per ini:
http://pcgamingwiki.com/wiki/Section_8:_Prejudice#Field_of_view_.28FOV.29
bSmoothFrameRate & bEnableMouseSmoothing like usual.

Rainbow Six Vegas 2 (R6Vegas2_Game.exe)

Very narrow FOV and not changeable, enjoyable in a cinema view setting. Now the UE3 Engine begins to look old and outdated
Maybe it helps to fiddle around with Widescreen Fixer:
https://www.widescreenfixer.org/
Very good G3D Effekt.

@Ralf: All the above called exe just need a copy/paste UE3-profile.

How the heck do you get medal of honor to work it just fails to start in steam when i rename it. I’m getting so sick and tired of this bs

[Ralf]

Considering that it’s the “DirectX Game Memory Management Service 2” that causes the issue, you could also check your GPU mem consumption. Just a guess, but playing a game with vorpX requires considerably more GPU memory than playing a game without vorpX.

With a recent GPU with >3GB video memory that shouldn’t be an issue at all in Skyrim, but maybe still worth to check in case you use extra huge hi-res texture packs for example.

There is a nifty little tool called nVInspector that allows you to monitor GPU mem consumption and a lot more.

[jhondidfool]

So, everything was fine until I updated to the newest nvidia drivers.
Then, for some reason, my Runtime decided it would not detect my DK2, so I reinstalled and fixed that issue.
Since then I’m getting BSOD about dxgmms2.sys ONLY when using Skyrim with VorpX.

I’ve tried everything I could think of, and it has not served any purpose; on the other hand, I have seen this library has been causing problems in Win 10 (The OS I use, Pro version) since as early as October, maybe before that.

10220 seems to be the Windows build that started it all, but I’ve had a newer version for a while and no problems until that point. “dxgmms2” standing for “DirectX Game Memory Maanagement Service 2”, and being such a widespread issue, one would think either MS would do something about it (they haven’t) or it would affect most games. Oddly enough, in my system, Skyrim + VorpX seems to be the only thing that triggers the BSOD. I can play Skyrim on screen and I can use VorpX with other games, even with FO4, which uses a more modern version of the same engine.

There is one fix, however, that has proven to work completely, and it is to install the last Win8 NV Drivers released before DX12 release. While this would be great if I didn’t use an OR, Runtime 0.8 needs a later version which, I have tested, still has the problem.

This clearly is MS’ fault, not Ralf’s, but, still, I’d like to ask you, Ralf, if you could take a look into it and possibly avoid calling this service since it has proven to be problematic.

Thanks.

[adisplinter]

That’s a nice trick. Thanks a lot man, I tried every other possible solution to launch Far Cry 4 with VorpX and it crashed at start-up every time. Disabled Uplay overlay, gone offline, disable Steam overlay, MSI afterburner, antivirus, everything…VorpX desktop shortcut for better hook chance…nothing worked. I almost gave up, re-enabled all overlays and tried your solution, resuming Watcher after the loading bar passed 50%…VorpX hooked, launched campaign, tweaked settings for perfect image…works flawlessly.

Also I might add that Far Cry 4 is a good game to be played with VorpX:
– minimum zoomed-in effect due to high FOV setting, especially combined with Letterbox 2
– very well optimized, runs great oh high settings
– visible HUD in-game on DK2 thanks to VorpX’s Game Settings optimizer for Far Cry 4
– very nice experience with driving, gliding, combat
– great graphics, atmosphere, physics…it’s a Far Cry game after all

[Ralf]

The 8:9 portrait images you are seeing are the goal of this. This is basically how native apps work, rendering an 8:9 image for each eye that does exactly cover one half of the Rift screen.

This doesn’t make sense for Virtual Cinema Mode though, just for full VR. For games that you want to play in Virtual Cinema Mode using normal widescreen resolutions is the right thing to do.

BTW: You can also use any other resolution now in full VR mode now. A good way to get part of the performance/quality enhancement of custom resolutions is using 4:3 resolutions like 1600×1200.

I do that quite often since it’s possible. Provides a quick and easy way to get many games working in full VR without having to deal with FOV at all. Just select 1600×1200 (or any other 4:3 res), zoom out a few notches in vorpX ([SHIFT][MOUSEWHEEL] or ImageZoom in the ingame menu) until the FOV feels right, and you’re good to go. Not perfect in every case, but a nice way to get games working as fast as possible. For example if you just want to briefly check something out.

[Gladi8or]

davidmi58 wrote:

I tried this with Fallout 4 by setting the 960×1080 in the ini. It worked and looked nice but the HUD and cursor is unusable. Is there another trick I can try?

The lock picking screen is missing with a custom resolution. I tried dishonored (g3d), outlast (g3d) and bioshock infinite (z3d). They worked perfectly with 1600*1800. The image quality was very nice.

[Sheepwolf]

Ralf wrote:

The black bars that move in from the outer edges when you sway your head are a side effect of the timewarp.

The “side effect of the timewarp”

Now I know what causes that delay when you move your head and the picture tries to follow your head (there’s no actual delay on the game itself, but the entire “screen” takes some extra time to follow your head)

I really can’t imagine why the picture can’t just be fixed on screen. I’m sure there’s a good explanation, but for someone who doesn’t fully understand how the Oculus works, it does look like something very easy to fix… just fix the picture on the screen, and let the tracker do the mouse movement. But what do I know… :P

You can really see the entire picture moving slower than your head (you don’t even need to do fast head movements, even moving slowly is noticeable, specially if you look at the game’s HUD) I wonder if this actually causes some extra headaches…

It does give you some disadvantage when playing CSGO (or any other FPS)

Everything else works fine, only the timewarp effect is the problem…

Ralf, is this something you might be able to fix in the future? Or does this have to do with the Oculus runtime itself?

Thank You!

[mainframecn]

When VorpX is running, every game i try to start crashes. No exceptions.
As far as i can tell the crash happens always when the game initializes the graphics.

Here’s an example of the eventlog entry. All refer to the same faulting module.
Faulting application name: SpaceEngineers.exe, version: 1.0.0.0, time stamp: 0x564f666a
Faulting module name: 9ea08b0b-0.tmp, version: 0.9.1.0, time stamp: 0x56436dee
Exception code: 0xc0000005
Fault offset: 0x0000000000063e2b
Faulting process ID: 0x10d8
Faulting application start time: 0x01d124333e47c2b6
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\SpaceEngineers\Bin64\SpaceEngineers.exe
Faulting module path: C:\Users\MAINFR~1\AppData\Local\Temp\vorpX\9ea08b0b-0.tmp
Report ID: 1a589114-6211-4ab9-a25c-d51e13ab02f3
Faulting package full name:
Faulting package-relative application ID:

My setup is:
Windows 10
Nvidia 780ti, 350.12 driver
OR SDK 0.6.0.1 (service running in comp.8 mode)
VorpX 0.9

I have no virusscanners, DX-hooks of any sort or other programs running as described in the “Basic Trouble Shooting – Please Read This First!” post.
Unless you count steam, but that’s a mandatory program.

I’ve tried uninstall and reinstall of VorpX and running as an admin.

I’m open for any serious suggestions.

[FormulaRedline]

I wanted to report that I’ve been playing Fallout 4 basically exclusively with the Oculus and vorpX (went through he tutorial in 2D until I could see all the parts of the HUD to make sure I wasn’t missing anything when switching to 3D).

The Z3D mode works surprisingly well. Not the crappy Z3D I remember from the “old days” of Nvidia 3D Vision with Cryengine games. I cranked the seperation in the vorpX settings and moved the slider all the way to the foreground. Depth is great, there is some Z3D induced shimmering around close foreground objects (e.g. your weapon or close in characters). The HUD seems to be put at the depth of the background. That actually helps make it easy to aim and read though at the cost of some of the text being a bit disjointed at times as it rolls over different objects. Nothing that will stop your from reading it.

The FOV setting are a bit tricky. Basically, you have to change it in 3 different files, as explained in detail here:
https://steamcommunity.com/sharedfiles/filedetails/?id=551069501&tscn=1447077828

I settled on 130 FOV for first person with 1:1 Pixel mode and the image zoomed all the way in. If you want to be able to see the compass at the bottom of the screen, just zoom the image out a bit (just a few Shift+Mousewheel clicks) though I find that makes terminals a bit harder to read. Maybe you can compensate with less FOV. With these settings, I tend to zoom out (middle mouse button) for crafting, building, or trading where I need to see the full HUD across the entire screen.

The FOV command in the ~ console actually controls the FOV for your gun and PIP Boy. So you can set the PIP boy “size” independent of your game FOV, which is nice. You can make it readable no matter game FOV you use.

I would also recommend taking out the mouse smoothing and adjusting the vertical mouse sensitivity as described in that same Steam guide (linked above) before adjusting your headtracking sensitivity in the vorpX settings.

So a few things to tweak, but it works great! Thanks for the early support, vorpX!

[Avol]

I try to play in Amnesia A Machine for Pigs using game settings optimiser, but it didn’t use all my field of view — I have big dark lines over and under the screen.
I’ve checked different resolutions — 1900×1080, 1900×1200 and even 1280×1440. With the last choice I have also lines on the left and right with small screen at the center.
How to maximize image size to play in DK2?

[smokedog]

on 0.7 none of my bi games would open due to battleye on 0.8, all start and display apart from A3 with the non bi launcher now it works for arma2 and OA this way i use arma launcher by head, it does a2 and a3 you just show the game directory and the game.exe with that I choose the non battleye .exe this should not effect anything as the original launcher uses the same .exe but fires the batteye one instead, in one of the a3 updates a while back it changed from starting arma up and having to enable BE and then restart the game to this way they have battleye start first which caused the rift to not work on 0.7 due to the above dll that was mentioned it sees the rift as a head track cheat device was in the messages I got on screen.

[Orion_uk]

Hi all :)

Is there a way to keep head tracking ON but NOT have it effect your steering when driving? It has taken me AGES to get vorpx, DK2 & GTA 5 working as I want it but cant get past the final phase of the car/bike etc ‘auto steering’ when i move my head! If I turn head tracking off the its like I am not ‘in’ the game but am sitting a few rowes back at the cinema and can see the edges of the ‘movie screen’ instead :(

I just want to be ‘in’ the darn game and control the car with my 360 controller NOT my head!!!

Any advice plz? Thank you :)

[feathers632]

adisplinter wrote:

One 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!