Another issue i think

[Angelus1971]

In previous version of MCX, when I imported an FS9 aircraft, I got the import dialogue box (see attached) - version 05/2016on e2bcf DEV 23/05/2016

But in the new version 1.4.0.0.c4e4ecf0 DEV 24/05/2018 the import dialogue box does not appear.

I'm importing the same FS9 aircraft.

 

[arno]

Check what value the use conditions option has. When set to user defined you will get the dialog.

 

[tgibson]

As Arno says, there is a new line in the Options, Use Conditions. That needs to be set to User Defined to get the same behavior as before.

Arno, perhaps User Defined should be the default until the new setting is fully debugged?

 

[robystar]

It already is for me, Tom.
It probably depends on the last settings you had before updating.

 

[arno]

User defined is the default indeed. The setting is not new either, it's there for years already. Such the visibility condition option is new.

 

[Angelus1971]

Hi, Thanks for the help. Got that working again.

Got another silly question. How to you reduce the size of a models crash tree? I find that on some mdl's, mine included, the crash tree goes for hundreds if feet past the aircraft in some cases while some objects are nice and neat. I cant find anything that affects the crash tree boxes. Does anyone have any ideas please?

I'm also getting an unhandled exception error when loading an MCX converted model into the mdl tweaker
************* Exception Text **************
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at ASToFra.FSUtils.RIFFObject.ReadChildren(RIFFSection riff, Int32 parlen)
at ASToFra.FSUtils.RIFFObject.Read(String filename, Dictionary`2 formatInfo)
at ASToFra.ModelConverterX.MDLTweakerForm.cmdMDLFile_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

[arno]

Hi,

The crashtree is calculated by xtomdl from the geometry of your object, you can't influence the size.

Which version of MCX are you using and to which FS version was the mdl exported when you get the crash?

 

[Angelus1971]

not sure why its calculating it wrongly then - I've attached a picture of what its doing. Its extending way below the heli. on another a/c, not one of mine - it literally goes for miles past the extents of the aircraft.

I'm using version 1.4.0.0.c4e4ecf0 DEV 24/05/2018

 

[arno]

Scaling on scene graph nodes can result in wrong crash boxes. But I have improved MCX a few months ago to minimize that. Maybe you still have some of those nodes.

Which mdl format you used with the crash?

 

[Angelus1971]

Hi

Sorry forgot to say - It was the FSX mdl

Scaling on scene graph nodes can result in wrong crash boxes
- Can I delete the node?

 

[Angelus1971]

I've got another error - I thought i'd re-export the FSX MCX file againto see if it made any difference and got this following error

But as you can see, I've got a valid GUID (32 chars and 4 dashes). I'm confused.

 

[tgibson]

Perhaps there is a hidden character in there. Delete it and retype it into MCX, or have MCX generate a new one.

 

[arno]

Hi,

That's a weird error. Did you edit the guid? Else you should not get such errors.