Epilepsy Warning

[=7CAV=SPC.Henson.K]

Is there a way to disable the warning? It sits on my screen for at least 5 minutes with no way to bypass it.

[pemmons1]

I'm not sure that this will help-- it won't disable it-- but you probaby have a lot of saved games on your hard drive, most of them "autosave". If you delete most of these, the time spent on this screen will go way down. You can do so in Windows or command prompt without screwing the game up in any way (as long as you keep the most recent saved game and a few others along the way if you wish). Someone gave me this suggestion way beck when and it worked for me.

Then check in options how often autosaves are made. Mine is set to ten minutes, which is probably more often than I need, but I seem to recall that the default is only five minutes.

[Green Bastard]

i have the same problem. I've dumped all save games, cleared directx shaders, verified game files, ran as admin, uninstalled, reinstalled, uninstalled with iobit uninstaller, reinstalled. Nothing seems to fix it. I'm not sure what else is left to do, besides complete format and reinstall of windows.

[Vyktor]

Yeah I am seeing the same issue and I suspect the cause is due to a poor connection to Ubisoft (I only have 1 step authorisation enabled for their account so maybe it is that?). The menu news items have failed to load a few times or half load, which makes me lean towards a handshake problem with the ubisoft server.

The delay in loading has got worse and worse since I bought the game a few days ago - I deleted all saves, even tried deleting the local shader cache. Once in game after the long delayed load - it works fine, but this is clearly an issue affecting multiple people so very likely on their end.

Awaiting a solution and will update here if I find one (my next step is upgrading to two step auth). Cheers.

[Green Bastard]

Update: I lost my patience and did a clean install of Windows. Game progresses past the warning in seconds now.

[Vyktor]

I added 2 step auth to my Ubisoft account, and tried deleting my direct X cache, but it din't affect things yesterday... then today - I'm not having this issue. My guess is it was a temporary server side issue.