Search Results for 'Inside'

[Mr.T]

Has anyone a idea how I can make vorpx move my head correctly inside this bus-simulator? You normally use your middle mousebutton to move the view around. Can’t figure out how to fix this :-/

[uswin]

sometime vorpx can fail to hook up on your dk2,
you might want to try the trick with oculus demo scene,
1. First, run oculus config demo scene keep it open
2. Then run your game as usual
3. After inside the game, press alt tab and close demo scene and oculus config
4. Check again inside your oculus, and see if vorpx is hook up on dk2 now,
sometime this little trick work fine

but sometime game made with UE4 tend to produce crash or freeze after the logo, anyone have similar issue ?

[Karlor]

I think what they mean is you have to launch quake with dx9, sort of like Bioshock 1 I think.. what you do is inside properties(right click, go to properties) then in the field and -DX9.. now I don’t recall what field and the exact thing you have to type in… but it should be something like that.. you should be able to find more info I’m just trying to point you in the right direction… Its easy once you figure out what field to change.. I just don’t remember right now.

[Phil_Giordana_FCD]

Not working. Maybe I should move this to the support section?

VLC shows a black window on the desktop and plays fine in the Rift. But even after clicking the window, borders or inside, still no way to get the ingame menu to come up.

I have the Xbox 360 pad plugged in. Could that be the problem?

[phoenix]

Thank you NipOc. Only one question:

What runtime version are you using to start. I have now 0.7 installed. Then i have to save the 0.7 exe in other location, install 0.5 runtime and copy the 0.7 one or inside out?
Apologize my short understanding to perhaps obvious questions….

[phoenix]

Forget Vorpx for FSX.
You have a sublime alternative to make it.

https://flyinside-fsx.com/download

As real as you are in the cockpit and zero configuration, it works out of the box.
It works as a dream with FSX Steam Edition, I re-bought FSX for this.

[megawaly]

OK, I did a bit more digging and it seems to be in the hands of BATTLEYE.
I found some comments on a youtube video (HERE):

“It appears that ARMA 3 game update 1.46 (enhanced battle eye protection) has broken Vorpx ability to engage. With Battle eye off Vorpx 0.8.10 is fully able to engage and display as per the above video routine. Email has been sent to vorpx and also battle eye, I will update once I know more, my installation was fully working online with battle eye on before the 1.46 update, and again with battle eye off it works fine, on it does not work, to me that means the battle eye is the issue.”

“In short Battle Eye cant allow Vorpx to access the Dirrect X files. There was a lot of back and forth about it, ben from road to vr was looped in on the emails and also given a cliff notes, I asked him to chase both sides to find out the inside scoop as there will be a lot of Arma 3 Dk2 players that are going to be devastated about this.”

These comments are from about 2 weeks ago. Does anyone have an update as of yet? Ralf, if you read this, do you know of any status?

[>>>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 :)