v1.5 Video Tutorials

Some instructional videos for v1.5 of the framework were recently created by one of our talented artists (also responsible for the sanctuary design) and uploaded to Vimeo.

The content pipeline is covered, including:

Exporting Maya models to Collada

Exporting 3dsmax models to Collada

Creator Importing and Publishing

The import/export pipeline is something that has been getting a lot of development attention recently and is quite advanced compared to the legacy import functionality of older versions of the framework.

Both the import and export providers are runtime loaded, meaning that others can build custom modules for the Creator.

By default the Creator ships with Collada import and File System export as shown in the video.

VastPark Pumpkin?

A friend of mine recently sent me a picture of a pumpkin she carved for Halloween that looks uncannily similar to the VastPark logo.

Do you see the resemblance?

VastPark pumpkin?

VastPark logo

On the topic of Halloween, it reminds me of some machinima that was shot using VastPark a couple of years ago:

VastServer Developer Edition RTW

Today marks the release to web of a new flavour of VastServer, known as VastServer Developer Edition.

As the name implies, this version of the server is targeted at developers and aims to provide more information on the framework’s behaviour, a little closer to the metal than has been possible in the past.

The user interface for the server is written with WPF and looks like this:

Click for larger view

Some of the more interesting features are covered in detail below.

Server Usage History

Many of the factors that contribute to server load such as send/receive rates, send/receive queues and client connections, are visible at a glance, with a rolling 60 second view of activity graphed:

It’s likely additional metrics will be made available in future releases, such as dynamic element counts, owned element counts, mutex holders, etc along with the ability to filter and manipulate the usage history graph.

Logging

Each world maintains it’s own log that displays IMML notifications such as those related to scene.ui:writeline, along with any world related notices, errors and warnings that the framework associates with that context.

A system log is also available via the View -> Log menu. It contains log information related to the networking infrastructure.

File Hosting Support

One nice new feature is the ability to host assets along side client IMML, meaning that IMML can be coded with relative URIs.

This supports the use case where a team wants to avoid setting up a web server or using a public storage provider such as Amazon S3 and is a convenient way to consider developing worlds.

For example, the model in this IMML:

<IMML xmlns="http://schemas.vastpark.com/2007/imml/">
  <Model Source="models/ground_path1.model" />
</IMML>

Is resolved to the client folder of the hosted context via the HostingRoot:

In the above example, the HostingRoot is at My Documents\VastPark\Server\ and the hosted context is called “sanctuary” (for some live shots of sanctuary in action, see here) .

Client Metrics

The client tab displays the behaviour of all clients connected to a specific world.

Information on user alias, connection time, framework version, ping, message resends, and time since last message provide the ability to troubleshoot scenarios where certain clients are experiencing difficulty with the system.

Both v1.3 and v1.5 clients are supported by this release of the server, the network stack has remained compatible between these versions of the framework.

Download

VastServer Developer Edition is freely available to developers for download with a limitation of 10 concurrent user connections across all hosted worlds. It’s built for windows and requires .NET Framework 4.0

License keys are available to partners and enterprise customers to remove the concurrent user limitation.

Link: http://www.vastpark.com/resources/downloads.html#server

show
 
close
Think I prefer the community attempt at the new #win8 logo (http://t.co/fKKeWpOb ) vs the official one (http://t.co/E46TN1JV)