- #Active sky 16 not installing into prepar3d install#
- #Active sky 16 not installing into prepar3d Pc#
- #Active sky 16 not installing into prepar3d license#
Once installed I opened P3D and FSCommander and they both work in harmoney without any modifications. What I have on my machine is included as an attachment:Īnother item to help out if it hasn't been mentioned is while using P3Dv4 I had to get the new version of FSUIPC 5. I am not being critical of your idea, but how would your idea be any different than what I am already doing? This method has work for me for a couple of years until P3Dv4. That way the application would choose or dectect if the correct simconnect is available for use.
#Active sky 16 not installing into prepar3d install#
So What I did was to install all simconnects into my system. However, Pilots did not satisfy my "on demand now" weather and I want to run Active Sky. When I added Active Sky Next to my system "Next" would not connect. To explain: While running P3Dv3 and FSCommander, it takes a certain simmconnect. It would seem that since I have all of them loaded the particular application will choose which simconnect to use. However, at the present time, I have FSX, P3dv3 and P3dv4 on my computer and all three (actually 4) simconnects are loaded in my system. One thing about what you mentioned was the ability of FSHostClient to detect which Sim or Simconnect a user is going to use and it would automatically lock on.
It is really kind of you to keep us informed.
#Active sky 16 not installing into prepar3d license#
And I currently only have a Prepar3D license for v4 (do you have to buy a license for each new version that comes out?)
I'd like to know how many flavors of FS you have installed (FSX, FSX:SE, Prepar3D) and which versions you have installed (FSX SP1, SP2, Prepar3D v1, v2, v3, v4, etc.) I'll probably need help testing FSHostClient with older versions especially. I'll most likely release a couple of beta versions that you guys can try out, and see how they work with the various flavors of FS. I hate to give time estimates because they're never correct, but rest assured I'm working on it and want to get a new version of FSHostClient out there as soon as I can. As you know, I do this in evenings and on weekends, so I'm trying to fit it in when I can. But there are still several things left to do.
#Active sky 16 not installing into prepar3d Pc#
So far I have several parts of this plan working, and I can now find all versions of SimConnect.dll installed on the PC and load a particular dll on demand. That hopefully will mean I won't have to play cat-and-mouse anymore, and FSHostClient will just work with whatever comes along. That way, one build of FSHostClient should support all flavors of FS, and all versions of SimConnect.dll, even new versions of the dll that get released in the future. I'm changing things so that FSHostClient will detect which versions of SimConnect.dll you have installed, and then try each one to see if it can connect to any of the three flavors of FS. And that means that it only supports one (or possibly two) flavors of FS. Basically each new build of FSHostClient just requires that it run with one particular version of SimConnect.dll, and it fails to even launch if you don't have that version of the dll installed. Juggling all these versions is tricky, and it's something that FSHostClient has never done very well. Microsoft's FSX requires a particular version, FSX Steam Edition requires a particular version, and Prepar3D requires a particular version - and sometimes a new version of FS:SE or Prepar3D will come out that requires a new version of the dll.
The problem has always been that different "flavors" of FS require different versions of SimConnect.dll. :-) I am still working on it though, and hope to have a fix as soon as I can. Those payments aren't much, but I suppose they just add frustration to the whole cat-and-mouse game. So I end up just paying for one month each time, to get their latest version and figure out what they changed. Not to mention the fact that they charge $10-20 per month for a developer license, which seems excessive when I only need it to change my program whenever they change theirs. This really doesn't give me a lot of incentive to make my programs work with theirs, as you can imagine. And the times that I've pointed this out to them in their forums, I got back pretty terse replies that indicated they had no interest in doing it any other way. I have to say I've been pretty frustrated by the team that does P3D because it seems like every time they release a new version, they change things that cause my programs to not be able to communicate with theirs anymore. I spent quite a bit of time on this the other day and didn't get very far. No problem, I know you guys are eager to get a fix.
0 kommentar(er)
