Forum Replies Created
-
Posts
-
Your key has been sent the third time, this time to your GMail address. If it still didn’t reach you, please let me know.
BTW: Please do not open multiple threads for the same issue. Doesn’t help to solve anything, but makes the forum unusable. Thanks.
The Evolve profile may be worth a try as a base. That’s the latest CryEngine profile IIRC. Z3D only though.
That shouldn’t happen at all and I honestly never heard of that before, so I’m a bit at a loss here, sorry. Head tracking is enabled per default in the Skyrim profile, you just have to adjust its sensitivity. Might make sense to reset the profile to default in the vorpX config app.
In regard to the big hands:
1. Open [Documents]\My Games\Skyrim\Skyrim.ini with a text editor
2. Set the fDefault1stPersonFov value to 120. If it doesn’t exist, add it under [Display]
3. Save and run Skyrim. You may need to swap between third and first person or even open the quad (star) menu and from there the map to apply the new value for some reason. After doing this once it will stick.Please follow the optional step in the post regarding the profile. This will allow you to raise the FOV above what is possible in the game and solve your issue.
I haven’t played Enderal yet, but I really liked Nehrim a few years ago made by the same guys based on Oblivion. There also was a NPC sitting around somewhere that was probably named after my Oblivion modder nickname. That alone made it worth playing. Seriously, everyone who likes Bethesda RPGs but sometimes wonders how they would be with a little bit less sandbox and more story instead should play this. Nehrim was fantastic, and I would be very surprised if anything else can be said regarding Enderal.
Usually I don’t look into official profiles for mods, but this one is large enough for that. If it requires changes to the Skyrim profile, they will be made.
@ fernas: please follow the optional steps in the second post of this thread to raise the field of view above what the game allows. That will solve your issue.
@ maximus: It’s mainly dubbed experimental because OpenGL support in vorpX never was 100% official and because there isn’t a Game Optimizer profile yet. More profiles will happen soon. The next update one more time mainly will be tech focused, but after that it’s finally time for more profiles again.
GPU and CPU having to wait for each other at several occasions is the main reason for both not being fully used. The frame rate drop you see is too extreme though. Typically you should expect 50-60% for geometry 3d rendering and then another 15-20% for the direct mode thread rendering/syncing. In your 120fps mono example that should yield something around 40fps (120*0.4*0.8) worst case.
If you experience something dramatically worse with a modded Skyrim, please try an unmodded game without any .ini tweaks besides the ones the vorpX game optimizer applies. Also do not use the “Ultra” quality setting. Try “High” or even “Medium”.
DirectX (especially DX9) can only handle a certain amount of draw calls efficiently. Skyrim itself already uses many of those, stereo rendering doubles them and the “Ultra” quality setting, mods or popular quality enhancing .ini tweaks (uGridsToLoad etc.) may finally be too much in some areas of the game with much geometry to render.
Also check for any hi-res texture packs you may use and get rid of them. Those might not get disabled by disabling mods. Since vorpX requires a fair amount of additional GPU memory, hi-res textures can cause a severe performance drop on anything but the latest high end graphics cards if textures have to be swapped in and out of the GPU each frame.
Probably something different then. The driver issue applied to almost every game, not just Fallout 4 and was Vive exclusive, Rift always worked. Usually games crashed after a short time in the game (<1 minute).
Just did a little test run with the latest FO4 (~10 minutes running across the map, GTX1080, Vive), but nothing to report except being killed by one of those giant mosquitos, which really look disgusting up close…
So maybe it’s indeed something Titan exclusive. If it only happens in FO4, something game config related seems more likely to me though. The usual drill for any Bethesda game would be to first and foremost get rid of any mods for testing, especially those using a script extender or (ENB) graphics enhancements.
Finally found the cause for this, thanks for the heads up. Not much you can do on your end right away unfortunately, but the underlying problem will be fixed in the next vorpX version.
SKSE may be hit or miss. It shouldn’t cause issues in the majority of cases, but if it does, you may have to do without. Both SKSE and vorpX hook into the game, which can cause issues that aren’t really resolvable.
Please check whether you have the latest nVidia driver (372.54). I had an issue here with extremely frequent crashes on a GTX1080 machine with the driver before that after the latest big Windows 10 update (“Anniversary”). The same probably also applies to your Titan. Trying to find a cause for this cost me almost a week of work… The 372.54 nVidia driver solved it 100% here.
The most likely cause of something like this is a conflict with your virus scanner or other “security” software. Please try to disable/uninstall it and see whether that helps.
If it does, exclude the vorpX program folder (usually C:\Program Files (x86)\Animation Labs\vorpX) from scanning. Most av scanners allow to exclude directories.
Please add Opera to the list of excluded programs in the vorpX config app. Sounds like vorpX may try to hook into Opera but fails.
In regard to the “screen being too big” please make sure to check the Essential Hints Guide in the vorpX hepl. You need to address the field of view (FOV) one way or the other. How that can be done is different for each game, the options you have are described in the guide.
The easiest (yet not perfect) way that works for almost any game the same way is described in the “One-Two-Three Game Setup” in the help.