|
Post by fardel on May 16, 2014 2:10:38 GMT -5
Hello gentlemen, I am a new user FSCaptain and I installed it on my Prepar3D v2.2 that is on a PC with Win7 64. I also have 2 other PCs with Win 8.1, where I connected with SimConnect and WideFS some programs like FSCommander, ivap (for IVAO) and vPilot (for VATSIM), TOPCAT, etc..; the main directory of Prepar3d is shared in read and writ with these two PCs and all works fine. Following the instructions in this forum, I tried to run the FCDU from the first and then from the second client PC, but I always got this error message Searching on Google, I found that the problem should be caused by Microsoft Visual C + + Redistributable, so I reinstalled all files (2005, 2008, 2010, 2012 and 2013) with their SP but to no avail - I always have this error message. May be the file FCDU.exe not compatible with Win 8.1 on the network? I tried to run, from the remote PC, the Manager and FCDU installer of FSCaptain and FCDU.exe without problems but getting this errorm only with FCDU.exe. Thanks for the answers Paolo
|
|
|
Post by mrspeaker on May 17, 2014 9:45:08 GMT -5
I have been asking about this for weeks now with no answer, I did the same thing as you, re installed all the c++ runtimes, I still get the same error. I don't think its a windows 8 issue. I'm running windows 7 on both my computers.
|
|
|
Post by fardel on May 19, 2014 5:13:05 GMT -5
Thenk you for answers.. we are waiting for any solutions
|
|
|
Post by i8aaq on May 22, 2014 9:18:06 GMT -5
I have the same problem. Windows 7 64 bit in master PC and Vista 32 bit in client
|
|
|
Post by i8aaq on May 27, 2014 7:46:02 GMT -5
anyone know how to fix?
|
|
|
Post by mrspeaker on May 30, 2014 19:17:02 GMT -5
I thought I read the support for fscaptain was great, so far I am not impressed. I have posted in several threads and have pm'd the developer, not a word so far.
|
|
|
Post by peter on May 30, 2014 19:59:28 GMT -5
Sorry, I can't help because I have all my FSX stuff on one PC. I have read that the developer has disappeared for several months before, but then came back to deliver excellent support. I joined late last year and support was great until January, when the developer had some health problems. Let's hope he will return soon.
|
|
|
Post by i8aaq on Sept 4, 2014 15:57:29 GMT -5
no solution?
|
|
|
Post by Travis on Sept 5, 2014 12:02:13 GMT -5
I'm sorry, but we have not yet been able to replicate this issue, so we're completely in the dark as to what could be the problem / problems.
It could be possible that there is a conflict with the FCDU.EXE and Windows 8.1, but I see you have a Win7/Vista32 setup.
(I have Win7/Vista64, and it works like a charm for me. Other SimConnect clients work as well.)
I'll talk over some strategy with Dutch, but let me ask you this first... can you successfully run and use the FCDU on your flight sim PC? Is it only giving you problems when you use it remotely??
Regards,
|
|
|
Post by Travis on Sept 5, 2014 13:38:48 GMT -5
One thing that I recall from doing "SimConnect network triage" for AivlaSoft EFB is to test the client application without any other SimConnect clients running - and with a "clean" SimConnect server... because sometimes a crash of your flight simulator may leave other server-based SimConnect programs running in the background which could block connections to a new instance of the flight simulator. For example I use a Saitek switch control panel that normally runs SAIPANELS.EXE. If my simulator crashes and I re-run the simulator, my remote SimConnect apps such as AivlaSoft EFB may not connect. If I shut down the SAIPANELS.EXE processes, EFB can connect. Then too just now, I was preparing for a flight with my remote clients. I had the EFB DisplayUnit running on my Vista64 PC and when I ran my FCDU.EXE remotely BOOM, my EFB DataProvider on the server PC crashed. Running the FCDU on the server PC works fine however.... So if you're having problems running the FCDU remotely, try this... boot both PCs, run your simulator and no other applications (shut down your weather engine, voice control, EFB, etc.). Then on your remote PC, run your remote/shared FCDU. If it still crashes, then please email us your crash report from your Windows Event Log. That may give us a reasonable place to start searching.
|
|
|
Post by fardel on Sept 7, 2014 4:28:35 GMT -5
Ok Travis I try run the remote FCDU on a Win7 client (in this case 2 PC with Win7) to see if work fine; after run the client on Win8 to send you the Windows event Log
|
|
|
Post by Air59 on Oct 14, 2014 7:22:20 GMT -5
Hi Fardel,
Did you find a solution to this problem (same proble for me with Win7 32)
Thierry
|
|
|
Post by air59 on Oct 27, 2014 10:45:33 GMT -5
Hi Travis,
Still have this problem. Tried a lot of things without any good result. All works fine in the same PC but i get this error when i try to launch FCDU from a client PC (win 7 x32) on wich simconnect is intaled and working (IVAO).
Do you know what C++ library FCDU is using ? May it could help me....when it is fixed...i buy FSCaptain (using demo mode).
Thierry
|
|
|
Post by Travis on Oct 27, 2014 14:05:27 GMT -5
Hi Thierry,
I'm still very clueless when it comes to the environment which support C++. (I am learning the coding bits, but all of the other items are a mystery to me for now.)
I will need to wait until Dutch is back from his trip to see what this could be.
For now though, can you answer three questions for me?
- Can you successfully run the FCDU.exe on your simulator PC and have it connect and work properly? If so, then the problem is likely in the networking / SimConnect.
- What version of SimConnect are you running on both your simulator PC and on your client PC?
- Have you tried running the remote FCDU with no other SimConnect applications running?? (Boot both PCs cleanly, run your simulator and no other applications (shut down your weather engine, voice control, EFB, etc.). Then on your remote PC, run your remote/shared FCDU.)
Regards,
|
|
|
Post by air59 on Oct 28, 2014 8:55:55 GMT -5
Hi Travis,
Thanks a lot for your answer.
Here is my config :
Server : win7 64 FSX (not used anymore), FSX SDK (sp1A), P3D v2.4, P3Dv2 SDK I have Simconnect.xml is "Appdata/lockheed.../P3Dv2/" (192.168.0.7, port 500) I have Simconnect.ini in Documents/P3dv2 files P3D folder is shared (read and write)
Client 1 : win7 32 FSX SDK (sp1A) Simconnect.cfg on "Documents" (192.168.0.7, port 500)
Client 2 : laptop with win7 64 P3Dv2 SDK Simconnect.cfg on "Documents" (192.168.0.7, port 500)
When i launch FCDU in Server, everything is working ok When i launch FCDU (shortcut) from Client1 or 2 i have the side by side error message. From Client 1 or Client 2, i can access to FSCaptain folder wich is on server and create a .doc file without any problem.
What version of SimConnect are you running on both your simulator PC and on your client PC? - Client 1, the FSX simconnect. It works fine with IVAP (IVAO) wich need a simconnect connexion. But something surprising : Although IVAP works fine, when I launch from client 1 the TrafficAI.exe (FSX SDK), i have a black window disparearing immediatly...In your "how to", when you speak about this test, do you launch trafficAi.exe from Client or from Server ? - Client 2, I only installed Prepar3D SDK (wich must contain a simconnect version) to test if this is the issue. No best result.
I tried without other programm running on server and client (except P3D), but it doesn't work better. I also tried without any firewall.
I used on client 2 the sxstrace.exe. Please see below the log file. May be it can help you (sorry it's in french). I must admit that is doesnt for me ;-)
Thanks for reading this.
I go on testing....
Regards, Thierry
"================= Début de la génération du contexte d’activation. Paramètre d’entrée : Flags = 0 ProcessorArchitecture = AMD64 CultureFallBacks = fr-FR;fr ManifestPath = \\TG-PCI7\P3Dv2\FSCaptain\Bin\FCDU.exe AssemblyDirectory = \\TG-PCI7\P3Dv2\FSCaptain\Bin\ Application Config File = ----------------- Information : analyse du fichier manifeste \\TG-PCI7\P3Dv2\FSCaptain\Bin\FCDU.exe. Information : l’identité de la définition du manifeste est (null). Information : référence : Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0" Information : résolution de la référence Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0". Information : résolution de la référence pour l’architecture ProcessorArchitecture x86. Information : résolution de la référence pour la culture Neutral. Information : application de la stratégie de liaison. Information : aucune stratégie de serveur de publication trouvée. Information : aucune redirection de la stratégie de liaison trouvée. Information : début de la recherche d’assemblys. Information : impossible de trouver l’assembly dans WinSxS. Information : tentative de recherche du manifeste sur C:\Windows\assembly\GAC_32\Microsoft.FlightSimulator.SimConnect \10.0.61242.0__67c7c14424d61b5b\Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect .MANIFEST. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect \Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect \Microsoft.FlightSimulator.SimConnect .MANIFEST. Information : manifeste pour la culture Neutral introuvable. Information : fin de la recherche d’assemblys. Erreur : impossible de résoudre la référence Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0". Erreur : échec de la génération du contexte d’activation. Fin de la génération du contexte d’activation.
================= Début de la génération du contexte d’activation. Paramètre d’entrée : Flags = 0 ProcessorArchitecture = Wow32 CultureFallBacks = fr-FR;fr ManifestPath = \\TG-PCI7\P3Dv2\FSCaptain\Bin\FCDU.exe AssemblyDirectory = \\TG-PCI7\P3Dv2\FSCaptain\Bin\ Application Config File = ----------------- Information : analyse du fichier manifeste \\TG-PCI7\P3Dv2\FSCaptain\Bin\FCDU.exe. Information : l’identité de la définition du manifeste est (null). Information : référence : Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0" Information : résolution de la référence Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0". Information : résolution de la référence pour l’architecture ProcessorArchitecture WOW64. Information : résolution de la référence pour la culture Neutral. Information : application de la stratégie de liaison. Information : aucune stratégie de serveur de publication trouvée. Information : aucune redirection de la stratégie de liaison trouvée. Information : début de la recherche d’assemblys. Information : impossible de trouver l’assembly dans WinSxS. Information : tentative de recherche du manifeste sur C:\Windows\assembly\GAC_32\Microsoft.FlightSimulator.SimConnect \10.0.61242.0__67c7c14424d61b5b\Microsoft.FlightSimulator.SimConnect .DLL. Information : manifeste pour la culture Neutral introuvable. Information : fin de la recherche d’assemblys. Information : résolution de la référence pour l’architecture ProcessorArchitecture x86. Information : résolution de la référence pour la culture Neutral. Information : application de la stratégie de liaison. Information : aucune stratégie de serveur de publication trouvée. Information : aucune redirection de la stratégie de liaison trouvée. Information : début de la recherche d’assemblys. Information : impossible de trouver l’assembly dans WinSxS. Information : tentative de recherche du manifeste sur C:\Windows\assembly\GAC_32\Microsoft.FlightSimulator.SimConnect \10.0.61242.0__67c7c14424d61b5b\Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect .MANIFEST. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect \Microsoft.FlightSimulator.SimConnect .DLL. Information : tentative de recherche du manifeste sur \\TG-PCI7\P3Dv2\FSCaptain\Bin\Microsoft.FlightSimulator.SimConnect \Microsoft.FlightSimulator.SimConnect .MANIFEST. Information : manifeste pour la culture Neutral introuvable. Information : fin de la recherche d’assemblys. Erreur : impossible de résoudre la référence Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61242.0". Erreur : échec de la génération du contexte d’activation. Fin de la génération du contexte d’activation."
|
|