Asset Managment System questions to the group.

Asset Managment System questions to the group.

UnKnown

12/28/2013 11:16:00 AM

So, I was hoping to address this at the meeting this weekend, but I forgot that it was canceled.

Been doing a little research for our system. Going off the impression that we are looking at a runtime management setup, I am trying to design with speed in mind. I am looking at using a Dictionary Storage (basically a hash table on steroids) and am looking at possibly doing some caching to increase speed. However, the problem I am having right now is I do not understand our current pipeline nor goal asset storage paradigm.

Anyone asset on giving me a quick explanation of the pipeline? I plan on reading up on common pipelines, but if we have anyone who can give me our cliff note version.

Also, are we going to continue using raw assets or do we have a schema in place for release version structures. Articles I was reading recommended putting like assets into one file like the old doom WAD or other similiar file structure. How are we planning on hiding assets not to be randomly modified or deleted by the end user.

I checked the design doc and right now the PC is the target platform with potential for porting to other assest. Are we keeping majority of assets server based or are we putting some on the client systems?

Reason I am asking is because these anwers will have lasting consequences and influences on the design of the asset management system.

Thanks,

Jeremy Moore.

Post Replay

All Replayies

mine read this link below for information on the pipeline. XNA/MonoGames converts all there asset to its own format no matter what format it was orginally in.

http://msdn.microsoft.com/en-us/library/bb447745.aspx

Most of the assets will be client side. However the status for these item will have some sort of check system client and server side to stop people from modifiying them.

By : 12/30/2013 9:33:00 AM

Forum Statistics

Posts

8,45.34

Replay

8,45.34

Users

8,45.34

Forums Thread