Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Honestly it may be best to just get the website version and add to it Steam as a "non-Steam" game in your library.
It is? Which version is on Steam?
OP is interested in the automatic update, how does that help him?
You have to be careful when updates come through as well, you're only given 1 chance to pass your current configuration through to the new update and that is found on the splash screen on the first start up of the new version. If you miss it, the update configures itself to a factory fresh install.
The steam version installs on your computer (in your steam library) and communicates with the Steam server to track your time using the product (displayed on your profile page). it also communicates to see if there is an update to download.
One of the major downfalls of the Steam version is that it will only install one version of Blender. If you need to roll back to another version, you have to switch version using the Blender Properties settings Betas tab to roll back. Once you select the version you need (back to 2.77 only) it will uninstall the version you have on your computer and reinstall the selected version.
Downloading from Blender directly, you can download either the install or portable versions, you can also augment the blender version by downloading nightly builds (which include bug fixes, updates to existing routines, etc.) If you download the portable versions you can have as many version on your computer as you want, they all work from their own individual folders.
As far as functionality goes, they are the same version to version...
With Python changes, it causes plugins/addons to break because the functions names within python have been changed. If a plugin/addon author doesn't rewrite their addon to meet the new change requirements, SNAP! It breaks.
This is why I have portable Blender versions dating back to Blender 2.49 sitting in ZIP files on my archive drive. If an update breaks an addon that I'm used in a project I'm working on, I can grab the portable version and carry on working and watch for the author to update the addon for the new version.
It's not a big deal, as you stated the portables are light and easy to find if required.
That when I found the idea of using blender on steam interesting (faster instalation + periodical updates)
Thank you all xD I think I'm going to give it a try and I'll see, honestly I think it's interesting to give it a shot
The problem with doing the above is that if Blender pooches after you copy over it and/or have to do a application cache validation, your replacement is going to be replaced with validated files from the steam server. Also, when the steam client looks for an update, you may screw up that operation... (Don't know, haven't tried, nor do I think I will....)
Sites like graphicall have nightly builds that have additional in development features which havent yet been added to trunk. So if you are looking for that steam version doesnt help there.
In order to go backward, you have to select the version want from the Betas tab (opt into field) of the property panel. Doing so completely uninstalls the currently installed version and replaces it with the opted for version. This is going to be a real pain when 2.80 finally rolls out the door, because 2.80 is breaking a lot of plugins that work in 2.79 and some of these useful plugins have either abandoned by their creators and won't be updated or creators are waiting for release candidates before upgrade their addons because the current state of the 2.80 alpha changes with each nightly build. (Why code a plug in for something that is going to break it in a day or 2??)
I personally use Steam for every day modelling, but I also have the portable zips for other major version releases sitting in the wings for when I run into addon compatibility issues.