Map view crashes ON1
Previously attempting to open map view for first time was causing ON1 to crash a few times before it would eventually load. Since upgrading to 2022.5 opening the map view is now crashing ON1 all the time so map view is just not usable.
Is anyone else experiencing this? Or know of a work around?
Thank
-
No crashes on my Windows 10 system. Neither street, nor satellite or outdoors view.
Only the streets view is rather dark. But I don't know, if this is new or was already dark in 2022.1
0 -
Map view works for me on Windows 11. No problem.
Streets are dark too. I mostly use Outdoor
0 -
Thanks for the comments. It looks like it could be a problem specific to my system. I've tried a clean install of 2022.5 but that hasn't fixed the problem.
0 -
Tony Prichard,
just as an idea/try: I remember quite some time (maybe even still related to 2021 Version or so, there was a kind of "hack" described in forum and facebook where you could manually alter some standard ON1 files and improve the view (not remembering all of the details). Maybe you did as well and it has sth to do with this (ON1 does not replace them with the new files at installation and crashes when having old format or so?) Just a guess. :-)
0 -
I think that you mean my "hack". But ON1 replaces all files concerning 'Map view' with each new installation. So this cannot be.
But are there any specific error messages in file
C:\Users\dani\AppData\Roaming\ON1\ON1 Photo RAW 2022\ON1 Photo RAW Log.txt
-1 -
Can we see those error messages from the log file please?
0 -
I've not applied any hack previously so that won't be an issue
These are the last few lines of the log file, which seems to be suggesting an error but I can provide more log file if needed.
2022-06-10 18:43:56 ON1 - PLLrMigrationCacheMgr::initialize - > cache manager initialized.
2022-06-10 18:43:57 ON1 - Marketing URL: https://www.on1.com/appmessages/?product=photoraw2022&version=2022.5&plus=yes&state=active
2022-06-10 18:44:07 ON1* - An OpenGL Core Profile was requested, but it is not supported on the current platform. Falling back to a non-Core profile. Note that this might cause rendering issues.
2022-06-10 18:44:07 ON1* - Installed Qt WebEngine locales directory not found at location C:/Program Files/ON1/ON1 Photo RAW 2022/translations\qtwebengine_locales. Trying application directory...
2022-06-10 18:44:09 ON1* - Unable to perform style diff: Style is not done loading. Rebuilding the style from scratch.
2022-06-10 18:44:09 ON1* - Error: The user aborted a request.-----------------------------------------------------------------
PC details - Windows 10 - 16GB RAM
Processor - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz 3.60 GHz
Graphics card - NVIDIA GeForce GTX 1060 6GB0 -
Looking for that directory C:/Program Files/ON1/ON1 Photo RAW 2022/translations\qtwebengine_locales.
This does not exist but C:\Program Files\ON1\ON1 Photo RAW 2022\qtwebengine_locales does and is populated with a number of .pak files
0 -
I created a translations directory and copied the qtwebengine_locales directory into it. Now the error is giving a bit more detail
2022-06-10 18:59:53 ON1 - PLLrMigrationCacheMgr::initialize - > cache manager initialized.
2022-06-10 18:59:54 ON1 - Marketing URL: https://www.on1.com/appmessages/?product=photoraw2022&version=2022.5&plus=yes&state=active
2022-06-10 19:00:02 ON1* - An OpenGL Core Profile was requested, but it is not supported on the current platform. Falling back to a non-Core profile. Note that this might cause rendering issues.
2022-06-10 19:00:03 ON1* - Unable to perform style diff: Unimplemented: setSprite.. Rebuilding the style from scratch.
2022-06-10 19:00:03 ON1* - Error: The user aborted a request.
2022-06-10 19:00:03 ON1* - Error: Cannot read property 'send' of undefined0 -
Hi Holger Danielsson, to go for sure: I hope "hack" was not sounding negative. Otherwise sorry, was not meant like this at all. In fact I found that modification great and used it by myself. :-) But I didn't update my "normal" computer yet where I did the modification only, because I want to wait there better with the update, especially as some issues recently came up. So I couldn't verify if that is was happened myself. As I wrote it was just an idea, not blaming that modification, to check as one possible option. Because the crash seems to not happening for far most users at least thats what you could get as impression if this topic seems not being reproduced a 2nd time so far. A modification only some users did is of course basically sth that could explain such a thing. So hopefully all good. :-)
Edit: Maybe to making the modification even solves the issue somehow? ;-D
0 -
This is something you'll have to talk to support about Tony.
0 -
Thanks for your help. I'll get in touch with support and see if they can help.
0
Please sign in to leave a comment.
Comments
12 comments