Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Unity for Architectural Visualization

You're reading from  Unity for Architectural Visualization

Product type Book
Published in Sep 2013
Publisher Packt
ISBN-13 9781783559060
Pages 144 pages
Edition 1st Edition
Languages
Author (1):
Stefan Boeykens Stefan Boeykens
Profile icon Stefan Boeykens

Assets and the Unity workflow


Unity was developed in the context of game development and provides an efficient integration into existing pipelines, independent of the used modeling and content creation software. Regardless if the team consists of you alone or you are part of a large group of designers, developers, artists, and technical directors, you need to get your workflow up and running to be efficient. This is equally relevant for architectural offices, which are also organized around long-running projects where different people interact and collaborate, using a variety of software applications for drafting, modeling, and presentations.

Inside Unity, you create a project, which is stored inside a single folder on your hard disc. Within the project folder, there are a wide variety of folders and files, which are mostly regulated in the background by Unity. The Assets folder is where all your files are stored that you need to manage directly, such as models, scripts, textures, and scene files. There is a direct relation between what you see inside the Unity project panel and what occurs as files in your local file system.

Unity also supports additional modules that facilitate the technical aspects of collaboration, for example, by setting the project up with the Asset Server system or by tuning the project metadata (the information about each file) into separate meta-files, that are better suited for version control systems (VCS), such as Subversion or Git. While such systems are common with software development, they are not widely used in architectural projects. They present an opportunity to share projects between different users, computers, and systems. Using a version control system with Unity, team members can check out files in the project and receive changes from other members. This is more efficient than copying the whole large project folder back and forth since only changes need to be synced. Only the Assets and ProjectSettings folders need to be synced; other folders are generated locally. More information on using external version control systems with Unity can be found at http://docs.unity3d.com/Documentation/Manual/ExternalVersionControlSystemSupport.html, the official Unity documentation website.

You have been reading a chapter from
Unity for Architectural Visualization
Published in: Sep 2013 Publisher: Packt ISBN-13: 9781783559060
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}