When a Chromium-based browser detects that you are using this hardware, it forcefully disables hardware acceleration thanks to a blocklist included in the browser. We highlight this because the majority of our players that encounter this problem are using older hardware and/or outdated drivers. If you are using an older, pre-2013 graphics card, you are likely to run into these issues. Therefore an update to Chromium will impact the actual browser that you use.īrowsers that use Chromium include, but are not limited to: For those that do not know, Chromium is the open-sourced browser project that most of the popular browsers develop from. While I don't wish to be overtly wouldn't have been terribly difficult for a member of FOE staff to advertise the above solution to a problem that appears to be occurring to a lot of players.As some of you will know through experience, recently there has been a host of issues for players that are using a browser that is based on Chromium.
So either bookmark and use that link or use your chrome most visited tab rather than the app tab where the FOE icon is. For now bookmark the main login page link and use this until FOE fixes the issue or offers an alternative solution as clicking on the app icon will continue to bring you to the wrong URL. You will then be able to go to your email account and click on a link to change your password and subsequently log in.įinally. If you don't remember what countries server you are on keep changing it until the submit on forgotten password works. Click on the drop down menu and change it. If it is not recognized it is because the flag at the top is directing you to the wrong serer location. If you do not have a password/user combo as you are using the chrome ID app click on the "Forgotten Password" LinkĮnter your Chrome email address and submit it. It may be a DNS issue but you are being directed to the wrong URLįollow this link for the main FOE login page If anyone else is having this issue having patiently waited for hours and getting no response I pieced together information from this thread and others reporting similar issues and found the solution.
0 kommentar(er)
