• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Unable to create library

S

sfrenchie

Messages
1,043
Country
us-northcarolina
After my other post I decided to test again.
Here is how it happened:
  • I created an element, All in One was not checked
  • Clicked Create/Save button...went fine
  • Selected All in One
  • Clicked Create/Save button...went fine this time
  • Clicked make library
  • Clicked Create/Save Library
  • Got the popup, apparently the BGL was created in the root folder instead of creating a Scenery folder and no texture were "saved/copied"
Untitled-1.jpg
Untitled-2.jpg
 
Patrick, your first message above never registered as a new post on my system, so I never saw it.

That message is generated by Windows and is simply reiterated by AFLT. It is typical of what you would receive if you attempted to copy into a scenery folder and FlightSim was active at the time.

apparently the BGL was created in the root folder instead of creating a Scenery folder and no texture were "saved/copied"
Click to expand...
What leads you to this conclusion? The message is telling you that the .bgl file could not be copied into the specified destination folder. If the .bgl file was not copied, then the textures wouldn't be. The folder in which the (inaccessible) .bgl resides is clearly not a root folder.
 
gadgets said:
Patrick, your first message above never registered as a new post on my system, so I never saw it.
Click to expand...
Yeah I figured that's what happened. I was busy anyway so I'm only returning to trying out your program now.

gadgets said:
That message is generated by Windows and is simply reiterated by AFLT. It is typical of what you would receive if you attempted to copy into a scenery folder and FlightSim was active at the time.
Click to expand...
I understand but what I had like to know is by what process the file is used since the only program using it is AFLT?

gadgets said:
What leads you to this conclusion? The message is telling you that the .bgl file could not be copied into the specified destination folder. If the .bgl file was not copied, then the textures wouldn't be. The folder in which the (inaccessible) .bgl resides is clearly not a root folder.
Click to expand...
This might be related to the previous paragraph, I don't know.
I create an element as follows, including the folders create under what I call root, "D:\Documents\Games\Flight Simulator\_Workfiles\AFLT"
Untitled-1.jpg


I then attempt to create the library in the path, "D:\Documents\Games\Flight Simulator\_Workfiles\AFLT" as follows
Untitled-1.jpg


I get the error message and when I check my folder I see:
Untitled-2.jpg


If I remember correctly reading the manual it said the folders would be created appropriately but I do not see a Scenery or Texture folder anywhere in my root. As you can see in the snapshot the only BGL created is indeed in my root folder.

I read in the manual: The Make Library function creates two object libraries for each FlightSim version. First is the "lights" library ("lib_AF_Lights.bgl"), which is FS9 based and is identical for both FlightSim versions. It contains the lights which will be attached to the models. A unique version of the "bases" library ("lib_AF_Bases_FSn.bgl") is created for each Flightsim version.
  • Notice that the only BGL created in my case doesn't match any name provided in the manual.
  • Notice that the file name referred to in the error message contains the word _Lights twice.
  • No Scenery folder is created
  • No Texture folder is created
  • No texture is copied
  • The only files found in the folders created by AFLT are an INI file and the MDL for the model
_Lights.BGL is indeed a library I can open in MCX however of course I get the following warnings:
Untitled-1.jpg


My resulting folders as they were created by AFLT are uploaded.
Thanks for looking into this issue or correcting me in something I am performing the wrong way.

Patrick
 

Attachments

I understand but what I had like to know is by what process the file is used since the only program using it is AFLT?
Click to expand...
It will be the destination file that is locked. Only you know what you specified as a destination.

If I remember correctly reading the manual it said the folders would be created appropriately but I do not see a Scenery or Texture folder anywhere in my root. As you can see in the snapshot the only BGL created is indeed in my root folder.
Click to expand...
And therein lies your problem. If you read the third paragraph on page 9 of the user manual you'll see that the libraries are automatically saved in the Library folder. Any folders you specify must be outside the "root" folder. (Its locked by AFLT.) If you specify an Addon Scenery folder, for example, the \scenery and \texture folders will be created for you.

Don
 
Thanks for the info Don. I'm having a bit of trouble with you program though, maybe I'm not quite understanding the tree structure that is expected.
Right now I selected a path in the Library Folder textbox. I got the message that this is not a scenery folder, should we use it anyway. I clicked on No and got:
************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\Documents\Games\Flight Simulator\_Workfiles\AFLT\INI'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)
at Microsoft.VisualBasic.FileIO.FileSystem.FindPaths(FileOrDirectory FileOrDirectory, String directory, String wildCard)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards, Collection`1 Results)
at Microsoft.VisualBasic.FileIO.FileSystem.FindFilesOrDirectories(FileOrDirectory FileOrDirectory, String directory, SearchOption searchType, String[] wildcards)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.GetFiles(String directory, SearchOption searchType, String[] wildcards)
at FS_Airfield_Lights.MainPanel.SaveGuidsUsed()
at FS_Airfield_Lights.MainPanel.GetFolder_Library(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
AFLT
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///E:/AFLT/AFLT.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5488 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
 
The exception should not have been thrown, of course. It will be fixed.

You appear to have been selecting the AFLT\INI folder as a Library folder. Why?

Don
 
The exception probably occurred due to AFLT attempting to access a non-existent INI folder. After a normal shutdown, the same Library folder should be selected automatically. but you didn't have a normal shutdown. Incidentally, I cannot recreate the exception regardless of my response to the query you received. What, specifically, did you enter into that field.

Don
 
Development Release 1.1.01(e), now available at http://stuff4fs.com, avoids the exception you experienced earlier today. As I suspected, the exception was due to AFLT attempting to scan a non-existent folder.

Don
 
You must log in or register to reply here.
Back
Top