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

How to kill shadow in array

Mr.Crocodile

Mr.Crocodile

Messages
243
Country
italy
Hi all, initially I didn't understand why some long shadows appeared using buried towers/supports but reading with more attention on the user manual I found that it is a normal behaviour if the shadow is not killed.

Now I would like to know which switch is to be indicated into the .def file to kill the shadow because I noticed that the .ini file generated when I make the array contains "Kill Shadow=False". If I change it manually in "True" before generating the library all is ok but if I forget it, when I need to generate the array again, the .ini file changes again the switch to False and the long shadow appears again.

Or is there another way to do it permanently using the array?

Thanks
 
You seem to have discovered a "hole" in the design of AFLT. There is no way to kill shadows for array objects individually. The workaround (for the moment) is to kill the shadow in the design of the .mdl file. (You'll note that none of the AFLT-stock objects of the type about which you are concerned cast a shadow, like strobe and approach lighting towers, cast a shadow.)

I will be releasing an update for AFLT shortly. (As I reported in another forum, I've just found the "recipe" for custom lighting in P3D v4.) I'll add a NoShadow option for array objects in that release.

Don
 
Hi Don, thanks for the immediate answer. When you talk about killing the shadow in the design of .mdl file you mean to change the .ini file as I did and explained in my previous message or there is something else I have to know?
 
Unfortunately, I read your earlier post a little too quickly and made an invalid assumption without checking the code.

It appears I made an "improvement" a while back that had in unexpected side effect. In an older version, when you clicked on the Element combo-box on the Main Panel, the list included all the array items and you could select individually which one's displayed a shadow and which ones didn't. In the currently released version, array items are not included in the list. So, for the time being, you will have to ensure the .ini item is set appropriately (it shouldn't change one you set it.)

As I said earlier, this will be fixed in the upcoming release. (With my work to implement a P3D version, I'm not in a position to release the fix just now - even though it's just a single-line change.)

Don
 
Mmm, ok. I think you're talking about the last version of AFLT. Actually I'm still using 1.1.0.3 because I'm working on an FS2004 scenery and there if I well remember there appear only normal items, not the array ones. Anyway thanks for the moment
 
I don't recall how long ago I made that change. Now, obviously, it was at least back as far as 1.1.03.

The fix is already in; I just can't release it yet.

Don
 
You must log in or register to reply here.
Back
Top