You can find the new release at the link above, in post #1. If you've got display problems, it's pointless complaining to me and expecting me to 'fix' it, because in this respect I'm as clueless as the rest of you! Remember I don't develop these things.all I do is to re-package them into 'portable' format for the community. These latter two are invariably at the bottom of getting that tiny little square jammed up into the top left corner of the display window. If you're running either an AMD or Nvidia GPU, you MUST have the official, proprietary driver installed & working the 'radeon' OR 'nouveau' kernel driver modules just don't cut the ice these days. Please be aware, kiddiwinks reasonably modern Intel integrated graphics are fine for this. C'mon, Google this is NOT progress.literally!Īpparently, this thing also now updates itself, but I'll believe that when I see it. The only way round this is zooming back out to satellite view, moving along a little way, then back into Street View.an annoyingly long-winded & frustrating process. You can spin the scroll wheel for ever, and you barely move at all. The only way to move around in Street View is now with the scroll wheel.resulting in moving at a very leisurely stroll. Where previously you could move around quite fast by double-clicking on the ground direction arrows, this appears to be no longer the case. Google's 'fix' has certainly resolved the issue of distorted image rendering, but at the expense of being able to move around quickly. I'm not sure as this is for the better, TBH. One thing that needs mentioning is a "fix" for distorted rendering in 'Street View'. v7., released some time on Friday just gone. Here is the Puppy 'portable' version of the new version of Google Earth. Google seem to have standardised on 3 things ATM the web client.the Android client.and the desktop client. The expected demise of the desktop client hasn't come about as I expected. Well, it seems Uncle Mike's prediction vis-a-vis the G.Earth desktop client not getting much more development was wrong. There's still a lot to be said for 'local' apps.Īnyways for anyone who'd like to 'kick the tyres' & give it a test run, you can find it here:. Which is great while it works everything you use is accessible, from any device, no matter where you happen to be.but if your connection goes down for any reason, you're effectively stuffed! This is, unfortunately, the direction everything seems to be heading in. And even then it's not exactly fast in operation, since unlike G.Earth - which runs a client/server model, where both ends have to be running the same series app - Earth for Web relies entirely on the data coming directly from Google's cloud servers.and if demand is especially heavy at any given moment, this naturally enough cuts down on the available bandwidth for its operation. I strongly suspect this will not be receiving very much more in the way of development, since Google are now putting all their development efforts into the new Earth for Web 'webapp'.which requires a reasonably modern, powerful machine with WebGL enabled, along with hardware acceleration & a discrete graphics card. The 5- and 6-series Earth packages have long since had their Google servers decommissioned.and even some of the early 7-series are now no longer functional, as peppyy discovered recently:. This is the most recent offering from Google the 'Pro' version, currently sitting at v7., built at the end of July last year. With this one, it's definitely advisable to run it from an external location, because if you fail to limit the cache size in the settings, the cache CAN grow up to a maximum of around 2 GB in size.! Upon shutting down, the sym-links are then removed the config stuff is, however, safe within the portable itself, since the sym-links mean it has in fact been written directly to the portable's CONFIG directory anyway. With the afore-mentioned pair, I perfected a file-manipulation method that initially creates the required directories/files within the 'portable' directory, then sym-links them across to where the app normally creates them itself BEFORE actually firing it up. Since successfully creating the Skype- & Zoom-portables, however, I've come to realise it IS possible, albeit in a different fashion. At the time, I was attempting to create a 'profile', along the same lines as the Chromium-based browsers, but this particular app didn't respond to that treatment, so.I put it on the 'back burner' for a while. I experimented with turning this into a 'portable' a while back, but that was before I fully understood the placement of the configuration files. Uncle Mike's quite pleased with this one!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |