[=;281691]
We expect users to use version control for their projects, even when working alone. Perforce, Git, SVN are all extremely useful and we highly recommend using any of them to avoid losing work.
[/]
Do you provide training or any monetary costs associated with such things? Because if you don’t, you can’t ‘expect’ anyone to use them.
[=arbopa;281705]
Do you provide training or any monetary costs associated with such things? Because if you don’t, you can’t ‘expect’ anyone to use them.
[/]
We do not provide training for using those services, but the service providers have many training tutorials on how to use them. For example. Some of these services are offered for free as well.
[=arbopa;281705]
Do you provide training or any monetary costs associated with such things? Because if you don’t, you can’t ‘expect’ anyone to use them.
[/]
Yes, they do.
Source Control Basics
Source Control Overview
Perforce Tutorial
SVN Tutorial
Git Tutorial
I’m sorry, but are we seriously talking about monetary costs for free software or what?
[=;281717]
Yes, they do.
Source Control Basics
Source Control Overview
Perforce Tutorial
SVN Tutorial
Git Tutorial
I’m sorry, but are we seriously talking about monetary costs for free software or what?
[/]
Glad to see they offer guidance. Who knows what is free or not? I do not see a package name and instantly know if it is free or monthly fee or buy outright. But my point was the ‘expect’ part of the comment. Seems it was an attempt to remove any responsibility from Epic for the times when UE4 doesn’t work as users ‘expect’ it to.
[=arbopa;281735]
Glad to see they offer guidance. Who knows what is free or not? I do not see a package name and instantly know if it is free or monthly fee or buy outright. But my point was the ‘expect’ part of the comment. Seems it was an attempt to remove any responsibility from Epic for the times when UE4 doesn’t work as users ‘expect’ it to.
[/]
If there is a bug in the software that causes corruption to an asset, we certainly want to know so we can get the bug reported and fixed, hence why we encourage developers to post to the answerhub. However, source control is understood to be the best method of backing up software so that, should something such as data corruption or irreversible changes occur to a particular copy of an asset, one can revert to a previous, undamaged version without losing a lot of work. There are backups of assets kept within the project \saved\backup\ folder, but it is typically expected that source control is the go to option for most developers. We can locate and work on errors that occur in the editor, we cannot ensure that developers have software set up to maintain backup versions of their projects and assets.