News:

ポストを行うにはアカウントの登録を行ってください
Please register account, if you want to post.

Main Menu

Cursor flickering/blinking on Overwatch [FIXED! Scaling was the issue]

Started by Junton, October 20, 2016, 08:29:10 AM

Previous topic - Next topic

Junton

Edit: The issue was on scaling. Put scaling to 100% so it works.


This is a new issue which I noticed a day ago, and I haven't found any fix for it. Tried to update from version 2.0.136 -> 2.0.139: no help.

And Overwatch is the only game I have seen an issue like this; other games work well. Earlier days the Overwatch videos recorded just fine.

Overlay shows source +60fps and cursor flickering appears on recording 30fps and 60 fps. On 60 fps flickering is just faster.
Among flickering/blinking the picture is kinda buggy too.

I made a comparement video to youtube in 60fps, where I used Dxtory and OBS. OBS seems to record it just fine and picture is much smoother/real 60 fps... but I don't want to use OBS for recording (not the best for that), and I paid for Dxtory.

https://www.youtube.com/watch?v=omeung3rACQ


ps. english isn't my motherlanguage, so sorry for typos etc :D

thesparrow

Try activating "MULTI GPU STABLE PROCESSING" in the advanced settings. Let me know if that worked for you.

Junton

Gonna test it when I get home, but how would that work because I have only one GPU?

Does it affect that I bought second monitor?

Junton

And second thing: is it possible that there is a downscale bug? Read this thing from another topic and thought about that. Resolution is 1080p, but I record 720p

Quote from: Supra on October 17, 2016, 09:09:14 AM
After miraculously trying to record in native resolution again and it working, I think I've found my real problems. It seems there's a downscaling bug with the recent versions, but without scaling I run into a hardware limitation.

Trying to record QHD@60 with Ut YUV422 peaks at around 140MB/s write speeds, and my single recording drive (WD Caviar Black 1TB) peaks at 127MB/s. Either that happens or I get 'Encode'(?) causing a bottleneck. Maybe it's time to get another HDD and get a RAID 0 drive array going.

ClassifyLP

Quote from: Junton on October 20, 2016, 03:34:54 PM
And second thing: is it possible that there is a downscale bug? Read this thing from another topic and thought about that. Resolution is 1080p, but I record 720p

Yes, there is certainly a performance problem with scaling in current versions, but that might not be the cause. To rule it out, turn off scaling.

Also, please post the environment information as described here: http://forum.exkode.com/index.php?topic=2.0

thesparrow

Quote from: Junton on October 20, 2016, 03:30:17 PM
Gonna test it when I get home, but how would that work because I have only one GPU?

Does it affect that I bought second monitor?
I thought exactly the same thing until I tried it. It worked for me. It's worth to give it a try.

Junton

Problem solved! Put scaling off (100%) and problem is gone!

Well the file size will be bigger. Sad that it takes more time and size from harddrive since I extract videos anyways to 720p.

Junton

Quote from: thesparrow on October 20, 2016, 10:53:45 PM
Quote from: Junton on October 20, 2016, 03:30:17 PM
Gonna test it when I get home, but how would that work because I have only one GPU?

Does it affect that I bought second monitor?
I thought exactly the same thing until I tried it. It worked for me. It's worth to give it a try.
And also this thing fixed it too! I think I'll be using this, so I can record straight to 720p :) thanks!

ExKoder

From ver2.0.130 in the implementation of DX11, it uses CommandList,
The bug of Dxtory.
Not only the cursor, the captured data is incorrect.
In a multi-thread is enabled DX11, when performing scaling in the GPU, the problem will occur.
Does not occur is a problem in the DX11 devices D3D11_CREATE_DEVICE_SINGLETHREADED flag.