New blog-based website ! Currently you are browsing the old site.

Rapid development/prototyping with Virtools ...

reality or phantom?

 

level: any
requirements: virtools dev and sdk

Hi,

this is a first, quick version of this article.

It's not only Virtools that sells it's technology a rapid prototyping tool, but also experienced users might sometimes fall into the trap of believing that something can really be done fast in Virtools without checking the case carefully.

What is it what makes the development fast?

  • a render-engine ready to use
  • behviour/logic-engine ready to use
  • a flexible and extensible frame-work
  • ready-to-use components
  • a all-in-one editor
  • built-in scripting with debugging
  • visual wiring/combining of high-level components

The most obvious are the ready-to-use components and the editor. To make a long story short, here is my proposition of a check-list, that can help you to find out, how fast you really will be:

 

List 1 - General: drag and drop building

  1. Is your team experienced in development for real-time 3d systems?
  2. Is your team familar with Virtools? Do they know the vocabulary (building blocks, SDK, exporter) ?
    1. if not, can you get good training?
  3. Does Virtools offer by default all the logic/behaviour components you need?
    1. if not:
      1. Do you have already developped them on an earlier project?
        1. Does they need to be adapted? (see list 2)
      2. if yes:
        1. are the components flexible enough for your needs (design/functionality)
          1. if not, see list 2
        2. are the components buggy?
          1. if yes, see list 2
  4. Does the render engine and it's material/shader framework offer all you need?
  5. Does the workflow, media-import pipeline need adjustments, extensions?
    1. if so, can it be done via action scripts?
      1. does it need customization of the 3d package exporter? (see list 2)
      2. does it need interface extension plug-ins? (see list 2)
  6. Is the performance sufficent? (rendering, behaviours)

List 2 - custom development

  1. when using the schematic view only, do you have all the components you will need?
  2. can it be done with VSL?
    1. does it need SDK programming?
  3. do you have enough people and knowledge in-house for development?
    1. if not, does your budget allow out-sourcing?

It's clear that even when you are hitting a lot into list 2, you will be faster with Virtools than by starting from zero. But you can't expect to be really, really fast, or to be able to do it alone! Even three people might not be enough for a not-sooo-small project.

Well that's my estimation based on my experiences. Fell free to consider them or to trash 'em ;). Contact me if you have improvements suggestions concerning the lists.

One more hint - things you should check carefully for your needs and about bugs:

  • character animation system
  • character control
  • everything GUI related (2d text display, homogenous coords, missing widgets ...)
  • material system
  • collision system
  • font system
  • skybox and fog
  • 3d package exporter

 

I hope I made clear that really rapid development can be done in virtools, but it depends heavily on your project's requirements, team-size, experience, virtools knowledge and budget.

Architectural walkthroughs and simple adventures won't be a problem. Games having a complex game-play, or complex character-interaction won't be developed fast with a small team.
But Virtools offers you the framework to develop such prototypes more quickly than starting from scratch - as descriped in the Virtools whitepaper about rapid prototyping.

You will only be able to do a realistic estimation by doing a in-depth evaluation/assesment.

Dominique,
Berlin, 03.08.04