Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Do you know which specific Update this is occurring on and which GPU are you using?
Would you be able to provide a video of the issue occurring?
- Ubisoft Support
Just to confirm, as active development has ended for the title, it may be that this will not be addressed as there is a workaround for this with the older drivers.
- Ubisoft Support
Dont bother. Its an issue that will never be corrected. Game support by Ubisoft has ended, and NVIDIA/AMD most likely will not fix either for a game barely played anymore.
Yea i hear you but its doubtful anything will be done. This has been an issue for a very long time. If something does end up being fixed than great, but I wouldn't hold my breathe,
https://www.youtube.com/watch?v=xJ-bZ7l_Xgw
https://www.youtube.com/watch?v=AJtuMhw66I4
Idk if its normal but im worried
GTX 1660 SUPER latest drivers
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]
Yes the old driver had a workaround, but no, drivers should not be required to work around these in the first place, games should not be shipping broken.
Refer to https://wccftech.com/exnvidia-driver-developer-game-ships-broken/
Older driver is not a workaround, new hardware may not even support those drivers, end of activate development does not mean that games should remain unfixed, companies should have responsibilities for sotware they sell and even old games should get a new patch at least once a year to fix critcial game breaking bugs (be it gemeplay, sound or graphics or other feature breaking bug) and all broken things and to enhance compatibility with new software and hardware. Lifetime maintenance patches for all the commercially sold software should be legal obligation for all sotware companies.
Thank you for your feedback v00d00m4n, it has been noted to the relevant teams, however in the meantime we still cannot confirm any additional updates will be made to the game.
Should this be change at all in the future, we'll let players known.
Thank you for your understanding and sorry for any inconvenience caused.
- Ubisoft Support
Has there been any progress made to this? It definitely takes away from the experience and is actually in the game breaking area for many people. It sucks because I really like the game, to the point that I bought it twice, on PS4 and PC (Uplay that's why it's not in my Steam library) and I'd really like to be able to play it normally without using incredibly outdated drivers..
Thats is a generic answer Ubisoft uses but Origins support ended already. No more updates will be made to the game.
Only thing that can be done is to report issue to AMD/NVIDIA to fix the issue.
Hey there Wik_Thor, thank you for getting in touch. As kindly mentioned by my colleague and animal_PLANET above, it's important to note that the game's life cycle has concluded. This means that the remaining issues will likely not be addressed. That said I welcome you to continue sharing any thoughts or feedback you may have regarding the visual water issue within this thread, and I will be sure to also pass this along to the dedicated teams.
-Ubisoft Support
I am no shader modding expert, but I have seen modders injecting custom shaders into previous games such as AC: Brotherhood to hide the white haze always visible at the top of the screen.
Perhaps something similar can be done to address the Water Shader Glitch, as it seems to be directly related to a poorly coded shader that got broken when Nvidia removed a workaround in their drivers.
We understand hearing this news is sad and disappointing, for this we are deeply sorry.
Hopefully, as you mentioned a mod will come along that can help address this.
If you need anything else please let us know.
Thank you.
- Ubisoft Support