Hi Tim:
Please post in here, a report of what symptoms and/or error message was generated by BGLComp which you saw associated with the compilation failure(s).
FYI: In addition to examining any screen captures you might post here, we might all learn more about this scenario from a review of any error messages which may be generated by the
BGLComp compiler.
I'd recommend using Arno's excellent "
CompileHelper 2.0":
http://www.fsdeveloper.com/forum/downloads.php?do=file&id=75
[
EDITED]
After the path to FSX SDK Resample and any other applicable SDK or 3rd party compilers is added to the CompileHelper info fields in its GUI, one can then use the Windows Explorer file manager (aka "Computer" or "My Computer") to Drag-N-Drop one's
ex:
*.XML file
onto CompileHelper ...rather than directly onto
ex: BGLComp.
After a (attempted) compile procedure, the FSX SDK Resample and any other applicable SDK or 3rd party compilers' output text messages (for either successful compilation or various errors etc.) ...are retained in the CompileHelper window for subsequent review for as long as that instance of one's CompileHelper task session is left open in Windows.
Compiler error messages captured and retained by CompileHelper can be copied and pasted into a post here; for better legibility, you can insert that text from CompileHelper in between forum formatting tags using the "CODE" delimiter (click the '
#' icon) in the '
Reply to Thread' editor
ex:
HTML:
[CODE]Error message text goes here[/CODE]
PS: To answer your other question above, you
may be able to change Y-axis orientation of a FS Effect depending on what type it is, and how it is coded.
FYI: You can test FS Effect (*.FX file) code parameter value changes interactively with a live 3D preview using:
* Arno's stand-alone
FXEditor:
http://www.fsdeveloper.com/wiki/index.php?title=FXEditor
...
or inside a FSX flight session by enabling
visualfxtool.dll in your
DLL.XML ...using:
* FSX 'Creating Special Effects' SDK "
Special Effects Tool" (aka : "
FX Tool")
To
conditionally enable visualfxtool.dll file, in the DLL.XML file, its entry should read:
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>
False</Disabled>
<ManualLoad>
True</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
At the prompt when FSX starts up, one can choose whether to run visualfxtool.dll each session manually, or every session automatically.
To
permanently disable visualfxtool.dll file, in the DLL.XML file, its entry should read:
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>
True</Disabled>
<ManualLoad>
True</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
One can find the DLL.XML file for enabling / disabling visualfxtool.dll and other FS default / 3rd party *.DLLs located in:
Windows XP:
C:\Documents and Settings\[user account or profile name]\Application Data\Microsoft\FSX
Windows Vista / Win-7:
C:\Users\[user account or profile name]\AppData\Roaming\Microsoft\FSX
http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_(FSX)_-_Troubleshooting
http://www.simforums.com/forums/fsx-sdk-install-guide_topic31522.html
BTW: A convenient FS utility with a GUI to manage the DLL.XML and EXE.DLL files used to enable / disable visualfxtool.dll & other FS default / 3rd party *.DLLs:
ModuleToolX 0.4
http://library.avsim.net/search.php?SearchTerm=moduletoolx_0.4.zip&CatID=root&Go=Search
Also, Finney Ground "
Cross Hairs Plus" (aka "CH Plus" or "CH+") is very good for previewing Effects with FSX SDK 'Fx Tool', as the cross-hairs 3-D model is relatively thin, and all but the tiniest Effects normally can be seen, especially with Jim Robinsons excellent 2.5 Meter sized version which is open in the center.
http://www.fsdeveloper.com/forum/showpost.php?p=124985&postcount=4
http://www.fsdeveloper.com/forum/showthread.php?t=19052
[
END_EDIT]
Hope this helps !
GaryGB