SketchUP 8
-
thnx to this Post
I wish they fixed problem what we watched on old versions -
@jbacus said:
@pitrak said:
Is there a roadmap for Back Edges mr. Bacus?
As a matter of policy (both Google's and before that @Last's), we won't comment on unreleased features or future directions for the product in any but the broadest possible terms. I recognize how much you'd like to know what's coming next, butwe need to preserve a quiet space in which the team is free to experiment with projects that may not work out. Software development is more like painting than manufacturing, and you're better off in the end if we're free to be creative.
john
.John, Whatever else I may have said, I do want to say thank you for the link to this article. Being the daughter of someone who considers himself a "computer SCIENTIST" (his emphasis, not mine,) I had never actually thought about software development in this way. Having studied painting though, I can see where the analogy may be true. Thank you for lending a valuable perspective on this. Also, I do very much understand the need for a peaceful creative space for developers to experiment in.
While we may disagree on some points and likely never agree on the direction SketchUp is moving, or the SU8 release, I think I understand now a bit more of the dynamics involved for the dev team.
If I ever actually begin making money off of my CGR efforts with SU, I actually will go Pro. Until then, well, the price tag is out of my league, which is a crying shame, because I would like to be able to support the dev team and keep them in cheese sandwiches.Oh, the reason I keep using SU, in spite of the PolyLimitation, and sometimes annoying flaws? It is still simply the best freeware modelling program available for my working style and workflow needs, which is invaluable for those of us who are trying to learn CGRengering and want to someday be as good as some of the heavyweights like Solo.
Cathryn
-
I wonder this myself at times. While I still like SU and I am glad to have it I think that it might have been better 1st if @Last would have not "sold out" to Google or might have partnered with another company that understands 3D and design. I am sure that if AutoDesk would have bought them we would not have seen the free version of SU but on the plus side development might have taken off a bit more or maybe more refined, maybe.
@frv said:
I just read that Sketchup is still bigger than Revit, right behind 3ds Max.
http://www.cgarchitect.com/news/Reviews/Review070_1.aspLooking at these numbers I understand the disappointment about were Sketchip is going according to Google's stated strategy. Obviously a large portion of SU's userbase would love to stay on board a winning ship. One wonders truly how a more dedicated CAD company would have handled such succes in the business. A good chance SU would become the industry standard in architectural modeling. Many feel here that SU needs another, younger and more enthousiastic captain more like the original one to command the current SU team.
But at the moment SU is still a great tool and SU8 is even better. But looking at SU8, SU will slowly drop down the list knowing that it could have been moving up.
Francois -
@unknownuser said:
I am sure that if AutoDesk would have bought them we would not have seen the free version of SU but on the plus side development might have taken off a bit more or maybe more refined, maybe.
I don't think AutoDesk would have been any good for SU. Of all the apps that cause the most grief here at the office, they all comes from AutoDesk. -
You CAN get vector DWG exported from Layout. It is a setting option. You need to change your Layout Image to vector first.
Take a look at this video:
http://www.youtube.com/watch?v=NWCve65JJhI&feature=player_embedded - Drafting in LayOut
-
I hear that a bit but honestly I have no issues with it. I open it up do my work and turn it off when I am finished. About the only time I see issues are when users don't have the correct hardware or if they just don't know what they are doing. Been using it for 15 years and there have been a release or 2 that had issues but they were some time ago.
To each their own I guess@thomthom said:
@unknownuser said:
I am sure that if AutoDesk would have bought them we would not have seen the free version of SU but on the plus side development might have taken off a bit more or maybe more refined, maybe.
I don't think AutoDesk would have been any good for SU. Of all the apps that cause the most grief here at the office, they all comes from AutoDesk. -
With each release I'm always surprised and disappointed that some basic improvements to texture manipulation are not included... small things like letting me create a shortcut for rotate texture 90d or adding a preference that lets me choose texture by texture the default location of the "red pin" -- is it going to be the center of the poly or at a vertex over on the lower left corner? Depending on the material it's always one or the other and right now it's a PITA when it's always some corner vertex.
How about letting me pick a color for all endpoints -- just the endpoints -- as black on anything really dark is almost impossible to see... or the colors of lines within a component. Show line color for "this" axis only would be useful too. Those are just object attributes, not rocket science.
How about select by material when a material has not yet been assigned? Can't be too hard to do....
Last two, probably a bit more difficult :
-
let me select a bunch of faces and when applying a texture, let me choose whether I want the texture applied individually to each face as-if I was doing them one by one (the way it's done now,everything is relative to the face) OR as a collective set where the red pin for each face has identical xyz values (i.e., where there is one absolute point for the set and all faces have their texture start from there).
-
Think stone arch bridge: Texturing multiple faces that follow the vertical faces above an arch is quite painful so how about a texture follow-me?
-
-
The "Get More Imagery" Google Maps replacement for the old "Get Current View" from Google Earth is even worse than I foreshadowed in my previous post. Not only can the view not be rotated to line up with the building, the imagery has the Google copyright notice splattered all over it. How is one supposed to use it to texture built-up terrain with writing all over it?
With that backwards step plus all the other bugs introduced in V8 I cannot see any benefit in using it at present.
-
@pmolsen said:
The "Get More Imagery" Google Maps replacement for the old "Get Current View" from Google Earth is even worse than I foreshadowed in my previous post. Not only can the view not be rotated to line up with the building, the imagery has the Google copyright notice splattered all over it. How is one supposed to use it to texture built-up terrain with writing all over it?
With that backwards step plus all the other bugs introduced in V8 I cannot see any benefit in using it at present.
I like the new way of getting terrain and imagery. Much easier than in 7.?.
Running Pro8 the logo is in the lower left hand corner and the imagery copyright is in the lower right.
If you do not want it in your model - can you grab an area larger than you need and crop it out?As for rotation - once in SU, unlock both the terrain and the image and you can rotate, copy, move, etc.
FWIW I usually bring my model into my terrain for presentation, and keep the model file lean and as simple as possible.
-
The copyright notice is all over the image, not just in the corners. See attached. (Click on the image to see it in full size).
Grabbing a much larger area results in a much less detailed image. When used to texture built-up terrain it looks terrible.
-
@bmike said:
As for rotation - once in SU, unlock both the terrain and the image and you can rotate, copy, move, etc.
I'm sure Peter meant to rotate the map in the "Add Location" window. For efficient modeling, we actually used only as much of the satellite image as necessary. That means if a rectangular building is directed towards south-west, we rotated the view in Google Earth so that the building fills the view as much as possible (for best resolution and to get rid of the corners).
There are lots of users who critizise this regression although I can understand that the SU team had to drop the Google Earth method for long term (deprecated). -
The problem of taking too large an image for low quality is reduced with this update - I like that I can go back and grab more terrain an imagery at a later date as needed.
For my needs, this works better.
Perhaps Google can add rotation / skew / etc. to the 'grab' process - much like those pins on material / texture adjustments. -
@pmolsen said:
The copyright notice is all over the image, not just in the corners. See attached. (Click on the image to see it in full size).
Grabbing a much larger area results in a much less detailed image. When used to texture built-up terrain it looks terrible.
To be honest, I think that is a small price to pay in return for a (free) colour landsat image. You wouldn't necessarily use that for a final image anyway, because it's so dreadful. It's fine to most clients- especially for mockups etc (which essentially is what SU is for anyway, right?). I'd rather use good post-processing tools to create an artificial landscape than use that crappy photo.
-
Google requires or at least strongly recommends that models be textured with their imagery for models submitted for inclusion in the 3D Buildings layer. Failure to do so can result in the model being rejected. Naturally for other purposes it is irrelevant.
When texturing built-up terrain it is essential to use the GE image in order to achieve a seamless result.
I have in the past recommended (and if Google is reading this, I recommend again) that Google add a new texture option to Sketchup called "Google Imagery". Any texture with that attribute would have the standard GE imagery (full resolution, not a grainy substitute) automatically applied to it when displayed in the 3D buildings layer. When viewed independently it would have whatever texture is actually applied to it.
The big advantage is that when the GE imagery is updated the model and built-up terrain etc. would automatically receive the new texture without the need for the user to re-texture it. It would reduce model size and would also result in perfectly seamless integration of models and built-up terrain with the underlying Google Earth imagery and terrain.
Naturally if there was a significant sideways shift in the imagery it could require manual adjustment of the building location by the modeller but for built-up terrain that would not be a problem.
This model of mine is a good example that would benefit from that: http://sketchup.google.com/3dwarehouse/details?mid=736735667eaa157548846c67671d9660
This is another one, which I have had to completely re-texture twice already due to new imagery: http://sketchup.google.com/3dwarehouse/details?mid=8f0ba6075e797f2248a0c60ecb66c42
-
You do have a good point there. I'm also a little perplexed and confused why high resolution isn't included in SU Pro, when it is available in Google Earth Pro. Maybe we have to buy that as well?
-
@pmolsen said:
This model of mine is a good example that would benefit from that: http://sketchup.google.com/3dwarehouse/details?mid=736735667eaa157548846c67671d9660
Looks like a fantastic model. Why can't I download it (no download button)?
-
@unknownuser said:
Looks like a fantastic model. Why can't I download it (no download button)?
It will be made available for download at some point, dependent on discussions I have been having with the Peruvian Tourist Bureau (Promperu).
(Linked at http://www.peru.info/en/culture/archaeology/machu-picchu-1140-2-576-4.1.16.7 )
-
One more basic feature that could be added: Why can't I type the rotation value when rotating a texture? Or the distance value when moving it or stretching it? It's just another object and should be open to manipulation by all of the basic commands.
-
@genma saotome said:
One more basic feature that could be added: Why can't I type the rotation value when rotating a texture? Or the distance value when moving it or stretching it? It's just another object and should be open to manipulation by all of the basic commands.
Great idea!
-Brodie
-
Two more very specific suggestions:
There are times where I take a component in a model and rotate it for use in another situation. Because the axis of the component instance also rotates. I have many situations where that's not acceptable, so I have to explode the new instance and make a new component under a new name. It would be far easier if there was a function I could use that reoriented the component axis to the same as the whole model -- the move axis feature is far too cumbersome... I simply want a single click - bang - it's done solution.
The other one is about textures (again). This morning I'm orienting textures along an arc'd surface... many polys, each of which requires a rotation AND positioning the red pin on a vertex. Now if these were poly faces I could easily grab a bunch and move them but textures have to be done one by one. So how about letting me highlight multiple textures-on-faces and let me move them all at the same time? The ideal would include another function to snap red pin to nearest vertex.
Advertisement