2. I still do local backups for upgrading so I don't have to clone a repo or reimport from scratch. This isn't as much of a concern for newer/smaller projects, though.
You absolutely should not clone a repo or reimport! Simply create a branch, switch to it and upgrade versions there; you can then switch back and forth as needed, whenever you want to work on the main branch, or back on upgrading the project to the next version. Then when / if you decide to upgrade, just merge the branch to your main branch. Or if you decide you don't want, delete the branch. Clean and easy.
Hey you with good workflows, stop it there! You shall not guilt trip me for my external drives of backups!
In all seriousness, I really got to get up to date with git usage. I learned some nasty habits from older people and still haven't gotten up to date on git stuff.
My wife looked into this and found that it's actually free to enroll but then you have to pay $49/month.Don't settle for any less than an amazing, full University of Michigan course... that just happens to be free:
https://www.resetera.com/threads/in...ome-help-learn-show-and-tell.463/post-5908836
I learned some nasty habits from older people and still haven't gotten up to date on git stuff.
git log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n'' %C(white)%s%C(reset) %C(dim white)- %an%C(reset)' --all
git fetch --prune && git branch -vv | awk '$1 !~ /*/ {print $1 " " $4}' | awk '$2 ~ /gone]/ {print $1}' | xargs git branch -D
My wife looked into this and found that it's actually free to enroll but then you have to pay $49/month.
You absolutely should not clone a repo, or copy / reimport! Simply create a branch, switch to it, and upgrade versions there; you can then switch back and forth as needed, whenever you want to work on the main branch, or back on upgrading the project to the next version. Then when / if you decide to upgrade, just merge the branch to your main branch. Or if you decide you don't want, delete the branch.
I've had nightmarish version upgrades that broke several things and took me several days to get back running. No way I'm going to work for that long on anything without version control. :P
How does this work? Do you not ignore you library folder?
If I upgrade from 2019.2 to 2019.3, things reimport and get changed in the library. And if I tried to change branch those changes wouldn't revert.
You can simply delete the library and obj folders whenever you change versions; Unity will recreate them (obviously do this with Unity closed, but since you have to close one Unity version and open the other, you can do that in between).
If you find yourself changing from main to the branch so often that it's much of a hassle, you can of course copy the project folder / clone the project, but always with an actual branch backing the changes in the "upgraded" version. You never know how long it will take you to find and fix all the broken stuff when changing versions, and you don't want to have a nagging pressure in the back of your mind to commit these changes to the main branch because they're not comitted anywhere else.
Ah yea that's a good point. I should clarify that for longer running upgrades I'll definitely branch. But I also do just make a local copy sometimes to see if the upgrade might not be too painful.
You just need a list of these git commands, and you're set for life:
- git status
- git config --global alias.[my custom alias] [whatever stuff you need here]
Bash:git log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n'' %C(white)%s%C(reset) %C(dim white)- %an%C(reset)' --all
Bash:git fetch --prune && git branch -vv | awk '$1 !~ /*/ {print $1 " " $4}' | awk '$2 ~ /gone]/ {print $1}' | xargs git branch -D
- git checkout
- git checkout --branch [my new branch]
- git branch
- git branch --delete [my branch to delete]
- git pull
- git push
- git push --force-with-lease
- git rebase --interactive HEAD~[number of how many commits to go back from HEAD]
Ok thanks! I'll let her know so she can look into it.You should be able to audit each individual course for free, from their individual pages. The option to audit is a bit hidden, you may need to scroll down on the Enroll popup.
When auditing you get access to all of the materials; you just don't get exams, nor get a certificate at the end.
IIRC you can turn it on through a command line argument:Unity needs to implement support for exclusive fullscreen so GSync can work.
Have yet to play a Unity game that supports this.
A common solution is to default to one mode and then allow the user to override it if they want/need. Users can specify the fullscreen window mode by using the standalone player command line argument -window-mode with either exclusive or borderless values when launching the game, e.g., -window-mode exclusive. This could be set up by users in Steam, or alternatively a custom launcher could be created to allow users to select this setting before launching the game with the custom launch options.