Forum Replies Created
-
Posts
-
For anyone who runs into the same problem: I finally solved it. If UAC is disabled, the virtual monitor / desktop viewer will not work. This is the first program I’ve encountered like that. It’s counterintuitive since that opens up more access, but in this case, it locks it off. That’s unfortunate, since UAC is frequently nag city and not particularly necessary when you’re monitoring what you use and have antivirus, firewall and malware scanning, but at least I know how to solve it now.
In the meantime, Virtual Display Driver might be a good alternative since that doesn’t require it to be enabled.
I can try a 100% vanilla OS setup on it later to see if it works, I would be baffled if it does. Do you think there’s any chance something from the Pimax software interferes with it on the Crystal Super?
Just an update: I completely reinstalled my OS and this is still happening. Following the troubleshooting advice, in the vorpService.log it says the following over and over when trying to launch the desktop viewer:
ERR: createProcessAsUserWithAdminRights: retrieving the excution token failed: -3
It seems like something on my system is preventing it from launching. Again, I should have full admin rights to launching everything. Is there some Windows service the virtual monitor depends on to launch or something? I’m low on ideas of what to do here.
By admin account I mean this:
I’m not running an additional account, it’s only this. Does that mean virtual monitor won’t work?
After a full reinstall, I still have the same problem. A few notes:
-I’ve had foveated rendering / quadview disabled since I don’t think I’m running any games that would support it (same goes for eye tracking)
-vorpX Service is running on startup, but from your description maybe something is interfering with it.
-When launching VorpX Desktop Viewer, I notice now the “disable virtual monitor” is greyed out in the system tray, despite “enable virtual monitor” being checked in the configuration settings.
-I think I read Virtual monitor is supposed to disable my existing monitor? That’s clearly not happening on my end. I even tried turning off my monitor while Desktop Viewer was enabled and it led to behavior where the previous desktop image was still on the screen and I could move the mouse cursor around, but none of my clicks registered.
Please let me know what else I should try to troubleshoot this.
Yes, I’ve tried “porsche” and it comes up blank. Again, I think this has to be a bug.
I’m actually not sure where it pulled the name from, but it seems to have some sort of ghost entry I can’t get rid of. I created a profile earlier like “porsche test” or something and pointed it to the executable for testing. I experimented with that, then deleted the profile since I wanted to make another one based on a different one. Since then, I keep getting this error and can’t get rid of it.
Is it possible to rollback VorpX to an earlier version?
Yeah, I also wanted to add maybe make this an expert option or add a warning. This always felt a little hypocritical limiting the depth limit while increasing the FOV is still allowed with a warning, as that ALWAYS causes obvious artifacts to me, whereas Z-3D artifacts are more gradual and I personally don’t find as distracting.
Locking away options from the default experience is fine and makes sense. Locking away options that people keep asking for over time creates tension I think.
Sorry, one more question in reference to this:
“Another Hack is using DGVoodoo2 2,71 backdwards to 2,52 and the DGVoodoo2 VorpX factory profile”
I know you said going past 2.60 can cause issues, for compatibility purposes is 2.52 overall better or does it depend a lot on the game?
Only Need For Speed 2 was Glide only, 3, 4, and Porsche Unleashed also supported Direct3D, but getting those running natively without the patch might not be possible, and if the patch is translating from Glide protocols, that might explain the problem.
I’ll look into the other options including disabling the logo, thanks for the advice.
That’s a bummer about Descent 3, that’s another one I was hoping to get working. Thanks for the bluntness at least. I admit it’s frustrating when I try DX7 + dgvoodoo2, nGlide, and OpenGL 1.1 and none of them work with VorpX. I guess I can try and run these with Superdepth3D, though that’s obviously a downgrade from Geometry rendering.
Thanks, but I haven’t seen one Z3D profile that has enough depth for me on VorpX, it’s too constrained. It’s more immersive for me to have artifacts, but proper depth levels. The only way I can get enough with Z3D is using the Superdepth3d shader, but obviously Geometry 3D in VorpX is preferable.
Modern OpenGL games and / or support for a glide wrapper. I’ve come across multiple games with wrappers that convert them to Dx9 or OpenGL, but can’t get VorpX to hook into those.
For example, Need for Speed II, III, and High stakes have fan patches than can render them in OpenGL 1 or OpenGL 3, no profile I found worked with any of them. Hexen II’s profile worked with OpenGL 1, but it was all flat. Doom 2016’s profile worked with OpenGL 3, but also flat. NGlide renders games in DirectX 9, but I couldn’t get anything to hook with it in 3D.
If we could get broader OpenGL support and / or a Glide wrapper support, it would open up dozens of games.