Google SketchUp 7.1.6087
-
Do you have the software renderer turned on? You can check this via Preferences, click on the OpenGL tab. There is an issue in Apple's software renderer that gets triggered by SketchUp which can cause crashes. Enabling the hardware renderer resolves this.
-
@dspringer said:
Do you have the software renderer turned on? You can check this via Preferences, click on the OpenGL tab. There is an issue in Apple's software renderer that gets triggered by SketchUp which can cause crashes. Enabling the hardware renderer resolves this.
Thanks, yes up and running, and all drivers current.
With me I'm pretty sure this is a translation issue with dxf/dwg, as seems like the only time I have issues is with these files. -
All this SU maintenance and updating is starting to interfere with the weekly vacuuming my wife has left me to do
Would it not be simpler to create a patch.exe for D/L, to fix these bugs: Instead everyone is downloading and installing yet another copy of GoogleSketchUpProWEN.exe
It would also make more sense to rename each new GoogleSketchUpProWEN.exe by including the revision number in the title ie. GoogleSketchUpProWEN.v7.1.4871.exe It would make it easier to distinguish the latest from all the other turkeys?
happy gobble gobble!
-
I didn't notice it mentioned in the release notes, but is the Shadow bug gone? I couldn't make it happen in a file that recently was displaying it very consistently. Have to go on testing.
Anssi
-
@tomot said:
Would it not be simpler to create a patch.exe for D/L, to fix these bugs: Instead everyone is downloading and installing yet another copy of GoogleSketchUpProWEN.exe
I recognize that it may seem inconvenient to have to download such big files every time we make an update, but in the grand scheme of things, it's not too frequent. Creating patches is actually an extraordinary amount of work in comparison to using our existing (automated) process for creating full product installers. I've seen an awful lot of complaints around the forums in general from folks who seem to think we have a team of thousands working on SketchUp and wanting to know why we haven't fixed every pet peeve bug. The truth is, we're a pretty small team and every minute we spend fixing problem "A" is a minute lost to problem "B". I think the amount of work it will take to create reliable patch files and the tech support effort it would require to make sure everyone installs and manages them in the proper sequence and manner would easily dwarf any benefit that such a scheme would provide.
You can also thank the good folks at Apple for never creating a fundamentally solid install/uninstall technology, which also contributes greatly to the problem on Mac. While we use a good MSI technology on Windows that makes managing installation a much easier affair, it still would be quite a bit of work to make such customizations. I'll also point out that if you were to perform a binary diff on all of the files in each release, you would find that the overwhelming majority of files were all changed, which is a byproduct of our product architecture. Fixing the underlying architecture to actually make patch distribution an efficient endeavor would be an enormous job which would go 100% unnoticed, unfortunately.
@unknownuser said:
It would also make more sense to rename each new GoogleSketchUpProWEN.exe by including the revision number in the title ie. GoogleSketchUpProWEN.v7.1.4871.exe It would make it easier to distinguish the latest from all the other turkeys?
We keep the filename the same for a few very good reasons. 1) We don't have to change all of our back-end code for serving files from the online store, etc. 2) It ensures that when people post links here on the forums, they continue to be up-to-date at all points in the future, which is an entirely worry-free endeavor.
When I post SketchUp for download, I actually do provide it under a specific link including the version number, in addition to the generic one, but it's not something that is well publicized.
For instance, http://dl.google.com/sketchup/gsu7/PW-2-1-6087-EN.exeI think you have to admit though that it's a lot easier to just go into SketchUp and use the "check for update" mechanism to find out if a new version is available, instead of having to remember and mess with version numbers.
@unknownuser said:
happy gobble gobble!
And the same to you and yours!
Cheers!
-
@unknownuser said:
I didn't notice it mentioned in the release notes, but is the Shadow bug gone? I couldn't make it happen in a file that recently was displaying it very consistently. Have to go on testing.
Anssi
I made a small test at work, and I'm asking myself the same thing. I'll have to make another test with an old model at home.
EDIT : I made another simple animation with some tree components with which i had always the shadow bug, but the bug is gone.
Is this a hidden bux fig ?
-
Guys, I also made a test the other day (with an interior where the sun was shining through the windows) and it is still there. Was flickering like a disco ball.
-
Ok, thanks Gaieus. But the bug seems to be less present, because it disappears in some of my models. Maybe the last optimisations of the 7.1 release are responsible for this, don't know...
-
Hi Andrew,
looking at your post where you write that SU at Google represents a rather small team. I wonder if that small team is in relation to the userbase of SU. I can't think of an architectural office that does not use SU. It might be even bigger than autoCAD. Is there not a bit too much presure on too few people at Google Skechup ?.
Maybe Google has underestimated the potential of Sketchup in the construction and architectural industry ?
Francois -
Is there an MSI version that I can use to push out via Group Policy?
Thanks,
Lindsay
Advertisement