The top and bottom

ChupaReaper · Post by **ChupaReaper** » Sun Sep 09, 2007 22:42

I hope so, finally, the end of the paper age! I'd use SkullTag if it supported weapon decorate and slopes, well basically everything GZDoom does, so changing would be pointless... GZDoom's added a bit of SkullTag in though...!
Anything about the airial hitscan problem?

HeX_Vulture · Post by **HeX_Vulture** » Mon Sep 10, 2007 5:28

ChupaReaper wrote:I hope so, finally, the end of the paper age! I'd use SkullTag if it supported weapon decorate and slopes, well basically everything GZDoom does, so changing would be pointless... GZDoom's added a bit of SkullTag in though...!
Anything about the airial hitscan problem?

DECORATE and slopes? Skulltag already has all that. Skulltag is based off of ZDoom 2.1.7 and has everything ZDoom has. The GL renderer is from GZDoom 1.0.24 and has most of what GZDoom has.

Have you even tried the port?

Post by **Torr Samaho** » Wed Sep 12, 2007 9:10

Karate Chris wrote:SkullTag now has 3D floors so they may have fixed the problem.

No, I didn't work on this problem yet.

ChupaReaper · Post by **ChupaReaper** » Wed Sep 12, 2007 19:16

Slopes and full decorate? I only checked the wiki and didn't try my project on the port. It doesn't use modeldefs though (does it?).

HeX_Vulture · Post by **HeX_Vulture** » Wed Sep 12, 2007 22:49

ChupaReaper wrote:Slopes and full decorate? I only checked the wiki and didn't try my project on the port. It doesn't use modeldefs though (does it?).

Just like the Skulltag wiki says, yes it does. You could try downloading the port and seeing what all it supports yourself.

Let me say this again:

Skulltag supports everything ZDoom 2.1.7 and GZDoom 1.0.24 has. The only difference is that 3D floors work only in coop-based game modes (coop, survival, and invasion)

And if it doesn't support everything ZDoom 2.1.7 has, then it should and you need to file a bug report. (but you might want to wait until version 97D final before bothering, it will be released soon ((NOT beta 4.1)))

Post by **Torr Samaho** » Thu Sep 13, 2007 9:28

HeX_Vulture wrote: Skulltag supports everything ZDoom 2.1.7 and GZDoom 1.0.24 has. The only difference is that 3D floors work only in coop-based game modes (coop, survival, and invasion)

That's only partial correct. Currently Skulltag has the GZDoom 1.0.24 renderer and everything ZDoom 2.1.7 has. It only supports some of the post ZDoom 2.1.7 features of the latest GZDoom release. Although I eventually plan to port over everything.

Further Skulltag does not and most likely never will support fragglescript due to the GPL.

ChupaReaper · Post by **ChupaReaper** » Thu Sep 13, 2007 22:23

What would be neet is if SkullTag, ZDoom and GZDoom mixed together into one new port, instead of taking bits from each other, they're all almost the same, just SkullTag has the multiplayer and GZDoom has the models and Legacy stuff. Though from what I know, I could be very wrong...

Post by **Enjay** » Thu Sep 13, 2007 23:43

Personally I like the fact that the ports are different and retain their own character.

Post by **Nash** » Fri Sep 14, 2007 9:57

ChupaReaper wrote:just SkullTag has the multiplayer and GZDoom has the models and Legacy stuff

Skulltag supports GZDoom models!

In fact, Skulltag's model support is already superior compared to GZDoom. The internal build of Skulltag has the following:

1) Model interpolation
2) Sprite billboarding
3) Model alpha
4) Model skin translating

TheDarkArchon · Post by **TheDarkArchon** » Fri Sep 14, 2007 14:14

Nash wrote: The internal build of Skulltag

That's the thing: It's not a public build.

Post by **Graf Zahl** » Fri Sep 14, 2007 17:20

However:

The model interpolation is rather crude. I'd like to do this differently so the chance that I'll port that code is slim. It wouldn't surprise me that for frame based model definitions it creates more problems than it solves.

The thing is, I am not particularly happy with the current model code but to do it right requires time I don't have. Also, when I really do this it will strictly require use of state labels for *everything* so retroactively defining models for existing complex actors is out. What I won't do for sure is to expand the current code.

ChupaReaper · Post by **ChupaReaper** » Fri Sep 14, 2007 22:42

But the modeldefs and the way to load models into gzdoom wont change though right? I've already made like 50 of them!
So SkullTag supports modeldefs too? Or does it have it's own way of model definition, does it do weapon models, etc, I'm gonna check the wiki...
I can't wait for this new model code though, from what I know a lot of time's put in it, what adsactly's going in the next version... there should be a 'Coming Soon' thread or something!

Post by **Nash** » Sat Sep 15, 2007 0:01

TheDarkArchon wrote:
Nash wrote: The internal build of Skulltag
That's the thing: It's not a public build.

Yeah but Torr PM'ed me some of the source for me to implement into my project's EXE.

Graf is right, the interpolation is rather crude, but I'd rather have it now than having to wait for Graf to come up with a better solution (which is fine and all, I totally understand how he doesn't have time but I need working EXEs to keep motivating me to finish this project).

If he eventually implements a better way, I would be happy to convert my models to the new improved format.

Post by **Torr Samaho** » Sat Sep 15, 2007 17:07

ChupaReaper wrote: So SkullTag supports modeldefs too? Or does it have it's own way of model definition

Skulltag uses the same modeldefs as GZDoom. The only thing I changed in the definition was adding support for a zoffset setting.

ChupaReaper · Post by **ChupaReaper** » Sat Sep 15, 2007 22:20

Well I downloaded the latest SkullTag (the zip from the website) and the models, etc, all work fine, but "unknown actor definition damagefactor" or something like that. Perhaps I should make a feature request on the SkullTag forums or something. GZDoom does enough so far in my projects develpoment, but I've already started making 2d weapon 'temps'. I'm sure the next GZDoom will be worth the wait, I've still a lot to do in my project.