Been fighting with this installation routine for three days now.
I've installed my FSDG scenery in D:\FSDG
The FIMP install routine created the following path:
D:\FSDG\FSDG-Mauritius\FSDG-Mauritius\...
I've run and re-run the configurator installer and pointed to EXACTLY the same D:\FSDG location, but continue to receive the "Error: XML configuration not correct".
When installing the configurator I choose the exact same path (D:\FSDG) as my FSDG sceneries, but the install creates yet another FSDG subfolder therein, refusing to run on matter what. The following unhelpful log entry is all that ever appears:
System.IO.FileNotFoundException: images/gmad_bright.PNG
at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at System.Drawing.Image.FromFile(String filename)
at _FSDGScenConfig.Main.initializeXML()
Based on the only other entry in this forum I've follwed the correct method in installing it in the same folder as the sceneries. This really shouldn't be so difficult if we don't want to clutter our C:\ drives with the default paths, and I'm starting to regret my FACT purchase (which I've not installed considering the problems with this one)....
Scenery Configurator Errors
- horst18519
- Posts: 2444
- Joined: Thu Dec 15, 2011 4:28 pm
- FS-Version: MSFS
Re: Scenery Configurator Errors
If you choose the same location for all installations you should not have any problems.
You chose 'D:\FSDG' as the install location of your choice, so Mauritius was installed into 'D:\FSDG\FSDG-Mauritius'
If you choose the same folder for the Scenery Configurator installation the config tool will be installed into 'D:\FSDG\FSDG' (not as you assumed 'D:\FSDG')
Don't try to force the installer to install into 'D:\FSDG' or the config tool won't work.
You may be wondering why we decided to do it this way. The answer is: not everybody uses a special folder for his FSDG products, so chances were that our config files ended up in a general folder together with non-FSDG stuff. The only way to avoid this was to create those FSDG(_AddonName) folders.
You chose 'D:\FSDG' as the install location of your choice, so Mauritius was installed into 'D:\FSDG\FSDG-Mauritius'
If you choose the same folder for the Scenery Configurator installation the config tool will be installed into 'D:\FSDG\FSDG' (not as you assumed 'D:\FSDG')
Don't try to force the installer to install into 'D:\FSDG' or the config tool won't work.
You may be wondering why we decided to do it this way. The answer is: not everybody uses a special folder for his FSDG products, so chances were that our config files ended up in a general folder together with non-FSDG stuff. The only way to avoid this was to create those FSDG(_AddonName) folders.
Re: Scenery Configurator Errors
Hi Thorsten, thanks for your reply.
I didn't force the installer away from the path beyond selecting the D:\FSDG folder as the target, so it sounds from your post that it correctly created its own FSDG subfolder.
The result is the configurator installed in D:\FSDG\FSDG while FIMP is in D:\FSDG\FSDG-Mauritius\FSDG-Mauritius\... (not sure why it doubled the folder name but the scenery works correctly albeit without any options/dyn lighting)
As I understand it these are the correct paths, but the configurator will not run with the log error I posted below. Any idea where the break might be?
I'm leaning towards removing the scenery and configurator in their entirety and starting again, perhaps just choosing D:\ as the install directory in case a do-over resolves it, but will hold off on the nuclear option for a bit
I didn't force the installer away from the path beyond selecting the D:\FSDG folder as the target, so it sounds from your post that it correctly created its own FSDG subfolder.
The result is the configurator installed in D:\FSDG\FSDG while FIMP is in D:\FSDG\FSDG-Mauritius\FSDG-Mauritius\... (not sure why it doubled the folder name but the scenery works correctly albeit without any options/dyn lighting)
As I understand it these are the correct paths, but the configurator will not run with the log error I posted below. Any idea where the break might be?
I'm leaning towards removing the scenery and configurator in their entirety and starting again, perhaps just choosing D:\ as the install directory in case a do-over resolves it, but will hold off on the nuclear option for a bit
- horst18519
- Posts: 2444
- Joined: Thu Dec 15, 2011 4:28 pm
- FS-Version: MSFS
Re: Scenery Configurator Errors
Now that we sorted the install paths let's look at the error messages. The tool crashes because of a missing GMAD file in the FSDG/images folder. This should be fixable if you re-install FSDG-Agadir.
Re: Scenery Configurator Errors
Thanks for all the input- in the end I decided to remove and reinstall all, taking care with the target. Have it working now and the folder structure looks exactly as you described it should.