Forum Replies Created
-
AuthorPosts
-
madcapParticipant
I’ll have another go or try and use my keyboard’s software to create a mapping profile for the game if I have no success. Thanks for the info. The ability to change the default mapping would be useful for us cursor freaks.
madcapParticipantThat’s what I did for the stick. Up/down/left/right on the stick was bound to wasd. I bound them to the cursors (matching game binds) but it’s not moving the character around. I tried saving profile and restarted the game, but it didn’t work. I notice the right stick cannot be changed at all (only its alternate mapping). Does that one use cursors by default?
madcapParticipantCopying the autoexec didn’t work. The DLL the mod uses must be breaking something. I posted the problem on modDB for the author to see, since this is a popular mod. If I find a solution I’ll post it here. Thanks for your time, Ralf.
madcapParticipantI did a full uninstall and cleaned registry (I did find old entries, but mostly obsolete paths). Installed GOG version and it worked. Installed Tactical Expansion Mod v1.1 and it broke the FOV command. My bad, sorry. I just thought that mod changed some A.I and weapons and was basically my go to mod. I can’t see anything in the mod’s readme (it does have a known issues part) but no mention of this problem.
madcapParticipantI’ll give it a go later. There may have been files/entries left over when I aborted the retail install. I’ll clean registry too.
madcapParticipantI think there’s a problem with this GOG version. cl_fov just isn’t applied no matter what value I enter (even in console) in or out of vorpX (no visual change). Crysis Warhead (Steam version) does work with your crysis profile. Both shortcuts (x64, but I did also try x86) are being started with -dx9. I could assume a corrupted install, but I thought these commands were coded into the exe and the other commands seem to work.
madcapParticipantI just found it in the autoexec.cfg file, but it doesn’t seem to be applied in game. The game isn’t on a system drive. Vorpx is currently running in admin mode.
The fov in the cfg is: cl_fov = 96.016045
Looking at console it seems to be displaying that setting, only that everything is distorting as it would if the fov was very low. The only way to get it near to how it should look is with Image Zoom.
This is a GOG version. The OS hates my retail DVD version (obsolete securom I think), so I can’t test it.
P.S. I tried with -devmode too, but it didn’t make a difference.
madcapParticipantVorpX handles the FOV perfectly for this one in full VR. You might want to prevent the game going to third person mode (when feeding etc) to keep things consistent. Unless there’s some mysterious reason why Index would have problems on VorpX then you should be good to go.
madcapParticipantWill you be fixing DirectVR for this game in the future? It is one of the games that swayed me into buying VorpX when I saw it advertised. I’ve tried with and without the mod. I think the mod is trying to work but VorpX just isn’t rendering GTA5 correctly to make it playable. Either the world distorts and sways and/or the scaling and ratio looks all wrong. It also isn’t aligning with the hmd display properly and feels like I’m staring at a big screen. Image Scaling only seems to shift on Z but the ratio is wrong.
I’ve put in several hours, tried image scaling, different rendering modes and options, game’s player fov, in-game resolutions etc etc, but it all looks awful. Crysis looks better (just a little high on scaling, but probably fixable), so anything like that would be acceptable.
madcapParticipantIt won’t let me edit above, but it was Bitdefender AV that prevented hooking on these non-steam games. I’ll try and setup an exclusion.
madcapParticipantp.s. using a Rift-S
madcapParticipantVorpx is totally ignoring GTA 5 (I have the disc version that works with Social Club directly, not Steam). Vorpx also totally ignores Crysis GOG version. It only seems to pick up games launched through steam. Am I missing something?
-
AuthorPosts