Forum Replies Created
-
Posts
-
No I never go ultra on anything these days. I always stick to middle ground.
Dellrifters suggestion seems to have done the trick. I re-enabled fluid and direct mode asyncs, and runs like a charm now. No judder anywhere at any time (with 45 minutes of gameplay). Just a leftover setting from earlier combating with the game.
Thanks!I think I did turn off Direct Mode Async when I was first trying to fix the original judder problem a week or so ago. So maybe I’ll try turning that back on now.
I think I tried with my O+ after the last update and it seemed ok. So maybe the latest update isn’t the culprit for me?
I’ll do more testing when I get a chance.So far, as a complete package, I’m liking the Rift S more than the O+. I think Oculus just has their sh!t together a bit more than WMR. Larger sweet spot, much better software, better controllers, 5 cameras. But I do miss the larger FOV on the O+ and brighter colors. I have a month to return it, so we’ll see who wins the battle.
Also, its not so bad that I would consider it “something wrong” necesarily, its just somewhat noticable, so I’m wondering.
It may “just how it is.”
I predict dellrifters next post will be some cowboy poetry or a song that he wrote one night while sitting by the fire up in the hills with his horse and harmonica. Haha ;)
But yeah jesting aside, I totally agree. Most atmospheric game I’ve seen in a while. Especially exploring up in the mountains. The views are actually jaw dropping. Its one of those games you need to sink into and forget about running waypoint to waypoint to “do missions”.
I didn’t know you could get a second horse to follow you. So many things I still haven’t figured out about this game yet. Just figured out how to switch ammo types yesterday. Wish I had more time.
I’ll check out longer days, I saw that but thought it there would be too little nighttime. Maybe it could be ok by the sounds of it. The one part of the game I’m not huge on is the deadeye system funny enough. I find it sort of a “pause and instakill” button like VATS which I also dislike. I’ve been replacing it with a “slow time” mod that I use to just slow time 20% in gunfights. So some benefit, but keeps the action going and uses skill instead of just pause and kill.
This version of VorpX directx12 was just released for people to play RDR2, its still in beta. Mostly, the flickering is just on the cutscenes I’ve noticed and are pretty minor.
No way I’ve found to get rid of it, but at least its not in gameplay.This game does indeed look cool, going to have to pick it up once I get over my RDR2 fixation.
Also, is JesusSaves guy and PraiseJesus guy the same guy? Or is the coincidence strong with this one?You know whats weird? When my RDR updated last, it reset all my graphics settings to LOW. And also Vulcan instead of directx. But VorpX was still running fine on Vulcan before I figured it out.
@rich0550, if you look back through this thread, you can see that the game has been quite unstable for it’s release. But I’m not aware of any issues of VorpX crashing the game. There really isn’t any setup to get it running. Try running the Launcher before running VorpX, see if that helps.
More info on the crash would help too. When/where, what does it say, etc. Does it hook? i e. do you see the little VorpX logo come up on the screen, etc.I did notice something similar yes, but haven’t tried enough without VorpX to say for sure. Would be weird, as vorpx seems to hook right away so not sure what it would be doing.
Sigh so many issues with this game. Well after the update last night to fix the game’s stuttering, now the FOV mod does not work – it just crashes the game immediately. Obviously not VorpX issue, but this seems to be the place to discuss this game.
I’ll see if I can find a fix, but for now its no FOV mod. :(