1.1.02

Post by **Graf Zahl** » Sun Mar 23, 2008 23:34

After adding a few interesting new features in the last few days I thought that a new release might be in order, so here it is.

So what's new?

- First version with ZDoom's new garbage collector which provides significant performance improvements on maps with lots of actors.
- Switch to Fmod Ex. (It doesn't use the latest still unfinished sound rewrite from ZDoom though.)
- Implementation of 3DMIDTEX feature, inspired by Eternity
- Linked sectors for complex moving structures that are not supposed to break apart when only one part gets blocked.
- Separate texture offsets and scrolling for upper, middle and lower textures.
- plus lots of smaller things.

StasBFG[iddqd] · Post by **StasBFG[iddqd]** » Mon Mar 24, 2008 2:00

Sound code is really messed up

Karate Chris · Post by **Karate Chris** » Mon Mar 24, 2008 9:02

Nice! Nuts in OpenGL? Sounds like it's worth a try!

DoomerMrT · Post by **DoomerMrT** » Mon Mar 24, 2008 9:28

Excuse me Graf, but after 1.1.0 should come 1.1.01 right?

nice work anyway

Post by **Graf Zahl** » Mon Mar 24, 2008 9:37

Yeah, typo.

And there's 1.1.02 which addresses a sound bug in Heretic.

In case you are experiencing any kind of sound problem, please try to switch between 2D and 3D sound.

Post by **Graf Zahl** » Mon Mar 24, 2008 9:38

StasBFG[iddqd] wrote:Sound code is really messed up

Just a hint: Reports like this don't help me AT ALL. Please describe your problems.

DoomerMrT · Post by **DoomerMrT** » Mon Mar 24, 2008 9:48

I dunno, it seems like a problem in the SNDSEQ lump.The sound what supposed to play infinitely til the door closes has an error.It stops after the sound ends and with a little gap it starts again.In 1.1.0 there wasn't a gap like this.
Also, sometimes the close door sound plays much more earlier than the door could reach it's closed sequence.

EDIT: both in 2D and 3D sound mode.

Post by **Graf Zahl** » Mon Mar 24, 2008 10:46

What WAD? What door? How am I supposed to test this if you don't tell me where to look?

DoomerMrT · Post by **DoomerMrT** » Mon Mar 24, 2008 10:53

Ok then You cannot test it.Sorry.

Post by **Tormentor667** » Wed Mar 26, 2008 8:10

Could you be so kind and explain the 3DMIDTEX's, the linked sectors and the seperate texture offsets a bit closer? Maybe with example wads? That would help alot

YouTube · Post by **Nash** » Wed Mar 26, 2008 8:53

Just look them up at the wiki man, it's all there and shouldn't be too hard to figure out.

Post by **Rex Claussen** » Fri Mar 28, 2008 23:30

Tormentor667 wrote:Could you be so kind and explain the .... linked sectors....

Info from the ZDooM wiki. I'm still trying to figure out the purpose of the 'Flat' argument, and how it ties in with the 'Type' argument. I guess that for a platform that can only get blocked from below the 'flat' would take a 0 value (for the control sector of the floor) and the 'type' would take a value of 2.

I'll need to download GZDooM v1.1.02 and the SVN of ZDooM to try it out.

Post by **Graf Zahl** » Fri Mar 28, 2008 23:49

'flat' and 'type' describe different things:

- flat is the moving plane in the control sector
- type describes which planes in the linked sector move in sync with that master plane. You can link floors to floors, floors to ceilings, ceilings to floors and ceilings to ceilings. You can also link both floor and ceiling to the same master plane.

Blocking should be handled the same for all linking combinations. The only exception is crushing, because there's only crushing ceilings with one exception that's not of interest here. Done this way you can create crushing 3D-floors if you link the 3D-floor's control sector to such a ceiling.

Post by **Rex Claussen** » Sat Mar 29, 2008 1:27

Graf Zahl wrote:You can also link both floor and ceiling to the same master plane.

Curious. The documentation did not indicate that both ceiling & floor could be linked to a single plane.

.... there's only crushing ceilings with one exception that's not of interest here. Done this way you can create crushing 3D-floors if you link the 3D-floor's control sector to such a ceiling.

From the wiki I couldn't quite tell how to implement a crushing 3D floor.

Essentially, what I need is a 2-sector 3D platform that rests on a piston (a third sector, which is not 3D) and which lowers and rises when activated by a switch. If it's crushing, so much the better. The platform sectors have tags 129 and 130, and the control sector has a tag of 131. For a non-crushing platform I would need to have two lines of code in my OPEN script as follows:

Sector_SetLink (131, 129, flat, type);
Sector_SetLink (131, 130, flat, type);

I'm guessing that 'flat' would take a value of 0 (false = floor), as the control sector's floor is what encounters the blocking. In that case, the 'type' would take a value of 2, to link the target's ceiling to the floor of the control sector.

Please correct me if I'm wrong, and please also provide some guidance on how to implement crushing. Thanks.

Post by **Graf Zahl** » Sat Mar 29, 2008 8:52

It's hard to tell without actually seeing the lift. One thing I can tell you: The plane you link to entirely depends on the movement you define. In this case, if you need crushing you will need a separate master sector and link both the lift and the piston to it. That's because you want the floor of the piston to move but downward moving floors can not crush for obvious reasons so there's simply no special that might be used to define such a movement.