Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hubberranz]

@Edlor,
Post Updated !
I propose these fix:
- positions hooks Engine EF
- removing duplicate hooks Engine1x/GearL2b/GearL2z/GearLy/GearR2b/GearRy
- positions all racks and bombs
- correction skin1o.tga
- fix shadows GearC2
https://www.mediafire.com/?49na5n8ntg2w9g2

Link is dead. Reupload please.

WAS probably this: https://www.mediafire.com/file/jthym36azga6ps4/Fix_Ki-30_new3D.7z/file
...content seems to fit the bill...

[tvister]

For what reasons can parts of D3 disappear at the time of damage? D1-D2 are displayed normally.

[tvister]

I’ll ask the question differently, does anyone know why during critical damage, parts of the model do not fall off, but disappear in the air.

[sosezi]

I’ll ask the question differently, does anyone know why during critical damage, parts of the model do not fall off, but disappear in the air.

that's  the main mystery lol

[gio963tto]

Normally for some error in Mehs files .

Gio.

[Mission_bug]

For what reasons can parts of D3 disappear at the time of damage? D1-D2 are displayed normally.

I’ll ask the question differently, does anyone know why during critical damage, parts of the model do not fall off, but disappear in the air.

The damage meshes need to be attached in a certain sequence and each should have a corresponding damage cap.

The damage cap should appear once a aircraft part has suffered catastrophic damage and been blown off/fallen off the component it was attached to.

Take a existing model that you know works and look how many damage meshes it has and check the hier as well, compare that to your model to make sure you have all your own parts named correctly and attached to those they are supposed to be.

Trial and error will get you there eventually tvister, double check everything or ask someone you are in close contact with to go through your model, they might see something you have missed.


Take care.


Wishing you all the very best, Pete.

[tvister]

Thank you all for your feedback. Initially, as an example, I used the D3A1 Val. All parts names are respected, although maybe I missed something. CAP stubs are created, they also do not appear. Perhaps there are errors in the meshes responsible for damage, but D1-D2 damage is visualized. All parts disappear at the moment of separation from the main model. And yet, there is no correlation of damage with the flying model. A plane can fly without a tail or without a wing, although pilots jump out.
Regards T.V.
Google translation

[Mission_bug]

Are all your meshes loading their textures tvister?

When Dimon released his original Bv-138, the tail booms would disappear, not sure if that was fixed or not, I cannot find anything here or at AviaSkins.

Could you please post a log and see if that gives any clues to help:


Read how to get the log here, and the instant log here.

Important: read here which part(s) from the log to post
and how to post it. (code option!)

When you want to post all lines of the logfile use pastebin, read here how to do this:
https://www.sas1946.com/main/index.php/topic,39780.msg627220.html#msg627220


Wishing you all the very best, Pete.

[Bison_M]

Thank you all for your feedback. Initially, as an example, I used the D3A1 Val. All parts names are respected, although maybe I missed something. CAP stubs are created, they also do not appear. Perhaps there are errors in the meshes responsible for damage, but D1-D2 damage is visualized. All parts disappear at the moment of separation from the main model. And yet, there is no correlation of damage with the flying model. A plane can fly without a tail or without a wing, although pilots jump out.
Regards T.V.
Google translation

Атрибут Separable в hier.him отвечает за отделение меша (Tail1_D0) при его повреждении для замены его на следующий меш повреждений (Tail1_D1) или полное его отделение от корня при повреждении.

Например:

Code: [Select]

[Tail1_D0]
Mesh Tail1_D0
Parent CF_D0
Separable
Attaching 1 0 0 0 1 0 0 0 1 0.00775 8.13663 -0.36824
CollisionObject xtail1
CollisionObject .xxcontrols5
CollisionObject .xxcontrols4
[Tail1_D1]
Mesh Tail1_D1
Parent Tail1_D0
Hidden
Separable
Attaching 1 0 0 0 1 0 0 0 1 0 0 0
CollisionObject xtail1
CollisionObject .xxcontrols5
CollisionObject .xxcontrols4
[Tail1_D2]
Mesh Tail1_D2
Parent Tail1_D0
Hidden
Separable
Attaching 1 0 0 0 1 0 0 0 1 0 0 0
CollisionObject xtail1
CollisionObject .xxcontrols5
CollisionObject .xxcontrols4
[Tail1_D3]
Mesh Tail1_D3
Parent Tail1_D0
Hidden
Separable
Attaching 1 0 0 0 1 0 0 0 1 0 0 0
CollisionObject xtail1
CollisionObject .xxcontrols5
CollisionObject .xxcontrols4
[Tail1_CAP]
Mesh Tail1_CAP
Parent CF_D0
Hidden
Attaching 1 0 0 0 1 0 0 0 1 0 0 0
The Separable attribute in hier.him is responsible for separating the mesh (Tail1_D0) when it is damaged, to replace it with the next mesh (Tail1_D1) for damage, or completely separating it from the root if it is damaged..

[tvister]

Thanks Bison! The problem was really Separable.

[Mission_bug]

Great to know all is now working.

Alex to the rescue again.


Wishing you all the very best, Pete.

[tvister]

Thanks. I looked at the corrected model in the game, many shortcomings were revealed. I will correct it.