glkx1011 1 Posted August 7, 2017 Share Posted August 7, 2017 Hi! When i try to launch the CRJ manager I get the following error message: "Microsoft Flight Simulator X (SP2, Acceleration or Steam edition) or Lockheed Martin Prepar3d (v.2x or v.3x) path could not be found!" I use the CRJ in FSX:SE installed in the normal path. Any ideas? Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted August 7, 2017 Deputy Sheriffs Share Posted August 7, 2017 Have you manually moved your FSX:SE installation after having installed it initially? Have you ever had FSX (MS version) installed on your machine, prior to FSX:SE? Link to comment Share on other sites More sharing options...
glkx1011 1 Posted August 7, 2017 Author Share Posted August 7, 2017 Yep, i've had standard FSX installed previously The SE installation path is the default one Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 7, 2017 Share Posted August 7, 2017 Please press Windows + R, type "regedit" and press Return. This should open the Registry Editor. Now go to this path: "Computer\HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition" There should be one entry called "Co-Existence" in there. We need to know whether this is 0 or 1 Next, go to the sub-path "10.0" and look at the AppPath entry. Does its value match the path to your FSX-SE installation? Link to comment Share on other sites More sharing options...
glkx1011 1 Posted August 7, 2017 Author Share Posted August 7, 2017 Done! Co-Existence = 1 and AppPath matches my FSX:SE installation path. And congratulations on a really great aircraft btw! Link to comment Share on other sites More sharing options...
Cheyenne Chief Pilot 829 Posted August 7, 2017 Share Posted August 7, 2017 I had co-existence at '1' and the correct path to the Steam installation. With parallel installations of FSX-MS/-SE and the CRJ only installed in Steam, the manager didn't work. Just installed the CRJ in FSX-MS as well and found the manager there working (the manager installed in FSX-MS, that is). Just for fun went to my Steam installation, started the manager from there, and now that manager works as well?!? (Both manager locations can see both FSX installations now.) Link to comment Share on other sites More sharing options...
GotZfunk 0 Posted August 10, 2017 Share Posted August 10, 2017 I'm having issues with this as well. I have co-existence at '1' and the correct path to the Steam installation. Should I install it to both MS and Steam editions? Link to comment Share on other sites More sharing options...
Hans Hartmann [OLD] 1419 Posted August 10, 2017 Share Posted August 10, 2017 Thanks guys. Sorry for being late with this. I already looked into it, but it seems I will have to remove all the other FSX and P3D versions from my PC to reproduce the issue. Link to comment Share on other sites More sharing options...
glkx1011 1 Posted August 11, 2017 Author Share Posted August 11, 2017 Managed to solve this issue myself with some googling after Hans's first answer. For anyone else having experiencing it, this is a link to the fix which solved it for me: https://steamcommunity.com/app/314160/discussions/1/490123832541365433/ Link to comment Share on other sites More sharing options...
GotZfunk 0 Posted August 12, 2017 Share Posted August 12, 2017 11 hours ago, glkx1011 said: Managed to solve this issue myself with some googling after Hans's first answer. For anyone else having experiencing it, this is a link to the fix which solved it for me: https://steamcommunity.com/app/314160/discussions/1/490123832541365433/ Thank you! It worked! Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4161 Posted August 12, 2017 Deputy Sheriffs Share Posted August 12, 2017 Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.