• 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.

P3D v2 Model Log; Question: Callback Parent Mouserect

Messages
10,163
Country
us-arizona
Hey all,

Just going through my model log (exported with 3DS Max 2014, V2.x SDK, animation issues) and I find a lot of *Callback Parent Mouserect* warnings. Anyone heard of these and know what they might be?


Example;

warning : Exporting: Callback Parent Mouserect
warning : Exporting: Callback Parent Mouserect
warning : Exporting: CBNode InnerText
warning : (L:LJ24B ALT STANDBY SWITCH, bool) ! (>L:LJ24B ALT STANDBY SWITCH, bool)
warning : 1 (>L:XMLSND12,enum)
warning :
warning : Exporting: Callback Parent Mouserect
warning : Exporting: CBNode InnerText
warning : (M:Event) 'LeftSingle' scmi 0 == if{
warning : 1 (>L:LF24B NAV1 TEST,bool)
warning : 1 (>L:XMLSND12,enum)
warning : }
warning : (M:Event) 'LeftRelease' scmi 0 == if{
warning : 0 (>L:LF24B NAV1 TEST,bool)
warning : 1 (>L:XMLSND12,enum)
warning : }
warning : (M:Event) 'LeftDrag' scmi 0 == if{
warning : 0 (>L:LF24B NAV1 TEST,bool)
warning : 1 (>L:XMLSND12,enum)
warning : }
warning :
 
Bill, I've seen those as well. They are a bit confusing since despite the "warning(s)" they still work!
 
It has to be a 3DS "warning" because I have never seen this in Gmax. And my coding is exactly like you posted including the sound entries....
And that "warning" makes no sense!

Unless it's 3DS looking for parent entries and warning you, lol
I noticed all 3 warning have the same sound entry!
Might be the sound entries using Enum.
 
That is unlikely. Those sound entries are making calls to my licensed sound module. The L:vars use the unit "enum" because there are three expected values for each call; 1, 2, or 3.
 
I wonder if this might have something to do with my malfunction of switches that is occurring?

I wonder what would happen if I un-linked them from their parent? The parent is the LH side of the instrument panel; switches and knobs are all attached to the panel, the LH unit. I wonder if that is starting to cause an issue, perhaps too many parts attached to one parent? (Off to check that out).

EDIT: I unlinked a great deal of switches from the main LH panel and the switches are still unaffected, the ones that were not animating properly are still not animating nor mouse-recting. However, they no longer show up in the warnings on the log. Odd.
 
Last edited:
Back
Top