Search Results for 'Fallout'

[funkyhunk]

Fallout 3 worked almost right out of the box, but not new vegas. Annoying.

[Lusiphur]

Agreed — that config worked for me for Fallout 3, but not for New Vegas.

[sajittarius]

ok i just got it working again with this:

samsung as main display
fallout launcher set to second GTX670 (still iAdapter=1)
vorpx set to ‘show only on Rift’ (was ‘show only on Samsung’ before)

so basically the same thing that worked before except i changed the monitor vorpx should use.

[sajittarius]

actually, disabling flash didnt work. I had to actually go into task manager and stop Vorpx Control for Firefox/IE to work.

I just restarted Vorpx Control and now fallout is complaining about the resolution, so im guessing it rechecked which screen is main/secondary. Ill let you know once i get it working again, lol.

[sajittarius]

ok so i went through all the settings and it appears to be working now…
I’m using a Samsung monitor and the Rift. Here are the things i tried (might help in improving vorpx handling in the future?):

Rift as main display
Fallout launcher set to second GTX670 (meaning 2nd display, same as iAdapter=1)
Vorpx set to ‘show only on Rift’
game displays on Samsung Monitor, vorpx menu appears in game, head tracking works (just displaying on wrong screen)

samsung as main display
fallout launcher set to second display
vorpx set to ‘show only on Rift’
game displays on Rift, no vorpx menu, no head tracking

Samsung as main display
Fallout launcher set to second display
vorpx set to ‘show only on Samsung’
game displays on Rift, everything works…

So it looks like Win8 or 8.1 is reporting primary and second display differently and Vorpx is using the wrong one?

Side note: once i got everything working Firefox and IE start crashing on open. I think its a problem with Flash player, I even put in exceptions for the flash plugin exes. The only thing that seems to work is completely disabling the plugin in the browser.

[sajittarius]

yea, sorry guys.. i swear i had it working, but I’m trying to run Fallout NV today and its giving me the same error (resolution not supported).

Its like windows switches to cloning the displays instead of keeping them separate. Not sure why…

[Ralf]

Issue confirmed. For Fallout 3 I found that changing the line iAdatper=0 in FalloutPrefs.ini to iAdapter=1 fixes the problem, for Fallout NV this doesn’t seem to help.

The above presumes that the DK2 is set as secondary display.

[Ralf]

Try the following ini-tweak:

In your FalloutPrefs.ini change the line iAdatper=0 to iAdapter=1 .

With the DK2 configured as secondary display this worked for me in Fallout 3 but not in Fallout NV.

[Lusiphur]

vorpX 0.7.1 / DK2 / Win 8.1 here as well. I also have display orientation set to Landscape (Flipped) and the Rift set as the primary monitor, but I am not able to successfully start up Fallout, even after trying sajittarius’s fix above. The DK2 is set to extended mode, obviously. After starting the game from Steam, I open the options, and configure the graphics to the first graphics adapter and change the video to 1920×1080, save that, but when I start the game it just throws up an error message: “”Failed to initialize renderer. Your display doesn’t support the selected resolution. Please set a different resolution in Fallout: New Vegas’s Launcher under ‘Display Settings’.” That happens with or without sajittarius’s display scaling change.

I did also try it in portrait mode — with that, and selecting 1080×810 in the game options config, the game did launch, and I got a 3d view with positional tracking… but it was sideways.

Any suggestions? I’m happy to provide more info on my setup if needed.

[funkyhunk]

Thank you for replying Ralf :)

I’ve checked, and doublechecked, the game config menu is set to 1920X1080,
And the falloutprefs.ini file under
[Display]

Is set to:
iSize W=1920
iSize H=1080

It didn’t help when I ran the game windowed.
When I set the rift config to direct mode, I get a small window in the upper left corner where the game starts up, reacting to rift movement, but nothing is shown on the rift.

I’m running Win7 64, on a i5 4690k @4.5ghz, and a 3gb GTX780oc card.
Are there other things I need to make sure is updated? the Vorpx drivers are the most recent, so are the display drivers. The dk2 has the newest firmware.

[funkyhunk]

Hi, I have a problem with New Vegas.
No matter the setting I always get the “failed to initialize renderer. Your display doesnt support the selected resolution yadda yadda yadda”

If I set the dk2 as primary, or secondary, or select the second display adapter in the NV config, no difference.
“show only on rift dk2” or “use system default” in the vorpx config, still the same.

I got it to work on BF3, Skyrim (although I get the “big hands”) and HL2 “native support”

Anybody got any tips?

[sajittarius]

Hi,

I have the Rift DK2 and Win8.1.

Just wanted to add that I had to go into the Nvidia Control Panel, and under Display-> Adjust Desktop Size/Position, change the scaling mode for the Rift2 to Full-screen and Perform scaling on: GPU. By default it was set to Display scaling, and games like Fallout New Vegas wouldn’t start because the Oculus was rejecting the resolution. Once i did that i was able to start Fallout if i set the Rift as the main display.

[helm8217]

ok, I think I have fallout 3 and skyrim working. I was using an emb with skyrim and I think that was causing vorpx to not “hook in” and recognize. As for new vegas I changed the resolutions, but still I’m getting the render error. Here is a new question. I’m using an xbox 360 controller and everytime I play skyrim or fallout 3 I don’t have any head tracking and need to use the right analog stick and suggestions on this issue?

[gustavor38]

I am using Fallout3. It works but it seems a flat big screen, i can move through it and looking around but i have no sense of 3D in the objects i see. All of them shows flat. Is it game related or is it vorpx settings
What settings must i investigate through the DEL key? 3D separation? I am new to vorpx and i am afraid to break anything…..

[gustavor38]

After reading roadtovr article about compatibility with skyrim in DK2 i ran to buy your product.
Now I find that really they are reviewing a not public version, right?. I think that this is not a good policy.
When i try to use the product i find that no head movement is detected by vorpx, not the camera (i know i must wait for the update), the rift alone. When I turn the head the image turns with me, i can´t look around is as i have a monitor glued to my head.
I tested it with fallout3, i tried stopping and starting the oculus service, the program opens ok in the dk2 forcing it with vorpx control. I tried using system config but the problem is the same.

Am I doing anything wrong?

Excuse my english, it isn´t my native language.