Search Results for 'Skyrim'

[Demosthenes]

Since I started this thread, and since I have been forced to revert to a previous Vorpx version to get Skyrim working again, I’d like to make a request for more information.

1] Please list exactly what ini edits Vorpx adds to Skyrim’s ini files. If possible add a note explaining what they do.

ie:
SkyrimPrefs.ini: [Imagespace] section, changes BDoDepthOfField=1 to bDoDepthOfField=0 , to prevent black water bug.

2] What exactly does Vorpx do in relation to Mod Organizer?

‘Support’ for Mod Organizer seems somewhat vague. I originally thought it meant it would be less likely to conflict, but it seems to mean Vorpx now knows to look in Mod Organizer profiles folder for ini files.

Does it edit only the ini files for that profile which are used upon starting a Vorpx game? Does it leave the rest alone?

I have a Vorpx profile and a non-Vorpx profile. For obvious reasons I don’t want it messing with the ‘non-Vorpx’ profile.

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

3] I may be remembering this incorrectly because of my brief experience with 17.3 but is it correct that Vorpx now edit files *before* giving you the option for those edits?

If the game will not start because of a particular change Vorpx has introduced then the user cannot access the menus that reverse that particular change.
This seems like a Catch 22.

You then have to resort to ‘disabling’ everything generally, which naturally you disapprove of.

Obviously, all these issues mainly concern games that can be modded. And indeed games that have to modded to be stable, like Skyrim 32bit.
For the rest of them I’m quite happy to trust your judgement, but with a Jenga-like construction of a modded Skyrim and the amount of time I have spent making it work, more information is vital.

[prinyo]

When did I tell him to permanently disable the auto setting?
How can he disable the setting per game if the game doesn’t start so this menu is not accessible?

Your response to my attempt to help is not based on what I’m actually saying. It is “bad advice” the same way any other user’s suggestion in the past weeks is “bad advice”. Repeating one and the same thing about what is good and what is bad without any technical useful information simply means there is no more customer support for Skyrim – a game where most of the players have custom setups. If you have a problem then it is your own fault – don’t try to debug it, don’t ask for help, don’t try to help others. Anything you can try is “bad”, the only “good” is whatever the black box decides to do, even if it doesn’t exactly work.
So I don’t see how my advice was bad, all I see is an attempt to avoid giving any specific technical information to help users debug their problems. It is here in this thread, the same yesterday with my problems with the resolution and with any other attempt of an user to ask a specific question to help them troubleshoot.

The thing is – Skyrim is a very popular game played by lot’s of people who want to tweak it a lot, so at some point helpful hints and info will need to be given.

This is new for the forums. Until recently people discussing specific SKyrim problems were left alone to discuss and exchange ideas. Now after every such post there is an official rebuttal that repeats one and the same thing regardless of what the user was actually saying. That’s why I said that if the community support is no longer welcomed here then no problems, we’ll stop trying to help.

[prinyo]

The reason that so many different Skyrim setups exist and work is because people have the basic information required to build and troubleshoot them. For example I know how MO fits with LOOT, fits with the game, fits with all other tools and mods I use. Until a month ago I used to know how VorpX fits in all this. At first it seemed there is a way to make it behave as before, now it is clear there is no.
People who play Skyrim (and even Oldrim) in 2018 are all “tweakers”, for us a change that introduces so many unknowns and black box elements is not “for better”.
Which MO ini is it trying to use? Why is it using so low resolution for my system? The reply that “it knows best” doesn’t really help.
I’m not trying to be confrontational, there is a way to make both the casual players and the Skyrim players (most of them tweakers) happy.

The way things stand now there is practically no support for Skyrim problems. The official position is (as before) “can not account for all different setups” – which is understandable, but now a community support is also impossible, as there is a lot of vital basic information missing.

[Ralf]

It is impossible to account for all the different ways you guys configure your Skyrim installations. So in case of issues always check an unmodified install of the game first.

What vorpX does in regard to MO is the bare minimum of ini edits in MOs custom Skyrim ini files that prevent severe graphical glitches likes shadows working not correctly. So actually this is the perfect example of a case where the only correct and useful advice can be to not mess with auto settings. It’s very likely that you will do more harm than good by disabling them.

In other games even worse things will happen, and even if not, you will miss most useful tweaks like disabling effects that look bad VR and so on. So once again: do not mess with auto settings unless you have reason to do so.

Change can be hard, I understand that, but this is change for the better. A lot better.

If you want the prior vorpX, where you had to do everything yourself, you can get that by disabling auto settings, but please don’t report any issues here that you encounter in that case. Thanks.

[prinyo]

Yes, that’s what I meant – disable it to see if it will run. Not keep it disabled.
He can’t disable “per game” in the in-game menu if the game doesn’t start.

Since the MO integration is another black box debugging it for the user is more or less fire shots in the dark and see what happens. How does VorpX know if the game is started via MO? How does it know which profile is active? Those are the kind of questions the user needs to know the answer to in order to troubleshoot their setup. I know this kind of answers for all the tools and apps I use – I might not know how they work, but I know what they do and how they are supposed to interact with each-other and work together. The problem with the latest VorpX update is that not only it takes away too much of the user’s control, but also the possibility to have a basic understanding of what it is doing. I understand it is important to make it plug and play and offer a painless setup for the novice users but there should be a balance.

About the “Skyrim pro’s”. It is a 6 year old game. Most of the people who still play it do it because they have created their own perfect modded setup that offers them something that no other game does. So most of the people playing it today have (or are trying to have) their specific setups – enabled by their understanding about how the tools and mods work together and how to debug and troubleshoot. A “black box” type of tool added to the mix is a serious problem.

As I said – it is a 6 years old game. The people who still play it are mostly “pro’s” – tweakers. The more people buy VR sets and VorpX the more serious the problem with the inability to troubleshoot VorpX problems because of lack of basic information will get.
For the past weeks the response to any suggestions about debugging has been “don’t change the defaults or bad things will happen”. This will simply not work with the Skyrim crowd that is, 6 years after the game’s release, all about tweaking and modding. At some point there needs to be some basic information about the way VorpX works and integrates with the game and the other tools. Or an “advanced mode” where it will work exactly it did before the update – when everything was easy to understand, predict and troubleshoot.

[prinyo]

Try to run Skyrim from the other MO.
Or check to never change game settings in VorpX Config and see if it runs this way. One of the situations where I have seen this way of crashing is if it tries to run with an unsupported resolution.

[Ralf]

Can’t really answer that, sorry. I understand that you Skyrim pros all use extremely individual setups and as you can see from even doing coding even for mod tools like ModOrganizer I do everything that is possible to account for that, but please first and foremost check whether any issue you encounter does happen with a completely unmodded Skyrim.

The current vorpX version works perfectly fine with Skyrim and also with a “normal” ModOrganizer setup. For anything else I have no answer.

[MarkG]

Yeah, looks like I’m running 1.3.11.

To summarize:

1. This worked (aside from the usual modded Skyrim crashes) just before Christmas.
2. It doesn’t work since Vorpx updated itself.
3. Unmodded Skyrim didn’t work after the latest VorpX update, but I did the ‘reset profile to default’ thing and it did start up after that.
4. Running with Mod Organizer just gets a flash of black, then crashes.
5. Running with Mod Organizer, no mods enabled, and the .ini files from the unmodded Skyrim still doesn’t work. So it’s Mod Organizer, not the mods.
6. Enabling ‘run as administrator’ doesn’t help.

Literally the only things that have changed on that computer are VorpX and possibly new Oculus software; I haven’t checked whether that’s updated lately.

So something’s changed in this version that broke something that was working fine before. Since you did explicitly made changes to support Mod Organizer, perhaps something you changed isn’t compatible with my Mod Organizer installation for some reason.

[Ralf]

That is with 200% certainty a concidence. Not only didn’t the latest version change anything in regard to D3D9, it is also out since a week. If there was a general Skyrim start crash issue, you would have read about that here.

Please try the usual trouble shooting in case of start crashes: first and foremost disabling your AV scanner if it is not Windows Defender, then every other program running in the background. And last but not least try an unmodded Skyrim.

BTW: vorpX works fine with ModOrganizer, SKSE or not. Please make sure to use the last ‘official’ Mod Organizer build from Skyrim Nexus (1.3.11). There are several forks and custom versions, those were not tested. In vorpX 17.3 actually functionality has been added to specifically handle Mod Organizer profiles since the tool apparently is quite popular.

[prinyo]

The reason I asked those questions is because I’m trying to understand what is happening on my PC with Oldrim. I have it set to 1680 as preferred, I also have it set to 2 upscale and yet the performance is way better than it is possible. Also when changing the preferred resolution I don’t see big changes happening. Do I need to restart the game for them to take an effect?
I have this in the ini file at the moment: iSize H=1460, iSize W=1933, but I don’t know if VorpX is writing to the files or is it simply ignoring those settings.

So the fact that I have perfect performance with upscale of 2 leads me to believe that the base resolution it is choosing for me is not good enough. And because it is already times 2 there is nothing I can do to get a better resolution. And seems there is no way to see what it choose for me. Or maybe the values in the ini are exactly what it did choose?

Or – is it changing resolutions continuously based on performance? I noticed that the framerate gets better shortly after I enter a “heavy” cell? For example I go to the streets of a town. At this point I expect the fps to be around 20 – 25. And at first it is, but then it goes back to 40 – 45. At least when I tested earlier today. If this is the case then in Skyrim it is impossible to get a good auto – resolution outdoors and the game will be blurry for the most of the time (as most of it happens outdoors).
But all of this is just guessing, hence my questions. It is all about options – until now I knew how to setup VorpX to work perfectly for my preferences, right now I’m not sure I know.

[MarkG]

So, I decided to try looking at this today. VorpX downloaded another update and… Skyrim no longer works at all, with or without Mod Organizer.

I just get a brief flash of a black window, then it shuts down with no error message. Skyrim works fine if VorpX isn’t running.

[Shugs]

Ralf,

Thank you for the response. How do I mitigate this issue? Skyrim is pretty much the whole reason I purchased Vorpx and I can’t get it running. I have anti-virus, but no CPU/GPU utilities or video recording systems. What is the work around?

Thank you,

Shugs

[Shugs]

I’m having trouble getting Vorpx to detect Skyrim SE on my computer. I have limited space on my C: drive so all my games are installed to my E: drive. Could this be the issue, and if so what is the work around? I have been unable to find an option to link Vorpx to the .exe file for Skyrim or any other game.

[Ralf]

Which only happens to work in Skyrim without creating glitches because in this game some settings are forced by vorpX regardless whether you disable auto settings or not.

To everyone else reading this: please do not disable vorpX’s auto settings feature in any game unless you are fully aware that doing so can and will screw up some games completely and even if it doesn’t, will usually do a lot more harm than good.

[kojo]

Apologies if this has been covered before, but I couldn’t find what I’m looking for.

I’m using the Vorpx Skyrim profile, with DirectVR and full geometry mode. Everything is essentially working fine. But when I put Skyrim into third person mode, I find the headtracking behavior very disorienting. Whichever direction I look, the camera position swings wildly in the opposite direction, to keep the character in the center of the view. This is making me reach for the bucket.

I’m wondering if there’s some combination of VorpX settings, Skyrim tweaks and mods, that keeps the camera following the player character, but allows for looking around freely, without the character always kept central. So that, for example, if I looked up and to the right, I would be looking at a patch of sky, without the camera swinging down below the player, to keep him in shot.