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

Compiling BGL_LIGHTS Broken

Messages
70
Country
unitedstates
While trying to compare the Effects lights to the BGL_LIGHTS performance and appearance, I found that anything with a model failed to appear in FSX but the LIGHT ONLY elements compiled and appeared fine.

Compiling options

Omni Blue, BGL_LIGHT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, No Format Override
Result = Nothing in sim

Omni Blue, BGL_LIGHT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, All-In-One Override
Result = Nothing in sim

Omni Blue, BGL_LIGHT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, Effects Override
Result = Working in sim

Omni Blue, EFFECT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, No Format Override
Result = Nothing in sim

Omni Blue, EFFECT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, No Format Override
Result = Nothing in sim

Omni Blue, EFFECT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, No Format Override
Result = Working in sim

Omni Blue, EFFECT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, All-In-One Override
Result = Working in sim, light on ground instead of lamp housing

Omni Blue, EFFECT, No. Lights=1, All-In-One=False, Light Only=False, Kill Shadow=False
FS9 Models, Effects Override
Result = Working in sim
 
I found that anything with a model failed to appear in FSX but the LIGHT ONLY
As noted in the manual, effects do not yet work with FSX models. All-in-one always uses FS9 models.

Regarding the others, All I can say is that I have not observed such difficulties. I will, however step though your resukts line-by-lime to confirm.

Don
 
Aaron, the only fault I have been able to duplicate is the elements designated as an effects with All-in-one override. where the light seems to loose its attachpoint coordinates .

That will be fixed. The other thing I noticed is on the main panel, when you check the Effect radio button, the No. Light textbox should be disabled and it is not. This, however, is purely cosmetic and inconsequential otherwise.

Regarding the other failure modes you noted. It would be helpful if you determined a reliable sequence of steps to force those errors. Incidentally, your items 3, 4 and 5 appears to be identical in setup but show different results. Perhaps there's a typo in there somewhere.

Don
 
There was indeed a problem when light elements specified to use effects were overridden as All-in-one. Development release 1.1.00(j), just posted at http://stuff4fs.com addresses this.

Other than the light source, there is no (and never has been any) difference between a light based on an effect and that same light based on BGL_LIGHTs with all-in-one override applied. So, form this development release forward, all-in-one will only apply to BGL_LIGHT-based lights. On the main panel, if Effect is selected as light source, the All-in-One checkbox is disabled.

Don
 
Thanks for testing and reporting Aaron. I plan to make the general release this weekend. It will also include update of effect colors when a RGB in the Colors.txt file is changed.

Don
 
will the altered effects light files be copied to the output directory of where the library is being compiled or will it just change the ones in the effects folder in the AFLT directory? Maybe a lookup of the fs version from registry for the slected versions path so it will copy the files during compile...
 
The effect files in the Effects folder for the version of FS for which you are creating the library are updated each time you create a library.

Don
 
for some reason I thought I read in the readme the installation requires you to copy the effects and the texture files to the flight simulator directory... didn't realize that you were doing that at compilation... awesome
 
I read in the readme the installation requires you to copy the effects and the texture files to the flight simulator directory
Yes, on initial installation

didn't realize that you were doing that at compilation
I'm not. I read the current version of the effect from the Flightsim Effects folder, update the colors as necessary and save it back there. I decided against doing the updates in the user's AFLT\Effects folder and copying from there at compile time because any changes a user makes to effects would then have to be made in that folder. Anyone "smart" enough to tinker (intelligently) with effects is likely to do so in the Flightsim Effects folder. As well, copying effects from the AFLT folder would necessitate an otherwise unnecessary recompile simply to get the updated effect into the Flightsim Effects folder and would overwrite any changes made directly in the Flightsim Effects folder. So, I decided the simplest way was to continue to have the user install the effects in the Flightsim Effects folder initially and, thereafter, work solely with the Flighsim Effects folder.

Don
 
Back
Top