-
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.
Flashing Lights
- Thread starter Foxi
- Start date
Not directly; the data entry dialog disables the directional controls for beacons.
However, it appears that if you created an array definition containing a beacon and specified the directional requirements, those requirements would be implemented when the models are created. Alternately, create a beacon using the dialog and manually edit its .ini file (a text file).
No guarantees, but from a cursory review of the code, it should work.
Don
However, it appears that if you created an array definition containing a beacon and specified the directional requirements, those requirements would be implemented when the models are created. Alternately, create a beacon using the dialog and manually edit its .ini file (a text file).
No guarantees, but from a cursory review of the code, it should work.
Don
Glad to hear it worked for you. There is no technical reason for not allowing for directional capabilities. It just didn't occur to me anyone would need a directional beacon. I will remove that restriction in the next release.
But, I am curious about your comment re AltitudeIsAGL. The Make Array capability sets that variable to True - suggesting you want it set to False - which is problematic other than when done "by hand".
If all you want is a simple, directional flashing light referenced to airport elevation (as opposed to on a tower referenced to ground elevation), another way to accomplish that is to create a new element type to which is attached a custom effect having the desired flashing light characteristics. The AFLT user manual includes instructions for doing so.
Don
But, I am curious about your comment re AltitudeIsAGL. The Make Array capability sets that variable to True - suggesting you want it set to False - which is problematic other than when done "by hand".
If all you want is a simple, directional flashing light referenced to airport elevation (as opposed to on a tower referenced to ground elevation), another way to accomplish that is to create a new element type to which is attached a custom effect having the desired flashing light characteristics. The AFLT user manual includes instructions for doing so.
Don
Oh, I see what you are saying. Beacons specified in .def files should also have AltitudeIsAGL = False. I agree and will fix it. (But, when specified as an object using, say, ADE, the specified elevation is the elevation of the light above ground)
Don
Don