Meeting Notes Progress Review for Unity

Meeting Notes Progress Review for Unity

UnKnown

6/12/2016 7:20:01 PM

After reviewing the project I notice that Unity or us I'm not sure which as all the files in the "Asset" folder. The automation system had this folder locked down just for our team assets. So that leads to some question of our structure we need to review based on this.

Is the asset folder the default location for Unity?
Does Unity convert asset into *.asset file like Paradox did?
If so should we figure another folder out just for the automation system to use for asset that are inserted onto the website?
I also notice the namespacing has been removed is this default why Unity does this can we have namespaces to keep thing organized?
I like the idea of us using the sandbox area to develop with but when we are done with that area like "Terrain" do we have a plan on how to structure it into the "Non-Sandbox" area of the project?

We just need to get a structure together like we had with paradox game engine that is structurally sound and allows our automation system to work right.
Attendance
463.95

SSgt Anthony Michelizzi Lead Game Programmer
16036.56

1stLt James Fleming Lead Game Producer

Post Replay

All Replayies

Assets is the default location for unitys assets. I typically see anyone who develops with unity organize with folders in the assets. I also do this. I separate everything into individualized folders.
Unity compiles everything on runtime. it's all stored as temp files and deleted, they are only compiled into asset files when the build is actually compiled.
Is there a way to have the automation system check specific folders only? Or even have it avoid folders like say sandbox and scripts? Otherwise yes, we could easily make a folder for the automation system to insert the assets from the website and monitor them.
I honestly having tried namespacing in unity. I would think we could do it, but I can't say it will add to the over all structure and neatness of the project.
i do have a plan, I just haven't moved anything because of the automation system. Unity still recognizes and compiles like normal so I would just move the files for the terrain into the appropriate areas. Like say script/terrain and texture/terrain. Then store the terrain in its own terrain folder under assets.

By : 6/12/2016 9:49:14 PM

Ok for now I am going to leave the automation system off until I see how the project is going to be laid out then I can exclude folders from it.

Thanks,
James Fleming

By : 6/12/2016 10:55:56 PM

So after reviewing the automation system I think a simple solution would be to put another folder in the project and just call it "Asset" which will hold all the website files created under their file folder such as "Texture", "Audio" etc... Instead of excluding any folder?

What do you think? So the "Asset" folder will be a mirror of all IsGameable files like it was with paradox? Will Unity pick this up with out any problems?

Thanks,
James Fleming

By : 6/13/2016 12:00:23 AM

Yes this will be no problem for unity. Maybe we can use a different naming convention though to avoid confusion? Maybe even isGameable? So then any future collaborators know those are the isGameables from the site? It does have to be located in the Assets folder too as a note

By : 6/13/2016 12:10:01 AM

Excellent idea I'll see about getting that setup tomorrow.

Thanks,
James Fleming

By : 6/13/2016 12:13:36 AM

@Anthony I have the automation system changes done. I've rolled this out now can you check the project to verify.

Also I notice we've more then one solution file in the project can you remove whatever one is outdated that is not being used please.

Thanks,
James Fleming

By : 6/13/2016 3:39:04 PM

Forum Statistics

Posts

8,45.34

Replay

8,45.34

Users

8,45.34

Forums Thread