« Return to Thread: Saving and Loading Spaces

Re: Saving and Loading Spaces

by Mark P. McCahill-2 :: Rate this Message:

Reply to Author | View in Thread

Excellent point - there has been a tendency to concentrate on saving  
at the island level rather than collections of island (continents?).  
A continent file format that names (or contains) the collection of  
island to be fetched is the way to go.

It would be good to also include something about which codebase is  
needed to execute the islands in the file formats.

I'm now running over to the cobalt bugtracker to add a couple more  
issues ;-)

Cheers!

- Mark


On Mar 20, 2008, at 9:22 AM, Nikolay Suslov wrote:

> Hello,
>
> Just want to share some thoughts about saving and loading spaces  
> functionality in the current SDK.
>
> As the current *.c3d file implementation works around saving one  
> active (user's avatar being in) island(world) per c3d file,
> assuming, that it is needed to support and the possibility of  
> saving all other current registered islands also (at the same time).
> So, when somebody saves an active island(world) containing a portal  
> to another already loaded island(world) from file,
> then it is impossible to restore the working portals(between  
> islands) just loading the saved one. It is required to load all  
> participating islands(worlds) by hand.
> So, if taking into consideration the concept of *.c3d as island/
> world's atomic file format, then may be to develop the support of  
> an additional file format,
> like archive solution, which could store all required islands (c3d  
> files) in one definite file?
> And after loading which, all islands will be restored automatically  
> with working portals.
>
> Regards,
> Nikolay

 « Return to Thread: Saving and Loading Spaces