Forum Replies Created
-
Posts
-
I cant remember the exact settings but IIRC the ingame HUD was one eye only or moving around i think. Your 3D strength was relativeley low , probably thats why the issue with the HUD wasnt much noticable.
You can always try the Shader Settings ( Enable expert settings required ) to see how they affect different elements of the game. You can also try different game engines (in this case early DX9 engines) and see if elements are rendered differently, then use the Shader Settings to make corrections.
If a HUD element is one eye only or not placed properly you can try settings like “no transform” or “HUD” for example, but you need to keep in eye that other elements may use the same shader like this game. So a compromise must be made by using a shader setting that doesnt mess up the 3D of the corresponding elements too much.
An alternative if anything fails and only HUD elements remain broken is Edgepeek+3D OFF, but this is not really good for a descent profile creation.
You can of coarse use 120 just use what suits best for the headset youre using. I thought i recommend a high value, 80 or 90 wouldnt have made sense.
Resolution: Use the highest that you can afford ,i used 1920 x 1440 and the game looked awesome, but with relatively small HUD elements. (Health counter ect)
Less experienced users would still be protected from messing up the profile database without even noticing it though.
May be connecting this to the “Enable expert settings” switch would make sense.I assume thats what you meant.
Man i was so exited about this that i had to try i right away.
GREAT Info on that DX9 Renderer!Unfortunately the HUD of your profile is broken and Guns are 2D only. This afternoon i did some tweaking with a different base profile so i now have a slightly optimized profile that has just enough Depth for an acceptable 3D and a proper Gun sight. Few objects remain at HUD Depth (guess we have to live with that) but i put the rest a bit more in place. Hope you dont mind me putting that up the cloud. (Was trying to get that game to work for AGES !)
For those who cant watch youtube for some reason:
– Unreal Patch 227i required
– Rename Unreal.exe to Unreal_1.exe (or Unreal1_Vorpx if you wish to use slydk1982’s profile)
– best played in FULL VR Mode
– set FOV (Widescreen) to 110
– use Edgepeek for HUD view
– gaining resolution above 1920 makes HUD very small.Got a fiew screenshots as well (for the Unofficial List)
May be something worth to mention here, with a driver update from 398xx to 417xx i was able to HALF the baseload of the GPU from 9 to around 4,5%. Though steamvr still draws the same power :-/
Thanks Ralf, the Essential Hints Guide explained it all. Very good ! (Not that i havent read that before, i’m just getting old
)you mean SteamVR home environment ?
Thats disabled here, still 20% CPU power. Enabled its at around 80%.*Very good that each game has its own thread now, so things can be updated in case*
Starpoint Gemini doesnt seem to work anymore with vorpX in G3D after one of the recent updates. VorpX hooks in 2D still though.
Last night i tried Doom3BFG VR.Shame on me, that was the first native VR game i went into a little deeper. There was something i noticed and i hope i can describe my observation properly without beeing sceptical. – With the native VR game everything was in place, it felt absolutely “real”. The environment looked stable and in place. Later on i was testing a few other games with vorpX and “somehow” they looked different. Expecially when using headtracking i had the impression of parts of the environment geeting bent, or lines on the ceiling followed the view away from the eye in a rather non natural way.(compared to the native VR game). The only explanation i had for that (after intensively reading the forum) is that FOV seems to be the most important aspect for realism in VR and if FOV isnt right a game with vorpX may not look as good as a native VR game (i assume its all about the camera position, wrong FOV, no precise camera calculation). – In summary: Bad FOV, bad VR. !?
Thanks for answering. A guy is selling two used Inno3d 1080ti (X3 ultra and X4) for a good price. I too prefer running hardware at normal levels and the X4 is only slightly overclocked factory side. This card beats many other in noise and cooling and is sold as an ultra low level noise card. Because noise is an important aspect to me, i consider buying it. One disadvantage is the slightly higher draw in current, but that should probably take effect only in rather demanding games.
I thought of downclocking this card for less current draw, that was the reason for my question above, but that probably couldnt be done without running tools in the background.
There may be a trick. (havent tried that with reshade yet and theres no guarantuee that it will work). Assuming that reshade consists of a d3d9.dll and possibly some other files that you put in the game folder you could try the following:
-backup everything first
-download a hex-editor like HXD somewhere
-rename the d3d9.dll (from reshade) in the games folder to r3d9.dll
-hexedit the games exe, change each “d3d9.dll” entry that you find to “r3d9.dll”
– if that dosnt doest work, look through any other file in the game folder that contains “d3d9.dll”, proceed as above file by file.
– dont hexedit the reshade files, but if the game doesnt run, go through those as well.Some games refer to the windows/system32 or syswow folders only, as a last chance put reshades “r3d9.dll” there (DONt overwrite any d3d9.dll !! )
We use this trick with DGVoodoo2 and certain DX9 games sometimes and it works well.(most of the time)
Make shure you dont break any laws by doing the above.