#HYPER REALISTIC QUAKE III ARENA MOD HOW TO#
#HYPER REALISTIC QUAKE III ARENA MOD CODE#
#HYPER REALISTIC QUAKE III ARENA MOD PC#
#HYPER REALISTIC QUAKE III ARENA MOD ZIP#

Now we can start loading content directly from the game. Std :: vector > q3apackages for ( auto file : dir ) Std :: wstring q3apath = L 'C:/Program Files (x86)/Steam/steamapps/common/Quake 3 Arena/baseq3' auto dir = LoadDir ( q3apath ) This is just like the package system from Leadwerks.

Next we load the game package files straight from the Quake game directory. Load Quake 3 plugins auto pk3reader = LoadPlugin ( 'Plugins/PK3.dll' ) auto md3loader = LoadPlugin ( 'Plugins/MD3.dll' ) auto bsploader = LoadPlugin ( 'Plugins/Q3BSP.dll' ) Notice we keep all our loaded items in variables or arrays because we don't want them to get auto-deleted. (Package files are read-only.) Plugins will allow packages to be loaded from file formats besides ZIP, like Quake WADs or Half-Life GCF files. These will also be loadable from the editor, so you can add new packages to a project, and the files will appear in the asset browser and file dialogs. You can load a Package object to add new virtual files to your project.

#HYPER REALISTIC QUAKE III ARENA MOD ZIP#

The ZIP virtual file system from Leadwerks is being expanded and formalized.

#HYPER REALISTIC QUAKE III ARENA MOD HOW TO#

The Turbo Plugin SDK is a little more low-level than the engine, so it includes a MemWriter class to help with this, since the engine Stream class is not present.Īs a test I am writing a Quake 3 MD3 import plugin and will provide the project and source as an example of how to use the Turbo Plugin SDK. Once your GMFFile is constructed you can save it into memory with one command. GMFLOD * lod = node -> AddLOD () //Add a mesh GMFMesh * mesh = lod -> AddMesh ( 3 ) //triangle mesh //Add a vertex Node = new GMFNode ( file, GMF_TYPE_MODEL ) //Add an LOD level Create the file GMFFile * file = new GMFFile //Create a model

#HYPER REALISTIC QUAKE III ARENA MOD CODE#

I've created new C++ code to create GMF2 files: This was written in BlitzMax, and allowed construction of a GMF file with easy commands. In Leadwerks 2, we had a bit of code called the 'GMF SDK'. There are real problems that need to be solved and making a 'tricky' file format is not one of them. I don't need to introduce unnecessary complexity into the design just so I can show off. There's enough complexity in this already. GLTF will continue to be supported, but the format is too much of a mess to use for plugin data.Ĭhar ID 'GMF2' int version 200 int root //ID of the root entity int texture_count //number of textures int textures_pos //file position for texture array int materials_count //number of materials int materials_pos //file position for materials int nodes_count //number of nodes int nodes_pos //file position for nodesĪs you can see, it is really easy to read and really easy to write. I am not sure yet if GMF2 will be used for actual files or if it is just going to be an internal data format for plugins to use. This means the vertex array never has to be iterated through, making large meshes load faster. Mesh bounding boxes are supported so they don't have to be calculated at load time. Materials and textures can be packed into the format or loaded from external files. Vertices are stored in a single array ready to load straight into GPU memory. GMF2 is a simpler flat binary format updated with some extra features: It's a custom fast-loading chunk-based binary file format. The GMF file format was used in Leadwerks. For example, DDS is supported through a plugin, but a backup PNG has to be included in case the loaded doesn't support the extension. Tons of missing functionality is added through a weird plugin system.

#HYPER REALISTIC QUAKE III ARENA MOD PC#

It's meant for web content, not PC games. There are 3-4 different versions of the file format and many many options to split it across multiple files, binary, text, or binary-to-text encoding. GLTF is a pretty good format but has some problems that makes me look for something else to use in our model loader plugins. This scared me so I went with a standard file format to feed the data from the plugin to the main program. I considered using a structure they both share in memory, but those always inevitably get out of sync when either the structure changes or there is a small difference between the compilers used for the program and DLL. The first thing I had to do is figure out a way for plugins to communicate with the main program. One thing led to another, and.well, this is going to be a very different blog. I wanted to get a working example of the plugin system together.

Hyper realistic quake iii arena mod