Not only could we then switch to a working map if say Google failed, but we could use other maps, like topographic maps, which are better for offroad geolocation anyway. Currently I have to use other mapping applications for this. If they can do it, Adobe certainly can.
This is so annoying! This connection detection stuff has always been way to aggressive anyway: try working on a train with phone tethering and intermittent wireless signal. Why do you need to show this offline image and block usage if I positioned the map correctly before I went offline? Better would be to cache image tiles and try to use these when offline, which is what a lot of apps do. Motion X GPS on my phone for instance will try to scale tiles when it can't retrieve the ones it needs, up to a point when it will show "map data not availlable tiles". Come on Adobe: fixing this current issue is an excuse to make this thing work much better in general.
Lightroom version: 6.10.1 [ 1117303 ] License: Perpetual Operating system: Windows 10 Version: 10.0 Application architecture: x64 System architecture: x64 Logical processor count: 8 Processor speed: 4.0 GHz Built-in memory: 32706.8 MB Real memory available to Lightroom: 32706.8 MB Real memory used by Lightroom: 3306.9 MB (10.1%) Virtual memory used by Lightroom: 3469.5 MB GDI objects count: 921 USER objects count: 2424 Process handles count: 2232 Memory cache size: 7618.9MB / 7920.7MB (96.2%) Maximum thread count used by Camera Raw: 8 Camera Raw SIMD optimization: SSE2,AVX,AVX2 Camera Raw virtual memory: 2381MB / 16353MB (14%) System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 2560x1440 Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Lightroom version: 6.10.1 [ 1117303 ] License: Perpetual Operating system: Windows 7 Version: 6.1 Application architecture: x64 System architecture: x64 Logical processor count: 4 Processor speed: 2.7 GHz Built-in memory: 8125.4 MB Real memory available to Lightroom: 8125.4 MB Real memory used by Lightroom: 2095.2 MB (25.7%) Virtual memory used by Lightroom: 2162.1 MB GDI objects count: 946 USER objects count: 2580 Process handles count: 2437 Memory cache size: 1675.5MB / 1775.3MB (94.4%) Maximum thread count used by Camera Raw: 4 Camera Raw SIMD optimization: SSE2,AVX Camera Raw virtual memory: 825MB / 4062MB (20%) System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1600x900 Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Same problem. With every bug and glitch and crash in LR and PS I am nearing the edge of the Adobe cliff. Now even the adobe forums are not working for me -
"System Error We're sorry but a serious error has occurred in the system."
Likely a change in Google's API. But Adobe (and maybe others) have failed to adjust for it. Companies always provide notice that they are changing things in their APIs.
Roelof's right, it IS a change made on Google's servers. The way we can tell? It's affecting much older Lightroom versions that Adobe hasn't touched in ages, and they all stopped working at the same time. There are multiple ways of accessing the information on Google's servers, and the way Adobe's been using stopped working.