Yup, for me too.
Yes, the new 1.9.8 works a treat. It was a little sluggish the first time it started (as you warned) but thereafter it’s been back to its usual fast start up. Thank you for the rapid response!
As a supplimentary question: should you/I/somebody be worried about these fonts crashing the parser or failing to parse? I’m not aware of any corrupt fonts as far as any other software is concerned. I tried a couple that the Scrivener log file complained about, and they both work fine, without complaint, in Microsoft Word and in Adobe Photoshop.
FWIW, I was not having an issue with the previous 1.9.8.0 update or the installer - at least I was not experiencing long delays opening projects. I went ahead and grabbed this new installer, installed over the previous 1.9.8.0 version, and noted that it does open a bit faster. Interesting. At any rate, I’m a happy camper still other than wishing you would have incremented the sub-minor version number (e.g., 1.9.8.0 to 1.9.8.1) to better tell the versions apart.
Had a slightly minor issue when installing the latest update. Could very well have been something that I did wrong, Nevertheless, I’ll describe my experience (and fix) here for posterity.
Currently running Windows 10.
When asked to update, I breezed through the steps, clicking okay/accept, thinking that this would be a routine replacement of existing Scrivener files. However, after the update completed and I attempted to open one of my projects in my documents folder, I got an error saying something to the effect of “you cannot open a project located inside the installation folder, please move the project folder outside the installation folder and try again.” Got this message on all my projects located at various points within my docs folder. I tried moving a project to the C:\ directory and still got the message, and there I saw that all the scrivener files were sitting right in my root directory (C:), not even in a folder. I should have checked the installation location when I was applying the update, because for whatever reason it defaulted to C:. Fortunately, the easy fix is to run the uninstaller and re-download (making sure to set your install directory to something other than the root). Like I said minor problem with an easy fix, but maybe someone else will run into this problem and could use a little guidance.
TLDR: When running the update double-check that you are installing to the right directory, because mine low-key defaulted to C:\ and I had to un/reinstall.
@grindzombie: The update installer indeed grabs the installation folder key from your own computer. This is what has been reported from previous installation. I cannot tell why this obviously unusual path was reported, but indeed it does come from your own computer and your computer registry. Something or someone must have changed or written it like this previously.
@Jestar: I agree that having a distinct version number would have been best. Unfortunately we had other reasons which prevented us from doing so. v1.9.8.1 is a beta version signature and we can not use it, v1.9.9.0 is the last update number available which we want to keep for releasing together with Scrivener for Windows v3, and we do not want to jump to v2.0.0.0. Hope you get the dilemma now, and understand we could not change the update number so easily.
Edited: Something also very important I missed is that using v1.9.10.0 is not an option as some old versions might get issues comparing against 19100 which is a digit longer than expected and might be still compared as being v1.9.1.0 unfortunately. We do plan fixing this in future releases though.
@mfjames: The Scrivener font parser is great but not perfect. We try do protect ourselves against crashes, but sometimes it is impossible, either because the font author has not fully followed the font specification, or because our font parser does not fully follow the font specification. We do our best but no matter how hard we try, we occasionally receive “broken” fonts. Obviously the Microsoft font parser is much more sophisticated and handles the font author issues more gracefully. Also in Scrivener we need the font PostScript name, which is typically not needed and not used in many other applications. As it is not needed, the other applications’ font parsers are much less likely to crash, as they are not parsing what Scrivener does. We need the PostScript font names to keep proper syncing of fonts between iOS and Windows. Unfortunately Apple did not left us any other option, and Scrivener for Windows had to “suffer” with the extra implementation burden to keep the Scrivener users happy.
Previously in v1.9.7.0 we would silently skip these problematic fonts. In v1.9.8.0 we decided to let the user know(at least once upon startup) about the font causing a problem, or the user would be wandering why my iOS font does not appear under my Scrivener for Windows.
Hope it makes more sense, now. We are truly sorry for the mess up with v1.9.8.0, but this was all caused by our desire to improve and make Scrivener faster. Unfortunately sometimes we cannot cover all user cases and you feel the pain. We feel it too, and try to make Scrivener great again as fast as possible. Thank You for staying with us guys and for all the help resolving the issue!
So there is still a plan for releasing Scriv 3 for us Windows users? It’s been so long since the Mac users got theirs that I figured we were just out of luck, especially when I saw the free upgrade to 1.9.8. (And luckily I didn’t see that offer until after it was fixed!)
@Scribhneoir: Scrivener for Windows v3 is in a Beta testing stage and can be downloaded from the Beta testing forum : viewforum.php?f=57
Just had the first opportunity to update to the new install and it’s working perfectly. Had another bad font message at the first start up – but none since,
It seems to opens a little faster than 1.9.7 now, but that could just be me. I never could tell time.
Nice job on the quick turnaround. That must have been fun.
-B
Understood.
I installed the 6/12 update and noticed the load time takes a very long time.
Then, I also noticed there was another update … to the 6/12 update … dated 6/16. However, when I go to Scrivener to check updates it says I have the most current version.
Not sure what is going on here… But, there doesn’t seem to be a way to update the 6/12 1.9.8 update to the 6/16 1.9.8 update.
Thanks, but I’m not interested in the Beta version. Any word on when v3 for Windows will be out of Beta?
Welcome! Here is the fix, from MM’s post on the previous page:
This has worked for myself and others here, hopefully it will for you as well.
Perhaps the important point from MM’s instructions is:
Mark
L&L’s goal/hope is Win v3 released sometime this year.
I just installed the hot patch and opened and closed the software several times. On the first start I had an error message that said a font could not be loaded and would be ignored. The software started up almost immediately afterward. I closed Scrivener again, then reopened and closed several more times, and it started fine every time. I think it might actually be opening faster than the 1.9.7 version did. Also, I only had an error message on the first attempt to open the software and after that it has opened without any error messages.
I installed the update and got the same message about moving my project out of the installation folder. A search doesn’t show a folder by that name so I"m not sure how to move it. Some suggestion in this thread say to uninstall Scrivener. If I do this and attempt to install it again, will my projects remain intact? Will I need my license number (which I don’t seem to have now)? I attempted to open a back up file which only gave me another message indicating I can’t access the file. Probably due to my failed attempt at trying to move one of my project files out of the appdata folder (couldn’t find it anywhere else.) So frustrating. Hoping someone here would give me some guidance. Thanks =)
Interesting. I’ve had the same not-loading issue for… wow. Two years and eight days, now. And as far as I can tell, this was the first attempt at a patch? I’m glad some of you got a quick response and a resolution, but I’d still quite like to know why a thread back then with even more people in it with the same issue was left sitting there for so long.
Unfortunately, the patch didn’t fix mine, so I’ve rolled back. Again. 