Forum Replies Created
-
Posts
-
Then there is a pretty good chance that you will be able to create a user profile based on the Dolphin profile quite easily. Let me know how it went.
I forgot what it was, but I’m pretty there was something that works better with DX11. Anyway, all will work automatically as intended with the next maintenance update.
Emulators in general are not really top priority TBH. Pretty much rainy Sunday stuff, but I’ll keep Citra in mind.
If Citra also has DX11 or OpenGL SBS output you might be able create your own profile using the Dolphin profile as a base for the time being. Fairly simple: just make a copy of the Dolphin profile in the config app and assign Citra’s main .exe. No guarantee that it will work, but worth a shot if it has SBS 3D output too.
Not necessary anymore. Thanks for heads-up though! Doesn’t work as intended due to a super stupid mistake. The routines that make the settings changes are never called unless Dolphin is fully hooked, which obviously isn’t the case until DX11 is selected.
Will be fixed in an upcoming maintenance release.
The PCSX profile is mostly an old experiment. No 3D support at all, I just included it years ago so that people can use PCSX2 in 2D.
Dolphin: Could you reset the settings to something else and then check whether vorpX can do the DX11/SBS setup automatically on your machine? It should do that normally (requiring one Dolphin restart after the settings have been changed). Let me know if that works for you or not.
If you “just” want to fix HUD/menu elements, then you don’t need the replacement shader stuff at all. Once that is finally done some day it will be used for more complex fixes.
HUD/menu shaders can be defined in the shader authoring menu, pretty much just point and click work. vorpX does the actual implementation, all you need to do is flipping through shaders using the authoring GUI and define them as HUD (plus maybe set some extra flags to enhance the detection if necessary). The HUD can then be scaled and moved in 3d space in the regular vorpX menu.
Should be relatively self explanatory. Basic instructions under ‘User Profiles’ in the help. If you have questions, shoot me a mail to support at vorpx com.
The only two DX10 games I can think of being still relevant enough to warrent that effort are Bioshock (already works great in DX9 mode, the DX11 remaster has G3D too) and Crysis (also DX9 G3D). So no, probably DX10 G3D won’t happen.
I have all the sympathy in the world for tinkerers, after all one could say that’s how I got into my line of work myself. But to play The Elder Scrolls Online in FullVR mode with correct field of view (read: without a zoomed in image) you will want to reset the profile to default in the config app and not touch any of the image size related settings afterwards. Trust me. :)
Attaching should only take a few secs normally. Send the trouble shoot data archive to support at vorpx com. No promises, but I’ll take a look at it.
Note that this is still very much a work in progress. Replacement shaders are only working for DX9 currently and there is a lot left do be done. Some basic docs are in the vorpX help, although most of that is probably subject to change later.
You can fool around with it and even fix some DX9 shaders if you are willing to dive into shader assembly (or even have experience with that), but the whole feature set is far from being ready for prime time.
I‘m not sure whether there still is a shader assembly reference for DX9 (shader model 3) on the web, but at least for shader model 4/5 you can find a full reference on Microsoft.com.
The best way to deal with menus that vorpX cannot scale down is switching to EdgePeek mode (ALT+MOUSEWHEEL or left (or right?) thumbstick button). In EdgePeek mode you can look around freely, which is way more comfortable for using menus, also useful for watching cutscenes.
If you haven’t done so already, check the ‘Quickstart Guide’ and the ‘Essential Hints Guide’ in the vorpX help. They contain tons of useful infos like the above.
There is no such thing as a “3 core bug”, neither in 3D-Vision nor in vorpX. I am aware that this rather odd myth is fairly popular among members of the 3D-Vision community for some reason, but it’s really just that: an odd myth.
The actual fact of the matter is that submitting work to the GPU in most current game engines is still largely a serial task. It doesn’t automatically get parallelized just because you use a CPU with more cores. If one core gets maxed out by the main render thread, the whole game is limited at that point, no matter how many cores are left doing nothing. That’s not a bug, that’s just how things work. The only ones who can change that are the game devs by making better use of multithreading in their rendering code (as far as possible, there are limits to that).
As for your original question, the recommendations I can give you are the ones above.
In case of performance issues your best options are to reduce graphics details in the game’s options menu or switching to Z3D in the vorpX menu.
If performance issues only occur in certain areas, you can also switch temporarily between G3D and Z3D using a keyboard shortcut. Per default that is ALT+K (can be changed in the config app). Caveat: in some games with more complex engines live switching from Z3D to G3D may cause graphical anomalites, so switching back and forth using the shortcut key isn’t always a viable option.
More detailed information can be found in the ‘Performance Optimization’ section of the vorpX help.
It’s automatically capped on purpose to fit the game’s maximum field of view setting. Raising the ImageZoom beyond the capped value would lead to a wrong FOV, i.e. the image would look zoomed in/distorted.