Google is Listening!
-
I'm experimenting with some UV mapping tools - so I'm curious of any idea. Would it like Pixero suggested?
In what usage scenario would you use it? -
@jbacus said:
Pixero: Please be civil if you want useful interaction with the SketchUp team.
Our development team believes that a 64-bit version of SketchUp will provide little to no actual benefit to you for the majority of modeling/rendering operations. In fact, a 64-bit version of SketchUp is likely to run slower in many operations. So my question is both an accurate and relevant one. What class of operations do you hope will be improved by a move to 64-bit processing?
If what you really want is the ability to export images at higher resolutions, please ask for that. We don't really have to shift to 64-bit processing to improve image export resolution.
If what you really want is the ability to interact with larger/more complex models at interactive frame rates, please ask for that. 64-bit processing doesn't have any relevance to this problem, but we do make performance improvements in this area with every release.
john
.Hi John!
If my post was uncivil I apologise, but likewise I found that quote from you an insult to me and other loyal SU users that have repeatedly asked for improvments to the core of SU. Something v8 didnt deliver. IMHO.
I'll try to be more polite in the future.First, I would like to thank you for replying to us in this forum.
I know it's not Googles policy to talk about unannounced features and such but I strongly believe that better interaction between users and Google would greatly benefit all.
In other software forums I visit many developers take active part in discussions and answer questions without revealing secrets.
I see this forum as the "true" SketchUp community home and would very much like to see you people around more asking questions to us, answering questions or just discussing features, solutions and workflows.To me, as a professional user, SketchUp is showing its age.
It still is a great modeling tool but more and more often I reach SU's limits and would like to be able to use it for things that I believe it was meant to do. Being a easy to use tool for architectual design and presentation.
To me that means it should deliver the tools and workflow to still be easy to use by todays standards.
The users are more and more relying on third party plugins (which are great) and several workarounds to get SU to do what we need.For example.
The shadow bug. The workaround is either to export the animation to images and edit out the "buggy" frames in a video editing app.
The result is not great since it makes the camera do a small time jump that doesnt look very professional.
Or rendering with a third party renderer. Still this gives us problems because of SU not beeing 64 bit the renderer cannot be either.
And renderers need all the memory they can get. I have never said or thought that 64bit would make SU a lot faster.
For me the main concern with it beeing 32bit is memory limitations.Exporting larger images. The workaround would be a script that lets you export the image in parts and you'll have to stitch them together in Photoshop.
(As a side note, I would for now be happy if I could export an anti aliased image that was in the range of 6500px wide.)
I could go on. The point is these are workarounds for problems that dont need to be there.As I said, SU is a great modelling tool and I believe you should rely on the community to enhance it by giving them even more access to SketchUp api. Who knows, Thomthom might even come up with a solution for better UV tools.
I've been a strong voice for improving the other aspect of SketchUp, - presentations.
I know you'll say thats what Layout's for but to many that doesnt suite the workflow.
Also, presentations can be more than a printed page.It could be a live walkthrough with a client.
If there was enhancements to materials (reflective surfaces) and lights (indoor lighting, coloured light, soft shadows) that would mean a lot. These things are quite possible in any game engine even on hardware that common people have.It could also be an animation. SketchUps animation is rudimentary compared to any competing software.
I have pushed and still am pushing the limits in this area and I believe I have some knowledge in the subject.
Since SU only do linear interpolation between scenes, making any kind of accellerating or decellerating movement is very hard.
I've developed a technique (another workaround) to make it possible but its unintuitive and slow.
http://forums.sketchucation.com/viewtopic.php?f=323&t=20173&p=167919&#p167962
Also the current way with scenes isnt really fit with rendering animations with third party apps.
I know others ask for the possibility to animate objects also.I don't think the things added in v8 are bad. But not as needed as other more important things.
And for a user that don't use GE or Layout, what are the reasons I should tell my boss to upgrade x number of licenses to v8?I also think it would be fair of you to release a free bug fix for the exploding toolbar problem also for v7.
Jan Sandström (Pixero)
-
Sure picked a well qualified area to adjust the UV mapping...
-
jbacus i still would like to know what you think of my post
http://forums.sketchucation.com/viewtopic.php?f=10&t=30586&start=60#p268908 -
Other apps integrate SU workflow step by step ...
-
thom thom: painting directly onto the model with a seamless texture.....(in the normal direction)....here you could blend different textures. ie. you could have a base texture and then add rust stains/dirt blah blah blah......dunno if this is possible but it would be SWEET! yeah like zbrush, but not as crazy.
with regrads to unwrap.....it would be nice if there was a console within sketchup (like curviloft) that displayed your unwrapped model into one plane.
here you could paint and blend textures from your materials with a brush (within the console).....hit enter.....the textures are updated (by creating one large texture that wraps around the whole model)
this would be beneficial for texturing concave forms where projection is uselss. UV tools only work (accurately) within spehercial or cylindrical-like shapes. by the way they are great
-
@khai said:
I get it. you prefer Collada even tho it is a poorly supported format at this time.
No, I'm questioning your assumption that it is poorly supported. I think it is pretty well supported now, and see evidence supporting that position.
john
. -
@jbacus said:
@khai said:
I get it. you prefer Collada even tho it is a poorly supported format at this time.
No, I'm questioning your assumption that it is poorly supported. I think it is pretty well supported now, and see evidence supporting that position.
john
.sorry I've actually given up. it's not worth the time arguing with someone who wont' see the problem when I can be getting on with things that are productive. take that as you will but that's how it is.
-
@unknownuser said:
jbacus i still would like to know what you think of my post
http://forums.sketchucation.com/viewtopic.php?f=10&t=30586&start=60#p268908I think it is great that you're digging into the real applicability of 64-bit computing for 3D modeling apps, and that you now recognize that 'performance' is the issue that you care about, not our adoption of some particular technology that you think will make a difference.
I want you all to understand that the dev team understands clearly how important general performance is in SketchUp. We work on it with every single release, though sometimes in ways that aren't entirely obvious from the outside. SU7.1 included an entirely new rendering pipeline that was in development for almost two years. In SU8, we reworked the way that raster image data is handled internally. We'll work on something else in the next release.
And while we certainly have a responsibility to increase performance in SketchUp at every opportunity, you must also do your part by managing the complexity of your model to fit within the 'polygon budget' of your particular system.
In game-theoretic terms, SketchUp's modeling performance is a classic "arms race". Every time we make SketchUp faster, you start making bigger models. Then we have to make SketchUp faster again, and then you start making even bigger models. There is no logical conclusion to this game where performance is infinite and you can make an infinitely large model. Eventually performance will plateau, and you'll have to learn how to work with the system as it stands.
john
. -
When I started with SU modelling, a large model was ~20-30K faces, then it grew steady to be 200K-300K, Now I have a couple of models of 1-2M faces - because my hardware and SU is better.
-
@khai said:
but no one's using Collada!
everyone's using OBJ.put it this way. OBJ is better...because ppl are using it. Collada maybe technically better on paper.. but if no one's using it.. it's not better.
right now, to use a Collada model I have to take the DAE into Softimage Mod Tools, save out as a FBX then take the FBX into Wings3D where I can then take it to OBJ...which everything else reads without problems.
take a look. do your own research and you'll see the problem. many apps are writing DAE.. but only a few - SU is one - that reads it...
it's comical!
I'm sorry Khai, but I really have to contradict you here. Yes, you are right, no one apart from Google are (seems to be) using COLLADA, but that doesn't mean that COLLADA is not better, it just means that everyone who are using OBJ (including developers) are ignorant! I have exactly the same problem as you. I need FBX for export to Unity, and hacking a COLLADA file just isn't doing it for me (I used to have to use Autodesk's bloody awful converter- which never works properly
). I have found the Sket2FBX application which works extremely well- but needs the entire Mono framework installed to get it working! No exactly elegant. With FBX, I can export models with faces containing image data and much more, OBJ, I cannot, and often get thousands of triangles that I then have to post process. Again why have this when COLLADA could do all this hassle free?I take my hat off to Google for pushing this along, it's really up to us users to now request COLLADA in the other tools that we use. Why Unity doesn't, I haven't the foggiest (and yes, it's preposterous that it seems like it is up to users to demand these little import/export updates). I really don't like OBJ, but people use it, because they are used to the file format, and don't want change or progression (well that's my reasoning anyway). A bit like the ongoing DWG/DXF's saga, really.
-
@jbacus said:
@unknownuser said:
jbacus i still would like to know what you think of my post
http://forums.sketchucation.com/viewtopic.php?f=10&t=30586&start=60#p268908I think it is great that you're digging into the real applicability of 64-bit computing for 3D modeling apps, and that you now recognize that 'performance' is the issue that you care about, not our adoption of some particular technology that you think will make a difference.
I want you all to understand that the dev team understands clearly how important general performance is in SketchUp. We work on it with every single release, though sometimes in ways that aren't entirely obvious from the outside. SU7.1 included an entirely new rendering pipeline that was in development for almost two years. In SU8, we reworked the way that raster image data is handled internally. We'll work on something else in the next release.
And while we certainly have a responsibility to increase performance in SketchUp at every opportunity, you must also do your part by managing the complexity of your model to fit within the 'polygon budget' of your particular system.
In game-theoretic terms, SketchUp's modeling performance is a classic "arms race". Every time we make SketchUp faster, you start making bigger models. Then we have to make SketchUp faster again, and then you start making even bigger models. There is no logical conclusion to this game where performance is infinite and you can make an infinitely large model. Eventually performance will plateau, and you'll have to learn how to work with the system as it stands.
john
.John, your post is a good example of why SU users are feeling unheard or misunderstood. It isabout "general performance" but it's also morethan that. It's also about a very specificmemory limit within 32 bit applications.
Your comment about "polygon budget," shifting the onus on the user is actually kind of insulting. It shouldn't be the case that one can't import one high poly tree into a model (much less a number of them and cars as well) because the poly budget is so low. SU is simply way under the bar in this arena in terms of it's fellow modeling software.
It is an arms race, as you say but at this point, in terms of poly budget (among other things like UV tools), we're still asking for handguns but we keep receiving shipments of frozen corn.
-Brodie
-
Thomthom have you seen this for ideas this, I haven't had time to use it much since job direction changed from modeling 3d interior objects etc to 2D ACAD, and had just begun expoloring workflow with sketchup. But I'll have to give the new Layout a try to increase my enjoyment.
-
@unknownuser said:
John, your post is a good example of why SU users are feeling unheard or misunderstood. It isabout "general performance" but it's also morethan that. It's also about a very specificmemory limit within 32 bit applications.
What we also have established is that this limit affects people who use render engines from within SU's process. So it's not something that affects all, or even most users of SU. Now, I do render with SU, so I'd love to have more memory available. But I also realise that it's not an critical issue for most SU users. SU is after all designed as a sketching tool - not a render engine host. So while we would like to be, we can't expect it.
We must also try to understand their position, that we're not the only type of user for SU, maybe not even the typical user. -
TO JOHN BACUS:
I really don't care if it's 64 bits or even 16 bits, multicore or half-core, GPU or a non-acelarated graphics card. As long as it works as the standard for their time, and SK is working almost as good as was 6 years ago (and that's not a compliment). I can't do much more than I could back then, I don't really think SK behaves differently between high cost professional hardware to a low cost one, there's no new modeling tools or ways worth mentioning (since follow me in 4 and intersect lines in 7), no mapping tools too (since texture projection in 4), and no new animation tools (i use SK since 3.1 and don't remember a change in this department...). The point is, for us users, it looks SK stopped in time...
And I still feel differences working in 64 bits especially the bigger and more data the file has. (there's MAX and PSD files I can't even open in 32 bits because out of memory errors but i can in 64bits and seems to run smoother too. Why?). Now the question is would Sketchup benefit from 64 bits and multicore architecture, even if just for the plugin makers?
So I thought it would be good to review again, with you and users of the forum, some articles from 2006 from 3d Software like Maya or 3DS Max, or XSI (the name now is Softimage, and it was the first to use 64 bits if i'm not mistaken)
http://features.cgsociety.org/story_custom.php?story_id=3768
"64-bit operation isn’t significantly faster than 32-bit, in fact 64-bit applications are commonly somewhat slower since they have more system overhead, but nothing is as slow as an application that crashes when it runs out of memory. (...)In practice, I noticed almost no difference between the software running in 32- and 64-bit modes until I hammered it with a huge dynamics system containing several million meatball particles. **The file readily crashes Maya in 32-bit mode (forcing a hard reboot), while it rendered, albeit slowly, on the 64-bit version.**It was no real surprise, but it was a welcome relief from the days of living with miserly particle and polygon budgets just to get things to render.(...) There’s no doubt that 64 bits is where things are inevitably headed and now’s as good a time as any to switch.(...) Of immediate benefit, even to 32-bit users, is that Autodesk has also made improvements to Maya’s multi-threading and operational performance in numerous areas. Users of multiple-processor systems, including those with the new dual-core processors, in particular, will enjoy performance in many operations, such as subdivision surface modeling, and working with hair and cloth. The program overall feels much snappier and more responsive."
http://www.cadalyst.com/design-visualization/first-look-review-autodesk-3ds-max-9-5954
"In 3ds Max 9, I found core-level performance improvements in several areas that provide better overall performance and a cleaner workflow.For larger and/or more complex models, the 64-bit version speeds through tasks much faster because of better use of and access to more system memory."
I can find more articles like these too and with different softwares, if you want, and i repeat: this is from 2006, i can be mistaken but i think that 4 years after, the 64 bits programming is much more refined and optimized now, especially for professional paid programmers. Now my question is: are this guys lying? Did all the professionals in the graphic industry just went nuts and blind for changing from 32 to 64 bits in software and hardware and saw differences? Or do you believe that your 32bits engine is as capable and fast as, for example Zbrush or modo (i choose these ones because the price is not much higher than SK, and in zbrush we get free upgrades forever...)and don't see the need for an update? Because i can choke SK with the less than half the polys the others can stand and still be workable...Isn't really nothing in the whole program that SK is, that would benefict from x64/multicore? one single item? Animation exporting, intersect operations, anything? or is the problem related to the old OpenGL engine SK has? And isn't OpenGL already multicore?
Honestly, I'm really curious about what you have to say about this.
About my opinion on SK8: it's a weak release, even weaker than 7, because 2 years have passed, we have exactly the same problems than before (even after giving ideas to you as you google ask us to do) and now we just got 1 new tool, and it does something that we could already do with a little more work using "intersect" or with a plugin called booltools (just for curiosity, are the solid tools a ruby plugin like DC components was in 7)...From this side it seems that your plan is releasing a new version every 2 years, with not much worth mentioning, gain some money and leave the heavy work and innovation for plugin makers (and all of a suddenly a cheap software get's more costly with all the paid plugins..)
For ideas for sketchup i got a few:
1- Multicore suport (why is layout multicore and sketchup singlecore?)
2- 64 bits suport (see above why i think we need it)
3- support more polys
4- Build a robust platform for others to work, compatible with current and future technology (multicore, 64bits, gpu accelerated) so that plugin makers can also take advantage of this and build better and faster plugins (even if you don't).
5- sketchup scenes that save the position of components and points (because points defines lines that define faces allowing some basic animation), or any form of animation more complex, and would be great if we could export the animation to other software's too.
6- Put the same line tools that layout has and make the existing one work properly (like offset)
7- make the import\export 3d model work and at least add obj import to the options
8- update the uv mapping tool (sphereical, cilindrical, unwarp, etc) and materials (like one material with 2 layer of textures with different mapping each, and/or basic reflex material for example)
9- Have the basic tools work as it should (offsets, follow me, from countors, shadows, 3d model formats import, and so on...) and do little updates on it ( like pushpulling more than one face at a time or working like jointpushpull, or do a scale not oriented with the axes but with a part of the mesh, or "add Detail" tool doing a basic smooth on meshs)
10- more ways to work with organic and curved meshs, either by new tools or by updating the old ones with smart and inovating ideas with the way they perfomed on cubic and organic meshs, and keeping things with lesser bottons)
11- give us a form to simulate basic lights other than the sun, and for the love of GOD fix the shadow bug ( how much time is this bug around without a workaround now? 6 years? isn't that too much time?)
12- Separate Layout from SK, (right now there's users that just want SK and don't have a use for layout, but with the current situation, feels like they are paying for Layout evolution and not SK's one, and overpaying for 2 programs just wanting one. If layout is that good it will survive on their own, and it is on version 3 now, not beta and unknown anymore...and i don't even know what to say about sylebuilder...)
13- a, basic and simple to use, physics engine would be nice, and there's so many open source (in case you don't know a physics is not just good for animation, but also modeling natural stuff and set up some type of scenes)
14- rebuild, if you have to, the SK UI so that this toolbar chaos and workarounds ends
15- and most important: LISTEN TO USER'S FEEDBACK (and if possible answer them)I tried to make a features list more wide as possible so that any user, independently of their use of SK, could benefit from them, and in a way that SK doesn't turn into a behemoth like 3DS Max but that can be a much better modeler and still fun and easy to use, just allowing in the process to do more and better stuff.
And I would really like to hear a answer or opinion about this from you Google guys.
Thanks for reading and sorry the long text.
P.S: a special word for Coen: thanks for standing up for us
-
@thomthom said:
When I started with SU modelling, a large model was ~20-30K faces, then it grew steady to be 200K-300K, Now I have a couple of models of 1-2M faces - because my hardware and SU is better.
Hi, Thomas.
Can you elaborate on your system spec?
I'm working on an i7-920 / 12Gb / GTX470 Workstation, and SU dies on me two-tree times a week.
Using Trees for example is out of the question...Thanks.
-
@emage said:
@thomthom said:
When I started with SU modelling, a large model was ~20-30K faces, then it grew steady to be 200K-300K, Now I have a couple of models of 1-2M faces - because my hardware and SU is better.
Hi, Thomas.
Can you elaborate on your system spec?
I'm working on an i7-920 / 12Gb / GTX470 Workstation, and SU dies on my two-tree times a week.
Using Trees for example is out of the question...Thanks.
My current system? Quadcore, 3GHz, nVidia GeForce 8800GT (home), nVidia Quadro 3800FX (work). 8GB RAM.
When you say SU dies, it crashes? While modelling? While rendering?
What trees you use? XFrog, Evermotion? -
It's easy to forget that when you are working in Sketchup you are working within a (more-or-less) real-time render engine... which, as a by product of how the developers see the market they are serving, is geared to use "lowest common denominator" hardware.
Sketchup is for the masses -- and the more power you give it the more powerful hardware is required to run it... thus excluding the very people they are trying to include.
Also, in my experience you can do very high poly models if you disable most of the features of the render engine in Sketchup... which will make the interface look very much like most other "pro" modeling packages.
That said, I think it would be wise for the Sketchup team to put a larger gap in the performance of the free version to the pro version... so that hobbyist and students can use the free version with low end hardware and professionals can have access to all the power inherent with high-end hardware.
Best,
Jason. -
@unknownuser said:
In defense of SketchUp in general, not in particular v8, I find that when I turn off Edges and Profiles, or more generally speaking all Style related aspects,
Yes, style effects can slow down a model as badly as shadows. (even Colour by Material and Colour by Axis slows things down as SU has to draw the edges in multiple GL operations) I usually have a "Modelspace" scene that turns on my optimized modelling style with all effects off. I model with that style and only swap to scenes with effects on when I'm ready to export.
-
@notareal said:
@unknownuser said:
...but still, what are you going to gain from more memory?
Maybe not important for everyone, but one simply reason for me, going to 64-bit SU would allow 64-bit renderer work in context of SU. It's already possible to create a SU scene that will not render with SU integrated 32-bit renderer, because of memory restrictions.
Sorry, but I find it amusing that you are still hammering through the 64-bit arguement even after it has been explained that you won't really notice any difference in speed improvement, then to start on about rendering, when you have links to renderers in you sig! Whatssup? Are these no good?
Advertisement