Thanks for acknowledging it. First I wondered if it was only my Lr version, but I guess it has to do with a Google Maps API update : I still had an old Lr5 version (that was way out of date) and I get the same flashing effect. On their announcements, you see a lot of activity on maps lately...
I have a similar problem with Lightroom 6.10.1 on Mac OS 10.12 [5]. The map module sometimes goes frozen and you have to toggle to another module and get back tio the map module to unlock it.
While we all would like to see it fixed ASAP, my guess is they won't issue an update for a single bug (however widespread it is). Most updates address multiple bugs.
Unfortunate, but probably what we'll have to deal with.
Regardless of what Adobe might say, nobody's version/OS info is going to help at this point. Google made changes on their end around the time this started, and it also affected YouTube on some devices with almost identical behavior. (pop-up saying the service is offline when it's clearly not)
Even 30 days to fix this would be fine IMO. A week without an ETA, though... not so much.
edit: apparently in addition to pretending that individual system specs or network information is useful in resolving this issue, they're telling users who call tech support that the issue is with their own (the user's) networking settings. Absolutely unreal.
Responses
manfred_kollegger
1 Message
•
62 Points
4 y ago
Version von Lightroom: CC 2015.10.1 [ 1117303 ]
Lizenz: Creative Cloud
Betriebssystem: Windows 10
Version: 10.0
0
0
thomas_7156296
1 Message
•
60 Points
4 y ago
Lightroom 6.10.1
Windows 10 w. Creators Update
0
0
franck_payen
136 Messages
•
2.9K Points
4 y ago
0
0
john_bronces
1 Message
•
60 Points
4 y ago
0
0
gaurav_manglik
1 Message
•
60 Points
4 y ago
LR and OS version are as follows:
Lightroom version: CC 2015.10.1 [ 1117303 ]
License: Creative Cloud
Operating system: Mac OS 10
Version: 10.11 [5]
0
0
adrian_kaminski
1 Message
•
62 Points
4 y ago
It started a few days ago when I was still running 6.10.
Never seen this issue before.
Then yesterday I have updated to 6.10.1 but it did not help and the problem persists.
This is really horrible, as I regularly use the map module for geo tagging.
0
0
george_nichols
37 Messages
•
820 Points
4 y ago
I love the map module - when it is working....
0
0
vacher_pierre
1 Message
•
60 Points
4 y ago
The map module sometimes goes frozen and you have to toggle to another module and get back tio the map module to unlock it.
Pierre
0
0
roland_giehl
1 Message
•
60 Points
4 y ago
Version von Lightroom: CC 2015.10.1 [ 1117303 ]
Lizenz: Creative Cloud
Betriebssystem: Mac OS 10
Version: 10.12 [5]
Anwendungsarchitektur: x64
Anzahl logischer Prozessoren: 8
Prozessorgeschwindigkeit: 2,3 GHz
Integrierter Speicher: 16.384,0 MB
Für Lightroom verfügbarer phys. Speicher: 16.384,0 MB
Von Lightroom verwendeter phys. Speicher: 744,1 MB (4,5%)
Von Lightroom verwendeter virtueller Speicher: 1.888,3 MB
Cache-Speichergröße: 115,4MB / 3.864,7MB (3,0%)
Maximale Anzahl Threads, die Camera Raw verwendet: 8
Camera Raw SIMD-Optimierung: SSE2,AVX
Virtueller Speicher in Camera Raw: 46MB / 8191MB (0%)
Monitore/Anzeigegeräte: 1) 2560x1600
Best
Roland
0
0
adam_welz
12 Messages
•
194 Points
4 y ago
LR v6.8, Camera Raw 9.8, Mac OS 10.11.6 - running on a 2014 MacBook Pro.
0
0
andreas_peters_ezflk3ml98su1
8 Messages
•
520 Points
4 y ago
It started a few days ago.
Never experienced this issue before.
0
0
gilles_subias
6 Messages
•
234 Points
4 y ago
1
0
richard_zimmerman_9z79veduohtw1
7 Messages
•
122 Points
4 y ago
Same problem.
Lightroom version: 6.10 [ 1111918 ]
License: Perpetual
Operating system: Mac OS 10
Version: 10.10 [5]
Also occurs on Macbook Air running 6.10.1 on Mac OS 10.10.5
0
0
valka_cz
5 Messages
•
140 Points
4 y ago
0
scott_burnette_e2ywma4hsvqrk
9 Messages
•
174 Points
4 y ago
Even 30 days to fix this would be fine IMO. A week without an ETA, though... not so much.
edit: apparently in addition to pretending that individual system specs or network information is useful in resolving this issue, they're telling users who call tech support that the issue is with their own (the user's) networking settings. Absolutely unreal.
0