Jump to content

Recommended Posts

Normally, I'd post this in the regular WIP thread, but as I want opinions and options (and maybe help), I'm doing a new thread. (

What I've done is, take the Nesher LOD and convert it to the Mirage 5F that eventually is used by the AdA.  Yes, I do know there's a AI-only 3W version. But I"d like to have a TMF one for everyone.

Has the right shape, with the pitot tube under the nose. Also has all the "correct" hardpoints, and I've even found and used a proper cockpit (also TMF -- thanks to BPAO and Crusader). Unfortunately, it has 2 extra blade antennas; one of the spine the other under the nose. I've been able to remove the lower unit, but for some unknowable reason the upper one refueses to disappear!!

Using Mue's fantastic LOD viewer, I was easily able to ID the 2 meshes. Below are the statements for the 'remove component' trick

Quote

//antenna removals//

Component[008]=Hide1
Component[009]=Hide2

[Hide1]
ParentComponentName=fuselage
ModelNodeName=Objet03
DestroyedNodeName=Objet03
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE

[Hide2]
ParentComponentName=fuselage
ModelNodeName=tacan
DestroyedNodeName=tacan
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE

and yes, I double checked spelling for the meshes, and numerical sequencing for the component listing! Shoot, I even switched them around just to be sure

"tacan" is the upper antenna, "objet03" is the lower. You can see in the picture below, the lower unit has vanished.

So, the questions are:

anyone have any other ideas? I'll be glad to send the bird over for examination

if it can't be fixed, would you all accept it "as is"? Right now, everything works (even the RWR)

thanks!

mirage5f-tmf.JPG

Share this post


Link to post
Share on other sites

This may or may not be the cause... but it looks like in the main LOD I grabbed from the link below there are two 'tacan' meshes in the model, one linked to the fuselage and another linked to the VertTail, could that be it?

image.thumb.png.a203b2a140b2ccfb135c59cced7d3b8a.png

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)

The reason the tacan mesh is not removed by the component trick is there's another mesh named tacan on the vertical tail.

The "Hide2" component removes the tacan of the tail.

I tried to add a third component 

[Hide3]
ParentComponentName=VertTail
ModelNodeName=tacan
DestroyedNodeName=tacan
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE

but it didn't solve the issue.
Once the tacan mesh of the tail is removed, the other tacan mesh of the fuselage stays ( ---> see the fix below)

Add "MassFraction=0.0" to all removing / hiding / showing components.

-------------------------------------------------------------------------------------------------------------------------------------

Edit :

Jimbib beat me to the line xD

664323c7d37c3_Nesherwithoutantennas.JPG.69052748a84fce60f8597b28c110567b.JPG

Try this :

//antenna removals//

Component[008]=Hide1
Component[009]=Hide2

[Hide1]
ParentComponentName=Nose
ModelNodeName=Objet03
DestroyedNodeName=Objet03
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

[Hide2]
ParentComponentName=Nose
ModelNodeName=Nose
DestroyedNodeName=tacan
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

---------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------

If you want to remove both tacan meshes :

//antenna removals//

Component[008]=Hide1
Component[009]=Hide2
Component[010]=Hide3

[Hide1]
ParentComponentName=Nose
ModelNodeName=Objet03
DestroyedNodeName=Objet03
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

[Hide2]
ParentComponentName=Nose
ModelNodeName=Nose
DestroyedNodeName=tacan
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

[Hide3]
ParentComponentName=VertTail
ModelNodeName=VertTail
DestroyedNodeName=tacan
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

Edited by Cliff7600
  • Like 5

Share this post


Link to post
Share on other sites

Great solution Cliff! Didn't know that was possible with two meshes with the same name, this would be a good addition to the knowledge base.

  • Thanks 1

Share this post


Link to post
Share on other sites

I'd have never thought of that!! Who knew you could have 2 with the same name!

I'm gonna go test this RIGHT NOW!!!

thanks gents!! :good:

  • Like 2

Share this post


Link to post
Share on other sites

yup, that sure did work!! the secondary tacan fins are/were the 2 flat features on the fin. I always thought they were some kind of stabalizer goodie!!

again, thanks brothers!! I owe you both a beer!!:drinks:  and, of course, you'll be 'mentioned in dispatches' in the readme!!

mirage5f-early-tmf.JPG

  • Like 5

Share this post


Link to post
Share on other sites
Posted (edited)

After checking, the entries need the "ShowFromCockpit=TRUE"

Component[008]=Hide1
Component[009]=Hide2
Component[010]=Hide3

[Hide1]
ParentComponentName=Nose
ModelNodeName=Objet03
DestroyedNodeName=Objet03
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

[Hide2]
ParentComponentName=Nose
ModelNodeName=Nose
DestroyedNodeName=tacan
ShowFromCockpit=TRUE
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

[Hide3]
ParentComponentName=VertTail
ModelNodeName=VertTail
DestroyedNodeName=tacan
ShowFromCockpit=TRUE
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

 

Edited by Cliff7600
  • Like 1

Share this post


Link to post
Share on other sites

For my education, what should be in the "ModelNodeName=" entry ? Same as the line before in "ParentComponentName=" entry or the one after "DestroyedNodeName=" ?

Usually, in other mods,  it is the one after, which makes sense because the one after is also a node name, whereas before it is a component name. Here above I see the 2 options.

Share this post


Link to post
Share on other sites
Posted (edited)

[Hide1]
ParentComponentName=Nose
ModelNodeName=Objet03
DestroyedNodeName=Objet03
DetachWhenDestroyed=TRUE
HasAeroCoefficients=FALSE
MassFraction=0.0

is the usual way to delete a mesh by ini.

So "ModelNodeName=" entry should be the same as "DestroyedNodeName=" and is the mesh you want to remove.

The "ParentComponentName=" is a component as you said but in this case the components Nose and VertTail have the same name as their main mesh.

Edited by Cliff7600
  • Thanks 1

Share this post


Link to post
Share on other sites

So Hide1 section is correct but Hide2 and Hide3 have the wrong "ModelNodeName=" in the example above. Thanks for the confirmation !

Share this post


Link to post
Share on other sites
34 minutes ago, pvince said:

Hide2 and Hide3 have the wrong "ModelNodeName=

Not in this precise case, turning the TMF Nesher into a TMF Mirage5F. The starting issue is to remove the tacan mesh form the top of the fuselage.

  • Thanks 1

Share this post


Link to post
Share on other sites

Ok, got it now, 'taca'n are 2 sub-NodeNames of 'VertTail' and 'Nose', that are also NodeNames. I skipped too fast the initial part. Thanks !

  • Like 1

Share this post


Link to post
Share on other sites

It's in for repairs right now, as I was informed I'd made some errors, both in forgetting the model builder and uploader for the cockpit (corrected in the read me now)

but it needs to use barracuda and phimat pods on the outer stations, and I'm jiggering around the hardpoints and groups. Hopefully, back up by week's end. I hope!!

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..