Releasing Dynamic Lighting for an airport

[nidaren]

Hello Everyone,

I would like to ask, if it is possible to use the Dynamic Lighting Library to release own Airport DL Patch?

I have made one for Drzewiecki Design EPWR airport.

Thanks!

[Kevin B]

Hello nidaren, yes you can, send it to us, we check it

Regards

[nidaren]

Hello,

Thank you for your answer. Please, find it attached below.

EPWR_nid_dynamic_lights_OBJ.bgl

[Kevin B]

I looked, great work, we will publish it

Thank you

Edited May 16, 2021 by Kevin B

[nidaren]

Hello, thanks!

What I would suggest - consider making the library license requirements a bit more lenient - as it is at the moment, it prohibits usage of it to any other projects than Dynamic Lightning posted on this site, even if you don't include any of the effects contained in it itself.

The problem with such strict requirement is that all in all, you don't really have any real influence on how people use it, since it is available for download freely.

What I think could be worth considering, is to allow the usage of the effects library, as long as it itself is not included and downloaded from your page, but only referencedin the project - like I did with mine - that way you get the traffic and exposure, while allowing modders to go creative.

This is the library license condition I have in mind:

• The use of these files are for iniBuilds Dynamic Lighting profiles only. The reuse, modification or decomplication of these effect files are not allowed without written consent from iniBuilds Ltd.

Could be changed to:

• The use of these files are for iniBuilds Dynamic Lighting profiles or could be used in your own modification as long as the effects contained within are not hosted elsewhere, decompiled and such. The reuse, modification or decomplication of these effect files are not allowed without written consent from iniBuilds Ltd.

I made some checks and your effects seem to be really light on FPS, which makes them desirable to be used more widely.

Another small tweak I would suggest:

• Consider adding ICAO identifier to the airports posted in your files section. Some of the city names can be misspelled or written using special characters and then it makes them unfindable in your searches.

(Sorry for the quality of my English,I am not a native speaker).

Thank you and have a good day!

Edited May 16, 2021 by nidaren

[nidaren]

I also thought about one more thing (It would not let me edit the last post):

Instead of dropping all your effects into main Prepar3d installation, you can create a true addon from it, the config file would look like that:

filename: add-on.xml

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">

<AddOn.Name>iniBuilds Dynamic Lighting Library</AddOn.Name>
<AddOn.Description>Contains effects required for dynamic lighting</AddOn.Description>

<AddOn.Component>
<Category>Effects</Category>
<Path>SomePathToExtractedFiles\Effects</Path>
</AddOn.Component>

</SimBase.Document>

That way you don't affect person's main installation, and make the usage clean, even for your own comfort when you want to remove an already existing effect. Makes it also so that there are less potential problems of people messing up the files and breaking their install.

It is then dropped into person's Documents\Prepared v5 Add-ons\iniBuilds Dynamic Lighting Library, and enabled at the next P3D run.

I have it set up this way and it works flawlessly 🙂

Edited May 16, 2021 by nidaren

[Kevin B]

Thanks for all these suggestions, for the rights I'll let @Sam see this,

For the Add-on.xml folder I never thought about it, it's a good idea, I'll do that later.

 

Regards,

[Sam]

Hi @nidaren,

Thanks for your comments. We won't be changing the effect library license terms. This is to ensure the quality and reputation of our dynamic lighting offerings.

However, we're happy to manually approve requests to use the effects (as we've done here) on a case by case basis.

As a reminder, this approval of usage is for EPWR only and credit, along with a link must be provided back to iniBuilds in the documentation of the patch.

[nidaren]

Hello @Sam,

Thank you for your answer, I understand the reasoning behind the current license conditions.

Quote

As a reminder, this approval of usage is for EPWR only and credit, along with a link must be provided back to iniBuilds in the documentation of the patch.

As I understood it from the answer of @Kevin B, it will be posted here, or do you mean that I should post it (host) myself and include the license terms conditions in a textual file and link to the library in it? If the latter is the case, would it be ok for you if I first post the text file here, to ensure it contains everything that is needed?

The patch itself does not contain the library and only reference the effects and a location (meaning the end user must already have the library for it to work at all).

Thank you.

Edited May 17, 2021 by nidaren

[Sam]

Hi @nidaren,

I've reached out to you via DMs where we can discuss this further!