SU upgrade to 8.0.4811 (Maintenance 1)
-
I have never had this issue on my PC. In fact, I have upgraded like 6 times for the last couple of weeks/months now without any problem and losing anything. It only overwrites the default, native SU content 8that comes with the install), nothing else.
-
wow, ended up being a nicer update than i initially thought
i found an issue with the shadow string fix though.. it fixes the strings but introduces another problem..
i'll post an example a little later. -
@gaieus said:
I have never had this issue on my PC. In fact, I have upgraded like 6 times for the last couple of weeks/months now without any problem and losing anything. It only overwrites the default, native SU content 8that comes with the install), nothing else.
Gaieus
I believe when I upgraded from 4 to 5 I lost all my plugins, materials and components. Never had the courage to try again. So, next upgrade I will save a copy of these three directory in another directory, and try your method to install over.
So, make this a duh!! moment for me.
Thanks Gaieus.
-
Gai,
Shadow bug fixed! .animation (codecs fixed)? Wow!
Maybe my office machine will create animations now.
Per Google: "/Largeaddressaware". Does this mean that 64 bit computers can now address bigger files, while 32 bit machines retain the benefit of speed?
I hope the api fixes will not cause problems for "workarounds".:-)
-
Ken; yes, testing it won't harm (just in case)
HDT: LAA, I believe, will only be useful on 64 bit. However you can also "hack" a 32 bit OS to be able to assign more RAM than 2 Gb to a single program.
-
A comprehensive release! Toolbar fix fixed
LAA Thanks Sketchup Team!
-
model.raytest fixed!! with the optional boolean attribute as well. THANKS!
And the shadow bug fixed. That's a nice surprise.
--
karen -
@honoluludesktop said:
Per Google: "/Largeaddressaware". Does this mean that 64 bit computers can now address bigger files, while 32 bit machines retain the benefit of speed?
Yes - Under 64bit Windows, SU can now address up to 4GB RAM. (I have tried it with a huge render.)
-
Ken,
@unknownuser said:
I believe when I upgraded from 4 to 5 I lost all my plugins, materials and components. Never had the courage to try again. So, next upgrade I will save a copy of these three directory in another directory, and try your method to install over.
My colleague, Steve, and I were responsible for creating the SketchUp installers for Mac and Windows. I have only been on the SU team for just over three years, so I can't speak to what technologies were in place back in the 4 and 5 days. However, on Windows, for SketchUp 7 and 8, which were built as MSI-based installers using Wix, if you're just installing a minor release (anything where the major version number stays the same, like 7.0 -> 7.1 or 8.0 -> 8.0 maintenance release 1), you should be perfectly safe to run the upgrade in-place. The Windows Installer technology is supposed to be smart enough to replace just the files that differ in your current installation vs. the new installation, without removing extraneous files or replacing directories wholesale.
This does highlight the point that if you've made any modifications to files we provide, those modifications could be lost in an upgrade. However, you should never (99.999% of the time) need to overwrite any of the files we provide for you with your own modifications anyway. If you need to modify something like a LayOut template, copy the file and make a differently named version with your modifications so they can be preserved separate from what we've provided. And, in the cases when it is possible (such as with LayOut templates), store your own files outside of the SketchUp directory structure, just to be on the safe side.
Obviously, with things like plugins, you have no choice but to put the files inside the SketchUp directory, so if it worries you, make a quick backup of the SketchUp directory before proceeding with the upgrade, but do know that we expect it should work without such intervention.
Andrew
-
@honoluludesktop said:
Per Google: "/Largeaddressaware". Does this mean that 64 bit computers can now address bigger files, while 32 bit machines retain the benefit of speed?
Sort of. In short, the flag will help many people, but don't be surprised if it doesn't improve your specific situation.
For all of the reasons discussed a million times before, migrating SketchUp to compile natively as either 32 or 64-bit is a very difficult and incredibly time-consuming endeavor. However, when we heard about the possibility that the functionality of memory-intensive operations might be improved without going all the way to a 64-bit migration, we jumped at the chance to try it.
Those who brought the /LARGEADDRESSAWARE flag to our attention touted it as a magical cure-all. Indeed, we had high hopes that it would make a marked impact for those folks who really want to work with much larger files; we invested quite a lot of work in turning that flag on, ensuring we had done it correctly and consistently throughout SketchUp, and testing the results. Unfortunately, in the specific case of compiling and linking it into SketchUp, Style Builder and LayOut, that flag is more snake oil than miracle cure.
I did some pretty extensive testing with large images after we first introduced that flag to our compilation, on both 32-bit and 64-bit machines with Windows XP, Vista and 7, all with varying amounts of RAM from 1 to 12 GB. After all, we also needed to make sure the flag didn't break anything either.
Although I found many cases that showed improvements on 64-bit machines with more RAM than was usable in previous versions of SketchUp, overall, I was disappointed because it didn't make the staggering difference we all expected. Although many of you will find the improvements to your liking, SketchUp is still going to fall short for those of you who want to perform actions that are an order of magnitude beyond what SketchUp has traditionally been able to do, such as exporting 10,000 x 10,000 pixel anti-aliased images.
It is worth noting that in some cases, the threshold for seeing problems varies by the operating system. For instance, I was able to export high-res PDFs from LayOut under Windows 7, which failed on XP. Oddly enough, I even showed such a test case that worked really nicely on a Win 7 machine with 1 GB of RAM, while failing on Win XP with 4 GB RAM. Although we were not able to pursue that issue down to its root cause, we believe that in some cases, the inconsistency is due to differences in the system libraries distributed with each platform, or possibly, in the way the kernel of each OS manages memory. Apparently on Windows 7, even with 1 GB RAM, the memory management for that operation is much better overall than what happens with Windows XP. Strange, but true.
Andrew
-
GREAT UPGRADE - THANK YOU SKETCHUP
-
@andrews said:
Those who brought the /LARGEADDRESSAWARE flag to our attention touted it as a magical cure-all. Indeed, we had high hopes that it would make a marked impact for those folks who really want to work with much larger files; we invested quite a lot of work in turning that flag on, ensuring we had done it correctly and consistently throughout SketchUp, and testing the results. Unfortunately, in the specific case of compiling and linking it into SketchUp, Style Builder and LayOut, that flag is more snake oil than miracle cure.
The people who will benefit the most from this are probably render engine users, like me. Some render engines run inside the SU process. Previously you'd be in trouble if you rendered large files as things would crash when memory usage creeped up to 1.8GB. I had found a utility to change the LAA flag in SU8M0 and that had saved me a few times when I had to squeeze out some larger renders. I'm glad it's not LAA out of the box and I don't have to use hacks to enable it. The extra 2GB availible has helped greatly.
-
Wow, I'm impressed. Shadow bug fixed and toolbars and large adress aware too...finally I will consider upgrading to v8.
-
I'm impressed! A proper release that appears to solve real problems, I can't wait to try it out!
Thanks,
Paul -
For me this point release have more pleasant stuff than v.8 itself.
Thank you google team. I just wonder is it (partly?) a reaction to the cold wave of criticism toward v8? -
I have some issues with this update :
I reduced my Sketchup Window in order to test the toolbars, then maximised the window, go to View > Toolbars > Restore position of toolbars : the position of toolbars is right, but there's many icons which disapeared !! For example, my Sandbox toolbar only show the tow first icons !! And the same thing on many other toolbars.
Anyone encountered the same issue ??
Regards.
-
@panga said:
Anyone encountered the same issue ??
I have experience that. Not sure when/why that happens. Doesn't happen all the time.
-
Good job Google, I downloaded the 8 demo when it was first released, didn't see much reason to upgrade, till now. Now if only we could get some better texturing tools........poor Google, it's never enough.
Mike
-
The bugs noted by me:
SketchUp 8 Bugs: http://forums.sketchucation.com/viewtopic.php?f=180&t=30583
-
Shadow bug fixed?! Are you kidding me? Is it Christmas all over again?
Seems like a really nice and comprehensive update and that brings joy to my heart.
Thanks to the developers for all their hard work!
Advertisement