7.14 (7.14.0.0024) is Now Available
Comments
-
I am still having this same exact problem as well. Have your issue been resolved? I have updated to the last release of 7.16.0.0012 and all my indexing has completed as well but I still get a blank screen in my Atlas tool [:(]. This is very frustrating indeed.
0 -
No, still not working. I think I will have to buy L8 to get it working again.
0 -
Michael Brand said:
I have updated to the last release of 7.16.0.0012 and all my indexing has completed as well but I still get a blank screen in my Atlas tool
. This is very frustrating indeed. Curious about Graphics hardware. Thread => Atlas still not working includes a Faithlife developer reply on 17 Jul 2018 => https://community.logos.com/forums/p/168614/987036.aspx#987036 that mentions embedded CEF used by Atlas inherited a blacklist of Graphic Processors (GPU's) so Atlas appears blank when using a blacklisted GPU (plus mentions future beta testing plans to modify blacklist).
Keep Smiling [:)]
0 -
I know I will truly be upset if they broke something in 7 and then decided to charge me in 8 to get it fixed when it was an update in 7 that caused it. I’m having the same trouble with the Atlas.
0 -
Remember that Logos has a free version ... one can upgrade without cost.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I have figured out my problem and it does have something to do with the GPU but it's not what I expected. After looking at my chrme;//gpu setting I noticed that it was not using my graphis hardware driver but rather software drivers. This was due to the fact that I am connected to a USB docking station at home when I home. The laptop in which I have the LOGOS software is a Dell XPS12 with a very small screen ( touch screen two in one) which has excellent hardware but when connecting to my USB docking station the docking station's software kicks in si it can project my screen to a larger monitor. I tested this theory out and the ATLAS tool works when undocked :-(
0 -
Michael, it sounds like you might be running into the same issue I discuss here that some users of older MacBooks are experiencing: https://community.logos.com/forums/t/168614.aspx.
Hopefully our change to override the GPU blacklist in CEF will allow you to use the Atlas tool once again. I'm sorry I don't know with which version of the application the fix will roll out.
0 -
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
0 -
Mike Tourangeau said:
After leaving mine overnight the "Atlas" tool is no longer grayed out. However it will not load, I briefly see the menu on the left but then it disappears and the screen is blank. If I turn off the internet and try to load the tool the tool opens and the menu's stay but it is unusable.Joseph Turner said:Mine is still not working. I have opened and closed Logos several times and tried to force an update of resources, but even after leaving it over night, it is still grayed out and says that the tool is unavailable upon hovering over it in the tools menu.
Mike,
We think we have fixed your issue in 7.17 Beta 2, it will be avaible as a stable release around August 6, 2018
0 -
Help me out with this part of the Atlas. For example, I can type in Bethlehem (of Judah) and clicking on that, it'll take me right to it.
But typing in Bethlehem (of Zebulun) and it'll take me to Zebulun (free of charge) but doesn't show Bethlehem there.
I've used the Atlas a little but not much. Why was I thinking if one scrolled upwards, the map would show more places or am I confusing that with Google maps? If that wasn't and still isn't a feature in the Atlas, is there anything in the works to make it work like that?
MSI Katana GF76 Intel Core i7-12700H, RTX3060, 16GB RAM, 1TB SSD, Windows 11 Home
0 -
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.
Then I had to restart Atlas to locate Mt Carmel...
It's a disappointing experience.
Dave
===Windows 11 & Android 13
0 -
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.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
This is weird. No way last evening could I find or see Bethlehem even when scrolling & zooming in. I looked for that and looked again and apparently the problem lies with me, not Logos, which you knew all too well anyway. I could not see that anywhere before tonight. I zoomed in, moved the map around and obviously it was right in front of me but I still couldn't see it. Thank you for the reply Dave.
MSI Katana GF76 Intel Core i7-12700H, RTX3060, 16GB RAM, 1TB SSD, Windows 11 Home
0 -
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.
0 -
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.
Dave
===Windows 11 & Android 13
0 -
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.
0 -
I do not have the Beta, but have noticed comments about hardware on this thread. I have a Lenovo laptop with an Intel HD Graphics 520 and an NVIDIA GeForce 930M attached to a Lenovo Thinkpad USB 3.0 Ultra Dock. Can I expect my Atlas to work when you release your next version? I am teaching through 2 Samuel this summer and really need the maps. They worked on this machine until earlier this year, so you must have done something. I have been with Logos since version 1b and don't remember something like this.
0 -
Mike Tourangeau said:
After leaving mine overnight the "Atlas" tool is no longer grayed out. However it will not load, I briefly see the menu on the left but then it disappears and the screen is blank. If I turn off the internet and try to load the tool the tool opens and the menu's stay but it is unusable.Joseph Turner said:Mine is still not working. I have opened and closed Logos several times and tried to force an update of resources, but even after leaving it over night, it is still grayed out and says that the tool is unavailable upon hovering over it in the tools menu.
Hi Mike,
We think we fixed your issue in 7.17. Can you please confirm?.
0 -
Philana R. Crouch said:
We think we fixed your issue in 7.17. Can you please confirm?.
Philana, I have been away for a bit but I just hit "update now" and got the update and it appears it works fine! Thank you so much.
0 -
Mike Tourangeau said:Philana R. Crouch said:
We think we fixed your issue in 7.17. Can you please confirm?.
Philana, I have been away for a bit but I just hit "update now" and got the update and it appears it works fine! Thank you so much.
Mike,
I'm am so glad it's working for you now. Thank you so much for your patience as we worked on fixing it.
0 -
I have downloaded 7.17, have restarted Logos several times, Have rebooted my machine twice. Atlas still does not work. Are you working to fix this?
0 -
Reuben Pitts said:
I have downloaded 7.17, have restarted Logos several times, Have rebooted my machine twice. Atlas still does not work. Are you working to fix this?
Reuben,
Can you upload your logs? You can find a link in the signature of this post on how to get them. Then reproduce the issue and upload the logs here. This will help us confirm that this is the same issue.
0 -
5040.LogosError.log1348.LogosCrash.txt2185.Logos.log
The cef.log file would not upload for some reason. Do you want me to e-mail it to you?
Many thanks,
Reuben
0 -
Reuben,
It would be easier if you ziped the entire logging folder then just upload that folder.
0 -
Here it is. Many thanks.
0 -
0
-
Philana,
Many thanks. Please keep me posted.
Reuben
0 -
-
There is no new version available when I try for a manual update. Do I need to follow some special procedure, or do I just wait for the general update of 7.18?
0 -
Reuben Pitts said:
There is no new version available when I try for a manual update. Do I need to follow some special procedure, or do I just wait for the general update of 7.18?
To get it you need to sign up to the beta testing channel - details are at http://community.logos.com/forums/t/52967.aspx . But please do note the warnings, beta software can cause problems!
If you are not normally a beta tester I would recommend waiting until the stable release is available unless this issue is a major problem for you
0
