-
UPDATE 2: I Quit Logos and reopened it and now the download is sailing! I downloaded 23% of the remaining 5.66 GB in the first ten minutes.
-
UPDATE: It was the "LogosCEF" function that was eating up my CPU and memory. I did a Force Quit to that process but not to the Logos 6 app itself. It doesn't seem to be running any faster. At this rate, it might be next week before I actually get to use it.
-
I'm loading Logos 6 onto a brand-new MacBook Pro running El Capitan (256 GB SSD/8 GB memory). It downloaded the first 63% with no problem then it bogged down and started eating up CPU and memory. The most recent 5 or 6% has taken as long as the first 20% did (the number of volumes updated has not changed in over an hour). I do have almost 5,000 volumes
-
I can find no official word on this forum or on Logos' website about Logos 6 compatibility with El Capitan. Seems I remember that I wanted information about Logos 6's compatibility with Yosemite when that came out but none was available then, either. I think this is the kind of support we should be able to reasonably expect from Logos given the amount
-
I'd like to see this, too, but apparently Logos has little interest in providing this since people have been talking about this for at least three years now on the forums! Apparently this is the sixth most requested feature. I agree with some of the commenters that Logos isn't truly mobile until helpful features like this are available. Here's the thread
-
Dave: I'm a Platinum user (and have been since L5) with almost 5,000 volumes in my library. I think I qualify for this feature.
-
I have a later Mac than you. And I shouldn't have to go through the trouble of acquiring extra hardware to run a program that already doesn't work as advertised. I'm not convinced it would work as it's supposed to even if I did that.
-
Mine does it every time, as well. I'm using the latest release of L6 and it took almost half an hour when I started it yesterday.
-
I disabled automatic updates so that I don't download and get notifications while I'm actually working in Logos. Logos for Mac is abysmally slow as it is, I'd like to be able to control it so that I can get my work done.
-
The About Logos says this: . I restarted Logos and after it finally restarted (Logos 6 for Mac is abysmally slow) the Bible Guide now seems finally to be working as advertised. I'll have to remember in the future to restart before posting something on here.
-
This is a small thing but it has become irritating. When I select "Install Updates" from the Logos icon in the menu bar I'm expecting Logos 6 to, you know, install the updates. Instead, Logos opens another app ("Logos Update Installer") and I have to clock "Install and Relaunch" in order for it actually to install. I realize this is a small thing but
-
If I type in "Epistle to the Philippians" it takes more than a minute for the drop-down to populate and when it does, the only option is still "Philippians Residence group."
-
As I noted above, I get one choice in the drop-down and that is "Philippians Residence Group."
-
So I watched the video about Bible Book Guides in which we are told to use the Factbook to produce a guide to a Bible book (excellent feature by the way, if I can get it to work). The example used was Romans (Judges was also mentioned in the email). I tried this with Philippians (since I'm working in Philippians for my dissertation) and the only option
-
I have had that problem often since upgrading to Logos 6, even when I have not downloaded any new resources.
-
Dan, purring like a kitten would be nice, but I'd just be satisfied with it working. I'd like to be able to open it and it work the first time, not have to try a half-dozen times before it opens. I'd just like to be able to click the library icon and my library actually appear without it crashing, or without having to wait 1-4 minutes. I'd be satisfied
-
John, I had that same problem but simply quitting and restarting Logos solved the RAM problem. The problem still needs to be addressed, especially given how slow L6 has been, but if that works for you, too, then maybe you won't have to reboot every time.
-
Thanks for the clarification, Dan. That makes much more sense. I'm not familiar with the "Logos.com pages" that you mentioned so I guess I'll have to do some digging.
-
It's odd that you would characterize the forums this way, Dan. As Jeffrey noted above, the forums are the first place Logos tells people to go for support but why is that the case if Logos staff rarely join in?
-
When I hear comments like this I wonder if we're using the same program, too, but apparently not for the same reasons. I'm not here to bash Logos either but I have almost 4,400 volumes in my Logos library and with that type of investment I expect it to work better than it does now. I noticed a distinct difference in performance when I switched from