Hi peoples I was wondering if anyone else has come across this problem. I have created a custom FSX <visibility> animation to control some gauge polygons in my VC radio stack. I have inserted the new animation code into the modeldef and attached the animation to the polygon using the attachpoint tool in 3DS. This works fine the visibility of the gauge polygon is nicely controlled by the C++ gauge logic. However as soon as i attach the visibility parameter to the gauge polygon all the mouse click points on the gauge become inactive the mouse courser dosent even change indicating the buttons are clickable. i can still control everything from the 2D panel but cant click on anything in the VC.Here is the modeldef code i am using <PartInfo> <Name>navcom_lights_on</Name> <Visibility> <Parameter> <Code> (L:NAVCOM_POLY, bool) 0 == if{ 1 } els{ 0 } </Code> </Parameter> </Visibility> </PartInfo> <PartInfo> <Name>navcom_lights_off</Name> <Visibility> <Parameter> <Code> (L:NAVCOM_POLY, bool) 0 == if{ 0 } els{ 1 } </Code> </Parameter> </Visibility> </PartInfo>Any ideas on this would be greatly appreciated CheersPaul

Since you mentioned the Attachpoint tool, I'm assuming that you are modeling in either Max or GMax.There are several possibilities you might try.1. make certain that your eyepoint isn't "inside" the headrest of the seatback. Try shifting your eyepoint manually to see if that works.2. create a small triangle poly at your model origin (0,0,0) and apply the Attachpoint Visibility to it, then Link your actual gauge polygon to the control node.

Hi billThanks for the reply yes indeed i am using 3DS max unfortunately i have already tried both of your suggestions. If i remove the visibility properties from the model the gauge works fine again so i know its not a viewpoint issue but i did try moving the eyepoint any way. I have also tried the control polygon and linking the gauge poly to it but it has the same effect, mouse clicks stop working. it really has me stumped.cheers Paul

Try creating a new gauge polygon for your radio stack, and suspend it in "space" (that is, hanging above the glareshield) and test from there. It may be that other geometry in the area around the radio stack is causing a problem.If that works, then try moving your "real" gauge polygons slightly so they "float" apart from the surrounding polygons.We are currently experiencing a somewhat similar problem with a model that was created by FSDS v3.51. Only a few gauge polys are behaving oddly, and that is only when battery power is turned on! What is truly odd is that I can use the exact same XML scripts in a "test panel" I ginned up quickly in Max7 and have had ZERO problems. Also, the exact same process works for the released FS9 version of the same aircraft... :( I've had remarkably few problems with any of my GMax models... Since both Max and FSDS use the same export module from the SDK (GMax uses a different export module), I've beginning to wonder if the problem might lie there... :(

Cheers at least im not the only one :( will have a go at this in the morning and let you know how i goPaul

I Think i may have solved the problem looks like it was an issue with the draw order i enabled Z-Write Alpha option in the lit gauge material at it seems to be working now YYYYAAAAAThanks again for all the help and suggestions Paul

I Think i may have solved the problem looks like it was an issue with the draw order i enabled Z-Write Alpha option in the lit gauge material at it seems to be working now YYYYAAAAAThanks again for all the help and suggestions Paul

Wow, I'm certainly glad you found the solution for your specific problem... :( With some luck it may well prove to be helpful for anyone else with the same issue...Several years ago I encountered a situation where an Attached mouse point simply would not be detected by the mouse in the VC. I never even though about trying Z-Write Alpha... :(