Sorry if I am in the wrong forum or this subject has been beaten to death, but I tried to conduct a search and I could not find the button on AVSIM FORUM home page. Here it goes. Enjoyed FS9 for years, computer crashed, could not find my discs, bought FSX. I am trying to install waypoints around CYYZ for increased realism but the

bglcomp.exe seems to be "wonky". When I drop the xml file onto the compiler (in FSX SDK), there is a flash of DOS Message, which I cannot read for the speed of closing, and the BGL file is not formed. I have FSX Gold Edition, installed the SDK off disc one, and after reading for the last three days online, I downloaded the msmxl package 3 from Microsoft. I read the FSX SDK material and even cut pasted their example (oil rig in Seattle) and tried it in the compiler. Did not work. I guess my first step is to slow down that DOS message but I don't know how. Thanks for your expertise in advance.

Cheers,

Ben

I apologize if I am in the wrong forum or if this topic has been beaten to death, but I tried to conduct a search and could not find the button on AVSIM FORUM home page. Anyways, here is the issue. Used FS2004 for many years, computer decided to crash, got new computer and could not find FS 2004 discs. I decided to buy FSX, to keep up with the times. I have to install many waypoints around CYYZ and I read the procedures that it involves. Unfortunately, it appears that the bglcomp.exe is not willing to work with me. When using the compiler, I get a flash of a message on a DOS screen, which closes to fast to read. I have FSX Gold edition, installed all the FSX SDK files as well as the msxml package 3 from Microsoft. Is there a way to slow down the error message in the DOS window? Thanks ahead for your expertise.
Cheers,
Ben

Check the wiki at FS Developer for details about SDK installation. Your SDK "level" must match your FSX "level", otherwise things won't work the way they should.

 

As far as the DOS prompt, at FS Developer is a tool by Arno G. to help capture any compiler erros or you could open a Command window in Windows and attempt the compile via the command line, which would yield any error messages.

See also http://www.fsdeveloper.com/wiki/index.php?title=CompileHelper

 

Rick

 

BGLCOMP does not run by left clicking the exe file on my PC. I have to run it from the DOS Prompt.

Check out Arno's tool here:

http://www.fsdeveloper.com/wiki/index.php?title=CompileHelper_2.0

 

scott s.

.

BGLCOMP does not run by left clicking the exe file on my PC. I have to run it from the DOS Prompt.

It doesn't run from any PC by clicking on it.

 

Drop a file on it or run it from the DOS prompt.

 

regards,

Joe

Thanks people for your expertise. As usual, the answers are very productive. Using the DOS Window made it easy to check the compiling process. The first error message states that the compiler could not open the xml file. Any thoughts? Thanks by the way for the link to FS Developers. That is my first time visiting and the information in there is amazing. Also, when you refer to "level", are you talking about "administrator" privileges?

Thanks again.

No, he's talking about SP1, SP2, and Acceleration, your SDK version must match your sim version, if you have Acceleration installed then you also need the Acceleration version of the SDK for example.

 

If you have Accel installed and you've only installed the one SDK off disk one, then you don't match. There are two more SDK installers on the Accel disk, you need to install the SP1a SDK first (fsx_sdk_sp1a.exe) and follow that with the Accel SDK which is just "SDK.msi" in that order. It'll warn you about removing previous SDK versions first, just let it do it's thing in both cases.

 

Jim

Good info. Wow, those discs contain a lot more than I thought. So I installed the SP1a first followed by the SDK.msi. When I tried to compile my waypoint (imeba), the same result occurred. Is there an xml file that you know that is accurately written so that I can check immediately if the compiler is working fine? Then I won't waste people's time with a file with a mistake.

Thanks,

Ben

Sure, this one should put an ISEC over meteor crater in Arizona:

<?xml version="1.0" encoding="ISO-8859-1"?>
<FSData
     version="9.0"
     xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
     xsi:noNamespaceSchemaLocation="bglcomp.xsd" >

  <Waypoint waypointType="NAMED"
    waypointRegion="K2"
    waypointIdent="CRATR"
    lat="35.0275540989464"
    lon="-111.023015895766"
    magvar="347.4">
  </Waypoint>

</FSData>

Jim

I greatly appreciate your patience with this issue. Here is what I did. I cut and pasted your message onto notepad and saved it as an xml file. I then brought the xmi file into the same folder as the compiler exe file. I opened a DOS window and wrote:

BGLComp.exe test1.xml (test1 being the name of the file I saved your message under).

Here is what DOS showed:

INTERNAL COMPILER ERROR: #C2623: Couldn't open file: test1.BGL.
INTERNAL COMPILER ERROR: #C2585: Unable to create output file 'test1.BGL

This is where I am at.

Again, your time is greatly appreciated.

Cheers,

Ben

I noticed in your first post you mentioned msmxl package 3, I assumed you meant MSXML 4. I'm not sure if that's the exact error but I do know bglcomp will throw a similar error if you don't have MSXML 4 installed. I'd check Control panel > Programs & Features and make sure you have that installed, mine says "MSXML 4.0 SP2 Parser and SDK" for example. If you don't see that get it from MS (a quick google search should find you the link) and try the test.xml again.

 

Jim

I do have the MSXML 4.0 SP2 Parser and SDK. I even had the SP3 parser, which I removed in case of conflict with one another.

Sorry to be such a headache :mellow:

No worries, not a headache at all. Are you by any chance moving bglcomp.exe out of the SDK folder into another folder to run it? If so you need to bring bglcomp.xsd along with it, that contains a bunch of definitions that bglcomp needs access to when it compiles something.

 

I googled your errors above and found a few hits where others have had this problem, nothing conclusive from a quick glance but you could also give that a try and maybe if you go deep enough you'll find a situation where someone posted a solution. I'll keep looking too.

 

EDIT: that doesn't seem to be it, it appears bglcomp will tell you if the .xsd is missing, still looking...

 

Jim