7.14 (7.14.0.0024) is Now Available

Dave Hooton said:

You have to zoom in (+) to see Bethlehem of Zebulum, or Jerusalem; even to see Bethlehem of Juda.

On a map of tribal territories you have to zoom in to see some names e.g. Benjamin.

Unexpected. It doesn't sound like a good user experience, since it's not obvious that we need to do that.

If possible, the map should be zoomed in to provide more detail from the start, as it's more natural/intuitive/instinctive to zoom out when you want to see more of the surrounding area.

Matt Preucil said:

Michael,

As Alan mentioned, you might benefit from the changes we're rolling out soon. In the meantime, you can test if this fix will work for you by:
- Going to app.logos.com and opening Atlas. I would expect a crash here.
- Going to chrome://flags and enabling "ignore-gpu-blacklist" and restarting Chrome.
- Going back to app.logos.com to see if Atlas is now functional.

Edit: That said, if the problem is that your docking station doesn't have (or allow/support) access to any GPU hardware, then this change will probably not have any affect for that configuration.

Edit: I just remembered that our change will only affect macOS. If performing the above steps confirms that ignore-gpu-blacklist will fix problems related to your docking station, then we can make an analogous change for Windows.

Good luck!

- Matt

Matt, I seem to be having related performance problems as well on my new Surface 2017 with the Atlas (i5 7300u, 8GB RAM, Intel HD Graphics 620), particularly those referred to by Alan (here). This might be related to issues that I and others have had with media resource like 1000 Bible Images. I've had similar problems in in the past with my old Surface 3 and an even older Dell laptop, although I don't recall the Atlas's performance always being so poor. The Surface 3 likewise used Intel HD Graphics. Pretty much everything else on my new Surface is blazing fast. There seems to have been at least some modest improvement with the Atlas recently. I'll have to experiment more when I have time, after I finish an intensive course that I'm taking right now. That said, dragging and panning the map is still sluggish.

Dave Hooton said:

Adam Olean said:

This might be related to issues that I and others have had with media resource like 1000 Bible Images.

Even if Atlas is cached, it is still essentially an online tool, where performance is dependent on factors outside your computer. 1000 Bible Images is sluggish on my laptop, whilst Atlas is slightly smoother with 4yr old Intel HD graphics. It isn't much better after switching to the dedicated GPU. I have 5th generation i7 5500U (2 core!) and 8 GB RAM.

Very true. I should have produced log files shortly after I purchased the computer and installed and updated everything. I recall that it was stuttering and stalling even worse then. Dragging and panning is still not smooth. It doesn't seem to make much of a difference whether I use wireless or Ethernet connections. 1000 Bible Images is far worse. At least the Atlas is now functioning smoothly on the Logos Web App. I'll use that for the time being and follow up later.

Many thanks.  I will do that.  Do you have an estimated release date?