Search Results for 'Ice Age 3'

[Karlor]

I don’t notice any slowdown when I play with Z3D, so I guess that’s the way to go for this one. I only really want G3D for positional tracking, but if you can get it working in Z3D then that’s cool too. I have a feeling down the road there will be memory patches, and other mods to help with frame rates. Bethesda games usually have a lot of trimming that can be done behinde the scenes and in a few months hopefully it will have better management over resources but who knows untill they really start digging into the game files.

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

[Contrabardus]

I’m running Windows 10 64 bit, latest AMD Catalyst Driver, and 0.8 OVR runtime. I’ve had VorpX since it launched and it’s always run fine until now. This latest update is absolutely refusing to do so.

I’ve uninstalled and reinstalled it at least fifteen times, and it refuses to launch after the install process finishes.

It goes through all the dialogue boxes without issue, all the bars fill up and I’m not getting any errors during the actual install. I get to the final screen that asks me if I want to start VorpX immediately, with “Finish” instead of “Next” on the button at the bottom of the box.

After that attempting to launch the program immediately freezes it up. It doesn’t matter if I try to launch it right away, or if I close the dialogue box, restart, and try to launch it separately.

I even went so far as to uninstall the registry stuff, but still no go. It installs everything, tries to launch when it’s finished, and then hangs immediately and stays that way.

I’m running Windows 10 64, I’ve got Oculus Runtime 0.8, and the latest stable AMD driver installed.

The Rift is running and the service is fine. It plays demos and works fine outside of this.

Going into task Manager after it hangs tells me that Setup/Uninstall is not responding.

Attempting to delete VorpX even after ending the hung task tells me that vorpControl.exe is the problem. It’s still being used by the system even after an uninstall and won’t delete. Restarting the computer lets me get rid of it.

I have restarted and run the uninstall program after that, and it gets rid of the file then.

If I let it install, restart, and then try to get it to launch, I just get an unending process that never shows up in task manager. I just get the spinning mouse cursor icon that tells me Windows is trying to do something indefinitely.

Attempting to uninstall VorpX in this state once again leaves vorpControl.exe behind and undeleteable until after a restart.

Something is massively screwed up here and I can no longer get VorpX to run at all. Not even with a completely fresh install.

I’ve tried everything, installing DirectX, putting it in a different directory, and nothing works.

Also, I’m on Windows 10, so reinstalling OVR 0610 isn’t really a viable option to correct this problem, especially with no guarantees it will accomplish anything. I know it’s technically possible for me to install that runtime, but it requires the installation of old drivers and running in compatibility mode, it’s not really an option here.

I have 0.5 installed and the runtime switch. Yes, I’ve tried removing that thinking that it might be getting in the way already. That isn’t the problem here. I’ve also tried hooking it on with the old runtime. None of that worked, so I’ve got no good reason to believe installing 0.6 again will either.

I’m at a bit of a loss here and this is very frustrating. I really wanted to try Fallout 4 in VR, and now I can’t play -anything- with VorpX because the new update has completely cocked itself up on my system and refuses to run.

Any ideas on how to fix this?

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

[gapper4]

That_Guy225 wrote:

hello,

i am running windows 7 x64 with oculus runtime 0.5.0.1
hd radeon R9 270x
16 gigs ram
amd 6100 6 core processor 3.3 GHz

i am trying to run space engineers and i know my oculus works, the test worked just fine and i ran a few games with it just fine. i tried the troubleshooting steps as well as advice from the forums, but when i run it this is what happens

1. the screen flickers back and forth on my oculus and monitor then it pauses
2. the game displays on my oculus with the message “vorpx init failed. vorpx will not start correctly, check the cables.. etc etc”
3 i press “ok” then the game works on the oculus as far as the vorpx message letting me know about the FOV and the shortcuts work as well, i can press the middle mouse button to show the full screen for menu use but the headtracking does not work.

i am not sure what to do, i have tried all different ways from the first setting my oculus to main display, to setting it as the secondary and changing the setting in vorpx config, unplugging and plugging everything back in, different ports, restarted multiple times, reinstalled, and still get the same thing no matter what i do. any help would be great

Bad news my friend. I was very much looking forward to 0.9 with DK2 runtime 0.7 for SE but no joy. It crashes on start-up…

[cha55son]

I still can’t get it to work properly. Works fine when vorpx control is not running. I don’t have much running on this computer. (I can list running services upon request) I’ve also disabled the steam overlay to eliminate that concern.

# Scenario 1
1. Start Arma 3 (non-admin)
2. Works (no hmd support, of course)

# Scenario 2
1. Start Vorpx control (non-admin)
2. Start Arma 3 (non-admin)
3. Fails

# Scenario 3
1. Start Vorpx control (admin)
2. Start Arma 3 (non-admin)
3. Fails

# Scenario 4
1. Start Vorpx control (admin)
2. Start Arma 3 (admin)
3. Fails

When it fails I get no error message, the Arma logo just disappears.

[Blakestr]

Version 9.0 is a godsend, despite what all the haters are saying. But i’ve noticed that Geometry mode seems to lower my framerate drastically…I’m talking about going from 114 fps to 10 fps. I know it is more hardware intensive, I am looking for ways to continue using geometry without losing so much performance…any tricks or optimization?

Specifically I am using Garry’s Mod. I find that Geometry is the only mode that gives a real sense of presence but maybe If someone can share their Z-Adaptive settings (I get graphical glitches/artifacts) then I can try that to…

Basically, post your graphical settings.

FYI I’m using a gaming pc that runs the Witcher 3 on Ultra with average 45fps

Thanks Ralf for all your hard work. Keep at it, stay positive. You’ll rarely hear things from the customers who had no problems.

[CylonSurfer]

Ralf wrote:

@ Cylon : Occasional jerkiness: check your framerate with [ALT][F]. There are two values now. Game FPS and Direct Mode FPS. The Direct Mode FPS have to stay at 75fps at all times or you get judder. Game FPS should at least be half the headset refresh rate (~40 fps for the DK2), better 60, and ideally 75, of course.

The easiest way to achieve this is obviously lowering graphics settings, but you can also lower the game resolution now, as vorpX doesn’t have to run at the headset resolution anymore. You can even choose 4:3 resolutions now, which can help in some cases as less stuff is drawn that is thrown away later. And if you wish, you can even experiment with custom square resolutions which can be created in the nVidia control panel.

Another new and particularly easy way to optimize direct mode performance in demanding games is syncing the game framerate to exactly half the headset refresh rate. This can be done on the display page of the ingame menu, setting is called Direct Mode Framerate Sync.

Thanks for the suggestion Ralf – sadly it has no effect on the odd jerk I experience.

I double checked both The Direct Mode FPS and Game FPS. Direct Mode FPS is at a solid 75FPS, it never dips. Game mode goes from around 66FPS to the full 75FPS depending on what I’m looking at. The odd thing about the jerk is that it happens in areas where I get a full 75FPS on both Direct Mode and Game FPS…

Setting Direct Mode Framerate Sync to ‘Half’ causes the games to become a blurry mess. I only get nice smooth game play with it set on full.

I also tried the custom aspect ratio settings after you mentioned it and reading about the 8:9 ratios on Reddit, its a nice performance boosting tip and very nice new feature. Sadly it does not help with the odd jerk I get.

What I do not like is that the jerk happens in all games across the board, even ones that achieve 75 FPS at all times. It’s not the stuttering we experience with low FPS, its an actual jerk, like the game freezes for a millisecond, in GTA V for example everything appears to stop for that very brief amount of time, including the passing traffic. As I said in my previous post, its almost like everything is playing catch up every few frames or so.

[feathers632]

Karlor wrote:

Stop stalling and buy it ! Its only $40.. Rift cost $300+.. pc $1000+… Games are $60 a pop… buying a great program, and the only program, that let’s you use all those together for only $40 seems like a good deal to me… just do it lol

I’m just concerned about wasting money if it doesn’t work for me. I persuaded a friend to buy it last year when he bought his DK2. He hasn’t had any luck getting it working with his games. I very rarely pay full price for a game anyway. GTA V is currently on sale below the price of vorpx. A demo would have been a great way to test it out before spending.

[Stereoman]

I’m having some issues with my DK1 setup and 0.9.0, the images are crossed eyed like the left screen is showing what the right screen should and vice versa this is happening in both Dirt 3 and in VorpX Desktop Viewer, I’ve tried recalibrating my IPD profile, even deleted the profile entirely and created a new one, I’ve tried selecting Do not use an oculus profile in VorpX and manually inputting my IPD, I’ve tried altering settings in game as well, not sure what’s going on, just removed 3dvision driver just incase that was interferring, it made no difference.

[Ralf]

Yes, it was removed. The idea behind it was indeed to address FOV issues, but it clearly was the worst idea during the whole development. Due to the distortion it introduces it can potentially make people sick.

There are many more ways to address FOV issues, ranging from perfect to OK. Please check the Essential Game Hints in the help for details if you haven’t done so already.

One particularly easy new way is setting your game to a 4:3 display mode (like 1280×960 for example), which is now possible and then zoom out a few notches (ImageZoom). In many games that is a nice way to address FOV issues quickly. Not 100% perfect but definitely better than the logarithmic distortion.

[Stephan]

Error messages from the website:

Sorry,

This account has reached the limit of 3 download(s).

If you have any questions, please contact Customer Service

[WolfTwo]

There is progress. It looks like the version error stops appearing. However, VorpX still doesn’t detect the HMD and will not start. Here is the dialogue from the X86 window.

OVR::DeviceManager – initialized.
OVR::DeviceManagerThread – running (ThreadId=0xBAC).
CameraFactory starts
[TrackingManager] Entering tracking thread
OVR::Win32::HIDDevice – Opened ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
Manufacturer:’Oculus VR, Inc.’ Product:’Rift DK2′ Serial#:’H1DE4CC6NHC4KM00Y100′ Version:’212′
OVR::SensorDevice – Closed ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
OVR::Win32::HIDDevice – Closed ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
[TrackingManager] Broadcasting new HMD count = 0
CameraFactory::inspectCamera starts
OVR::Win32::HIDDevice – Opened ‘\\?\hid#vid_2833&pid_0021#7&e632a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
Manufacturer:’Oculus VR, Inc.’ Product:’Rift DK2′ Serial#:’H1DE4CC6NHC4KM00Y100′ Version:’212′
CameraDK2::Initialize starts
Repeated 2 IMU samples: 2000 2 0
Lost 2 IMU samples: 5004 2 4
Lost 3 IMU samples: 4002 2 5
CameraDK2::Initialize: sending GET_CUR
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST probe GET_CUR succeeded
Device reported frame index 1, format index 1, frame interval 166666
video frame size 0x58200, payload transfer size 3000
PROBE SET_CUR to fmt 1 frm 1 int 166666 frmsiz 360960 xfersize 3000
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST probe SET_CUR succeeded
COMMIT SET_CUR to fmt 1 frm 1 int 166666 frmsiz 360960 xfersize 3000
IOCTL_OCUSBVID_EXECUTE_VIDEO_STREAMING_REQUEST commit SET_CUR succeeded
Lost 2 IMU samples: 3002 2 4
Lost 2 IMU samples: 3002 2 4
Lost 2 IMU samples: 2001 2 4
Lost 4 IMU samples: 2002 2 6
[TrackingManager] Broadcasting new HMD count = 1
CameraFactory::inspectCamera ends successfully

And VorpX won’t give me the time of day.