Logos 6.3 Beta 1 (6.3.0.0015) now available
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.
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.
Comments
-
Best item on the list: No more restarts required for resource updates! Great job Faithlife!
0 -
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.
0 -
Dylan Rondeau said:
enter the Update Now command
Now that Logos Now has been released, the Update Now command is ambiguous. Are people going to think this will only update their Logos Now features?
0 -
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?
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
Fred Greco said:
How can I fix that, or at least go back to my previous version?
Type "set update channel to stable" in the command bar. You should then get a download of the stable version and be able to go back.
0 -
Devin,
I can't do that - Logos crashes too quickly
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
Please upload the logs of the crash so we can see what is going on.
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 -
Can you remind me how to get a log and where to find it? I don't have that memorized.
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
It appears related to synchronizing. When I am in offline mode it does not crash. As soon as I turn on the internet mode, it crashes
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
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
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 -
OK. Got it. Here is the Zip.
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
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.
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 -
Note you should generally start a new thread when reporting beta problems rather than attaching it to the announcement of the beta.
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 -
MJ. Smith said:
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.
0 -
Thanks. Dylan, if you are able, I am happy for you to move all posts related to my issue to Mark's thread to keep this clean. Sorry for posting it here.
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
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.
0 -
Without knowing you hardware/OS that could be quite reasonable.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
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.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Before this beta it took about 18 hours for a first time index on this machine. Something changed and it was not my computer.
0 -
Matt Hamrick said:
Before this beta it took about 18 hours for a first time index on this machine.
If you have detailed logs (logos.log and logosindexer.log) for that session then please upload them from your \Documents\Logos Log Files folder. If you have a recent LogosIndexerError.log or LogosError.log they may help, otherwise enable permanent logging (especially for a Beta) and report any occurrence of excessive indexing times in a new thread.
Dave
===Windows 11 & Android 13
0 -
Fred Greco said:
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?
This crash should be fixed in 6.3 Beta 2.
0
