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

FSXA Make Mouse Pass Through Object

Messages
466
Country
us-california
Is there a way to make an object "invisible" to the mouse interaction? For example, an invisible polygon is over a box, but you need to be able to click the box. You wouldn't be able to because the polygon is in the way.
 
Click the box to make the polygon visible and clickable, then click the polygon to make it invisible again?
 
Thanks for the replies, guys. I guess I should have explained this a little better. I've created a quick demo scene and added a screenshot below:

63RVhuV.png


My problem pertains to interaction in FSX, not 3DS Max. I need the mouse to pass through the purple polygon so that the blue box can be clicked below it in-sim. Ideally, the polygon needs to be bigger than the clickable box, which is why I didn't just make the polygon a click spot, too. If there isn't a solution, I can just shrink the polygon. However, there are a lot of these, so I was hoping for an easier solution, as it would require lots of remapping to change the size.
 
I still don't quite understand what the polygon is supposed to do in-sim. Is this a lightmap that's supposed to be above the cockpit geometry?
 
Hmm.. I may see where this is going as I may face a very similar issue that involves light maps on VC parts...
WE have
1- a polygon for a light indicator, OFF state. can be clicked to test. Upon mouse release, test is over, light goes off
2- another poly on top of this with a light map applied. This is the light in ON state.
problem. when clicking on 1, 2 appears in front obscuring the mouse. This makes 2 disappear. test lasts only a frame.
I can't apply a gauge and have to use a 3D part, because light maps make transparency (0,0,0) of gauges and vc backround go black. the off state can't have the lightmap since the light is whit when OFF and a color when ON (Red, green,blue,yellow...)

Perhaps the OP is facing a similar issue...
 
I still don't quite understand what the polygon is supposed to do in-sim. Is this a lightmap that's supposed to be above the cockpit geometry?

It's going to be used as an annunciator light that is controlled by a gauge (there are many annunciators and they can have varying brightness, so using multiple objects would be overkill). The user will need to be able to click a button below the light in some cases. I have done all of the current ones with square polygons that in some cases, extend past the button (mostly was for ease when mapping). I could of course redo all of them to fit within the bounds of the buttons and tag them with attach points, but I was hoping there would be another (quicker) solution.
 
It's going to be used as an annunciator light that is controlled by a gauge (there are many annunciators and they can have varying brightness, so using multiple objects would be overkill). The user will need to be able to click a button below the light in some cases. I have done all of the current ones with square polygons that in some cases, extend past the button (mostly was for ease when mapping). I could of course redo all of them to fit within the bounds of the buttons and tag them with attach points, but I was hoping there would be another (quicker) solution.

Why not simply make the light polygon clickable?
Parts can have both mouse rectangles and visibility conditions applied.
 
It's going to be used as an annunciator light that is controlled by a gauge (there are many annunciators and they can have varying brightness, so using multiple objects would be overkill). The user will need to be able to click a button below the light in some cases. I have done all of the current ones with square polygons that in some cases, extend past the button (mostly was for ease when mapping). I could of course redo all of them to fit within the bounds of the buttons and tag them with attach points, but I was hoping there would be another (quicker) solution.
I don't think there is any way around that. You'll have to use the invisible poly for the click spot. Remap them and be done with it. :(
 
I think a polygon with a $panel texture can be clicked if it's behind a polygon that is not clickable. I've got a VC model in which I can manipulate the HDG knob despite the yoke being in the foreground.
 
Back
Top