ZDoom

It still happens in 4.4.2.
Error message btw "Unexpected JIT error : Unknown REGT value passed to EmitPARAM".
Test example
[attachment=0]vector_in_out_bug.zip[/attachment]
Load it, start new game and type into console "summon v_bug". As soon as console is start closing vm abort happens.

In some cases Gzdoom just print "Unexpected JIT error : Unknown REGT value passed to EmitPARAM" message into console without vm abort, destroying actor that cause this.

Well, if it works for structs being treated as pointers, would it be possible to export DVector2/3 to ZScript somehow? That would allow for treating it like a pointer then, though that might ax any possibility of adding dynamic array support for it.

Turns out the reason for this is that, when it's a FxLocalVariable, it still emits shit as if it were a vector instead of a pointer. FxStructMember (used for struct and class members) works, though, so I'm not sure what the hell's up with this.
I have no idea how to deal with this crap.

As it says in the thread title, you can't pass variables as to Vector2/3 out parameters. Turns out there's some other issue my fix doesn't deal with. Heap-allocated values (e.g., member variables) can be passed just fine, while stack-allocated values (e.g., local variables) just crash GZDoom.
There seems to be two issues - First, it seems like it [i]may[/i] still be calculating the wrong amount of parameters in the function call code. Second, there must be some issue where it doesn't correctly calculate or pass the vector's memory address.