Home & News Screenshots About  
  Downloads Development Media  
  Documentation File Bug  
JW Games >>
Jimmy's World >>
Reader Comments
Onyx Moving Forward
Posted 2005.03.14 08:07pm by Aaron
This news item is 5153 days old.

It has become apparent to me that without some kind of major shift in the development path of Onyx that no reasonable state of completion will ever be reached. Along with this realization I've come to accept that I no longer have much, if any, interest in continuing work on the project. At the same time I absolutely refuse to abandon it until it has been completed. This all implies that there needs to be a major shift in the development path, or I need to get out of the game development business right now, before I waste any more of my or my contributors time.

Abandoning the project isn't acceptable. As a result I'm going to list everything that needs to happen by section to release a tech-demo (maybe generally, perhaps just to beta teams) that will fall short of chapter 1 but will allow asset acquisition to continue.

To make that clear. Once the following list is done, perhaps slightly before, a tech demo WILL be released, horrible assets, incomplete effects and and all.

Here's what's going to happen, by section (careful, it's long):

Story / Game Universe Development:

  1. Race expansion will be frozen, but not curtailed. No new races will be introduced, even if game assets have to be sacrificed. New races may be introduced after chapter 1 has been released.
  2. Ship, weapon, universe and map development will proceed as required without change.

Visuals and Effects:

  1. Ambient debris must be added to allow for player spacial orientation cues.
  2. Explosion tweaking will continue.
  3. Light sources must be definable as point or area sources to improve rendering speed for large numbers of objects.
  4. Better LOD selection for connected objects such as missiles. Basically this requires the ability to disable missile and PD turret rendering entirely for very low LODs.
  5. Localized damage debris from impacts or ambient emissions is required. This is hand-in-hand with generic connectables for locating emission points.
  6. Generic effects may eventually be implemented, but for now a specific effect need be added for ships entering or exiting spacial compression, including action temporaries for disabling controls, disabling collisions and modifying the camera as appropriate.
  7. Jump engines will not be visible anywhere in the initial release.

AI Development:

  1. Basic follow/collide AI required for missile weapons.
  2. Basic formation, attack, strafe, evade and destination seek AI's required for ships.
  3. Basic target selection and tracking AI's required for PD turret weapons.


  1. Arbitrary and relative based location triggering required for mission termination and game events.
  2. Ship type destruction counts, wing destruction counts and faction destruction counts required.
  3. AI Application actions required.
  4. Damage % Triggers required.
  5. Set ship status actions required.
  6. Mission objective alteration actions required.

Game Physics & Mechanics:

  1. Conversion to spacial hashing.
  2. Generic connectables to replace location seeking.
  3. Full collision hull replacements will be created to replace generation from visualization hulls.
  4. Afterburners will be detached from energy consumption and replaced heat based limiting.
  5. NAV point travel needs to be stabilized and brought out of beta, as well as a method for selecting destinations. See: Other.
  6. Capital ship turrets need be added without the ability to be manipulated. First releases will purposefully avoid any scenario where capital ship turrets need be manipulated or fired.
  7. Locational damage application with substructure DU.
  8. Dynamic kinetic energy conversion required for explosive damage to work properly.

Game Assets:

  1. No audio game asset acquisition will take place in this area until the AI is completed. This may not make sense to look at, but there's good reason.
  2. Any untextured models will be immediately mapped with detail textures only. This is the single largest area of compromise. The number of model assets already created, plus the scheduled additional ships AND the addition of more scenery objects is completely imbalanced with the near zero textures being generated. This decision is one that I desperately wanted to avoid, but it has become obvious that no magical solution is forthcoming and an untold number of paths are blocked by the generation of textures. It is very likely that this compromise will render the final project (at least for chapter 1) completely uncompetitive in the market, but.... well, life sucks.
  3. Music asset acquisition will also be frozen pending the completion of basic AI.
  4. Pilot portraits will be disabled (how this will effect pilot creation is unclear without causing incompatibilities between versions) pending basic AI development.
  5. Turret/weapon separation as well as object connection point definitions need to be completed. The union of objects need only be done once for the physical hull and therefore the different objects may be rendered as a part of the same game entity. This is important to limit the scope of change to the turret game object class.

HUD Development:

  1. Generic VDU rendering class needs to exist with the HUD built in such a way that VDU's may be stacked at different appearance locations. HUD elements need to be reconfigurable for different ships, but that isn't required for now. It should be considered. (Colours and fonts and many HUD elements are already configurable)
  2. Status and target status need to be replaced with 2D visualizations.
  3. Missile selection VDU is required.
  4. System damage VDU
  5. Gun grouping MAY be supported if a trivial way to do so is apparent. If not secondary fire will be disabled and all weapons will always be grouped in the primary.
  6. Radar needs to be reconfigured to be much clearer as low gamma screens are virtually impossible to use. This may apply to all HUD elements.
  7. Mission objective VDU required.
  8. HUD sound effects (generic bleeps is fine) need to be added.

Other Development:

  1. Briefing room creation with scripted (may use trigger infrastructure) simplistic animations similar to Tie-Fighter. Single map display and single dialog for now. Story based 'conversations' or story development will happen in-engine with triggers.
  2. Configuration room creation to allow weapon load-out and ship selection.
  3. Debriefing screen creation to allow for missions to conclude.
  4. Pilot viewer needs to be completed in the archives.
  5. Audio configuration is broken and need be fixed if easy to do, or completely disabled in the menus.
  6. Weapons display needs completion in the archives.
  7. The archives need limiters for pilot experience, which won't ever be updated in the tech release. (This lets me cheat a lot for now)

Critical Paths:

  • Basic AI Completion.

    Assets are waiting on this, not to mention the game cannot be completed without.

  • Detail texture mapping for all models.

    Debris creation, game balancing and campaign development are all waiting on textures for models.

  • Basic camera/ ship AI configuration and dialog cut scene scripting

    Doing ANY story elements require at least basic controls over ships and the camera. Any first release needs to have at least minimal support here.

Eye on the Future (aka Next stage Critical Path)

  • Campaign development will be crucial to spark any required development in the fleet, barracks, pilot, character and faction classes. Major stability issues WILL arise once campaign data is stored from mission to mission.
  • Capital ship turret manipulation needs to be completed as soon as the basic release is completed.

Post a New Comment

Jimmy's World.org, JWGames.org & Onyx pages, associated art, files and documents are copyright Aaron Cameron 1996-2019
For more legal information and page contributers see the license page.