Forum Replies Created
-
Posts
-
No. In case of a ‘hardware cursor’ (which is a special way windows displays the cursors that can’t be stereo duplicated) vorpX uses its own. Most of the time vorpX can detect when it should display its own cursor, but in cases where that might fail, you can use ALT+C.
Software cursors are entirely handled by games, so they should always be visible whenever the the game sets them visible.
I’ll reinstall the game and check whether I can replicate your issue. I don’t really expect anything though. For a fairly long time Mass Effect was one of the usual test cases here. Never encountered such an issue.
It’s Z3D only. IIRC there was an issue with stereoizing the ground plane when I checked Geometry 3D, which in the end made me decide to leave it at Z3D.
@ hemingwaysghost: Did you try it vorpX? If it works I’d happily check this myself and write up a little guide for those interested. nVidia’s custom resolutions typically work great from my experinece, but things are different for AMD, so AMD users in particular might find this interesting.
No worries, the new environment will become the default, but switching back to the original scene is just one click away.
The latest update on Uplay I got today when I launched the game doesn’t seem to work anymore either. I’ll take a look at it, but no promises. If possible I’ll fix it, otherwise it will be taken off the supported games list.
Short update: mystery solved, but no good news: instead of using a dedicated DX9 .exe like before the game now always runs through its DX11 .exe even if DX9 is selected in the graphics options. The profile would have to be redone completely to account for that. I’ve taken the game off the supported games page for now. It might come back later, but don’t hold your breath.
You might be able to hook it by removing ‘fc3_blooddragon_d3d11.exe’ from the excluded programs list in the vorpX config app, but even if that works, vorpX will not recognize the game, so 2D only without any features available a game with a profile would normally have.
I don’t have the game installed currently, but IIRC the hardware cursor has to be disabled in the game options. Typically vorpX does such things automatically via DirectVR or at least shows a hint, but apparently not in this case.
Let me know if that helps and I’ll check whether it can be automated.
Don’t get too excited. Even with the shader replacement system reeady (which took a bit of a backseat due to other stuff admittedly) fixing such glitches will require a considerable amount of work per game only doable by people with a high level of shader programming skill. How well this turns out in the end depends entirely on people’s willingness to dedicate time and effort for fixing shaders. Maybe you want to become one of them?
Apart from that tnstead of hoping to get these things fixed for every game out there better follow my advice above and don’t overdo it with the 3D-Strength, as tempting as pulling all sliders to the max might be. That’s really not how most settings in vorpX work. Just like you don’t tune a guitar by applying maximum tension to all strings.
That’s what the shader replacement feature that is still planned would be able to handle. Requires individual fixes for every game though, which would mostly be a community task.
I believe I gave you the following reply to basically the same question several times already, so just in case I’m mistaken in that regard: your best way to deal with the matter is not cranking up 3D-Strength above realistic levels. In many cases shadow glitches only become highly annoying when you set the 3D-Strength value higher than it is supposed to be. For official profiles just leave it at (or close to) default. Like many other settings in the vorpX menu this is not a more-is-better setting.
Due to popular demand since a few versions there is a ‘Generic 3D Display’ device that you can select in the config app to play SBS on your monitor.
Caveat: this is not officially supported. vorpX is meant for VR, you are basically on your own using it for SBS monitor gaming.
That’s not really a vorpX issue but related to how many first person games handle weapon rendering. To look good on a monitor often weapons are rendered as a separate layer with different projection settings (read: lower FOV for the sake of simplicity) than the game world.
That’s not true for all games, but I’d say about 2/3 or so handle it that way. If Geometry 3D is supported for a game, you can get around that by using the ‘Camera Height Modifier’ option in the vorpX menu (under ‘More 3D Settings’ to lower the weapon a bit. A little height offset can do wonders.
BTW: In Geometry 3D games typically 1.0 is the correct value for natural world scale, at least as far as official profiles are concerned. Base G3D parameters are usually dialed in during authoring to ensure that. Might not always be 100% perfect, but at 2.0 the world will typically be too small. For Z3D things are a bit different. 2.0 is usually a good value for correct scale at medium to far distances where you look at most of the time while actually playing a game.
Should be fixed now. Since your license wasn’t activated yet, it wasn’t added to the license database. Hence the server did not recognize your download request as valid.
If you still did not receive a link, please let me know.
BTW: You should also have gotten a download link from MyCommerce, both as e-mail and directly after the purchase process.
That was pure speculation, sorry for the confusion. What I said was that it *theoretically* *might* be possible to do something like that instead of hooking into documented APIs like DirectX or OpenGL. That’s not something vorpX currently does though. Would also require a lot knowledge that only nVidia/AMD have since they don’t document the inner workings of their drivers.
Don’t mean to sound rude, but I believe it’s the third or fourth time now that I’m trying to explain to you that some games do not like mouse and gamepad input at the same time. So whenever that is the case and vorpX has to emulate a mouse for head tracking, its internal gamepad to mouse/kb mapper is used instead.
The alternative to using the mapper in games that don’t like both input methods simultaneously would be no gamepad at all.
If you have disabled the gamepad override the vorpX menu, please re-enable it or reset the profile to default in the config app. Do not touch any related settings afterwards. The default is the default for a reason.
I’m not quite sure whether I understand the question. Of course vorpX will still be able to add stereo 3D to games, just as always.
If you have further questions in this regard, please make a post in the technical support forum. I’d rather not see a thread becoming totally off topic with the very first reply. Thanks!