Forum Replies Created
-
Posts
-
No, and at the same time yes in a way ;). This year’s holiday season is the last chance to get vorpX at the current price.
The price was kept stable for more than 9 years while games got typically 20%-25% more expensive during this time. With the latest inflation spike for the first time ever there will have to be a price adjustment after the holiday season. In that sense keeping the price stable until then is this year’s Black Friday offer.
A good salesman in this situation would probably have raised the price earlier and now offer you a faked discount on the just recently raised price, but that’s not what I wanted to do.
When I look at the new official prices, I can‘t help but think that it wasn’t exactly the best collective idea in history to show GPU vendors during the chip crisis what insane prices their customers are willing to pay for a GPU. Now they know, they act accordingly, and they won‘t back down again for sure for the foreseeable future.
The internal forum search is currently unavailable. Please use Google as described by Saalivar two posts above for the time being.
Would indeed be better if the headset vendors would make their auto fps-reduction configurable, at least for developers. In case of vorpX’s multi threaded rendering these things get in the way more often than they do anything useful…
Nothing to worry about. A brief look at the forums could have told you that I’m answering questions here almost every day, also the last maintenance update is merely a few weeks old. Not sure how you got the impression there is anything to worry about in the first place.
As usual, announcements regarding future developments will be made when it’s time to announce them.
Sounds as if the game script portion of the mod might not kick in correctly, maybe an incomplete mod install or missing write access to your Cyberpunk folder (an its sub folders).
Judder protect uses hard CPU/GPU syncing and is thus *really* slow, also almost certainly CPU limited in most situations. Don‘t use unless necessary. Pimax headsets are a bit iffy, but even with a Pimax that shouldn‘t be necessary usually.
I hope something like that will never happen again. I really don‘t want to get into details about how pissed I was (and partially still am), but the whole thing pretty much just became necessary as a precautionary measure because someone for whatever reason deemed in appropriate to publically drag vorpX (as well as other modders) into their own legal issues.
What I truly promise is that I will think hard about whether I can deal with the matter in a different way.
In principle yes, but only for custom profiles. As said above for official profiles only the user settings, not the ‘system’ part of a profile is exported. Also the ones you are referring to are currently explitely blocked in newer builds.
I haven‘t decided yet how to deal with the matter in long run though. Trust me I‘m as annoyed by the whole matter as you are.
Looks as if the FOV hack that vorpX applies is not complete… I’ll fix that for the next update. For now you can do it manually:
- Launch the game once with vorpX enabled and exit it.
- Browse to [Far Cry]\Scripts\Default\HUD.
- Open ZoomView.lua with a text editor (e.g. Notepad)
- In the second line (‘IsActive’) change the 0 to 1.
- Save the edited file.
With this change the FOV fix should work as intended. Remember to use the weapon zoom (right mouse button per default) once to apply it after entering the game.
@ Thavex:
Sounds as if the alternate frame 3d method (meaning that the left eye is rendered at frame 1, the right eye at frame 2 and so on) is not for you. For some (many) people that is too uncomfortable in motion since the brain doesn’t expect timing differences between both eyes. The mod tricks aways some of the issues introduced by that, but not everything can be tricked away.
You can switch to Z3D in the mod menu instead. Doesn’t look as natural as the default method does, but on the other hand doesn’t come with confusing timing related glitches.
@ matteo:
Thanks for the heads-up. Stick to nVidia DLSS then please. I’ll check whether it’s possible to also make the AMD method work with Z3D, but no promises.
Hey matteo, I got to admit that slowly I’m beginning to wonder whether you want to somehow fool me by posting questions half a dozen times, considering how often that happens… :)
You already know the answer to that question. Someone just replied to you asking the very same question about two weeks ago or so – in a thread that contained the answer to it two posts above yours anyway.
Again I’d politely ask you to only post a question once. Answers won’t change just because you post the same question over and over again. Many, many thanks again for your understanding!
Almost certainly a virus scanner issue. Some of the more invasive ones can’t really be disabled or have several modules that have to be disabled separately. Never heard of Webroot SecureAnywhere, but that’s clearly the prime suspect here.
Try to exclude the vorpX program folder (may also have to be done in several places with some highly annoying AV programs). You might also want to consider switching to Windows Defender by simply uninstalling your third party AV. Defender since several years offers excellent protection without being as invasive as some third party solutions.
No such problem here, Quest (2) is the main dev platform since quite a while. Also no other reports like this, so it’s fairly safe to assume that this is some conflict specific to your config. Judging from the symptoms you describe probably something getting in the way that also hooks into games. If you have any other mods installed, try without. Also disable/remove any tools/utilities you may have running in the background. A lot of tools hook into games these days.