Intersect with Model
-
Is an invaluable tool. I use it after I have imported geometry from other programs.
It gets rid of all those added faces that sometimes accompany the imported geometry. I'm importing some geometry at the moment, which is being processes by SU, after I initiated the Intersect with Model command. Its been 1/2 hour since the proceessing began. My Quad core machine shows Core 2 doing most of the work while the other 3 cores appear to be on holidays.I have used some rendering addons for SU where all 4 cores are being used close to 99% of the time. Why can't SU make better use of the additional cores?
cheers!
-
sketchup doesn't support multi-core mcahines i'm afraid!
it's somthing tht everyone wants though.
pav
-
The stuff Sketchup does can't necessarily be split into multiple tasks to be run simultaneously on multiple cores like rendering operations can. It's not as easy as just throwing more cores into it.
-
It's simple: Because Sketchup does not fully support multi-core.
Please see here:
http://forums.sketchucation.com/viewtopic.php?f=15&t=22173&p=194806#p192442
http://productideas.appspot.com/#15/e=2191e&t=220cc&o=32&v=27 (click on the answer for multi-core) -
@thomthom said:
The stuff Sketchup does can't necessarily be split into multiple tasks to be run simultaneously on multiple cores like rendering operations can. It's not as easy as just throwing more cores into it.
It would really nice if Google threw some money at developing SU. Its not as if they are not making any. Also, its starting to look like Google is taking a page from the AutoDesk playbook. AutoDesk has done virtually nothing with AutoCad over the last 20 years, except change the revision numbers prompting a new release each year.
-
@tomot said:
AutoDesk has done virtually nothing with AutoCad over the last 20 years, except change the revision numbers prompting a new release each year.
I have to disagree on this, Tomot. I have actually used AutoCad daily for about 23 years now, and it has developed quite a lot. When I started with it, it had no menus! You had to rig up a tablet to be able to use it. The illusion of no change comes from ACAD being so backward compatible that about everything ever tried or added is still included. That they have been able to keep up and even increase the usability of the program with all that overload is quite a feat - things that nobody ever uses have been starting to drop out but just lately. And things that you used to need third party apps or programming skills to do have been incorporated into the main app. Autodesk is perhaps not the frendliest software developer in the world, and their pricing structure is somewhat surrealistic, but the product is very different today from the buggy DOS drawing program I started with.
Anssi
-
@anssi said:
I have to disagree on this
Great looks like we both go back, many years. (how time flies) I used to create my own menu system so I could actually use the program. I recall v2.5 came on 6 floppies. I finally quit using it around release 14. I always thought the AutoCad Users Group was there really only for Autodesk to test their buggy releases, while at the same time charging its customers for that privilege.
But the more important question is why are we still producing 2D drawings for construction in the 21st century? Some of my students ask me that question. My response is, because that's the way its always been done. Hopefully some day in their lifetime some CHANGE will occur.
Advertisement