Search Results for 'Just Cause'

[Sune Jorgensen]

Using the newest software as of February 2018 (PiPlay V2.0.7.54 and vorpX V17.3.2) when I try to run Assassin’s Creed Origins I always get “unable to load library dbdata.dll” at launch.

I have turned off Uplay overlay.

vorpX works fine with FarCry4 and Just Cause 3.

Any help please ?

[yonkiman]

Ralf: I’m not taking anything personally, I’m just trying to optimize my game for this new environment.

One thing I didn’t understand until today is that tapping EdgePeek keeps the display in EdgePeek mode until you tap it again. I was pressing and holding (because EdgePeek exited when I’d let go after a look), so I thought the only way to use EdgePeek was to hold the middle mouse button down while I tried to do everything else. That’s why I was considering it a PITA. Now that I understand it’s just one tap I see why you were saying it’s not that bad.

[Ralf]

After the latest Oculus Core 2 update I encounter a pretty severe issue here and like to know whether that is something that happens for everyone. To check you have to 1. be signed into the Oculus public test channel, 2. have the new Oculus Home enabled.

What happens here is that I can’t launch any DX9 fullscreen games anymore as soon as Oculus Home 2 is running. Running games windowed still works, fullscreen fails (black screen), games have to be closed via CTRL+ALT+DEL/task manager. It doesn’t matter whether vorpX is running, this is purely caused by the new Oculus software.

All you need to do for testing is making sure the new Oculus Home is running and then start two or three DX9 games in fullscreen mode. Leave vorpX off to take it out of the equation. If you are affected, the issue occurs with or without vorpX.

It would be great if a few of you could let me know what happens (or not) for you and whether you are using an nVidia or an AMD GPU. Thanks in advance for your feedback!

BTW: A fix is already being worked on and working well, before I release it I’d just like to know whether this is a general issue with the latest Oculus 2.0 beta or some rare glitch that only affects a small minority. Strikes me as a bit odd that noone reported this so far.

[prinyo]

About ENB Boost working I was replying to the post by lipplog. Just wanted to make it more clear that the way to use ENB Boos with VorpX is to use the Injector version of ENB. He says that it can, but doesn’t say how, so I wanted to clarify.

About the Windows update, I hope I’ll be able to test it this weekend with MO2.
In general it is expected Oldrim to keep crashing as before. Here is a discussion I had about this ( I was expecting the crashes to be fixed). https://www.reddit.com/r/skyrimmods/comments/757orf/minor_update_to_windows_10_performance_guide_for/do48ts0/

If Oldrim is indeed not crashing for you because of the memory usage it would be very cool if we could find out why.

[nieda113]

Hi i did not say enb boost doesnt work with vorpx and i used myself the injector enb version. But as for the latest enb there is no injector vesion because boris has not managed to get the 64 bit version run for skyrim se. For old rim the enb boost is not needed relating to my own experience, after upgrading to the win 10 fall update and deleting enb boost from may old skyrim my old skyrim runs perfekt with tons of mods that used to crash even with boris enb boost.
And yes there is a 64 bit enb boost usable for skyrim se but no need for it just a waste …

[nieda113]

no i just was a suggestion,, one more thing though some graphics settings can cause g3d turn off. As well as wrong fov settings ccan look like g3d setting is off. ENB is a candiate as well……just trying to give some options….

[nieda113]

@ralph i just wonder never got any game except skyrim having a sharp image when playing. Isit because of nvidas driver devolment to introduce more ways to tune the image. Skyrim is very limited when it comes to adjust screen effect like msaa, or what ever these fancy kind of screen tuning is named.
GTA 5 is the worst of all anyways….. I really miss reshade that was the only way to get a decent image ……

[chukovskiy]

As Blizz allowed to play the new allied races, I started leveling a hunter with Oculus and first person camera all the way (G3D ofc). And this is sooo cool. You can experience all the locations, stories (especially if you are questing there for the first time), interiors, etc from natural character’s POV and it fills like 90% of your field of view. This is just the next level of immersion. Well, maybe I’m a bit biased, maybe it wouldn’t feel THAT great all the way, but anyway. It opened a brand new page of the game for me. Like, just travelling by foot from Duskwood to Stonetalon to begin my questing I’ve found a bunch of places that I really enjoy and that I could never “feel” if I played the usual way (2D, 3d person, monitor, you know).

I mentioned the hunter class because melee’s 1st person view is generally kinda shitty when it comes to combat, while hunter is ranged + he has a pet-tank, so he’s in the perfect position to be a spectator.

[haints]

Ralf wrote:

If you disable the auto resolution feature, vorpX doesn’t touch any resolution settings regardless of full VR/cinema mode, the behavior you observe has to be caused by something else.

One thing I can think of: please check whether you maybe have a “commandline.txt” file in your GTA V folder from manual resolution experiments. if so, delete it.

Thanks for responding, Ralf. I did have a commandline.txt in my folder, but I only added it after I ran into trouble trying to change the resolution–so it wasn’t the cause.

No, the real reason was even stupider. I’ve been using Notepad+ to change resolution in the Settings.xml file. I changed it from whatever VorpX had defaulted it to, but no matter what I changed it to, the res seemed to stay the same … because Notepad+ wasn’t actually implementing any of my changes. I would make a change and then close the Settings.xml file and I assumed Notepad+ had saved my changes since there was no “Would you like to save your changes?” style message. And when I would open the file up again with Notepad+ I could the resolution I had selected … but that was an illusion. I accidentally opened the file with some other program and was shocked to see that the resolution was still the exact same one that had been set by VorpX. Notepad+ wasn’t showing me the actual file but a phantom, unsaved version of the file. I think I’m just going to go back to regular Notepad.

[haints]

Haven’t tried with VorpX yet but it does run well with Tridef 3D (not sure if it is okay to mention that software here?) and Virtual Desktop. BUT … I gave up playing it because you can’t turn any of the stupid hand-holding HUD options off and in the end I just found them too annoying. Really destroys any sense of immersion to have a giant red X superimposed on enemies when you kill them, etc etc.

[haints]

Thanks Ralf. I guess I’ll leave it as is, though there’s something odd that happens … after a while of playing with the 360 game pad, when I push backwords on the joystick I go forward instead, or kind of jerk back and forth. It’s like it is reading backwards on the joystick as both backwards AND forwards. It only seems to happen with GTAV. Maybe I’ll try an xbox one gamepad or the rift controller and see if this fixes my issue.

I want to say I really appreciate how much time you are putting in around here and the fact that I can always count on you for a response. As you may or may not know I was a harsh critic of VorpX for a while but the software has completely won me over. Now when I post about it on the Oculus forum I rave about it so much someone always accuses me of being the developer! I am actually having more fun playing games with VorpX on my Rift than I am playing actual Rift games, and I’ve played a ton of them. You could say that’s because games like GTA V, etc are just more fully realized than almost any VR game, and that’s true, but I would never go back to playing them on a flat screen without VorpX, because VorpX really makes them come alive.

Anyway–thanks again and if there is anything I can do to help get the word out, let me know!

[haints]

Ralf wrote:

GTA V has DirectVR FOV handling, no need for a FOV mod, which would probably cause a conflict even if it worked. You can apply a +/-20° offset on the DirectVR page of the vorpX ingame menu.

Be aware though that doing so will cause image distortion, the FOV computed by vorpX is objectively the correct FOV.

Yes, I see what you mean, Ralf. I tried adjusting the settings you specified and ended up going back to the defaults. Thanks for the information!

[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.

[AlienAndy]

It’s pretty old. 2015, IIRC (the video). The strange part is that the headset, sensor and my Xbone wireless controller all show up in green and say “connected” and it works fine. I just can’t alter any settings in Oculus, because it wants me to set it up and it won’t.

I can load Fallout 4 VR and it works great and looks fantastic, I just can’t do anything hahaha. Well, other than looking around :D

[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.