Sounds quite indicative of not having Simconnect not installed or "talking to" the aircraft.

Try this... in the P3D root folder, locate:

\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi

Execute the Simconnect.msi. Not much will happen in the way of prompts or anything but it will no doubt install. Open up P3D and let us know if the problem is solved.

By the way, this also happens with the P3D version of the 777 so it really doesn't have much to do with using the FSX version. Odd.

Hmm, that's odd.

I'm using the correct P3Dv2 version but, as stated, still have simconnect issues, the symptoms of which are exactly as you describe. Said issues are immediately fixed upon executing the simconnect package.

Some folks have claimed to successfully use the -300 and freighter versions in P3D, even though CS has only released them for FSX. I would have figured that this would mean the base model would work as well. I can't attest to this since I only have the base model.

Have you tried following the proper activation procedures (running the installer as administrator, using manual offline activation, etc.)? Have you deleted the Captain Sim registry keys?

Also, I assume that you had FSX installed at some point? I wonder if something is still pointing the aircraft files to your FSX installation, whether you've deleted it or not...

Then my hunch is probably correct: I think lots of folks try to simultaneously install aircraft into both FSX and P3D and yet it will only work in one or the other... although typically only FSX. That it works in P3D legacy mode seems to essentially confirm that.

I can't blame you for wanting to keep your FSX installation (I've moved on, so I can't entirely relate) but we need someone to chime in that's successfully installed a CS aircraft--or any 3rd-party aircraft--into both simulators at the same time in order to see if there's a method that works.

Not to upset CS (although I'm becoming doubtful that they meander into their own forum with any regularity these days) but I'm pretty sure you don't need to purchase another 777. Once you have a setup with only one simulator, I'll betcha it works.

If you have space left on your hard drive(e.g. 40+ gb), you could try partitioning off a large block and installing windows, P3D, and the aircraft to ensure that it works. If it does, delete the partition and merge it back into the rest of the drive. But that's a lot of hassle...

garrettprs wrote on Oct 1^st, 2014 at 2:52am:


Well, I don't use FSX anymore (in fact it doesn't even work, for whatever reason), and I do not have CS777 installed in FSX.  But FSX remains, just as a placeholder, until I get all the way moved over.  I generally remove stuff as I get it working in P3D.

Quote:


Sorry this is not the case, as I explained above.

Are you suggesting that it work if removed FSX entirely? 

Remember the darn thing works fine in P3D if I enable Legacy Mode.  I'm only looking for a way to get this working in Normal Mode in P3D.

Quote:


Again you are saying it will work when FSX is totally uninstalled?  Because I DO NOT have CS777 installed in two places.

Quote:


Agreed.  Not going there.

Don't be fooled into thinking that because your user account is an administrative account, that you are running FSX and/or P3D as an administrator. With Vista, Win7 & Win8/8.1, you are only really running them as an administrative if

1) you right click on the FSX/P3D shortcut and select the Run as administrator option:

http://i669.photobucket.com/albums/vv58/Markoz958/runfsxasadministrator_zpsb2349...

2) right click on the FSX/P3D .exe files, select Properties, select the Compatibility tab, then checkmark the (place a tick in) box beside Run this program as an administrator (under Privilege Level):

http://i669.photobucket.com/albums/vv58/Markoz958/runfsxasadministrator.jpg~orig...

It is highly recommended NOT to install FSX (and I assume the same applies to P3D) in the C:\Program Files or C:\Program Files (x86) because Windows has too many restrictions on these folders (and everything within them). You are better off installing them in the C: root, i.e. C:\Microsoft Flight Simulator X and C:\Prepar3D v2.

My FSX and P3D are install on the F: drive in Windows 8.1 (because Win8.1 is installed on my F: drive): F:\Flight Simulator X and F:\Prepar3D v2, and they both work fine.

I noticed that I do not have any simconnect entries anywhere.  Probably that is my problem. 

However, simply running that simconnect.msi does do anything as far as I can tell...

garrettprs wrote on Oct 3^rd, 2014 at 9:38pm:


Sure do.