SU pro 8 - Can't import DWG
-
Expired means your Pro licence is no longer valid. So something is missing from somewhere?
Did you post this on the GSU forums?
-
No I only use this forum. Perhaps I can download SU 8 again and start from scratch but I'm hesitant to as it is an upgrade so could these cause problems?
-
Sketchup version 8 only has DWG import/export when it's 'Pro', which is for the '8 hours evaluation use' before it reverts to 'Free', OR when it's properly licensed as a proper 'Pro' version.
So if you have a 'Free' version 8, then DWG import/export won't work after a while.
If you had a 'Pro' v7 license you need to upgrade it to a 'Pro' v8 license - it will now cost you a few $$$...
-
http://sketchup.google.com/support/bin/topic.py?hl=en&topic=13709
Have you actually paid for your upgrade or just decided to download v8 Pro?
As TIG says you'll need to pay Google some cash to upgrade your v7 licence.
If you have paid then I'd suggest contacting them directly as they've the keys to the kingdom. We're only mere peasants
-
Yes we paid real money!! Thanks for your advice!
-
Hi, Think I have solved this if it's of interest. I removed both SU 7 Pro and SU 8 Pro using a app called appcleaner, I then reinstalled SU 8 Pro typed in the license info and all seems good.
-
Why did you remove both of them? Did you try just re-entering the license info for SU8 Pro?
-
Versions 7 and 8 can co-exist independently - there is no overlap...
-
@TIG: Wouldn't the v7 revert to free version, while the v8 would be pro? Edit: I mean in this particular upgrade case.
-
No... if you have a license code for each version, then each will work separately... The license string for each will be different and valid...
There is no interaction between them or their licensing codes...
-
TIG is correct...otherwise beta testers would have real problems. Most beta testers continue to run a licensed Pro current version while also running a separately licensed Pro beta version of the next release on the same machine. There is no interaction.
It sounds like in this instance there may have been some hiccup in the installation procedure. I've experienced similar...usually by forgetting to run the install as an administrator, or something like that.
Advertisement