The Fuzor Collaboration Server is software separate from Fuzor that you run on a central server (hardware not provided by Kalloc) which all of your other machines runing Fuzor would have access to.
The Fuzor Collaboration Server provides a central storage and access to Fuzor project data. You create users and projects on the server, and assign permissions to the users for project access. All interaction with the server is done through the regular Fuzor application.
These are the primary features provided by the server:
Every user with access to a project can download the most recent version of the model for that project. If they already have the model downloaded, then the changes made to the model since their last download will be applied to their current model. If any changes conflict, then the user is presented with the ability to merge the changes. Users can then upload any changes they have made to the model, making those changes available to other users.
The purpose of this feature is to allow multiple people to work and collaborate on the same Fuzor project. Multiple people can simultaneously make changes to the same model, and then grab changes from their peers as they come in, and then upload their own changes when they are ready. The centralized server assures that there is always one "master" version of this model, and that changes to the model are made in an orderly fashion without losing work.
Objects in a project can be annotated using the Fuzor annotation system, and these annotations are immediately uploaded to the server, and all others working on the model will immediately see the new annotation. Edits to annotations are also propagated to everyone. Annotations are persistent and centrally stored on the server, so there is no need to create or pass around .ano files.
There is a persistent chat for each project which allows for real-time communication about a project. The full chat history can be browsed by anyone in the project and is never lost.
Issues can be created, assigned, re-assigned, commented on, and more. The Issue Tracking system is highly flexible and configurable to your project needs, and allows for all issues to be tracked in a central location to ensure that nothing is lost or dropped. Issues are linked to the model similarly to annotations to give context to the issue for faster resolution.
Anyone running Fuzor Ultimate can host a Peer-to-Peer Collaboration session, which can then be joined by other Fuzor users (of any SKU). No centralized server is required.
Everyone who joins will download an exact copy of the model currently being run by the host. Any changes made to the model by the host will also propagate to all the clients. Everyone can also chat in real-time as well as create annotations which are seen by everyone. The host can save a summary of chat and annotations as a record of the session. The host can freely switch between "Tour Guide" and "Free Roam" modes, which determines how restricted the client movement is around the model. The host and/or clients can also enter VR mode, where they can view the model in the Oculus Rift.
The purpose of Peer-to-Peer Collaboration is to act as an enhancement tool for meetings, brainstorming sessions, client presentations, or other similar situations where several people want to get together and simultaneously view the same model.
When purchasing Fuzor, you can choose between a Standalone or Network license. The Network license has an extra cost to it, but is more flexible.
Standalone licenses are used directly on the machine that you install Fuzor on, and use up one seat when the install occurs. Licenses cannot be transferred to another machine without the assistance of Kalloc Studios, and is evaluated on a case-by-case basis. This type of license works best for when Fuzor will be used on a specific, physical machine. Standalone license are not intended to be used by virtual environments.
Network licenses require setting up a Network License Server, which is software provided by Kalloc when you purchase your first network license. The software is installed on a centralized, always-online server which all machines which want to run Fuzor can access. The license key(s) are added directly to this server, and then are shared by anyone running Fuzor. Each license seat can only be used by one running Fuzor at a time, however as soon as Fuzor is closed, it can be immediately used by a different user. This type of license is useful if Fuzor will be run from several different machines, but is not needed to be used simultaneously.