Search Results for 'Inside'

[>>>Finlander<<<]

That “burning” was mainly caused by malfunctioning watercooling unit :/

but I didnt notice it before because nothing else cant run this PC 100%…

Believe me… last thing that you want to get when using VR is exploding radiator inside your PC and Total VR jam and after seconds Bluescreen inside DK2 :D

[Grumdark]

This 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.03

page 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.00

page 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.

[NipOc]

I think this is a problem of the game itself.
Some games like skyrim draw the hands and weapons really big, because it looks better on a 2d monitor.
Ralph said to this problem in a thread about skyrim problems:

For some reason hands and weapos are rendered separate from the rest of the world and they aren’t easy to detect inside vorpX.

[shadie]

My friend got FSX working quite well (please note: This isn’t the steam version.)

What he did was run VorpX with FSXRift and everything should work out just fine :)

Pretty straight-forward plug’n play :)

NB: FSXRift is for proper headtracking inside FSX :)

[Kimi]

Maybe i have a solution for those with doublescreen which also doesnt see the Vorpx menue inGame when you have set your DK2 as Primary and your LCD as secondary:

I had the same issues: Crashed after Update, Double Screen, No InGame Menü.

Solved these for me with:

1) Set DK2 into HMD Mode first. Started Flawless widescreen and GTA5 Plugin.

2) Started “ConfigVorpx” without Admin Rights (normal double click)(First time i had the “crash report also”, second time worked for me) Restored all Games in TroubleShooting Menü and unchecked “Run as Admin in Config Menue”. Apply & Close.

3) Vorpx wrote “you are currently running in HMD … etc”. Just left that Dialog and went to TaskManager where are killed the Vorpx Task. Both closed (32 … and the “non” 32 :D)

4) Then i started it again with running as Admin (windowsAdmin right click run as admin..) and set my HMD to Extended (I´m Running DK2 as Primary in nvidia Systempanel, LCD as second) it worked in the background as usual (sry, German lang question following: @Ralf … StartVorpx läuft wohl automatisch an wenn man die Config startet ne? Is gut so, bloss nicht ändern :D Beim Ausführen direkt, also “startvorpx” stürzts mir immer ab :-/ ob mit oder ohne WinAdmin.

5) Then i took on my DK2 and startet GTA5 directly as Admin from inside the Rift (Before i started it from the LCD and switched automaticlly into the DK2) Now i could see two Dialogs: First one was “Vorpx will not run correct with D3D9.DLL (have ReShade and SweetFX installed), just clicked on OK. Then another Dialog appeared but i can remember what it said. just clicked ok :D sorry :D

GTA5 starts normally and i saw the vorpx ingame menue for the first time :) Changed some settings like image zoom, but deactivated virtual cinema and set chromatic aboration fix on, image zoom for me at 0.67 – 0.70. Format: Letterbox1 was standard. i set it to 1:1 … looked better for me.

Ok. Well now, no crash, everythings fine. But: without Headrolling … its horrible :D Staring to the front and moving the mouse to look around is inside the Rift “german said”: SCHEISSE! XD” … but its playable and looks very good i think. Better than i thought. Would be nice if GTA5 has a direct Rift Support.

Sorry for my bad grammatic btw :)

Ralf? kann man das nicht implementieren? irgendwie? den Headroll mein ich :D

[Karlor]

I was mad the first time I had to do it to lol but its not a big deal after you get it down. xpadder is good but I like joy 2 key better, is just easier to get things like double buttons working for me. 2 tips are to do all your set up outside the rift and also it may be easier to set up a profile with kb+m how ever you like with what ever keys you like inside joy 2 key. Then change the in game set up with your new custom mapped pad. Sometimes this is easier then going back and forth trying to match the mapping.

[Karlor]

One more tip is to go into the game settings and turn up the mouse sensitivity inside of the vehicles. I put mine up past halfway. It makes turning your head in the rift more responsive while inside something.

Pretty much the only thing it needs now is a mod for the HUD. In game there is a “safezone” setting that adjusts the HUD but it only goes so small. Maybe something a modder could adapt sort of like the FOV mod.

[Karlor]

OK I had a bit of a hiccup last night and I got it working again. I had tried a million different things and then for some reason my Rift wouldn’t get recognized after I was all done messing around. This is what I did and it fixed it for me. I do not know if it was what I did fixed it or it just healed itself lol if you mess it up worse or get confused or turn something off that your not supposed to I’m not listening.

Anyway:
Go to search under start menu. Type in msconfig.exe. I selected selective start up. Hit ok, then restart when asked. Then when It started back up It worked. It also could of been something I tweaked inside of this page but I think all I did that mattered was hit the selective start up. Don’t ask me how or why it worked it just did for me. Hope it helps someone :)

[Ralf]

This was indeed added more or less for you. I somehow doubt that this will be played very often by anyone else.

I certainly won’t stop you buying another copy. :)

The game has a Game Optimizer profile which forces 1920×1080 (yet stretched) which you should apply in the config app. The vorpX settings are dialed in to work best with this forced resolution. Together with a bit of aspect ratio mangling inside vorpX this way it looks as good as it gets for a game without widescreen support.

[Karlor]

I get what your saying here and it would be cool to be able to dial it up or down inside vorpx. Although I haven’t had to much of an issue with it. I use a game pad usually so for those instances I can make up for it with just using a joystick to fine tune the aim if need be. I could see some games, depending on how they handle the aiming speeds could make it a real pain if you wanted to rely on head movement(realism) over just navigating with a controller.

Outside of vorpx:
You could maybe try setting up a key press that after a certain amount of time of being held(such as to aim) it switches to a faster mouse setting. You might be able to figure out how to do this outside of vorpx with xpadder or joy 2 key maybe. There also might be a way to hotkey some system mouse speeds then you could set up a way so when you aim it also presses the system mouse speed hotkey you set up. Sort of an automatic toggle thing.

[Karlor]

Oh also inside of vorpX (del) go over to where you can set what is assigned to the game pad buttons via what vorpx assigns when you select handle game pad internally. Go into these buttons and change them to something that dose not ever get used in the game like (.) that way it minimizes the interference of vorx and the game pad works inside the game engine itself.

[Karlor]

There are 2 main things I have noticed that makes it do that when you get close to an object. The first and most important setting you need to get set so you feel comfortable and that is IPD. the rift comes with a ballpark setting of like 75. But a ball park is pretty big, its like buying a one size fits all pants and expecting them to fit great. My IPD is 62.2. Getting this set correctly is A #1 on the list of things to do. Next is go stand next to something until it gets the double effect going then reduce your 3D strength inside vropX menu until you feel comfortable. Works for me every time.

[Karlor]

I had this happen with my DK2 before. Im not sure why it stopped but I was messing with alot of settings and experimenting around with all kinds of input devices and other stuff.

Solution:
Open vorpx config, go to general, then under device settings inside of general you can select what device vorpx uses. In your case pick dk1. Hope that helps

[mgabb]

I’ve managed to have Metro2033 work somewhat:

deactivated Oculus
launched Metro2033
set the game for Dx9 and quit
reactivated Oculus
relaunched Metro2033

now the mouse cursor is still stuck in the left area of the screen, yet the keyboard allows by continuously tapping over the menus to continue a game or start a new one, at least I can progress: inside the game everything works, although the mouse pointer is limited (in menus only) to the left area

[Neodementia]

I just finished Bioshock Infinite with dk2 and vorpx which was one of the greatest game experiences of my life. This was the steam version, running windows 7 on an evga nvidea 640 with 8 gb ddr2, with graphics set to very high. I used the following setup:
In game settings:
Start Bioshock Infinite without vorpx first.
Go to options, graphics, set field of view to max.
Ensure game is fullscreen, and 1920X1080.
Start New Game, enter the light house, exit game.
(Ensuring ini creation, and a good point to trigger autosave to jump in and out of game while adjusting)
Startup Vorpx.
Right click tray icon, Configure Vorpx, General Settings,
Under Disaply/Monitors set to Show on Rift DK2 and disable Aero on game start.
(I have had alot of luck with this working correctly since the patch)
Apply and close.
Restart Bioshock Infinite with vorpx on.
You should be able to see well enough to continue your game.
(Use middle mouse click edge peak if needed to enter game)
Ingame vorpx settings:
Once ingame push Delete on your keyboard to bring up vorpx menu.
Click Mouse wheel to zoom back in to see menu clearly.
On Main tab:
Set 3d Reconstruction Z Normal
Seperation (3d-strength) 2.00
Depth Weighting (Near-Far) 1.00
(These are the most immersive 3d setting I found, that do not distort quality or cause my stomach to turn)
On Display Tab:
Fix Chromatic Aberration On
Image Zoom 0.67
(This will pull the camera back far enough to capture most of the screen without taking you out of the screen)
On Input Tab:
HT Sensitivity .38
HT Roll On
HT Smoothing Very Low
(This will seem a bit slow, once you reach the target practice area i suggest you practice till perfect learning to aim and shoot using head tracking before you proceed, and tweak these settings to what suits you. Alot of people dislike this method of shooting and want the crosshair disconnected, but having tried steamvr halflife 2 I can tell you hands down, I love aiming with headtracking. You will also want to tweak your right joystick sensitivity ingame control options to your liking, I also found that a lower sensitivity worked for me.)
Handle Gamepads Internally Off
Head Tracking as Gamepad Off
(This will allow you to play with an xbox controller using in game setup, which does not coflict with head tracking for me)
OK&Save (exit vorpx panel)
Exit Game one more time.
INI Settings:
Open the following folder:
C:\Users\(your username)\Documents\My Games\BioShock Infinite\XGame\Config
Open XUserOptions.ini with notepad.
Change:
MaxUserFOVOffsetPercent=00.000000
To:
MaxUserFOVOffsetPercent=28.570000
(This will boost your fov back far enough to make the depth feel correct)
Save and Close
Open XGame.ini with notepad.
Change:
[XCore.XScreenManager]
bUseDefaultSafeRect=true
SafeRectX0=0
SafeRectY0=0
SafeRectX1=1920
SafeRectY1=1080
MaxDefaultSafeRectAspectRatio=1
To:
[XCore.XScreenManager]
bUseDefaultSafeRect=false
SafeRectX0=0
SafeRectY0=0
SafeRectX1=900
SafeRectY1=700
MaxDefaultSafeRectAspectRatio=0
Save and Close
(This last edit alters the positioning of your hud elements. These settings will pull your healthbar, vigorbar etc inside your field of view. This will allow you to enjoy the game without ever having to use edge peak)
Restart Bishock infinite and enjoy.