Hey all,

it has come to my attention that some users are experiencing problems displaying the map in Firefox. It usually seems to work fine in Firefox, but several people reporting seeing a white screen that is only occasionally showing the map when being resized. It seems to manifest strongest when playing Darkfall together with viewing the map.

If you are experiencing this, try this link to see whether it fixed:
http://www.feylines.net/yourmom/Compatible.aspx

Read on to see why:
After diagnosing this issue with Minijag it seems I have discovered the cause in incorrectly handling hardware GPU acceleration on some combination of systems and graphics cards. Disabling it doesn't seem to have a noticeable impact on performance - this is the only thing the link above does. Although the preferable option is to keep it on, you can safely keep using the link above for the map indefinitely as it is updated just as well as the normal one.

If this applied to you or have a still unresolved problem with the map, please post into this topic and explain. I should be able to resolved all technical difficulties.

Great news Jason ;)

let me know if you notice any performance down-gradation. The tests I was running showed next to no difference, but it again may be dependent on each exact machine.

This compatible version is running really fine and stable. Thx very much!

As people have *confirmed* problems with the "official" version and the reports so far show no problems with the "compatible" version (that is, without gpu acceleration), is there any reason why gpu acceleration should be left on by default?

Leaving a problem because not everyone has it? Sounds like AV's handling of the out of virtual address space error, tbh. ;)

Since I believe it has better performance with GPU on, removing it altogether as a global fix would negatively impact a large amount of users while benefiting only some.
However I'm not sure of the exact CPU load difference between on and off, seems to be dependent on used browser for me. If you and a few people could test it for me exactly, with and without the DF client (CPU% usage & subjective FPS - especially with DF client running), it might reveal whether it's worth it to cling to the GPU-on as a default option. If it is worth it, I can try to add some browser autodetection and turn it on only for MSIE which seems to be issue-free. If not, I'll just forget it exists and make it same for all. So far I cling to it as the default option as its absence through my development was causing serious CPU utilization even when the map was in idle state in Chrome. Haven't confirmed yet whether it is a widespread issue.

Very thanks for link, works now!