Nice one! Is this a pawn from Rune???

Rune uses completely different model system. Straight porting cannot be done as they are not even meshes. I told this to someone recently. So I'm not sure what kind of tools you used, but within the "normal" methods I'm using it can't be done. I didn't check every program or tool that's out there, so if you used umodel for this and conversion, it might be possible. Either that or Rune demo is very different and uses standard meshes.

The models in Rune are half-geometry, use similar system like for displaying movers and can be independently animated/moved.

Apparently yes:
http://www.ut-files.com/Utilities/umodel/readme.txt

Rune support was even back then.

First, I didn't send any messages to you about it. It was a forum post that I made. Second, I never claimed it won't be possible to port them. But a straight conversion isn't possible because the format is very different and for example in rune the individual limbs can be severed and used as a weapon. This is all because of the "SkelModel" format. I am looking at it from the perspective of the game engine. The normal "Model" format in Unreal is used for movers.
This is why Rune is so unique, after all it was the wizardry of the Hexen guys.

I'd like to see 'em yea.
The more content we have the better.

I'm not trying to draw out any argument. Funny that I thought you are trying to send me on a guilt-trip.

Obviously we both tend to wrongly assume things due to our experiences.

My amazement in Rune lies within the extra stuff that Ben Gokey has incorporated into it. It's very different than skeletalmeshes found in ut/227 or other unreal engine games. This was also developed from version 100 of Unreal by branching off it seems and then merging later code in. But most of it is own former Raven work.Tim's log from 1996 mentions a potential deal with Raven and this is where this comes in play. They developed this since 1997. When they split off and weren't interested in further deals with id software. They went looking at Epic and entered the secret deal though it took a bit long for the game to come out obviously.

It even uses separate mesh file with the extension .ums just like Unreal Alpha once did. Not like the 227 .usm files anyway, it's something else.

The game uses polyobjects which were a major innovation for the Doom engine when Hexen came out. The same people coded this.

Leo T_C_K wrote on Jan 16^th, 2017 at 7:48pm:

Nope, you can get Gizzy or Bob to show you how to process the PSA/PSK files into direct import code that can be pasted to the top of a uc and compiled with the engine. You can do the entire process from Rune models to imported Unreal assets in less than 10 minutes and that includes texture conversion and assignments.

Even then you just have a raw (but functional) model with animations but absolutely no code at all to make anything work. You'll have to find an appropriate monster to follow and begin plugging in the animation calls to the behavior code. This can be time consuming because you have to also time everything out so the anims are smooth and have some flow while also coding for behaviors appropriate to the monster you are creating. It took about a week per monster on the KF ones to get them decent and even then I could have done better. I'm no modeller though, just a hobbyist hack.

Some of the Rune models could end up being very cool because there are a TON of anims on many of them. Some of the player models looked to have several hundred animation sets. Poly count was way better than the KF ones too so you could have more on the screen without issues.

I'm really very interested in this as a project but it's likely going to be someone else that does it if it gets fully done. I'd help a bit but I'm just not in a place right now to take on a full project. In fact I'll be out from Thursday on, I have to do another crappity smacking treatment.