Forums Thread

Welcome, everyone, to another sprint. As we push forward in our project, the challenges we conquer as a team, absolutely amaze me.  With that being said, lets get started :).

Does anyone have any comments, questions, or concerns about the agenda they are assigned too?  If you need your agenda defined better or you're not sure where to start, please post on the kanban discussion any questions and we can start figuring it out as a team.

I must say its nice to see a sprint running with so many of us on it again guys. :)

Thanks,
James Fleming

This weekend is when I will have time to get to my agenda. It's good to be back.
-Matthew-

@Anthony When you get a moment can you look at this (NetComm) for me tell me your thoughts on it please?

Here is a sample of its use as I think we should implement our network structure.

Thanks,
James Fleming

@Team Our 3d department has suggested the following 3d Model for testing please review and let me know what you think before the end of the sprint otherwise this look like the one we will be purchasing.

www.turbosquid.com/3d-models/3d-robot/997544

Thanks,
James Fleming

@Matthew No worries thank you for keep me updated

Thanks,
James Fleming

@James. I think that framework is a good idea. Saves us from writing wrappers around sockets ourselves which should save some time.


  - Anthony Michelizzi

@Anthony I'm going to work up a flow chart for the structure of the network tonight.

Thanks,
James Fleming

That's a nice looking Mech!
-Robert

@Anthony Here is the chart and a brief outline of my thoughts.  If you check the Server.Interface and the Server.Administrator.  You will see a working simple sample code.

So each Server.* is a stand alone instance sharing the Server.Library for functionality.  This way we can run each of these on a dedicated server in the end.  The Server.Administrator will be a WinForm application for controlling these server remotely as a utility so direct access to the server is not needed.  The unity client will connect to each of these server as the application calls for.

You will notice that there is a Model, Logic, and Data folder.  Each of these folder will house their respect classes.  The Data folder will be for only Data items like direct access to SQL server.  Not the code for retrieving object but more of a data binding.  This goes for any other data item we choose to use like XML.  Once again its not to get class object but used to parse out the data in a standard format we can use.  I will fill the SQL Data class out tomorrow when I have time so you can see this in action.  Next we have the logic folder which will hold the transforming of the data object pulled back like SQL table into a usable object (Model).  Then last we have the Model folder which will house extremely generic object for the data to be stored in.  Finally we have the Service folder these will house all the connection and sorting of server networking calls.  Probably a somewhat large switch statement that the Main Program class executers.

Do you see any issue with this Networking structure?

Thanks,
James Fleming

From the looks of it, looks like you're leaving all the pregame stuff in unity itself?


  - Anthony Michelizzi

@Anthony Oh yes let me review that real fast from our forum conversation to get that worked in too now.

Thanks,
James Fleming

@Anthony To mock this up I'm thinking of three application an "Updater", "Interface", and "Game" set up.  The updater will only be for checking the game and interface if they need to be updated.  Then the interface will be everything we need outside of the game and finally we have the game as a stand alone application.  I think you are right and that breaking these down into smaller application will make these easier to manage.  So I'll work this into the flow chart now.

This is just the client side all application will be a unity project so we can execute it on multiple platforms.

Thanks,
James Fleming

Thanks,
James Fleming