Smooth Doom [UPDATE 9/25/19]

[faslrn]

Weird colours right? Need to convert the sprites to PNG I believe.

So why isn't this by default?

Any wads that would use colour translations (like Colourful Hell) to take the default monster sprites and apply a colour too them wouldn't work at all then. Having the sprites as the standard Graphic (DOOM) option allows for greater compatibility.

[wolfmanfp]

Trying to run this wad with a voxel mod results in both style barrels flashing between eachother. Anyway to avoid this other than editing one of the files?

I ran into this problem too.

[zrrion the insect]

Voxel mods don't replace the actors (usually) and instead they replace the frames that things use. The smooth doom barrel uses more frames but the voxel mod only has 2 or so frames of animation, so it can't replace all the frames in the animation.

[Gifty]

Voxel mods don't replace the actors (usually) and instead they replace the frames that things use. The smooth doom barrel uses more frames but the voxel mod only has 2 or so frames of animation, so it can't replace all the frames in the animation.

I haven't looked at the voxel mod yet, but based on this information I would say your best bet for a compatibility patch would be to modify the voxel actor to have all the extra frames that the smooth doom barrel has.

[cortlong50]

I’m gonna download and play with this tomorrow.

But dude next time you do a video do me a favor and slow down so I can actually see what the hell is going on haha

[lwks]

Will it take too long until the next update? It's been a couple of months so I'm curious.

[lwks]

There's a chance a spectre will continue to hunt you down as a ghost monster (no pun intended) even after you killed it.

It's probably due to gibbing it with a super-shotgun. I disabled that option and it doesn't happen anymore. Prior to that it happened twice, on the same map. I know it's a normal bug as well when an archvile resurrects a monster, but there are no archviles on the map, and the bug doesn't occur with any other monster.

Are you sure the SS Gib is the source of the error? Maybe it's just that the error is so random that you didn't see it twice. How can you be so sure? It happened to me just now, three immortal spectres that didn't count as monsters, "kill monsters" or "mdk" did not kill them.
Edit: This is a nasty bug, if anyone knows the fix please share with us.

[StroggVorbis]

There's a chance a spectre will continue to hunt you down as a ghost monster (no pun intended) even after you killed it.

It's probably due to gibbing it with a super-shotgun. I disabled that option and it doesn't happen anymore. Prior to that it happened twice, on the same map. I know it's a normal bug as well when an archvile resurrects a monster, but there are no archviles on the map, and the bug doesn't occur with any other monster.

Are you sure the SS Gib is the source of the error? Maybe it's just that the error is so random that you didn't see it twice. How can you be so sure? It happened to me just now, three immortal spectres that didn't count as monsters, "kill monsters" or "mdk" did not kill them.
Edit: This is a nasty bug, if anyone knows the fix please share with us.

IIRC it happens with SSG gibbing enabled. If you're not in the radius to gib it and reduce its HP to zero, it doesn't enter its normal death state and from then on roams the map for all Eternity (heh) with no way of killing it. Hitscans, projectiles, the player and monsters will pass through it and splash damage doesn't affect it either.

EDIT: I just double checked and was able to replicate it by 100%.

[lwks]

Ok, I got it, so is there any way to solve the problem?

[JohnnyTheWolf]

The solution to this issue has been found a few pages earlier by Blue Shadow.

The lack of a Goto Death at the end of the spectre's Death.GibbyHaynes state sequence is what's causing the "ghost" spectres issue.

[NathanVPer]

Can i run this with ZDoom?(NO GZDOOM)or another version that will work with it?

[wildweasel]

Can i run this with ZDoom?(NO GZDOOM)or another version that will work with it?

Why no GZDoom? You know GZDoom still has the software renderer in it, right?

[lwks]

The lack of a Goto Death at the end of the spectre's Death.GibbyHaynes state sequence is what's causing the "ghost" spectres issue.

About the immortal Spectre bug, THIS solves the problem.
Though I don't get why, the normal demon also doesn't have "Goto Death" in the end of the Death.GibbyHaynes state and it behaves properly.
I think the OP should be updated with this. This is a nasty bug.

PS.: Just to share with you huy, I could not replicate this bug using "summon spectre", summoned 100 and no one glitched. But when I loaded my custom map with 3500 Spectres it didn't take long until the first glitched Spectre appeared.

[Korell]

The lack of a Goto Death at the end of the spectre's Death.GibbyHaynes state sequence is what's causing the "ghost" spectres issue.

About the immortal Spectre bug, THIS solves the problem.
Though I don't get why, the normal demon also doesn't have "Goto Death" in the end of the Death.GibbyHaynes state and it behaves properly.
I think the OP should be updated with this. This is a nasty bug.

PS.: Just to share with you huy, I could not replicate this bug using "summon spectre", summoned 100 and no one glitched. But when I loaded my custom map with 3500 Spectres it didn't take long until the first glitched Spectre appeared.

This was already discussed (a fair few pages back now though). It's to do with the flow from one state to the next, so if a state ends without a goto then it flows into the next state. If you compare the Demon and the Spectre states you'll see that they are in a different order. This is the bug. Put the spectre's states into the same order as the Demon's and the issue goes away. Here's my previous post about it.

---

Without a flow control keyword to direct to the next state, they fall through to the Death state, since that's the state that comes next.

Which is why I re-ordered the GibbyHaynes state in the smoothspectre actor so that it comes before Death state, just as it does for the SmoothDemon actor, but JohnnyTheWolf was saying that it still didn't fix it. Here's the code I'm using:

Code: Select all • Expand view

ACTOR smoothspectre : spectre
{
   States
   {
   Spawn:
      SARG AB 10 fast A_Look
      Loop
   See:
      SSRG AABCDDEF 2 fast A_Chase
      Loop
   Melee:
      SSRG G 8 fast A_FaceTarget
      SSRG GGGHIII 1 fast A_FaceTarget
      SSRG J 1 fast
      SSRG K 1 fast A_SargAttack
      SSRG L 4 fast
      SSRG G 3 fast
      Goto See
   Pain:
      SSRG M 1 fast
      SSRG N 2 fast
      SSRG M 1 fast A_Pain
      Goto See
   Death.GibbyHaynes:
      TNT1 A 0
      TNT1 A 0 A_JumpIf(CallACS("StudioGibbly")==0, "Death")
      TNT1 A 0
      TNT1 A 0 A_JumpIfCloser(128, "GibDeath")
      TNT1 A 0
   Death:
      TNT1 a 0 A_JumpIfHealthLower(-30,"Gibdeath")
      SSRD A 3
      SSRD B 3 A_Scream
      SSRD C 3
      SSRD D 3 A_NoBlocking
      SSRD EFGH 3
      SSRD I -1
      Stop
   GibDeath:
      SARG o 3
      SARG p 0 a_playsound ("misc/gibbed")
      SARG p 3 a_scream
      SARG q 3
      SARG r 3 a_noblocking
      SARG stuvw 3
      SARG x -1
      stop
   }
}

[lwks]

Without a flow control keyword to direct to the next state, they fall through to the Death state, since that's the state that comes next.

Which is why I re-ordered the GibbyHaynes state in the smoothspectre actor so that it comes before Death state, just as it does for the SmoothDemon actor, but JohnnyTheWolf was saying that it still didn't fix it.

Sorry I just got a little confused because of this. I was even going to ask why changing the order of the states wouldn't fix the bug, but I just read the next comment lol.