• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3Dv4.4 MDL import/export corrupt mouse rectangles in VC model

roland_lfor

roland_lfor

Messages
118
Country
france
Hello Arno,

It seems that there is something wrong when exporting a VC model in P3D 4.4 format.

Some of the mouse rectangle capture areas are in the wrong place or are not working anymore.
For example:
- the pressure altitude rotating knob now move the flap lever
- the heading rotating knob is not working anymore

I first thought it was due to my modifications done on the VC model, so I tried a simple Import / Export operation without changes between and the problem is still there.

* The model imported is a native P3Dv4.4 model with PBR textures
* The SDK is the last from LM - version 4.5.13.32097
* The Prepard3D version is the v4.5 HF2
* ModelConverterX is the last version (today's download), but the issue is there at least since the last 2 released versions (did not try before)

Thanks
 
I forgot to join the MCX Log, here is it.
I see that there is some lines on the mouserect events, maybe usefull.
 

Attachments

Other Test results:
- Import/Export of a native P3Dv4.0 VC model makes the same issue, so it's not specific to 4.4 with PBR
(tested with the Majestic Q400 Pro)
 
OK, would you be able to make a simple test model that also shows the problem? E.g. only one or two mouse rectangles? That would make debugging easier.
 
Yes, but a complete aircraft is hard to test. So would it be possible to make a simple test object with only a few mouse rectangles that also shows the bug?
 
Do you also see this issue with some of the default P3D models? All models you refer are addons that I don't have, so I can't test the issue here. Or like I said before a simple test model would be even better.
 
Hello Arno,

I tried with the following default P3D aircraft: J3-Cub, Mooney Bravo, Maule.

I don't see any issue with any of them after import/export in P3Dv4 format.
I wonder which property raises the issue on complex addon aircraft. Both cases use custom DLL and dynamic textures.
 
Last edited:
Hi, I guess it must be something in the specific mouse rectangle definitions then that gives the issue.
 
How can I help finding the cause?

Could custom_anim be the cause?
It seems that I have issue only with rotating knobs.
 
In principle the custom definitions should be OK. What you could do is compare a specific knob before and after export to see if the definition changed.
 
Hi,
I have exported with MCX the original MDL to an X file, then tried to find some <MouseRect> sequence as found in the SDK documentation.
This sequence does not exist.
How can I find them? Is there other possible type of MouseRect declaration in the X file?

Is there a SDK tool to transform a MDL into an X file?

Sorry I'm a newbie in VC panel.
 
Ok, I think I have to export both "ModelDef.xml" from MCX (original and exported) and compare MouseRect definitions.
 
You can also compare in the hierarchy and modeldef editors in MCX itself if you load the two mdl files.
 
Compared both ModelDef.xml with WinMerge: The Exported miss several <PartInfo> sequences beginning from line 5388 (in Original file).
Also - not related - I see that many <Animation @length> are changed to '360'.

Here is a zip containing both ModelDef.xml exported with "Used only" option.
 

Attachments

Hum, I just wake up on understanding how all this is working, reading the pinned thread about "visibility conditions" :rolleyes:
It's possible that the original model uses an enhanced ModelDef.xml.

Does it means I'm supposed to:
  1. load the original model
  2. Export the eventually enhanced ModelDef.xml to the SDK folder
  3. make my modifications
  4. Export the new MDL using the enhanced ModelDef.xml
?
 
MCX uses its own internal modeldef.xml representation which includes all custom entries after loafing the model. When you export that one is used. So there should be no need to update the SDK one.
 
Ok thanks.
So assuming the issue is related to a MCX bug, tell me if you need a MDL to debug and I can send you a download link through a PM.
 
Having a test model should help, if you can tell me which knob or lever gets broken on export.
 
You must log in or register to reply here.
Back
Top