Hi,

I was was wondering if anyone would have an idea on what effect file or texture has changed this on the PMDG service fleet. The beacons are now GREEN.

It is not limited to this and I have a sneaky feeling it was after I installed a Virtual Col Embraer. I guess the way to remedy this is to install the standard effects and textures folder but if anyone know which specific file this might be, it would be much appreciated. I have attached a screenshot and you might have to zoom in.

Edited March 27, 20206 yr by Steve_Ellis

Have you tried reinstalling your PMFG a/c to see if that fixes the problem?

Not as yet, looks like i may have to though, although its not just the PMDG vehicles it is affecting,

28 minutes ago, Steve_Ellis said:

Not as yet, looks like i may have to though, although its not just the PMDG vehicles it is affecting,

Sounds like one (or more) of the default effect lights got overwritten. Look for a green effect light with a different date from the others. Possibly renamed to *.OFF or something else to show difference from other files in that folder.

Maybe the VirtualCol Embraer installer made a text file listing the filenames it installed and their location. Usually located in the same folder as the uninstaller executible.

Have a backup?

This occurs when some developers by mistake replace the FX_1.BMP and FX_2.BMP inside the P3D\Effects\Texture default folder or when they install via the add-on.xml method textures with the same names (FX_1 or FX_2).

I find it extremely annoying as this is against P3D / SDK recommendations.. it is not that difficult to create your own textures and effects for god sake!

To Fix:

• Disable the last installed add-on via the .xml method. If the problems goes away, then that is the culprit.
• If the above fails, perform a "content" repair. It will restore the original FX_1.bmp and FX_2.BMP.

How I know this? effects is my area of expertise.. it is the add-on;s I build all the time!.

Regards,
Simbol

Well some success

I replace the FX1 and FX2 files as I had a backup of these but this was not the cause. I then replaced the beacon fx files but that did not seem to work either.

I ended up reparing the P3D content and this has fixed my issue but still do not know what caused the issue in the first place.

Thank you Simbol, Twenty6 and pgde you all for your help  and suggestions

16 minutes ago, Steve_Ellis said:

Well some success

I replace the FX1 and FX2 files as I had a backup of these but this was not the cause. I then replaced the beacon fx files but that did not seem to work either.

I ended up reparing the P3D content and this has fixed my issue but still do not know what caused the issue in the first place.

Thank you Simbol, Twenty6 and pgde you all for your help  and suggestions

When you replace these files it requires a P3D re-start.. maybe that is why..

Anyhow glad to know you got it fixed.

S.