Forum Replies Created
-
Posts
-
FYI – F1, F2 and F3 work to move through the different pipboy menus. I mapped these to the D pad since I don’t use weapon hotkeys there and it’s working well.
Finally have it running good enough to be playable. For getting out of console screens I use the FOSE command line “cam” for close all menus, it’s relatively quick and easy to do. Can’t seem to click the red ‘power’ button to get out otherwise.
MSE seems to have borked mine too. I thought I saved the install file but apparently got excited to start using it and forgot! I’m not 100% sure the issue was MSE, but my vorpx.exe suddenly dissappeared and it happened while MSE was doing a scan.
Ok, the FOSE issue was my fault. The fose loader wouldn’t run b/c I removed the d3d9.dll file that it needs when I was trying to troubleshoot the general inability to run the game at all through vorpx earlier. I put the fose files all back fresh into the folder where fallout3.exe lives and now it will launch from the script extender and is rendered on the rift fine.
This is great b/c many of the UI mods require the script extender.
I’ll report back if I get a good working 360 controller setup that allows reasonably easy pipboy navigation.
And yes, I’m anxiously awaiting the E3 event too. Should be good regardless of what they show there, but I think a lot of us are hoping for fallout 4 news!
Good tips, thanks. Sorry for the delayed response, got busy with work (and playing elite!)
Hopefully none require FOSE. Some people seem to be running things like iHud that require FOSE but vorpx never hooks when I try to launch using the scipt extender.
Ok, makes sense. I’m using a wireless 360 controller with MS drivers.
Ya, I am using HUD scaling, set to 40% I think to get the other menus looking good and readable. I’ll experiment with the alt-mousewheel adjusement when in the pipboy, that might be part of the problem.
Can’t quite figure how to setup xpadder to allow full control of the pipboy with the gamepad. Other forums and example mappings indicate it might not be possible. The native support for the gamepad in fallout handles this behind the scenes, e..g LT/RT change between menus but have other functions when not in the pipboy. When 360 controller is disabled and the game goes to keyboard/mouse controls, I don’t think there’s a dedicated, mappable button set for pipboy menu navigation.
Last night I just ran it w/out headtracking using native 360 controller support through the game and it was pretty awesome. Head tracking and gamepad would be best since I always played this game with a gamepad and find it easier than hunting for keys with the oculus on, but considering this game was never meant for VR it’s hard to complain too much considering that in general it does work mostly OK.
Makes one appreciate the thought that went into the detailed mapping configuration options that went into a game like Elite Dangerous, and all the other things they did to allow smooth operation in VR.
It’s going to be awesome when more games build in official support. Let’s hope fallout 4 is 1) as good as I’m hoping it will be and 2) has decent support for playing in VR. Apparently it’s supposed to be officially announced some time this year.
Update – got the 360 controller mostly working using the vorpx emulator, but then switched to xpadder for more flexibility.
Note that in the vorpx gamepad emulator, the start/back and left stick/right stick buttons are switched. I.e. mapping a button to ‘start’ will cause it to activate when you use the right stick button. I think this is a known bug and not a show stopper but makes things trickier.
Most everything is OK now and working except for one very important thing – I can’t seem to change which menu screen the pipboy is on. The fallout 3 manual says ‘left click’ changes the menu screen displayed, basically you click the round button to alternate between ‘stats’, ‘items’ and ‘data’ screens.
I can move the cursor around while in the pipboy using the right analog stick or the actual mouse, but using left click on either the 360 controller (as mapped in xpadder), or on the actual mouse, does not result in the buttons being clicked.
I tried changing the pipboy FOV in the INI file to make sure it’s all shown and not close to being off screen, but that doesn’t help. It’s as if the buttons aren’t ‘live’ and are un-clickable.
Am I missing something obvious?
Uninstalled all mods, did a fresh install, fixed the INI file so it would run on win7 and vorpx works! I also finally got the game and menus fit to screen. The vorpx in game menu does lots of useful things, but it doesn’t seem there’s a comprehensive write up on each setting though so there was a lot of trial and error required to figure out how to do what I needed. Letterbox mode was the biggie along with menu scale. Otherwise couldn’t see the menu to even start a new game.
Head tracking didn’t seem to work but it was getting late so I didn’t fight with it much. Probably more trial and error needed with the head tracking and gamepad settings needed. I think the issue was having the 360 controller turned on but not disabled in the game menu.
Thanks for the reply. The renamed file was just to add ‘.bak’ on the end so it wouldn’t be found by vorpx as a dll. Will deactivate all mods related to graphics enhancement, sounds like something there is the likely culprit.