There are NO dates for SU 7.
-
John Bacus asked me at 3D BaseCamp whether I can name any 3D modeling software with pulti processor support.
Of course I could not - after all I1m not a 3D software specialist. Can you? (Note that I do know some that support multicore but only at the rendering end, not the modeling process). -
cinema4d, you can put at render-process, then continue to work in same project-scene or another while rendering. Additionally you can make preview render while rendering of main file(not stop it)
-
When SU was with @Last, there seemed to be a good level of communication with the developers - keeping us informed with developments & release dates etc.
Since it's gone to Google, I feel like a brick wall has gone up - nothing gets in, nothing comes out. Has anybody heard anything? Are they still working on SU, or is it just sitting there?
-
Released for the 10-12 Years birthday of Google?
So 15 september
-
@ilay7k said:
cinema4d, you can put at render-process, then continue to work in same project-scene or another while rendering. Additionally you can make preview render while rendering of main file(not stop it)
So that's what I mean. WITH the rendering processes it is possible.
You can keep modeling on a quad core machine while two other cores are rendering your Kerkythea render and maybe the fourth is renderin a preview in Kerky again.Are we now at the same point? Sure SU does not have a built in renderer (unless you count the native SU output - but that needs RAM, not more processors).
-
Maya and autocad both support multiple cores for modelling
-
I'm not sure about this, remus. As far as I remember, Pete (solo) brought some of these examples up as well and turned out that only some tasks could be split off the modeling core.
But again; as I said I1m not an expert of this field. John did however seemed quite convincing by explaining a couple of things.
Like for instance memory and counting hungry rubies which do several things could maybe run on another core?
-
Im not very well versed in the details either, so i may be wrong.
Like you mentioned though, i imagine its still possible to split some of the stuff SU does on to another core. Calculating shadows, running rubies etc. or perhaps some shiny new SU 7 mystery feature
-
AFAIK shadows (as well as textures) are already run by the memory instead of the processor - although they can be dynamic and are vector based.
-
Thats interesting, never realised that before.
-
as far as I know, Remus
-
Well it sounds pretty plausible, at least.
-
@gaieus said:
John Bacus asked me at 3D BaseCamp whether I can name any 3D modeling software with pulti processor support.
Of course I could not - after all I1m not a 3D software specialist. Can you? (Note that I do know some that support multicore but only at the rendering end, not the modeling process).Looks like you got a shitty reply.
To me that sounds like the performance issue Sketchup has, is being ignored.
One should not look at his neighbours to solve in house things.I am not the techy savant, but yes there are a lot of 64 bit versions of different modelers (C4D,Max,etc...). Clearly 64 bit pays off when rendering.
Who still uses default sketchup nowadays in presentations? Sketchup has numerous professional 3d party render engines.....which all are handicapped because of SU being stuck to an unoptimised 32 bit core.For a lot of 3d party developers like Asgvis ( Vray for Sketchup), it is very frustrating that their software cannot unleash its full power because of a handicapped SU core.
For instance,and this goes for ALL render software apps, the export phase from Sketchup cannot use more than 3 GB RAM because of 32 bit. A very complex scene (or a medium complex animation) will simply crash at export, even if you have 16 GB RAM installed.
Those developers are left in the cold. No news about future improvements or modifications for Sketchup.And to me it is not about "64-bit" and "multicore" itself, it's about being a dynamic and speedy application.
Having 64-bit is just one of the strategies. (DirectX support is one as well among others )
If Google comes up with another solution, that's ok too.
But I can't help thinking that multicore optimising and having a 64 bit version would solve a lot and could settle the software for much more years to come... -
@remus said:
Maya and autocad both support multiple cores for modelling
No they don't. Rendering and some other things like writing/reading files and the LISP interpreter are able to be multithreaded.
I wonder if the inferencing system is the greatest resource hog in SU. It reminds me of the object snap system of AutoCad 15-20 years ago. If you turned on continuous Osnap the system slowed down into a crawl. Then Autodesk rewrote it, and your old 386 started flying again...
Anssi
-
I'd be interested if anyone has a large model that kills their SketchUp, but works just fine in every other modeling software. I'd like to see what everyone is talking about. Thanks,
Chris
-
@chris fullmer said:
I'd be interested if anyone has a large model that kills their SketchUp, but works just fine in every other modeling software. I'd like to see what everyone is talking about.
You kidding?
Try a nice Evermotion interior. You'll notice straight away SU starts to lag like h*ll. Or try an exterior, with some pretty, elaborately modeled trees. Orbiting will become next to impossible. If SU doesn't go into a coma, that is.If all the high poly stuff I have weren't copyrighted, I'd give you a model straight away - you'd immediately see what the fuss is about.
Now, let's look at the positive side here. If (IF!) Google adds high poly support, SU will be a killer app.
-
I, too, have models I can't share but can have SU lagged into oblivion.
Place them into Cheetah 3D, for example, and no lag whatsoever.
The way things are going in the 3D modeling world, we aren't even looking for high poly support; we are looking for a little less than average poly support.
With the amount of polys that Cheetah, Silo, and Z-brush can handle, it is pitiful for SU to lag out with a few 100,000's.
I feel like a blacksmith, who has been shown a new induction forge (which is fecking unbelievable, btw) and then is forced to use coal and a bellows.
Every day, Su falls further behind.
And don't even get me started on one core rendering exports. I mean, you have got to be kidding me, right? How long have 8-cores been out?! Nothing frustrates me more than watching an animation export take 39 hours, all the time using 1 of my 8... Ridiculous... And looses me money, to boot.
Almost 2 years since 6 came out and Layout is still beta?! Animation exports on the MAC side of things is still completely fubared?! Image textured models can't be shared between MAC and PC?!?!
When you see how often "smaller" softwares,like silo (2 guys) and 3d coat (basically 1 guy) update, improve, and add features, all while maintaining a wonderful web support environment, it gets even more depressing. When was the last time a Google developer/coder came on here and asked what issues we need addressed and then an update came out 3 or 4 days later. HAHAHAHA, now the very thought of that happening is hilarious; you know that ain't going to happen.
Google buying SU was every bit as catastrophic as I thought it would be. It is obvious that pro users, who are pushing things to their limits, are very very far from Google's priority.I wrote a solicited (!!!), details report concerning all of the issues I have been experiencing with Ver 6 (on a MAC) over a year ago and how much of what I talked about has been addressed? Absolutely none of it. Thank goodness I wasted a few hours compiling and typing all of that out.
and I am still patiently waiting....
-
@unknownuser said:
When you see how often "smaller" softwares,like silo (2 guys) and 3d coat (basically 1 guy) update, improve, and add features, all while maintaining a wonderful web support environment, it gets even more depressing.
While I like to stay positive, this I firmly agree with.
-
I have to agree, i was browsing the MoI forums recently (another 1 man development team), there was a feature request, then the next day it had been fully integrated in to the next beta release. Granted it was a relatively minor feature, but the fact that the developer just read it and added it is friggin awesome. Damm google and their NDAs shakes fist
-
Yeah ... that guy is amazing. He offers great support. Very dedicated. I oughta use my copy of MoI more often.
Said it before, and I'l probably say it again, but if 7 don't offer high poly support, I'm not upgrading, not a chance - hell, I might even seriously consider switching to another ap partially. I can totally imagine myself doing rough modeling in SU, and taking the model into another app for further refinement.
Advertisement