Dear Simbol,

I have changed my most FSPXAI models for A330/340/380/777 to TFS models V2.1 (without wingflex) and all works perfect now. TFS models greather V3 works not, because wingflex and embedded effects in model.

1. Question: Your program realize lights only via light sections in aircraft.cfg? If effects are used embedded in models (and if that effects reference to P3D standard effects) are also realized by your program during scan process?

In my prevoius post you wrote:
... Regarding FAIB, are you using wing flex or non wing flex? Wing flex models attach effects via the Model and again limitations will occur. Another thing to check is to be sure you don't have a effects names conflict. Be to use the expert interface, as it forces individual effects names, etc. All our tests with FAIB NWF are successful...

2. Question: Where I find in the expert interface the individual effect names, to see, if ther eis a conflict?

TFS model maker say to me, I can delete the wingflex and effects from model via ModelConverterX and put light position in aircraft.cfg. Will you program then realize the models and integrate your lights?

Thanks.

Best regards

Oliver

 

20 minutes ago, airbusa said:

1. Question: Your program realize lights only via light sections in aircraft.cfg? If effects are used embedded in models (and if that effects reference to P3D standard effects) are also realized by your program during scan process?

AILRP will detect all lighting configuration in accordance with P3D SDK guidelines. These include effects attached via the model using 3DSMax, however as I explained before on these forums there are some limitations of what you can do with effects attached via the .MDL specially if these are using the default system effects names IE: fx_navred.fx. This effect is used by other airplanes and since it is attached with that name it means any settings you perform to this effect is shared with such models.

It also affects the Live Preview Module and accordingly you will see a warning on this regard. This is because all effects under P3D are cached so as soon as you fire the effect fx_navred.fx P3D will cache all the settings (texture, parameters and all settings for this effect.), and since the effect is attached via 3DSMax with a fixed name, you cannot create a temp effect to show you how the configured setting might looks like at runtime. As a consequence AI models with effects attached via 3DS are not recommended to be used to preview your settings directly inside P3D.

However they will work, as soon as you click Apply AILRP will prepare effects for these models using your desired settings and ask you to restart P3D so the cache of the effects is flushed and you will see these AI models having great lighting.

FAIB wingflex models use custom effects names for their models (as you should!), for example FX_FAIB319_NAV_Red. This allows these models to avoid effects names conflict with other AI models and being able to have it owns settings if you want to do so. However they will not be great for live previews for the reasons explained above.

The reason I recommend non wing flex models, is because such models gives more flexibility in terms of lighting as a general rule of thumb and avoid all the limitations explained above. But AI Lights Reborn Professional edition is a clever and complex software able to understand the entire configuration of your AI Models lighting as long as they are P3D SDK complaint.

It is great the TFS model maker is willing to collaborate, tell him to get in touch with me at [email protected], so I can share technical details with him as we will be able to understand each other easily. Although as far as I am aware all his models work great with AILRP already.

Hopes this helps to understand things better.

Kind Regards,
Simbol

Thanks Simbol for explanation, then I know now that standard effects will be also be usd by your program (as long as they compliant with SDK).

Also usefull information, that in case of effects embetted in model, that a restart of P3D is necessary to show the replace effect in the Preview mode.

Best regards

Oliver

1 minute ago, airbusa said:

Also usefull information, that in case of effects embetted in model, that a restart of P3D is necessary to show the replace effect in the Preview mode.

A restart of the sim is required to flush the cache of the effects and see the effects changes in the simulator.. it doesn't matter if you are using the Live Preview mode or not because If P3D was already running it is very likely that some effects has been caught by the cache (specially if they are default names). This is why when you click "Apply" AILRP is telling you to  restart P3D 😉.

S.