Search Results for 'The Thing'

[slydog43]

in BF2 I can’t seem to do a Alt-L for directVR scan, anyone else see this?
Also can’t change the 3d reconstruction mode from none to anything else. I also change the sensativity of the head tracking down to about .50, is that normal?

Thanks

[neodraig]

A side effect of changing the resolution after the direct VR scan, that I didn’t notice during my tests, is that the icons of the items are completly offset in the menus.
Also if you try to aim with a weapon that doesn’t have a zoom, it gets right in the middle of the screen and you can’t see anything. This can be fixed by changing the camera height (+1.0) in the vorpX settings.

[neodraig]

(Sorry again if it’s a double post, I always have problem posting on that forum)

Thanks for the reply.

It is not a hotkey issue as I never use the keyboard and only use my Xbox One controller. The only change I make is instead of using the thumbstick buttons, I use start/back (can that be set as default by the way?).

Anyway the problem happens, as I said, specifically when I find an item with stats (so everything except money and ammo).

But to be sure, I reseted the game profile, ran the game without changing any vorpX settings, and to my surprise it worked just fine.

I then added my usual tweaks in the vorpX settings, and the geometry 3D was still working, no more problem :O

I then saved my settings, quit and restarted the game, and saddly the problem was back :(

As it was a problem with the setings I was using, I spent a couple of hours running some tests and I finally pinpointted the problem: the resolution !

By default, vorpX sets the game resolution to 1680p (2240×1680), but the result isn’t very good (to my taste) with a lot of jaggies and a not very sharp picture. So instead, and as my new graphic card can handle it, I created some extra custom resolutions, and for Borderlands I use a narrow custom resolution of 2058×2160 (the game is not very well optimized and the 4:3 and 16:9 2160p resolutions don’t run well, also I had to edit the config file of the game to have the game running without stutters even without vorpX).

The result of my tests is that I have to start the game at default vorpX resolution, and once the direct scan is done, I can change the resolution to 2058×2160 and the game will work just fine with geometry 3D.

The only problem is that I have sometime to start the games 10 times to play with those settings as I noticed that when the second direct VR scan (field of view scan I think) fails the first time, it will never work and I have to start the game again.
Also after that the direct scan is successful, quite often when I change the resolution (has to be done after the direct VR scan to keep the geometry 3D working), the game will just hang and won’t work in the headset anymore (it will still work on the TV screen though).

Still, it’s a weird bug as just looking at the the stats of an item deactivates the geometry 3D, but if I put back the “normal” resolution (2240×1680) when that happens, the geometry 3D will come back.

In the vorpX settings, the default game resolution goes up to 1680p, you could maybe add 2160p ?

So for now I can play again using the trick (changing the resolution AFTER the direct scan), but I’ll keep you informed if I find anything else.

———————————————————

I don’t know if its relevant, but here are the other settings I change in vorpX for that game:

Sharpen amount 1.50
Game hud scale 0.895
Game hud scale horizontal 0.50
Game hud depth 0.00

G3D shadow treatment No S3D

——————————————————

Also here are the changes I made in the config file to have the game run without stutters (not vorpX related):

Location C:\Users\”your_user”\Documents\My Games\Borderlands\WillowGame\Config\WillowEngine.ini

[AppCompat]
MeasuredCPUScore=xxxx.xxxxx (leave it as it is)
CompatLevelComposite=5
CompatLevelCPU=5
CompatLevelGPU=5

[Engine.GameEngine]
bSmoothFrameRate=FALSE
MinSmoothedFrameRate=0
MaxSmoothedFrameRate=0

[RJK_]

With the vice pro its really hard to come to proper conclusion. After testing around for some hours this morning it seems the “advanced supersampling filter – enabled” makes a better image while -application resolution- is set to 100%. But mostly important each time you put on the pro the image looks different in regard of sharpness. That may sound funny but because of the high resolution of the Headset together with the bad lenses you have to exactly meet the sweetspot for a sharp image. Ok, may i am overdoing it but i personally measure the sharpness on TEXT areas.

As far i understand now application resolution is nothing else than the supersampling setting in older steamvr versions. Quite confusing, they should have just left it the way is was before.

Reading this still made me a bit suspicious on how the pro would be treated on a GTX970 for eample.

[real_trisk]

OK, ran the old version, and all the hair and physics things like water surfaces and herbs are all back visible and working. It is definitely something broken in the new patch. Honestly, I recommend rolling everyone back until you can figure out a fix. the weapon ghosting thing is far less game breaking, and can be worked around just by raising the camera height in the Vorpx settings popup so you can’t see it. Capcom has your head height placed low to begin with, anyway.

Thank you very much for posting the old setup file. I’m back to playing the game with everything working.

[real_trisk]

I’m going to try the older profile right now. I’ll report back if it is working, but it should be… the game was working fine before the update.

I did try different mesh detail settings in the graphics, as that was the only thing that looked like it might be related, but it didn’t change anything, everyone was still bald. I re-installed my Nvidia drivers, and I’m using the newest ones. No change.

i7 6600k 16GB RAM 2080ti Vive Pro.

[Ralf]

Odd, I don’t think the character model of the girl in the first mission was bald when I revisited the profile. At least I don’t recall that, not 100% sure though.

I can’t check anything myself this week. If anyone wants to try, it might be worth a shot to experiment with different graphics settings. If that doesn’t help, going back to the earlier state with the weapon shimmer using the 18.3.0 profile probably is the only thing that will.

[Grumdark]

Yes, but that option was only tested by me in only one occasion to make one of the attempts, the rest of the attempts tested were with the option deactivated (unticked), they were not successful either.

Damn translators … they never correctly express the message I want to convey.

The problem is that I can not get into this title in any way, and nothing has changed in my system.
Now I am getting a message with 3 buttons, meanwhile, DAO inquisition announces (does not respond).

[Ralf]

That sounds pretty weird indeed. Never heard of anything like that before. Only thing I can imagine currently is maybe you are pressing the hotkey to disable 3D inadvertantly? You can re-assign it in the config app.

I can’t check the game this week, but will see next week whether it’s some general vorpX issue. Sounds unlikely though, there have been no changes to the profile for quite a while.

[neodraig]

I tried the main game but the problem is the same.

When I open a locker, a chest or safe containing an item with stats ‘weapon, shield, mod…) the geometry 3D just turns off :O

I had made some tweaks in the nVidia panel for Borderlands so reseted them, but that didn’t change anything either.

That’s weird that the games runs well in geometry 3D but as soon you find a new object with stats (it’s not a problem with amno or money) the geometry is deactivated.

[RJK_]

I am not shure and i dont want to raise any trouble but somehow my steamVR + vorpX update seems to make image quality slighty worse to before. When turning up that slider all the way to 500% the image seems to become noticably clearer to me. Note: I have the Vive Pro, may be that has something to do with it.

I wonder how everyone elses impression is in regard of sharpnes after steam has introduced the motion smoothnes stuff (not available on Win7 which i am using).

[Ralf]

One can’t use other people’s savegames for this game, so checking anything besides the beginning is difficult. Playing through whole games to make profiles is not really an option unfortunately. I’ll look into it.

In the meantime try the 18.3.0 profile. Provided your issue is indeed related to the vorpX update, the older profile will fix it.

To apply the profile simply drag and drop the downloaded file into the ‘Local Profiles’ list in the config app.

BTW: Glitches that only apply to certain sections of a game are annoying for sure, but no reason for despair. You can temporarily disable stereo 3D, play in mono and re-enable stereo 3D after the glitchy section. Stereo 3D can be disabled in the vorpX menu or with a convenient hotkey (ALT+X per default).

[Ralf]

Leave it at the value Steam suggests or at least do not raise it above 100%. The important resolution for vorpX image quality wise is the actual game resolution. The second pass resolution for rendering to the headset – which this value affects – should be the normal headset resolution to not waste unnecessary resources without gaining anything.

[Taylorig]

Well hello again.

Just thought I would report back in regards to the issue I was having. Thought I would give VorpX another try today after noiticing that there had been a update to V19. And low and behold, It works now :O

I haven’t changed anything since the last time I tried it and also forgot to close MSI Afterburner before running VorpX and it still worked as intended. Although I did have to do a bit of tweaking with some of the settings like FOV etc. But apart from that I’m very happy now that it finally works.

Thanks again to the creator Ralf for all your work ;)

[dellrifter22]

I could have made it more clear that I’ve had game optimization enabled from the start. The hint of live switching was useful, thanks. Launching the game with geometry as default seems to solve the lighting issues.

Having tested in both steam and oculus, I still get sporadic artifact flicker throughout the image (random splashes every few seconds). It’s enough to be distracting for sure, but something I could learn to ignore. I just want to know if this is normal for the profile, or if there is still some setting I need to hunt down – maybe some ini lines for comparison.

Either way, it looks pretty neat already, and there’s still decent Z3D, so Stormtroopers best watch out.

Oh, and for haints: Origin has been giving me trouble too. I have to try to launch the game some 5+ times before it actually boots =/