Sketchup crashes when saving
-
hmm... might be worth running a check on your HD?
-
really?
-
@edu1987:
Do you happen to use CCleaner? (Piriform.com)
An interesting feature of its User Interface is that it lists the name and model of your graphics card on the frame(? not sure of the terminology) of the interface window.
This software may assist you in other areas, but proceed cautiously.Otherwise, use start all programs accessories system information.
-
I've been getting this as well since upgrading? to win 7 from xp.
I get a bugsplat on exiting su every 4 or 5 exits, but the file saves ok. An annoyance but no harm done, but sketchup seems buggier all round on win 7.
baz -
I dont use cc cleaner i use tuneup utilities and it has the same feature, now i know my video card
its a Mobile Intel(R) 965 Express Chipset Family....and by the way thomthom i did a disk scan using this same tuneup utilities and didnt show any problems, maybe i can use another program?
-
@edu1987 said:
...it appears to happen only when i model from scratch, i tried saving a model that wasn´ t mine and everything ok i even tried savig a model i did a few months ago with this same SU and OS and laptop and it saved normally.
So only with new models? Not with old ones that you open?
@edu1987 said:
my video card
its a Mobile Intel(R) 965 Express Chipset Family.Well, that's not an ideal card (most probably does not support OpenGL at the level SU would need) but disabling HW acceleration should "fix" any issues with crashes.
-
@baz said:
An annoyance but no harm done, but sketchup seems buggier all round on win 7.
baz"Buggier" - in what sense? Sounds like a system issue. Probably a graphic driver issue.
-
Baz, by upgrade, do you mean going from WinXP to Win7 on the same PC? If so, perhaps that has resulted in your problem?
-
Yes Gaieus it only happens with new models, when i open an old one (even one made in this same laptop with the same SU) it saves fine i even do some new modeling in the file and still saves fine.
@unknownuser said:
Well, that's not an ideal card (most probably does not support OpenGL at the level SU would need) but disabling HW acceleration should "fix" any issues with crashes.
Yes may not be the best for SU but this have never happened before i dont even remember SU giving me that much of bugsplats or any other mayor problems it used to work fine, and i have dissabled the hardware acceleration, in fact ive always worked like that in SU and still this is new; is there any type of video card configuration i can try or something i can tweak? maybe a win7 update messed that up...
-
Have you updated your graphic card drivers?
-
@thomthom said:
@baz said:
An annoyance but no harm done, but sketchup seems buggier all round on win 7.
baz"Buggier" - in what sense? Sounds like a system issue. Probably a graphic driver issue.
Its a bit hard to pin down 'buggier'.
I definitely get more bugspats, usually when asking a ruby to something intensive. Somtimes it takes forever to explode a group or Comp, which I had never noticed before. The whole app just seems a bit clunkier. Also something weird is going on with components: when I do a 'save as' the comp does not appear in 'explorer', even after a refresh, tho it does in the comp dialogue in Su, but without the name i gave it, just the generic name (Group#2). Hang on, I just tested that again and it now works! Although when I closed the file I got the bugsplat again.
Re the move to win 7, I did a clean install and updated all the drivers inc the latest nvidea one.
I havent had any problems with my other apps, tho apart from Photoshop they are all pretty lightweight.
I dont have any games so I cant test the graphics card against them.
baz -
Raz, if you installed Win7 from a newly formatted drive, it sounds like a bad match between Win7 and SU, but others haven't mentioned it, have they? Could your selection of rubys be a problem? How about opening and closing a problem model after temporarily moving them to a temp folder?
-
@honoluludesktop said:
Raz, if you installed Win7 from a newly formatted drive, it sounds like a bad match between Win7 and SU, but others haven't mentioned it, have they? Could your selection of rubys be a problem? How about opening and closing a problem model after temporarily moving them to a temp folder?
thanks, it does'nt seem to be any particiular model, but I'll give that a go.
-
@honoluludesktop said:
Raz, if you installed Win7 from a newly formatted drive, it sounds like a bad match between Win7 and SU, but others haven't mentioned it, have they?
No - I have used Win7 since the first public beta. And we have Win7 on all the machines at the office. So it has to be some system specific issue.
-
@thomthom said:
@honoluludesktop said:
Raz, if you installed Win7 from a newly formatted drive, it sounds like a bad match between Win7 and SU, but others haven't mentioned it, have they?
No - I have used Win7 since the first public beta. And we have Win7 on all the machines at the office. So it has to be some system specific issue.
Well that good news and bad, I guess:(
baz -
Good news in the sense that it could/should be fixable. Had it been a Win7 issue you'd be out of luck.
-
@edu1987 said:
Yes Gaieus it only happens with new models, when i open an old one (even one made in this same laptop with the same SU) it saves fine i even do some new modeling in the file and still saves fine...
Hm. This is really interesting. I do not have Win 7 but I can imagine that for some reason, it does not allow SU to create a new file (i.e. there is some writing permission problem).
Well, I hope someone from the SU Team can chime in and it can get solved somehow.
What happens if you open an old file and want to "save as" or "Save a copy as..."?
(This could be a workaround; you could always start new models from existing ones).
I remember an old Vista bug when it did not allow to start a new file either but allowed to start SU from an existing one. It does not happen nowadays but when Vista was a new thing. I cannot remember the details either.
-
problem solved!!! i did a restore system to a few weeks ago and that did it! i think a crash bandicoot ps1 game was the one that messed up everyting...so now it works fine thks for all ur help guys!
-
Haha... Congrats (although it seems it wasn't our help...)
-
@gaieus said:
Haha... Congrats (although it seems it wasn't our help...)
Well kinda cause that way i knew what wasn´t causing the problem
Advertisement