Hi.

 

I usually try to solve this kind of problem myself (well, not by myself per se, but googling problems and solving using what other suggested in the past till it work), but I'm at a loss.

So, I made a fresh install of FSX today, tried to install FSinn, first I didn't see it in the Addon menu, then tried some solutions while googling the problem and now I have no Addon menu at all.

 

 

What I did so far - step by step:

 

FSX, aircraft and sceneries installation:

 

• Installation of FSX (Gold, which includes the acceleration already, if it makes any difference...) Also, it is my second fresh install of FSX today, I thought something went wrong with the first install since I didn't have the exe.xml file, and it wasn't until after I already uninstalled that I was told here in the forum it shouldn't be there after FSX install but only after it's needed for some addon. Either way, I removed the first install, including the 2 sceneries and the PMDG, I restarted and ran a check with Revo uninstaller to make sure no leftover files and registry entries are left behind.

• Opened the FSX installation folder, right clicked fsx.exe and marked "run as administrator"

• Loaded FSX

• Placed desired settings for realism, graphics, key assignments etc

• Closed FSX

• Installation of PMDG 737NGX with SP1c

• Installation of AIRAC

• Loaded FSX

• Loaded free flight with the 737NGX at a random location, switched from full screen to window with alt+enter

• After flytime of 5 minutes, closed FSX

• Ended flight

• Closed FSX

• Installation of Aerosoft EDDF

• Installation of Aerosoft LFPG

• Loaded FSX

• Loaded 737NGX at a gate in LFPG, placed it in a cold & dark state, and saved as my default flight in FSX

• Closed FSX

 

Installation of FSInn
 

• Installation of FSCopilot with SetupFSCopilot17B2_4 (as instructed in VATSIM sticky manual)

• Installation of FSInn with SetupFSInn13B2_3 (as instructed in VATSIM forum sticky manual)

• Opened "Start", right-clicked on FSInn UI, clicked "run as administration" from drop-down

• Once FSInn loaded, clicked "chat" button on the right, a chat window opened

• Closed the chat window, clicked the small X in the FSInn control panel, asked "Please confirm you want to close FSInn?"

• Clicked "Yes", FSInn control panel closed

• As instructed in the FSInn manual, opened the file "FSInnNet1.ini" in "\FSFDT\FSCopilot\FSInn" directory with notepad

• Replaced the line "SIStatusurl=http://usa-s1.vatsim.net/data/status.txt" with "SIStatusurl=http://status.vatsim.net/status.txt"

• Saved the file and closed it

 

Loading of FSX for the 1st post-FSInn installation
 

• Loaded FSX

• In the main screen (the "free flight" tab), chose a different livery for the 737NGX than the default one

• After confirming my selection, where I should see the airplane, I saw just the "skeleton" of the plane, while the "inside" (the plane itself), was half transparent half white

• Waited for 30 seconds to see if its stabilizing and passes

• Closed FSX

• Loaded FSX again

• Left the default flight as it is (PMDG default livery)

• Loaded the 737NGX at a gate in LFPG (the default flight I saved earlier)

• Screen resolution wasn't right (forgot to set it while I was setting the graphics earlier), so in "display" settings I changed to 1366*768

• Opened Addon menu, no FSInn, only "VistaMare" or something like that

• 20 seconds later, FSX crashes unexpectedly for the first time

• Installed FSIUPC

• Loaded FSX

• Loaded 737NGX at a parking in LFPG

• Opened Addon menu, no FSInn, but there is "FSIUPC"

• Waited for 2 minutes - no crash

• Closed FSX

 

 

 

-----------------------------------

 Troubleshooting begins

-----------------------------------

 

- First solution tested -
 

• Checked dll.xml - FSCopilot is present and is at the bottom

 

- Second solution tested -

 

• Opened FSXML Version 1.0.6. My dll.xml is loaded automatically in the program

• I'm not familiar with that app, but from what I see I basically need to select sections from the left and move them to the right in the order I wish to build a new correct dll.xml file. Problem is, the only sections available are "Visual Effects Tool", "Traffic Toolbox", "Object Placement Tool", "Level-D Simulations" and "FSUIPC 4", so I gave up on that one.

 

- Third solution tested -
 

• Installed SquawkBox to check if it'll also won't show up in the menu

• Loaded FSX

• Asked to confirm "trust" for some files

• On the third time I'm asked to confirm, the window freeze and gets stuck

• After waiting for 5 minutes for it to unfreeze, I terminated FSX via task manager

• Removed SquawkBox and when asked to reboot at the end of uninstall I didn't since there was one other solution I wanted to try before restarting that also required restart anyway.
   

 

- Forth solution tested -

 

In some forums, I read that others had this problem also, and in many cases it's related to people with "big foot" network card or something like that.In the FSInn help forum in Vatsim, one member posted he found a solution after contacting support service for his card, which is resetting the TCP/IP

• Opened CMD as administrator

• Executed "netsh winsock reset"

• Restarted Windows

• Before loading FSX, opened dll.xml to make sure FSInn is at the bottom. For some reason, 3 SquawkBox entries were still there, so I deleted them manually, saved and closed dll.xml

• Loaded FSX

• Loaded 737NGX at a gate in LFPG

 

Now not only there's no "FSInn" in Addon menu - there's simply no Addon menu.

Also, all the buildings of the scenery in LFPG (the terminal, the catwalks etc) are completely white for some reason...

 

-------------------------------------------------------------

 

To sum up the components:

 

• FSX installed with acceleration (meaning including SP1 and SP2)

• PDMG 737NGX SP1c installed

• Aerosoft LFPG and Aerosoft EDDM installed

• FSInn and FSCopilot installed

• FSUIPC installed

 

• fsx.exe has "run as administrator" ticked

• FSInn app files does not have "run as administrator" ticked

• FSInn UI ran (opened and "chat" was clicked) to update .ocx registration

• FSCopilot is present in dll.xml

• FSX is running in windows mode

 

 

System:

 

• Dell Inspiron 3537 Touch Screen IN-RD09-7506 

• Intel Core i5-4200U 1.6Ghz

• 6GB DDR3 1600MHZ

• 1000GB SATA 5400RPM

• AMD Radeon HD 8670M 2GB

• Windows 8.1 64Bit, recent install (restored to factory settings 5 days ago), all drivers are up to date.

 

 

Current dll.xml content:

 

<?xml version="1.0" encoding="Windows-1252"?>
 
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Object Placement Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>Visual Effects Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
  <Launch.Addon>
    <Name>VistaMare Core</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>VistaMare\ViMaCoreX.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
    <Name>FSCopilot</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSCopilot.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
</SimBase.Document>

 

 

Any suggestions? I would appreciate ANY THOUGHT you may have on this issue, thank you!

Hello Sir,

Looking at all your checks and info, i do not see any regard to installing sp2? without having sp2 or acceleration installed into fsx, you will not find the fsinn components showing up onscreen- maybe i,m wrong and missed something ? there must be a certain order for installing -1. install and run fsx-2. install the sp1 sp2 or acceleration and activate-3, download and install fscuipe followed by fsinn copilot then fsinn.  Hope this is helpful ? ( When i first stated with vatsim i similarly often forgot to include sp2, till the modulator turned on the light )

OK,

 

I decided to give it another shot, starting fresh.

I restored my laptop to its factory settings (brand new Windows 8.1 installation).

 

After Windows installations, I installed NO software (Office, Chrome, Photoshop etc) other than NET Framework & vcredist_x64.

 

Then, installed FSX > opened and activated FSX > installed FSX Acceleration > opened FSX > installed FSUIPC > opened FSX > installed FSCopilot & FSInn as instructed > opened FSX.

 

STILL, I don't have FSInn in Addon menu!

What am I doing wrong? I've been dancing around this thing for almsot a week now, and I still can't get it to work.

 

Please try to help, whatever you may think, whether it'll work or not.

You might find what you need over on the Vatsim FSInn forum,,,

 

http://forums.vatsim.net/viewforum.php?f=43

I already posted there as well but since there are many more active members here I thought someone here might be able to help as well

UPDATE:

 

After 2 full system restores (installing Windows again), and many (many) different attempts, I figured out the simple solution. It's a bit frustrating to see that is all it was...

 

I simply needed to delete my firewall (Zone Alarm). In the firewall control panel I allowed EVERYTHING for all FSInn and FSCopilot files, and I even tried the "Games Mode" which allow any connection request from any program while running, but it didn't work, only full uninstallation of it did.

 

Thanks!

Just to save some of the people that have this issue sometime, the solution that worked for me W7 FSX SE is below. Follow the steps. To summarize, FS creates seperate Module folder outside the FSX Folder, so FSX doesn't find the FSCopilot.dll DLL. So you need to go to C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE open the DLL and change the path of the FSCopilot to the actual path in the FS folder not the FSX Module folder. This worked for me!

 

Hope this helps!

 

 

FSX Steam edition does not come with a "Modules" folder, and even if you create one manuallly, it does not do any automatic handling of the DLLs you happen to place into it.

The major difference with FSX Steam Edition, is that you must add additional DLL's to the dll.xml file (path referenced above) manually.

One complication is that FSX Steam Edition does not necessarily come with a dll.xml file in the folder:

C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE

If you happen to use the installers for other modules, you may find that one of them has already created a dll.xml file for you, but if FSInn is the first module you are attempting to add, you will likely find that you have to add it yourself.

FSX Steam Edition comes with a sample of this file that can be copied and edited. It is found in a rather obscure location within the steam flight simulator main folder:

D:\steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\config\DLL.xml

Which can then be copied to:

C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE

In this sample file, the following 2 items will need to be edited:

Name: Change to "FSCopilot"
Path: Change to the path where FSX (steam) can find FSCopilot.dll on disk

The path element for users that already have FSX (boxed) installed can simply be pointed to where the FSCopilot.dll file resides within the boxed FSX installation. For example:

D:\FSX\Modules\FSCopilot.dll

This means that the FSCopilot.dll path entry for FSX Steam Edition can simply point to the FSCopilot.dll that is ALREADY in the FSX boxed installation.

If you were installing FSCopilot/FSInn from scratch, your path for the DLL will need to point to where ever the FSCopilot/FSInn put it, or where ever you choose to copy it to. For example, if the FSCopilot created a "Modules" folder for you, and placed the FSCopilot.dll in that folder your path entry would like like "Modules/FSCopilot.dll" or you could even use the entire path if you wanted to such as "D:\steam\steamapps\common\FSX\Modules\FSCopilot.dll"


If you have followed the above steps carefully to add FSCopilot.dll to the FSX Steam Edition, you will know FSX:SE has found the FSCopilot.dll successfully when it starts up the next time. Because it will ask you for permission to execute and "trust" the FSCopilot.dll

Just noticed that you also have a double "Launch.Addon" command at the end of your dll.xml file.  It should end with "</Launch.Addon>" only.

 

 

Just to save some of the people that have this issue sometime, the solution that worked for me W7 FSX SE is below. Follow the steps. To summarize, FS creates seperate Module folder outside the FSX Folder, so FSX doesn't find the FSCopilot.dll DLL. So you need to go to C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE open the DLL and change the path of the FSCopilot to the actual path in the FS folder not the FSX Module folder. This worked for me!



Hope this helps!





FSX Steam edition does not come with a "Modules" folder, and even if you create one manuallly, it does not do any automatic handling of the DLLs you happen to place into it.

The major difference with FSX Steam Edition, is that you must add additional DLL's to the dll.xml file (path referenced above) manually.

One complication is that FSX Steam Edition does not necessarily come with a dll.xml file in the folder:

C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE

If you happen to use the installers for other modules, you may find that one of them has already created a dll.xml file for you, but if FSInn is the first module you are attempting to add, you will likely find that you have to add it yourself.

FSX Steam Edition comes with a sample of this file that can be copied and edited. It is found in a rather obscure location within the steam flight simulator main folder:

D:\steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\config\DLL.xml

Which can then be copied to:

C:\Users\USERNAME\AppData\Roaming\Microsoft\FSX-SE

In this sample file, the following 2 items will need to be edited:

Name: Change to "FSCopilot"
Path: Change to the path where FSX (steam) can find FSCopilot.dll on disk

The path element for users that already have FSX (boxed) installed can simply be pointed to where the FSCopilot.dll file resides within the boxed FSX installation. For example:

D:\FSX\Modules\FSCopilot.dll

This means that the FSCopilot.dll path entry for FSX Steam Edition can simply point to the FSCopilot.dll that is ALREADY in the FSX boxed installation.

If you were installing FSCopilot/FSInn from scratch, your path for the DLL will need to point to where ever the FSCopilot/FSInn put it, or where ever you choose to copy it to. For example, if the FSCopilot created a "Modules" folder for you, and placed the FSCopilot.dll in that folder your path entry would like like "Modules/FSCopilot.dll" or you could even use the entire path if you wanted to such as "D:\steam\steamapps\common\FSX\Modules\FSCopilot.dll"


If you have followed the above steps carefully to add FSCopilot.dll to the FSX Steam Edition, you will know FSX:SE has found the FSCopilot.dll successfully when it starts up the next time. Because it will ask you for permission to execute and "trust" the FSCopilot.dll

 

 

 

That's terrific info.  Thanks so much.