Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Feature Request) Add support for Vera Visions formats #172

Open
pixe1reality opened this issue Mar 11, 2024 · 1 comment
Open

(Feature Request) Add support for Vera Visions formats #172

pixe1reality opened this issue Mar 11, 2024 · 1 comment

Comments

@pixe1reality
Copy link

pixe1reality commented Mar 11, 2024

It would be helpful for developing FTEQW standalone projects (and help make custom maps for the game The Wastes that uses FTEQW) if there was support for VVM models and .mat shader files.

VVM models are IQM models with extended features for in-game usage. IQM models have existing support in AssetLib, but since VVM models have a different file extension it is not recognised. Specifications for the format, in case it differs too much from IQM can be found here: https://github.com/fte-team/fteqw/tree/master/iqm

The Nuclide SDK for FTEQW has a special material file format derived from Quake 3's shaders that exist as separate material files per shader definition. NetRadiant-Custom already supports Quake 3 shaders, but I'm not sure how much more work it would be to recursively find shader files within the texture folder. Specifications for the material commands (in case editor-specific commands have differences) can be found here: https://developer.vera-visions.com/d5/de1/mat_commands.html

@Garux
Copy link
Owner

Garux commented Mar 11, 2024

I'm not volunteering to support number of formats flavours added by single game. But from description these two things are doable via PR.

Assimp may handle multiple extensions per loader, so basic IQM loader may be reused for your format flavour.

.mat support seems okay, if implemented modularly enough, as in not bloating existing shaders loading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants