Sketchup for Mac
-
It is normal to constantly see a spinning wheel when using Sketchup an a Mac and spend considerable time waiting?
Also when deleting with the eraser you only get one crack and if the item to be deleted is not so, you must click elsewhere and then re attempt to delete?
-
Hi marx1947
I consistently work on large models, and through proper layer management, and merging files, I am able to keep that nasty wheel of death from spinning too often.
If you are working with shadows turned on, that too will cause you problems.
My questions would be:
What mac are you on?
What are the size of the models your are working on?
Do you have your open GL settings set with hardware acceleration on?
Have you made sure your drivers are updated?
Are you using a great deal of vegetation?
One of my rigs is an old G4 laptop, which requires even more management, but it is do-able.
Cheers -
What mac are you on?
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHzWhat are the size of the models your are working on? - Lately about 7MB but that does not seem to matter is is mainly when I try to orbit.
Do you have your open GL settings set with hardware acceleration on? Yep
Have you made sure your drivers are updated? Yes
Are you using a great deal of vegetation? No I would expect with a lot of warehouse downloads and vegetation that I would have the problem hence my question. I work on the same model at work on a PC and never have the problem.
And the eraser as I said you get one crack at it if you just slightly miss then you have to click elsewhere in order for it to work on the first [missed] target again.
I was considering buying Pro but would not with this sort of performance, I don't think Google are fair dinkum about Mac. -
Hmm im running
2.4GHZ Intel Core 2 duo
4GB DDR2
i do get the color wheel a lot but thats when im working on large models of 20MB+
the only thing i find constantly gives me color wheel is whe i put shadows on then it really takes the piss. Its impossible to orbit around anything about 10MB without having to wait for about 10 seconds, then once in a while SU will just quit. -
It is like it is two different developers or the under done work on Macs.
I do not have any of these on the PC at work the only problem I have is using a PC.
It seems especially worse when one of the Google tops was on the Apple board. -
I think its also a mac thing and the way it uses the hardware, I have bootcamp so run xp on my MAC also.
Running programs on the windows partition is much faster for example if I play call of duty on my mac i have to run it at lowest graphics but if im playing it on windows on the same computers I can ramp up all the settings! Same goes for my 3d software, running max and mudbox on the windows side are amazing but try anything on the mac and it just slows down as the poly count gets larger!
its a pain really think I just need to upgrade from a laptop really! Maybe I should spend my money on a nice new tower rather than flying to basecamp in america lol! -
I find this strange. I did a model for a client not to long ago that was just under 47mb with really a lot of vegetation, a couple of vehicles, etc. That model rotates easily with all layers on as long as shadows are off.
I'd love to hear from others on this.
I have had some weird crashes recently, which I have been forwarding the info requested in this thread http://forums.sketchucation.com/viewtopic.php?p=254903#p254903 But other than that no major slowdowns.
It's hard for me to compare the PC, because the one I use is starting to show its age. -
Dale,
Although I am not attempting files that large, it is usually shadows that slows down orbiting. For example on a 5MB file, I can usually orbit fine, but the shadows do not appear until 5 sec. after I stop orbiting. I say "often" because sometimes there will be a short hesitation to operations, or some elements go to wireframe for a few seconds.
MBP 2.4 GHz Intel Core 2 Duo GB Ram, GeForce 8600M GT 256 MB VRAM
Isn't there a test file that we should use to compare, trying certain operations in a particular view? (Do other operations have different slowdown from orbiting?) Is the size of the file alone a measure of the burden(s) a file imposes on the system?
Peter
-
Peter
A test scene would be interesting, but would probably have to be developed with a specific test in mind, or contain layers that could be turned on progressively as the test goes on.
In my experience, shadows, poly count and scale are the things that can cause difficulty.
I always have the shadows off or at least have created a scene where they are on that I can reference to.
Poly count, that's hard especially when something like trees and other vegetation of any quality are part of the model, I guess just good layer management.
By scale I mean, if the area being modeled is large problems can occur, but usually that is more clipping than slowdown.
Anything that I can learn that serves a better work flow I am interested in.
Advertisement