Inheritances on MODELDEF

Remember, just because you request it, that doesn't mean you'll get it.

Moderator: GZDoom Developers

Inheritances on MODELDEF

Postby Ozymandias81 » Wed Mar 28, 2018 5:33 am

While I think the title is clear enough, and that possibly it has been requested already, could be this possible so we can save hundred lines for each model to be included on a project?
How much hard this should be to include on QZ-GZDoom atm?
I also wonder if the inherit logic could save some "load time" for parse actors (not sure which exact term to use here, sorry, but guess you get what I mean).
Thanks in any case :3:
User avatar
Ozymandias81
Doom is a State of Mind... Out of Control.
 
Joined: 04 Jul 2013
Location: Mount Olympus, Mars
Github ID: Ozymandias81
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia (Modern GZDoom)

Re: Inheritances on MODELDEF

Postby Tormentor667 » Wed Mar 28, 2018 6:38 am

Seconded
User avatar
Tormentor667
needs more detail
 
Joined: 16 Jul 2003
Location: Germany

Re: Inheritances on MODELDEF

Postby RockstarRaccoon » Wed Apr 11, 2018 11:02 am

Yes. This or anything like this. Yes.
User avatar
RockstarRaccoon
Totally Babies
 
Joined: 31 Jul 2016

Re: Inheritances on MODELDEF

Postby R4L » Wed Apr 11, 2018 2:57 pm

I'd like this as well!
User avatar
R4L
Ordinary Vanity
 
Joined: 03 Mar 2017
Discord: R4L#4655
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: Inheritances on MODELDEF

Postby RockstarRaccoon » Wed Apr 11, 2018 3:46 pm

Same for GLDEFS as well: I have tons of code that's just applying the same brightmaps and such to a bunch of textures...
User avatar
RockstarRaccoon
Totally Babies
 
Joined: 31 Jul 2016

Re: Inheritances on MODELDEF

Postby Graf Zahl » Thu Apr 12, 2018 12:53 am

How would you implement inheriting brightmaps? Textures have no relation to each other, save for patch composition,.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: Inheritances on MODELDEF

Postby Iniquitatis » Sun Sep 22, 2019 12:01 am

Or maybe something more universal, like:
Code: Select allExpand view
Model PLSG
{
    Path "Models/Blah"
    Model 0 "Blah.md3"
    FrameIndex A 0 0
    ... etc.
}

?

Yeah, yeah, compatibility. :blergh:

We already have global/shared/whatever definitions inside the TEXTURES lump, but why not in the MODELDEF?
User avatar
Iniquitatis
 
Joined: 24 Oct 2009
Github ID: Iniquitatis
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia (Modern GZDoom)

Re: Inheritances on MODELDEF

Postby S_Andrew_S » Mon Oct 05, 2020 9:27 am

I know this is a rather old topic, but I personally need this feature quite badly. My current project is requiring modeldefs that take up more space than most mods themselves do because I am creating a set of enemies that are made of a combination of parts and thus have potentially hundreds of variants, plus each variant uses about 50 animations. On top of that because I am still working with Zandronum I get to multiply each model definition times 3. With inheritance, I could just define all the frames for one variant, and clone the 1000+ other ones with just a few lines or less, and probably shave off millions of lines of modeldef (this isn't some exaggeration, given that each variant has about 4000 lines of modeldef code, and I know there's atleast a thousand variations, that right there would amount to 4 million lines). I also wouldn't have to go back and fix everything variant or redo all of the modeldefs in case I mess up somewhere on the original modeldef either.

Some of the potential gains from implementing such feature would give other modders here even more incentives to use models, particularly anything that has variations.

I need this feature so much, that I'm considering trying to make such feature myself, although the only thing really setting me back is that I'm not too experienced with compiling code from repositories. Of course, if I can do this, then I can certainly backport such feature to Zandronum as well. From what I've scouted from the source code, I can mostly understand how the modeldefs are parsed, so it doesn't look all that hard to implement.

EDIT 2: Because there are multiple model definitions that can be made for an actor which can be in different files might be taking off a bit more than I can chew.
User avatar
S_Andrew_S
 
Joined: 03 Apr 2014
Location: USA

Re: Inheritances on MODELDEF

Postby CBM » Tue Oct 06, 2020 9:01 pm

Same here

And s_andrew_s ... i am excited About your project based on your description. I love 3D models.
User avatar
CBM
Imp Slayer
 
Joined: 09 Oct 2019
Location: The Shores of Hell
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: nVidia with Vulkan support

Re: Inheritances on MODELDEF

Postby Cherno » Wed Oct 07, 2020 5:22 am

I support this. I had a similar problem as S_Andrew_s where I had multiple models with hundreds of frames (each with 4 submodels) that where all the same save for the model file name. I went so far and wrote a small program that auto-generates the frame definitions for me but inheritance would be so much easier.
User avatar
Cherno
 
Joined: 06 Dec 2016


Return to Feature Suggestions

Who is online

Users browsing this forum: No registered users and 0 guests