Forum Replies Created
-
Posts
-
I have a little suggestion too:
It would be helpful to set a desired size-value for edge peak mode. Because when you increase your virtual distance in edge peak mode, because normal edge peak size is still to near and when you switch back then to normal vorpX-focus you have to zoom back to fullscreen manually.
By the way: all Bethesda-games are quite good to be played with Oculus Rift. They deliver a very nice vr-experience. Not to fast gameplay and very focused on exploring. I hope Ralf will all of them get to work properly without graphic issues and with positional tracking.
What woks really good and out of the box besides Skyrim is Fallout 3. I had a problem, which caused crashing, but it seems one of the mods/patches I posted in this forum yesterday helped.
Skyrim is at the moment vorpX best supported game overall. Oblivion looks very good in 3d, but vorpX support should be improved to enhance conveniant gameplay, especially this fov-issue is at least anoying.
Oblivion looks great in g3d. The only issue at the moment: fov jumps back, when you are talking with npcs. But Ralf wrote, this will be fixed in a future update. Looking really foreward to this. Because Oblivion is really nice to play. It has a very different atmosphere than Skyrim, but both games are different compared to my elderscrolls-benchmark, which is Morrowind. For me the best Elder Scrolls experience, although oblivion and especially Skyrim are a lot more immersive because of their gameplay-features.
But anyway – if you like Skyrim, play Oblivion. It’s a very good game and I hope Ralf will fix some shader and fov issues.
Played more than 1.5 hours without crashing, so it seems one of the patches did it. I guess it was a memory issue because Fallout 3 is not Win7 optimized. Absolutely phantastic vr-experience now! Wasteland is heaven! :-)
Perhaps a solution:
today I installed some useful (i hope!) mods. Now the freezing of the game seems not to happen again. (But this is just a first impression. I had’nt the time to test the game longer than ten minutes per session, but the crashing/freezing didn’t happen again.) So I guess, one of the following mods helped, to stabilize the game. If you have the same problems like me, perhaps the following links will help:
(complete links seems to be deleted, so go to http://www.nexusmods.com/ and paste the following adresses)
– Purge cell buffers: /fallout3/mods/7817/?
– Games for Windows live disabler: /fallout3/mods/1086/?
– 3GB Enabler (4GB for 64 bit): /fallout3/mods/6510/?
– UPDATED Unofficial Fallout 3 Patch: /fallout3/mods/19122/?
It seems you have a mod included which is causing this errors. Like I wrote: I had a fresh install of Morrowind, claculated distant land and everything worked finde- Then I used Vurts Groundcover, calculated the distand lands again and everything which worked fine before was messed up now, same way like you described it. Pretty uncool, because grass is such a nice thing to have in Morrowind. :-/
But again: with a fresh install there seems to be no problems. Copy MGE into the folder and open it. Create distant land just by clicking thru the steps the programm leads you. It should work.
I used quite low settings: not to high resolution for world textures, medium meshes and so on, because my PC is not powerful enough to get smooth fps. Perhaps when you set the settings a bit lower it works better? Or lower the visible cell-distance. I set mine to five.
Unfortunately it’s a lot of experimentation at the moment.
Cool, thank you! Let’s hope that Ralf will add this to the list. The ingame-screens I’ve seen are looking really good promising.
By the way, what graphic card do you have? Do you use g3d-mode or z-mode? I’m asking because you wrote you always have smooth 75fps. I’m running the game on a GTX660, no problem in interiors, but outside it’s a bit to slow for smooth g3d. (Using only 5 cells distand land, 2x AA, no fancy shader settings, just sunrays and hdr.)
Thank you, it’s looking quite nice with the texture pack. Fortunately also the Morrowind Code Patch, which helps to reduce game bugs, is working and makes no trouble. So it seems normal retexturing causes no trouble, but mods who are changing the environment.
I did’nt try to reinstall Morrowind Overhaul again. I made a backup of my working Morrowind-folder. So I just tried Vurt’s Groundcover then, to enhance the environment with grass. But unfortunately just this mod alone seems to break the graphics when vorpX is running.
Only with MGE it workes fine. Today I installed Morrowind Overhaul 3 and things went totally weird unfortunatly. Without vorpX it’s running good and looking very nice, but with vorpX the graphics are totally messed up.
@Ralf: So you tested it with Overhaul 2 and it works? Unfortunately the only Overhaul-version I found in the web was v3.
I forgot something: of course you can try to disable shadows, reflections or other effects in the game menue which are causing trouble. At least, when it’s ingame impossible, you can try to do some ini tweaks.
For example: I disabled in Oblivion the shadows, because there was unfortunately the same kind of problem. (In this game this is possible in the ingame-menue.) Also you could disable in Oblivion the HDR-Rendering to get rid of a glowing effect around your weapon when it’s hidden by the sun. The effect not rendered correct in g3d too, unfortunatley. But for my taste this was not so distrubing and I don’t want to miss the effect for global illumination.
That’s the problem when a game or its engine was not desigend for VR.
You will recognize that in Z-Mode this problem does not appear, it’s a G3D rendering issue, when shaders are not rendered correctly to 3d. Unfortunately there is nothing you can do at the moment to solve this issue by yourself, except switching to z-mode. So we are all in gods hand – also Ralfs programming skills could help. :-)
Perhaps your FOV is still not adjusted. Go into corpX menu, there are optimized game settings, also for the Bioshock series. This should help to change your FOV.
A short while ago I had made usefull experience with the IPD. I described how it’s possible to find out the correct IPD in vorpX itself. Try this, perhaps it helps you too, when you are not sure: