Logos 6.3 Beta 1 (6.3.0.0015) now available

Reply

Dylan Rondeau | Forum Activity | Posted: Wed, Apr 15 2015 10:29 AM

6.3 Beta 1 (6.3.0.0015) is available for testing.

To update to Beta 1, enter the Update Now command if you’ve switched to the beta channel before, or enter the Set Update Channel to Beta command if you’re on a stable version (such as 6.2). To install Beta 1 from scratch, see the notes and download links on this thread.

Release Notes

Known Issues in this release:

Concordance (Logos Now)

• This release adds new concordance types which require the Concordance to regenerate the first time it is run for a resource.
• The Concordance takes significantly longer to generate, especially for Bibles with Reverse Interlinears. Good news: once it is done generating, there is a lot more interesting data available for concording. We plan to spend some time optimizing generation in a future release.
• Sense and Biblical Entity results should have richer previews.
• Sense and Biblical Entity results should have more type-specific refinement options.

Grammars Guide Section (Logos Now)

• The results are not ordered in any meaningful way.

Application

• Unhiding a resource does not make a resource visible again
• Clicking the notification hyperlink to restart the application does nothing (you can manually close and relaunch the application).
• The notification bar may prompt for application restart every time the application runs.
• Canceling a download when auto-update is turned on will stop the current and pending downloads, and then after a short delay the downloads will start up again.

Reply

Matt Hamrick | Forum Activity | Replied: Wed, Apr 15 2015 11:19 AM

When mine went to install is says it cannot find the source files so it did not install. I will reinstall it and see what happens.

Reply

Fred Greco | Forum Activity | Replied: Wed, Apr 15 2015 2:33 PM

Installed this and now every single time I open it, Logos crashes in about 20 seconds. How can I fix that, or at least go back to my previous version?

Reply

Fred Greco | Forum Activity | Replied: Wed, Apr 15 2015 2:36 PM

Devin,

I can't do that - Logos crashes too quickly

Reply

Fred Greco | Forum Activity | Replied: Wed, Apr 15 2015 2:39 PM

Can you remind me how to get a log and where to find it? I don't have that memorized.

Reply

MJ. Smith | Forum Activity | Replied: Wed, Apr 15 2015 2:45 PM

Okay, let's step back and both get a log and possibly get you up and running.

1. Hold down the CTRL key when you start the program.

2.If given the opportunity, open to blank page.

3. Keep holding down the CNTRL key until you see the application itself come up.

4. When it crashes, upload all the files with today's date and time from Logos Log Files

Reply

MJ. Smith | Forum Activity | Replied: Wed, Apr 15 2015 2:54 PM

Thanks - they should be useful for Faithlife - you are failing on an invalid key in a dictionary which is probably a true bug. Congratulations - the purpose of betas is to find bugs. If you didn't mean to get involved in an early beta, you are correct to revert to your previous version. I'd check for a system sync point to go back to as the quickest way to revert.

Reply

Dylan Rondeau | Forum Activity | Replied: Wed, Apr 15 2015 3:22 PM

MJ. Smith:

you are failing on an invalid key in a dictionary which is probably a true bug

Mark Smith reported this bug also, earlier. A developer is currently looking into it. Thanks for the report, and sorry for the trouble.

Reply

Matt Hamrick | Forum Activity | Replied: Sat, Apr 18 2015 10:07 PM

Above I said I had to do a reinstall. I removed Logos Bible Software in its entirety and reinstalled it. The index took about 72 hours. I get a first time index takes a while. I get I have just over 13,000 volumes. But 72 hours? Really? In a world we live in today, with technology. It takes 72 hours for a first time index? That seems far to slow for Logos 6.

Reply

Mark Barnes | Forum Activity | Replied: Sun, Apr 19 2015 12:38 AM

Dave Hooton:

Without knowing you hardware/OS that could be quite reasonable.

For a library that size 72 hours would only be reasonable (IMO) on an incredibly ancient machine. I have a similarly-sized library, and it takes less than 12 hours to do a full index.

It's probably more likely that the PC went into sleep mode at some point and indexing was paused. If it didn't (and it's not ancient), then something is wrong — but without logs/spec, it's impossible to say.