Forum Replies Created
-
Posts
-
Oh thanks for your answer.
It’s called Remote Play PC. You can find it here.
http://tmacdev.com/forum/files/
It begins to be very popular and I must admit I am enjoying playing Bloodborne on my computer without having to buy another PS4.
Anyways if you have time, it will be cool to take a look. If not, thanks for all your work anyways :)Rgds
Its already done on my control panel :(
My previous vorpx version played ALan Wake without these artifacts, so I guess it s linked to the new version only (and the new DK runtime of course :()I have been able to reproduce this black artifact in cinema mode as well as in real 3d mode with skyrim. and the fact is that in the lowest settings there are no black artifacts in skyrim
like you witouht vorpx i can play these games maxxed without a difficulty and all other dk2 games are running flawlessly so you re probably both right : its a matter of workload and this workload probably is added by the new vorpx reconstructing the 3d image in the the new runtime environmentHi again Ralph, it seems that you’re (as usual ? :) ) right…I still have artifacts, even with 358.50. I have tested Skyrim and no artifacts whith lower graph settings… I can understand for Skyrim that perf matters but with Alan Wake (old) a 970 SLI and i53570K must be largely enough :(
Hi Ralf,
I finally have found the cause of my artifact : nvidia drivers. I was using nvidia 358.70 and 358.78 beta drivers. Revert back to official 358.50 solved the issue. The Oculus config panel complains (he want 358.70 apparently) but everything is working well.
Do you know if 358.70+ are really mandatory ?Side question : for my personnal knowledge, in cinema mode, when trying Alan Wake I have Z-normal selected in Vorpx settings and with Assassin’s creed 1 it s off. Is it normal behavior or something i m doing wrong ?
Thanks
more info. Games tested in virutal cinema mode : Alan Wake, Assassin’s Creed 1 (don’t think it s a matter of power. I have 970 SLI and with or without SLI, black bars are presents)
Hi Ralf,
I have exactly the same problem :(. Please help !
nvidia driver version : 358.70
Great work nevertheless !Well I have just read a Battlefield 4 post that may answer most of my questions :
– You can’t have viewing on DK2 and targeting on mouse. I guess I just have to lower the mouse sensitivity in game or head sensitivity in DK2 options to improve the targeting precision with head (what is better head or mouse sensitivity ?)– I have to set a FOV near 100 to have a better scale (any other Vorpx expert options to achieve that ?)
Ok Ralf. After dealing with real life and doing few tests, I’m back with good news.
I have done what you suggested but it doesn’t solve my problem.I finally decided to remove all my USB stuff and unnecessary apps running in background of my Pc and find the culprit !
It was a tiny useful firewall called “Windows 7 firewall control”. Vorpx was authorized but, I don t know why, even in that case, this firewall only blocks the action of VorpX !! (it has no antivirus action so it s a mystery why…)Well now it s working. I hope that my experience helps other users.
Thanks for your help and time.No no I m pretty sure I have the latest version. I’ve clearly seen (with a big smile on my face) the update :). Nevertheless, to be sure I can give you the executable size.
I have a logitech mouse with its related logitech driver. Do you think that it can cause incompatibilty with Vorpx ? (again why are HL2 and desk scene working anyway)Thanks for the quick answer Ralf. I am actually at work but will try that as soon as I’m back at home. The DK2 firmware is already updated.
I am a little worried as the Desk scene and Half Life 2 are working flawlessly. I am wondering if this is compatible with the possible cause of a bad runtime installation ? :(