So many great Unity assets, so little time. 🙂
For my next personal challenge, I want to create a procedural dungeon, reskin it, insert a player character that can perform a melee attack, insert one (or more) baddies that also attack, implement a basic inventory system, allow the user to save progress, and have a ‘win game’ condition (even if it is simply just reaching the end of the dungeon).
Here are the assets I will likely be working with:
Eliot AI Framework
Invector Shooter Template
I have completed another small project for a larger game project I am contributing to. This project is a 3D character editor for a sports game. The screen shots below show the progression from the original draft to the final version.
This was a fantastic introduction to the visual scripting system Playmaker as well as a good project for drilling deeper into Unity’s UI canvas.
Here is the first draft of the editor scene:
And here are screen grabs from the completed scene:
You can also try out a low-resolution WebGL build by clicking here.
One of the first things I noticed when importing Adobe Fuse models into Unity was that all of my characters seemed to have super-bright nostrils. Notice the brightness of the nostrils in my “Jill” model above.
A relatively easy way to repair this is to open up the character’s prefab and locate the body diffuse map (in my project, it was Jill_Body_Diffuse.png). It took me a while to figure out where the nostrils were, but they are above the “head” in the texture map, as indicated in the image below (note the red arrow).
For a quick and dirty fix, open the image in your preferred image editor and darken the nostril areas. The key is to do this iteratively with a soft brush and low opacity. I just did one quick pass, and already the results are better.
Feel free to play around with my Jill model:
[Jill Unity Package]
Fun article about college basketball rankings, Blue Ribbon, and ESPN from my days working on EA Sports’ NCAA College Basketball. Blue Ribbon is still considered to be the “bible” of college basketball forecasting.
ESPN, Blue Ribbon and Team Ratings
It’s been a minute since I’ve used source control tools on mid-to-large sized software projects. Back in the day, we used Perforce and I recently revisited Perforce (which has a nice, free package for small teams). Plus I believe Unity has built-in support for Perforce integration. But I simply could not get it up and running.
Next up I considered using Github, which I have used more recently for a number of (small) Angular projects. The Github workflow took some getting used to, but I did finally get the hang of it. However, I closed my paid account last year (the paid account allows, among other things, private collaboration).
Until I take the plunge for a full, paid Unity license(s), I’m looking for a source control solution that is inexpensive (or free) that isn’t too complicated to get set up and running. Thankfully, I found this tutorial on the Unity website:
Creating Your First Source Control Repository
The gist of this setup is that you use these three tools:
- Bitbucket: A free repository for small projects
- Git: A popular source control system, integrated with Bitbucket
- SourceTree: A user-friendly GUI that works with Git and Bitbucket
I was able to get a sample Unity project up, running, and synced in just under ten minutes. I’m able to commit changes and push to the repo. Still trying to figure out how to rollback to a previous commit, but for now, this looks like a nice, clean solution for collaborative source control.
* Update 4/21/19: After much trail and error, I decided to go back to GitHub and GitHub Desktop. I couldn’t get Bitbucket and SourceTree to work across multiple devices (though the was likely due to how I had things set up on my Mac and Windows boxes). Additionally GitHub now offer collaboration on privates repositories on its free plan.