ZDoom

Yes, because of [b]RegType[/b] in [b]VMFunctionBuilder::FramePointer[/b] is [b]REGT_NIL[/b] to be precise.

Is this caused by the zero-length struct?

I actually compiled a debug build myself before reporting and saw the same assertion failure. Since it was during startup however I thought it was unrelated and that I compiled something wrongly...

Anyhow, I fixed it in my mod, thanks for the clarification. :)

version "2.4"

struct S
{
    void Func()
    {
    }
}

class A : Actor
{
    override void BeginPlay()
    {
        S s;
        s.Func();
    }
}

Here is a minimal sample. It will trigger a failure of [url=https://github.com/coelckers/gzdoom/blob/14094ebeb941d3d529802290be5d76fcfb299ac2/src/scripting/backend/codegen.cpp#L9006]this assertion[/url] first, and then, summoning A will lead to this error on JIT code generation.

[code]version "2.4"

struct S
{
void Func()
{
}
}

class A : Actor
{
override void BeginPlay()
{
S s;
s.Func();
}
}[/code]
EDIT: To workaround this engine bug in the mod, it should be enough to make [b]ParticleSpawner.SpawnParticles()[/b] function [i]static [/i]and avoid creation of [b]ParticleSpawner[/b] instances (which is the right thing to do anyway).

I thought I did, must have done something wrong the first time. This time it was sent correctly.

Send the mod please.

Execution could not continue.

Ambiguous operand size: mov [r12+32], 0

As the title says, I have an issue with the "kill" command and my mod (which I will send to the developers).

The only error message I am getting is:
[code]
Execution could not continue.

Ambiguous operand size: mov [r12+32], 0
[/code]

Only 64-bit of GZDoom is affected while 32-bit works fine.

This build (gzdoom-x64-g3.7pre-302-g927d33306) and previous ones are working fine on both 64 and 32-bits
From this build onward (gzdoom-x64-g3.7pre-733-g101ebe173) it only works on 32-bit while 64-bit gives me the given error message. It doesn't matter if I try to kill specific monster types or just "monsters".