Thanks Gary!
Using the (
MCX)
Attached Object Editor I got halfway there at least.
Some effects however don't show up in MCX. All you see is the attachment point and then there's no light or any effect there. Maybe some issue with a parameter or something perhaps?
That is difficult to determine, as there are many variables which may influence run time display (or non-display) of Effect *.FX files, whether attached via AttachPoints in MDLs, or whether an AttachPoint "equivalent" is coded via BGLComp XML code in a 'placement' BGL.
In the case of P3D v2.x / v3.x, one may need to review not only the latest P3D Special Effects SDK documentation:
http://www.prepar3d.com/SDK/Environment Kit/Special Effects SDK/Creating Special Effects.html
...but also posts on this topic of new considerations for use of Fx with P3D 2.x / 3.x by Don Grovestine as cited above:
http://www.fsdeveloper.com/forum/threads/effect-library.437944/#post-750745
...and posts on Special Effects by Larry Robison (aka "L_Rob") as this Google search finds them at FSDeveloper:
https://www.google.com/search?q=sit...-AEBmAIAoAIAmAMAkgcAoAcA&sclient=gws-wiz-serp
Do the effect (.Fx) file need to be in the effects folder of P3D for it to show up in the MCX preview? Probably not right?
Yes, all FX files must be in the [FS install path]\Effects sub-folder, and all mapped textures for those Effects must also be in the [FS install path]\Effects\Texture sub-folder, so that all such scenery content can be read / indexed when FS is started.
CAVEAT: If you add 'new' Effect content such as copied /edited / re-named or newly-created *.Fx files and/or any textures mapped to them, they must be in their respective sub-folders (as cited immediately above)
before FS is (re-)started, so that all such scenery content can be read / indexed ...or they may not be displayed in FS at run time.
NOTE: To re-start FS (
not re-start a flight from FS' main menu), one must exit FS completely, and
re-start FS from the Windows desktop.
I also downloaded AFLT (good tip on that software) It seems to have all of the effects I was looking for, but still the problem persists where they wont show up visibly in MCX after I place the effect using "Attached Object Editor".
After some trial and error at least I managed to get red obstruction lights (default effect) on some of my models so it's off to a good start at least!
I am not certain as to whether Arno's Fx Editor has been updated yet to be fully compatible with the constantly-evolving code base of P3D v3.x.
Perhaps Arno may wish to comment in this regard ?
I would recommend that you also try previewing and testing changes in Fx code parameter values in P3D at run time via installation and proper activation of the
P3D Special Effects SDK 'Special Effects Tool' (aka "
VisualFx.DLL").
NOTE: When using SDK
'Special Effects Tool', you may need to utilize a temporary "offset" of Effect display position on 3D models etc. via either the Fx parameter values (within the tabbed GUI of the Special Effects Tool cited above), in order to display small effects at a distance from the visible model of the user aircraft in a flight at run time;
otherwise the 3D visual model may surround and conceal the Effect object being displayed at the 3D model's central datum.
Alternatively, you may wish to utilize the Cross Hairs Plus (aka "CH+") 2.5 meters livery utility aircraft created by Jim Robinson, which has a central open circular area which may better display smaller Fx such as lights:
http://cat-tamer.com/flightsim/downloads/Crosshairs_Plus.zip
http://www.fsdeveloper.com/forum/threads/effect-emitting-other-effect.426851/#post-645058
Hope this helps a bit more !
GaryGB