165 replies to this topic

[Moreartillery]

I've also tried typing none in the in the motion names and it didn't make a difference. Hardpoint 1 and 3 are the same, hardpoint 2 is the heavy bolter. And I've tried with and without 'name for this weapon choice' filled in.

Attached Files

•  asdf.PNG   235.85KB   0 downloads

[Gambit]

I suppose the 1st "projectiled" weapon is coded in either hardpoint_01 or hardpoint_02 right?

And in hardpoint_03, the 2nd projectiled" weapon is coded, and this is where the projectile is problematic. Correct?

 

If so, I can only suggest removing (leave blank) ALL motion variable name values (those with the _3), and keep ONLY the harpoint_weapon_variant_motion, simply using <None>, as a name.

And retry.

 

It worked for me...

[Moreartillery]

So apparently, unlike every other part of a unit, the muzzle and origin don't update when loading a save game, so you have to train a new unit for the change to take effect. Animations, fx, textures, and even map data will update properly when you load a savegame but not muzzle and origin. Thats so weird and inconsistent.

[Gambit]

Brother Moreartillery, I tested it extensively and for me, the 2nd projectile ALWAYS comes out from the proper origin.

I tested on the Dark Angels Vengeance, which fires 2 plasma cannon bolts.

And it is perfect.

Even after a save->load...

You may have to perhaps re-check your code?

[Moreartillery]

It works now, I was just saying I had to train a new tank for the new origin to be applied.

 

My new problem is that a die_jumping animation I made gets cut off before finishing. I can see the unit start to fall out of the air but it disappears before hitting the ground. It works fine in the OE.

[Gambit]

If it is AE (fro example, a spawn_ext or a special_attack anim), it sounds like a problem with the time setting.

Otherwise,... you must ask a modeller

[Kekoulis]

If it is AE (fro example, a spawn_ext or a special_attack anim), it sounds like a problem with the time setting.

Otherwise,... you must ask a modeller

No,he does not have to ask a kodeller,or else the modeller would have replied.

 

As long as it is fine in OE,then the only thing they have to do,is to set the correct timings in Corsix.

[Moreartillery]

I keep getting the following error when I try to import the hive tyrant. See attached screenshot. It doesn't extract the ref or anim files.

Attached Files

•  error.PNG   113.09KB   0 downloads

[Kekoulis]

I keep getting the following error when I try to import the hive tyrant. See attached screenshot. It doesn't extract the ref or anim files.

Yeah,the model is damaged or the Importer borked.

 

Either way,I am afraid you can't import it.

Edited by Kekoulis, 29 October 2019 - 10:42 AM.

[Moreartillery]

I've finished the wyvern and hydra aa. You can add them to UA if you want.

 

https://www.moddb.co...arys-animations

[Kekoulis]

I've finished the wyvern and hydra aa. You can add them to UA if you want.

 

https://www.moddb.co...arys-animations

I did not know you were working on a Wyern.

Good stuff I see.Well done.

Edited by Kekoulis, 06 December 2019 - 03:03 PM.

[Moreartillery]

I've been trying to add a spawn anim to the great unclean one but can't make the body and head visible at the same time, even with a vis_all anim. I can use override visibility in the OE to see the body or the head but never both at the same time.

[Kekoulis]

I've been trying to add a spawn anim to the great unclean one but can't make the body and head visible at the same time, even with a vis_all anim. I can use override visibility in the OE to see the body or the head but never both at the same time.

ΟΕ only?
It is due to the 4gb limit and skin batching issue.

It will work just fine in-game.

[Moreartillery]

The body mesh doesn't show ingame. There is a skinbatching message in the debug window, what does it mean? I already installed the 4GB patch.

[Kekoulis]

Skinbatching is normal with that model.Blame Iron Lore for never updating the debugger.

 

Which GUO are you using?The DOW II one or the one from Chaos Daemons?

 

Either way,make sure the meshes are properly skinned and all meshes are ''editable mesh'' and nothing else.

[Moreartillery]

Its the DOW 2 GUO.

Edited by Moreartillery, 17 December 2019 - 11:24 AM.

[Moreartillery]

Its still not clear to me why the skin batching problem happens or how to fix it.

[Kekoulis]

Its still not clear to me why the skin batching problem happens or how to fix it.

Skin smaller meshes.

Skin batching is a cap Relic implemented as a way to prevnt the engine from crashing woith high polygon models(before LAA was a thing).

So,cut the bigger mesh into sub meshes/parts and skin the accordingly.

You will notice you are correct once the entire model is visible in OE.

[Moreartillery]

I reimported the model to max and even unedited it still has the skinbatching problem. It makes me wonder how the creator was able to make it work the first time.

[Kekoulis]

I reimported the model to max and even unedited it still has the skinbatching problem. It makes me wonder how the creator was able to make it work the first time.

It just happens tbh.

You have to be lucky.

Does it render correctly in-game?

Sometimes,a model not rendering in OE works fine in the actual game.

Especially with LAA patch installed.