Search Results for 'Skyrim'

[chukovskiy]

Long story short, as OR/VIVE has not that high res, an option to “use a binocle” aka zoom an image (decreasing FOV) is a must.
Maybe

[lipplog]

I remember the “I can’t believe it’s not ENB” mod working with original Skyrim. I’ll have to look for an SE version.

[nieda113]

old skyrim will work with the injector version, but skyrim se nope.
As soon as u enable the enb it kills 3d effect.

[nieda113]

as of win 10 fall update 2017 no need for the 32 bit skyrim version to use enbboost since they fixed the vr memory allocation . Skrim (old) runs flawlessley ….Anyways, if enb is enabled it kills the vorpx you wont have a 3d effect in skyrim se.

[lipplog]

Hi guys,

Has anyone tried ENB with Skyrim Special Edition? Since the memory fix isn’t necessary in SE, I was wondering how that changes the ENB set up.

[Ralf]

DirectVR is a collection of multiple features that help to make games a better experience when you play them on the headset, it is not linked to the kind of stereo 3D that is available for a game. It can take care of resolution, FOV, settings-tweaks and head tracking. Which of these four potential DirectVR options are available varies from game to game.

Oculus Touch/Vive wands work with almost every game, that is unrelated to DirectVR. You can use the VR controllers to either emulate mouse and keyboard (freely configurable) or a gamepad.

Games that have all four potential DirectVR features are for example the ones below, a lot more have support for at least one of the potential DirectVR features.

Skyrim (original DX9 version is usually the better choice)
Fallout 3
Fallout New Vegas
Fallout 4
Portal
Portal 2
Far Cry 3
Far Cry 4
Far Cry Primal
Left 4 Dead 2
Mirror’s Edge
Bioshock (DX9)
Bioshock 2 (DX9)
Bioshock Infinite
Borderlands 2
Borderlands Pre-Sequel
Dishonored
Deus Ex Human Revolutions
Black Mesa Source
Half-Life 2
Half-Life 2 Episode 1
Half-Life 2 Episode 2
Aliens Colonial Marines
Dear Esther (Source engine version)
The Stanley Parable

[Ralf]

Sounds like a virus scanner issue, normally the watcher shouldn’t use more than a few percent of your CPU. Try to exclude the vorpX program folder from your AV scanner or ideally use Windows Defender, which shouldn’t cause such issues.

BTW: the watcher goes into a pause state when vorpX hooks into a game, so provided everyhing works as it should, the CPU is fully available for games.

Unrelated, but also useful:

If possible use the original DX9 Skyrim, performs better with vorpX and is also the better choice for various other reasons.

If you have to use the Special Edition, set graphics settings to medium. Doesn’t really look worse, but is a lot faster.

[Ralf]

Reading that from someone who got a personal feature programmed entirely for himself just three weeks ago sounds a bit funny, but thanks for your feedback.

—

Regarding the matter at hand:

The mod organizer integration was meant to simplify things both for you and for me. it did the exact opposite. You are either confused or even openly dislike that things happen ‘behind your backs’, and I spend an awful lot of time replying to this forum thread instead of doing useful work.

Entirely my fault, not yours, since I didn’t consider how important it is for you guys to have full control over every single line in your ModOrganizer ini-files at any time.

If you can’t or don’t want to trust me that the mod organizer integration is a good thing, so be it. This was an attempt to do something good for you – which it does and TBH I still have no clue what the actual, real issue is you are having with that besides some vague feeling of losing control, but I can only conclude that this kind of help is not wanted. So it will be removed.

In turn you have to consider Skyrim installs with ModOrganizer unsupported (and quite likely glitchy) again just like before.

—

Thread closed. Since the MO integration will be removed it has run its course.

[itsrumsey]

So I bought VorpX a long, long time ago and never really used it much due to the difficulty involved with all the tweaking, but with the new update that eases a lot of that pain I wanted to give it another shot.

I know running games through VorpX is intensive but I wasn’t expecting this. My CPU is an i5 3570k OC’d to 4.2Ghz and I was getting 23FPS in Skyrim with geometry 3D. I noticed my CPU was pegged at 100% usage which wasn’t too strange, but when I quit the game almost immediately (because let’s face it 23FPS sucks) I noticed VorpX control was still using CPU… a LOT of CPU.

Is it normal for VorpX by itself, with no game running, to use 60% of a 4.2Ghz quad core processor? Everything else on my PC was using ~1% or less, and as you can see this leaves less than 10% for the game I want to run. Now how in the world am I going to get decent FPS with that?

Assuming this is normal and expected usage, is VorpX multithreaded and would buying one of the faster Ryzen processors fix this? I was thinking I could set the affinity to VorpX for a few threads on the Ryzen still leaving plenty to play games.

As it stands now, I basically can’t do anything with this.

[Demosthenes]

Yes, I suspected you would reject requests for basic information.

I don’t use MO any different to a normal installation for Skyrim.
You misunderstand and over-complicate to think everyone uses it differently, and you misdirect your attention when you think it is mods that are always the problem.
Very few mods touch memory functions or startup, and the ones that do work fine with Vorpx.
My Skyrim installtion is working fine with the *previous* version of Vorpx – with 400+ mods, 253 plugins and a 1080ti.

My only problem is that, for mysterious reasons, you won’t give someone who’s supporting your program any information on how the *new* Vorpx behaves.

If that genuinely is too much, I would again advise you to remove Vorpx’s messing with MO’s files and just say ‘it does not support it’.
MO users can provide support to each other and I and others can stop wasting time asking questions that won’t be answered.

This is the best option.

And will still be the best option when Vortex releases at the end of January.

I know lone wolf programmers tend to think in bizarre ways, but it’s still disappointing to discover that paying customers asking for basic information about Vorpx’s own features is considered verboten.

[Demosthenes]

Yes, I suspected you would just ignore my requests for basic information.

By the way I don’t use MO any different to a normal installation for Skyrim.
You misunderstand and over-complicate to think everyone uses it differently, and you misdirect your attention when you think it is mods that are the problem.
Very few mods touch memory functions, and the ones that do work fine with Vorpx.

The problem is that you, for mysterious reasons, won’t tell someone who’s paid for your program whether Vorpx changes the ini files for all profiles or just for the launched instance.

It really isn’t that hard, and it won’t hurt.

If that genuinely is too much, I would advise you to remove Vorpx’s messing with MO’s files and just say ‘it does not support it’. Then MO users can provide support to each other and I and others can stop wasting time asking questions that won’t be answered.

This is the best option.
And will probably be the best option when Vortex releases at the end of January.

And I guesss I will have to find those ini edits out for myself through file comparison since copy and paste for the developer is too much trouble.

I know lone wolf programmers tend to think in bizarre ways, but it’s still disappointing to discover that paying customers asking for basic information about Vorpx’s own features is considered verboten.

[Ralf]

Believing I could help you by handling ModOrganizer was a mistake on my end, sorry for the confusion. I did not consider that apparently every ModOrganizer user uses the tool in a different way so that doing it right would actually mean taking care of each one of you personally, which is just not possible. So the only help I can offer in regard to potential issues with a heavily modded Skyrim is suggesting the procedure that always has been suggested until now.

In case of any issues with a heavily modded Skyrim please first check whether your issue also occurs with an unmodded version of the game and without any additional tool. Then add your tools and mods back one by one to isolate the mod/tool that causes the issue.

[Demosthenes]

The replies have made me more uncertain as to what Vorpx is doing.

I honestly don’t understand the reluctance to providing basic information.

Previously you said you were now providing ‘support’ for Mod Organizer ini profiles and you asked for our help with that:

Quick question for Skyrim modding pros

You said “Today I added support for ‘Skyrim Mod Organizer’ managed ini-files to the new settings optimizer. “

Now you say “I can also assure you that definitely no other customization tools like ModOrganizer will ever be considered by vorpX.”

???

Anyway, I would like to know what Vorpx ‘support’ of MO profiles means in practice. **What does it do?**

At the risk of repeating myself:

1] What ini edits does Vorpx add to Skyrim’s ini files?

If possible add a note explaining what they do, although *this is not necessary* as I can figure that out for myself.

2] Does it edit only the ini files for that profile which is used upon starting a Vorpx game?

Does it leave other profiles and their inis for the same game alone?

Is the behaviour the same for every game?

If I set the MO profile ini files to read only for testing particular changes will Vorpx crash / fail to hook or just continue and ignore it [the game will start you just won’t have those optimizations] ?

As to the ‘support’ for MO, it would be better just to remove it and say it is not supported, than to have the changes it is making, and even what it is doing, so obscure.

These issues are going to keep coming up again especially when Vortex, the new Nexus mod manager being developed by the programmer of MO, is released shortly.

I want to upgrade to the new version of Vorpx without hours of troubleshooting and wasted time that could have been avoided with a little info.

If you feel this small amount of information is too ‘dangerous’ for your general users to know, fine, then can I send you a support email which you reply to with the info?

Thanks.

[prinyo]

Ok, so here is how I understand the situation.

Disabling the auto changes globally does revert to the old way but as the game optimization screen is gone from the VorpX Config any new game you try will not be optimized. It is like running the old version without optimizing the game first. Which is definitely a bad idea. And disabling the global setting is indeed a bad idea and a last resort temporary measure only.

There is a similar option – per game. However in order to get to it you need to start the game as it is located in the in-game menu.
If the game wont start with the new version – disable the global auto config option and try to start it again. If(!) it starts press Dell, find the option to not auto configure the game, turn it on, close the game and return the global option to it’s default status.

All this makes sense if you already have optimized ini files for the game. So for example it should work if you want to recover a Skyrim setup that was working before and doesn’t work now.

The global auto config needs to stay on and the only time it makes sense to temporary disable it is if a game is not starting at all with a hope to recover it.

About the in-game auto config option – it is also a good idea to keep it on. There is an additional option – only about the resolution. If you, like me, find the resolution VorpX chooses to be too low and have the stomach to handle higher reprojections, keep the auto config on, but the auto resolution off and set your preferred resolution in the ini.

About the MO problems, two general ideas that might help – install MO again on top of itself. Nothing in you setup will change but the registry values will be recreated. If you for some reason have 2 MO instalations make sure the MO you start the game with VorpX is the last installed one. Not sure how this will affect people who have MO and MO2 installed at the same time.
You can also try and create a new profile – just copy the one you want to use. Maybe there is a problem with the current profile.

Also – if you do not know what MO is then nothing in this thread is relevant to you.

Added: Curious if people who have problem with MO + Oldrim also use MO2 with SSE.

[Ralf]

Please disable auto settings if you believe that improves anything. It doesn’t, I can assure you that, the opposite is the case. But if automatic changes make you feel uncomfortable, you can disable them nonetheless. Be aware though that left unhandled ModOrganizer definitely will cause glitches.

So before reporting any glitches/issues you encounter with auto settings disabled please always make sure that these issues also occur with auto settings enabled to avoid reporting issues that do not exist when vorpX can do its job fully.

I can also assure you that definitely no other customization tools like ModOrganizer will ever be considered by vorpX. What I take away from this thread is that you as users of such tools apparently favor complete control over everything else, even if it helps you. Strikes me as rather odd, but it’s your loss, not mine. I don’t have enough time for discussions like this one.

From now on the only official recommendation in case of any issues with a heavily modded Skyrim install is again to please first check whether your issue also occurs with an unmodded version of the game and without any additional tool. Then add your tools and mods back one by one to isolate the mod/tool that causes the issue.