Unite 2016 was full of interesting presentations for upcoming features. One of the things that was especially exciting to me was the Roadmap presentation part where Lucas Meijer talked about the efforts related to C#, GC and the upcoming ScriptBehaviours.
To me, engineering is for the most part about getting the desired result with the tools that we have available. It is not about theory, not about being exceptionally clever, it is about creating a system with the available resources and constraints that are present. It is also not about cobbling it up together, it is about advancing your craftsmanship and improving your skills and work ethic with regards to the big picture.
We already know values held in our prefabs are serialized values of fields saved on disk. Unity saves data about the field - its name, type, value. This can create some issues with renaming fields.
I show a simple distinction about Unity serialization that could save you a lot of debugging and prefab-modifying time. If you thought changing code in your scripts is safe for your data, you might be mistaken.
MeshCombine wizard and Source Code available here
There are quite a few well known techniques in the modern world of AI for games. There are decision tress, finite state machines, hierarchical finite state machines, behavior trees, 2nd generation and event-driven behavior trees, goal oriented behaviors, goal oriented action planning, hierarchical task networks to name the most prominent ones in order of complexity. The decision which one to use comes down to weighting complexity vs. benefit, and the availability of libraries for some developers. I have been researching the topic recently and have decided to make my own AI model for fun and practice. It is not meant to be the best, most perfect thing ever, it is one solution to the problem. The major benefit is simplicity and speed in all aspects. What is it and how to do it? Read on!
Since Unity Technologies is now closely collaborating with Microsoft, it's relatively easy to set up Visual Studio Code editor to work with Unity Engine. You do get Intellisense and advanced debugging capabilities, but you don't get syntax coloration properly like in full Visual Studio. The highlighter in VS Code is not context aware, it does not have semantic highlighting. The highlighting is based on regular expressions, upon which a chosen textMate theme is applied. This means your own types, Unity types, all fields and method calls will simply be white. It also seems roslyn (OSS compiler) already has the required API capability to implement this and it is a matter of time when Code will get it. Well, it's been about a year and we still didn't get it... Even the
prettyprint on my site that you can see below has better syntax recognition!
Revolutionary version of Dialogical that brought the techniques for working with parameters.
How do you use a runtime class like WWW on the editor side without creating a blocking operation?
Code reviews and performance profiling is something you do every weekly right? Well, you should, because when the project grows unmonitored the changes will accumulate and cause an avalanche of refactoring later.