Skip to content

Latest commit

 

History

History
44 lines (33 loc) · 1.67 KB

File metadata and controls

44 lines (33 loc) · 1.67 KB

Content Standards

Naming

For any files of the following node object types, please use the following extension. Any legacy documents might use node or world.n - these should be updated to the standard conventions as well.

Object Type Extension Notes
config .cfg.n
effect .eff.n
material .mat.n
model .mdl.n
lights .lit.n
project .prj.n
program .sha.n
room .rom.n
brush .brs.n

The following are specific to the cook utility and are not supported by the engine directly. Typically, you shouldn't need to worry about these as they'll be generated by the tools.

Object Type Extension Notes
cookModel .cmf.n
cookTexture .ctf.n

Any binary forms should use the same convention going forward. To avoid any conflicts, these should ideally be generated into an alternate root location.

Materials/Textures

Ideally these should go under your <project>/materials/ directory. In some circumstances you might find them under <project>/textures/ instead, which is unfortunately due to a tooling limitation. That said, whenever possible, the former is preferable.

The engine has support for a large range of different formats, that said we would recommend using industry standard formats such as the following.

  • PNG
  • TGA
  • DDS

In future, per the cooking process, these will be converted into a .tex format.