

There have been recent reports of graphics flickering underwater in Assassins Creed Origins.
A video of the issue can be found here: '>
As you can see in the video I managed to isolate the smallest boat in the game; you can see the problem is far reduced on this object. As the sailboat comes into the camera's view the problem becomes much worse. Resembling the "flickering" that people have been reporting.
If a developer sees this, there's a support ticket open with my dxdiag: 15409941
Good Frame
Bad Frame
Reproduction steps: (sorry about the aspect ratio, that's what Nvidia capture does when the resolution is 16:9 on a 21:9 monitor)
Here's everything that's known about the issue (if anybody else has any information I'll add it to this list)
Cheers!
Liam
Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.
Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.
Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.
Was hoping to keep everything in the OP, but there's a restriction of 300s to edit the OP <sigh>
The video link appears to not be working. This is it: https://www.
Forcing DirectX into debug mode yields the following errors during the bad frames (These errors are not present in 461.92):
D3D11 ERROR: ID3D11DeviceContext::OMSetRenderTargets: The RenderTargetView at slot 0 is not compatible with the RenderTargetView at slot 1. It is only possible to render to multiple RenderTargetViews if the effective dimensions of the Views are equal, as well as the Resource types, multisample count, and multisample quality. The RenderTargetView at slot 0 has (w:256,h:256,as:1), while the Resource is a Texture2D with (w:256,mc:1,mq:0). The RenderTargetView at slot 1 has (w:1024,h:1024,as:1), while the Resource is a Texture2D with (w:1024,mc:1,mq:0). If the Resources are Buffers, the Resources' Widths must match also; unless GetFeatureLevel() returns D3D_FEATURE_LEVEL_11_0 or greater. [ STATE_SETTING ERROR #388: OMSETRENDERTARGETS_INVALIDVIEW]
D3D11 ERROR: ID3D11DeviceContext::OMSetRenderTargets: The RenderTargetView at slot 0 is not compatible with the DepthStencilView. DepthStencilViews may only be used with RenderTargetViews if the effective dimensions of the Views are equal, as well as the Resource types, multisample count, and multisample quality. The RenderTargetView at slot 0 has (w:256,h:256,as:1), while the Resource is a Texture2D with (mc:1,mq:0). The DepthStencilView has (w:1024,h:1024,as:1), while the Resource is a Texture2D with (mc:1,mq:0). [ STATE_SETTING ERROR #388: OMSETRENDERTARGETS_INVALIDVIEW]
Hey there!
Thank you for the report @LFisher122 !
This is something that has already been passed onto the team for further investigation, so I've added your report to this.
We don't have any further information regarding this investigation at the moment, so in the meantime please continue to use the 461.92 driver if this is working as normal for you.
Should we have an update from the team, we'll share it here to keep you in the loop.
Thank you!
last edited by LFisher122