Ground Texture Flicker

[Midenos]

Someone else experience ground texture flicker with latest amd cards and driver?

[Hydrogenius]

Just want to say that we have same issue here. I'm using 3070 and bought version no issue, while my wife is using 6800xt friend pass version with issue :/. Let me try the dx12 fix

[Orange Shards]

Originally posted by KenLee:

Originally posted by tonighttheworlddies:

Yes I have the same problem. Does anyone have a solution to this yet?

It's a depth fighting issue. AMD's 6000's driver has poor compatibility with dx11.
However, since this game is made with ue4, you can for the engine to use dx12 as engine RHI. Just find your exe in path like:
`D:\Steam\steamapps\common\ItTakesTwo\Nuts\Binaries\Win64\`
Then start it with cmd"
> .\ItTakesTwo.exe -dx12
Enjoy.

hi there , this disables origin overlay and i cannot invite friends after. is there a way to bypass this?

[Orange Shards]

Originally posted by I_come_in_peace:

Originally posted by Edith:

this is soultion about that flickering problem

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

That's a very long and complicated video for something rather simple :-)
I made 3 screenshots to illustrate where to enter what in Origin:

https://www.dropbox.com/s/job5h7t3z891y1x/it_takes_two_01.png?dl=0
https://www.dropbox.com/s/z71djfl31bcs28u/it_takes_two_02.png?dl=0
https://www.dropbox.com/s/1tfh1xmbibkqi0o/it_takes_two_03.png?dl=0

this disables origin overlay so i couldnt invite friends. any fix?

[Wok]

I think you need to add that -dx12 flag inside Origin overlay, rather than Steam launcher.

[Orange Shards]

Originally posted by Wok:

I think you need to add that -dx12 flag inside Origin overlay, rather than Steam launcher.

i added that in origin but it wouldnt let me invite

[Frostb!te]

Same problem with my AMD 6600XT.
The -dx12 cmd line parameter works. I think it adds some stuttering from time to time. But it's playable.

[RomDaDon]

doesn't let me invite friends either putting in the command in origin overlay

[Schmuppes]

I've encountered the same bug on a brand new RX 6600 XT. Hazelight wouldn't help me and pointed to EA when I finally got a response from them via e-mail. They don't seem to be interested in this, so seeing as the issue has been a thing since day one, I'm not very confident it'll be fixed. I've yet to try the -dx12 command line argument though, so I'm kind of confident that I may do a second run with the game towards the end of the year. The way the devs can't be bothered to show any reaction whatsoever is pretty shameful. The game will sell a lot more copies if the price drops a little, so they absolutely should see to it that the game runs fine on AMD's current generation of graphics cards.

[I_come_in_peace]

Originally posted by Schmuppes:

I've encountered the same bug on a brand new RX 6600 XT. Hazelight wouldn't help me and pointed to EA when I finally got a response from them via e-mail. They don't seem to be interested in this, so seeing as the issue has been a thing since day one, I'm not very confident it'll be fixed. I've yet to try the -dx12 command line argument though, so I'm kind of confident that I may do a second run with the game towards the end of the year. The way the devs can't be bothered to show any reaction whatsoever is pretty shameful. The game will sell a lot more copies if the price drops a little, so they absolutely should see to it that the game runs fine on AMD's current generation of graphics cards.

I also reported the bug several times and didn't even get a response. That's really a shame and it puzzles me as I think that the game has been quite successful. I know AMD has only ~ 17% market share on GPUs, but you'd still think that's a large enough user base to fix such a relevant issue.

[Schmuppes]

Originally posted by I_come_in_peace:

I also reported the bug several times and didn't even get a response. That's really a shame and it puzzles me as I think that the game has been quite successful. I know AMD has only ~ 17% market share on GPUs, but you'd still think that's a large enough user base to fix such a relevant issue.

It's ridiculous. I even joined their Discord server where several guys from the Dev team are present most of the time. There is zero reaction from them directly. EA has claimed to have filed my bug report and forward it, to whoever that may be. I understand that

a) The share of PC copies is pretty low in comparison to console sales, and that
b) The share of PC users with AMD cards is relatively low, and that
c) The share of AMD GPU users with 6000 series cards would be relatively low for the time being.

That said, it's still probably a four or five digit number of users experiencing the bug. It can't be too hard to implement the -DX12 hotfix officially in a way that doesn't mess with the Origin overlay and friend invites if you can't play locally. Even if the bug really was caused by AMD's drivers, Hazelight ignoring the bug is really bad. I'm not the guy who can contact Epic (who sold the engine license to Hazelight) or AMD (who are responsible for the GPU drivers) and I sure as hell didn't write the code for It Takes Two. I'm just the guy who paid nearly full price for the game and should be able to expect fixes for bugs that were in the game on launch date.

[RomDaDon]

I found that you can still play online with the -dx12 command line
buddy was using the free game pass download from steam to join my game rather than the origin overlay. i hosted the game twice with him joining the game with game pass, one without the command line which lead to ground flickers and one with the command line. He never saw any flickers on either playthrough but he has a nvidia gpu.

So as long as your friend has the game pass download from steam they can join your game with the hotfix without origin overlay

[I_come_in_peace]

I actually got a reply from Hazelight today regarding the problem:

"We are aware and hopefully this will get fixed soon. "

So fingers crossed ...

[Schmuppes]

Originally posted by I_come_in_peace:

I actually got a reply from Hazelight today regarding the problem:

"We are aware and hopefully this will get fixed soon. "

So fingers crossed ...

How did you contact them?

[I_come_in_peace]

Originally posted by Schmuppes:

How did you contact them?

By their official contact email: [e-mail]

[Schmuppes]

Originally posted by I_come_in_peace:

Originally posted by Schmuppes:

How did you contact them?

By their official contact email: [e-mail]

That's what I tried as well. Their first response was "Nasty bug, try reloading the last checkpoint" and when I reiterated my issue and told them that it wasn't that simple, it was "all bug reports need to go through EA, bye!"