SketchUp 2019 release
-
My version of 2019 does not autosave, does make backups
-
-
For anyone interested: I replied to their reply of the ridiculous reason for not sharing their roadmap:
-
To me, It doesn't look like the message is listened to by the su-team (looking at the posts on the official forum). Web dev and different stuff Will keep taking much of the resources while the desktop pro wont get the fixes It really needs asap.
Maybe were just a minority. Would be very interesting to see a poll on peoples reaction on 2019 and trust in future developments for their needs.
I'm done ranting. Eyes open for alternatives while using 2019 this year.Its sad many of the 'old' faces will move to different software. The ones that showed already in the early days Sketchup was a valid alternative to big cad. Gratefull for all your helpfull responses on the forums, posts on impressive modelling you did with early Sketchup versions, creators of impressive plugins and helpers to people with Ruby problems.
-
These are big, heartless corporations! There is no passion anymore, no craftsmanship! The suits are not identified with their products - they see reports, budgets, expenses, balances! Look around You - under the hood everything is the same - just different label and logo! Traditions are gone, people are just employees from 8 to 5 PM, most even don't know the final product! The founders are gone - and with them the soul of the creators!
-
Hmm.. What are conditions for AutoSave file creation?
I haven't seen v2019 creates one -
@rv1974 said:
Hmm.. What are conditions for AutoSave file creation?
I haven't seen v2019 creates oneI've seen the option to create backups and autosaves, you need to see if both boxes are ticked.
Generally autosaves will only happen if there was a change in the content of the file since the last save.
-
Example.. I forced (via task manager) a file crash. On reopening v2019 asked whether I'd like to open an autosaved version which didpreserved latest changes (similarly to PS). But untill now I haven't seen a single Autosave file in the project folder.
Maybe v19 creates them in Temp?
@Juju: bot options are V-ed -
SU2019 does not create a autosave-file anywhere.
-
@klip53 said:
SU2019 does not create a autosave-file anywhere.
I guess it helps with speed and stability, I always disable autosave anyway, got into a habit of saving before running any plugins.
-
Can’t help but suspect the overhaul of the UI & wanted features will come, but will only be introduced after the subscription model is in full effect.
Seeing where SketchUp Classic pricing is located on there web page, like Autodesk, I think the permanent license will eventually be phased out.
-
@solo said:
.. I always disable autosave anyway, got into a habit of saving before running any plugins.
The only problem with this is that due to 'richness' of native tool set, SU modeling is almost non-stop plugin usage
-
"SketchUp in 2019: where great ideas get to work"
( https://forums.sketchup.com/t/sketchup-in-2019-where-great-ideas-get-to-work )
-
I have a personal pro licens with maintenance that ends in April.
If I decide not to continue the maintenance what will it cost me if I do decide to upgrade in a year?
Also, will bug fixes be downloadable still? -
In the Netherlands my reseller has the following info on their website:
- continue the maintenance (while license is still valid): 110,-
- upgrade after license has expired less than 1 year: 165,-
- upgrade after license has expired less than 3 years: 220,-
It all depends of course how long they will keep the classic license.
I expect bug fixes will only be downloadable if you're maintenance is still valid.
-
Thanks, but isn't the latest install always available in the download page?
Is the license somehow crippled to not work with installs after maintainence expired? -
1 year +55€ / +$60 (= 165€ / $180)
2-3 years +110€ / +$120 (=220€ / $240)https://www.sketchup3d.de/bestellung/
https://help.sketchup.com/en/maintenance-and-support-policy#reinstatement-feesAs far as i know you can always install the latest point release (same serial). But maybe someone can clarify this.
-
@kaas said:
It all depends of course how long they will keep the classic license.
I would give it 2 years based on what I'm seeing compared to what happened with Autodesk. This seems to be playing out closer to that than Adobe. If you didn't go through the Adobe & Autodesk subscription transitions this is the basic playbook:
- Decide to push your customer base to a subscription model to increase and guarantee revenue.
- Bundle your "flagship" product with other low selling or low cost apps/ services to increase perceived value.
- Price your new subscription offering at half the perpetual license cost to offer easy entry but higher returning revenues past 3-4 years ownership vs. perpetual licensing.
- Convert software development to a rolling release model. No need for major updates unless there is a disruptive competitor in the market.
- Market your perpetual license customers to get them to switch over to subscription with "special one-time" offers to convert.
- Make owning perpetual licenses progressively more expensive/difficult and keep any substantial new features as subscription only. Do not reveal any future plans for perpetual licenses. Rely on FUD to move them over.
- After about two years or so cancel perpetual licenses to force the remaining hold-outs to subscription. Grandfather special subscription rates on on former perpetual licenses and then increase costs until there is no difference anymore.
Adobe is done.
Autodesk is on step 7.
Trimble is on step 4. Step 5 has already been mentioned over on the official form as a "customer loyalty" program. -
@derek edison said:
@kaas said:
It all depends of course how long they will keep the classic license.
I would give it 2 years based on what I'm seeing compared to what happened with Autodesk. This seems to be playing out closer to that than Adobe. If you didn't go through the Adobe & Autodesk subscription transitions this is the basic playbook:
- Decide to push your customer base to a subscription model to increase and guarantee revenue.
- Bundle your "flagship" product with other low selling or low cost apps/ services to increase perceived value.
- Price your new subscription offering at half the perpetual license cost to offer easy entry but higher returning revenues past 3-4 years ownership vs. perpetual licensing.
- Convert software development to a rolling release model. No need for major updates unless there is a disruptive competitor in the market.
- Market your perpetual license customers to get them to switch over to subscription with "special one-time" offers to convert.
- Make owning perpetual licenses progressively more expensive/difficult and keep any substantial new features as subscription only. Do not reveal any future plans for perpetual licenses. Rely on FUD to move them over.
- After about two years or so cancel perpetual licenses to force the remaining hold-outs to subscription. Grandfather special subscription rates on on former perpetual licenses and then increase costs until there is no difference anymore.
Adobe is done.
Autodesk is on step 7.
Trimble is on step 4. Step 5 has already been mentioned over on the official form as a "customer loyalty" program.Spot on! Couldn't say it better!
-
Question is, will current users migrate in sufficient numbers to deter the slippery path development model?
Advertisement