Python install disables Pilotedge

[Cobra13]

i've been using Pilotedge successfully for the past year, until recently when i installed the python 2.7.3 64bit, per all instructions and forums i can find. relating to the NOAA weather plugin and using Sandy Barbours python, etc.

that appears to work as it's in my plugin list.

but my PILOTEDGE plugin is NOT in the plugin list!! ouch. so, i checked the log file:

- Finished Reading DataRefs
----------------------------------------------------------------
Loaded: C:\Users/Owner/Desktop/X-Plane 10/Resources/plugins/FTS Pilot Panel/64/win.xpl (FTS Pilot Panel\SimAvioUDPInterface).

C:\Users/Owner/Desktop/X-Plane 10/Resources/plugins/PilotEdge/win.xpl : Error Code = 193 : %1 is not a valid Win32 application.
PythonInterfaceVersionNumber = 2.73.06
Loaded: C:\Users/Owner/Desktop/X-Plane 10/Resources/plugins/PythonInterface/64/win.xpl (sandybarbour.projects.pythoninterface).

Loaded: C:\Users/Owner/Desktop/X-Plane 10/Resources/plugins/ReloadPlugins/64/win.xpl (xplanesdk.sandybarbour.ReloadPlugins).

x-assign startedLoaded: C:\Users/Owner/Desktop/X-Plane 10/Resources/plugins/xassign/64/win.xpl (barbarossa.xassign.3b7).

so as i learned, that apparently the win.xpl for pilotedge is supposedly 32bit, and since i installed 64bit python it doesn't allow it to run??... yet i run my xplane 10.35 ONLY in 64bit mode. and i sure don't see any option in Pilotedge for 32/64 bit.

is there a fix or workaround that anyone knows i can do??

i miss not using my Pilotedge.

thanks in advance.

Dave

[Keith Smith]

My guess is that the Python installation is a red herring, as is the error message about the 32-bit PilotEdge plugins. I run 64-bit Python and 64-bit PilotEdge, no problem.

Here's the relevant part of my log.txt

Loaded: F:\X-Plane 10.30b/Resources/plugins/PilotEdge/64/win.xpl (com.pilotedge.plugin.xplane).

PythonInterfaceVersionNumber = 2.73.05
Loaded: F:\X-Plane 10.30b/Resources/plugins/PythonInterface/64/win.xpl (sandybarbour.projects.pythoninterface).

The question is why it's failing to load the 64-bit version of the PE plugin on your system. Is there any error messages about the 64-bit plugin failing to load or initialize? If not, can you verify that the plugin does exist in the PilotEdge/64 folder?

[Cobra13]

thank you for responding so quickly. much appreciated.

looks like, no. the win.xpl does not reside in that folder. and i've even deleted the Pilotedge folder, redownloaded, unzipped and put back into the plugins. i'll have to triple check.
i do show the win.xpl in the root of PilotEdge..
note my jpg's attached.

should i move the win.xpl?

[Cobra13]

Keith,
that solved it! thanks!!
i deleted PE folder again in the plugins. used same download from yesterday. unzipped and placed back in the plugins directory.

now the win.xpl resides in both the root and in the 64 folder.

i wonder if either the Anti-virus moved it out? or one of the Python installs removed it. i don't know.

doesn't matter now. but good to know where the files SHOULD reside.
thanks again! really appreciate the support and PE as well.

[Keith Smith]

Very good. Just for the future, the win.xpl in the root folder is not the same file as the win.xpl in the 64-bit folder. So, copying from the root to the 64 folder wouldn't have worked. Sounds like you're all set now. I can't speak to why the file was missing to begin with, it's definitely included in the distribution. Now you know what to look for in the future, though. I'm glad you're back up and running.

[Cobra13]

Keith,
as a matter of fact, it was Mr. Norton. for some odd, very odd reason, Mr. Symantec Norton the III, decided to remove that specific file on it's own accord. it quarantined it based on its own heuristics. i.e. it didn't recognize the file. yet, it left the other win.xpl alone in the root PilotEdge folder and the 32.
it never removed it before, but then it wasn't until i installed the Python, and in trying to get PilotEdge to work again, i deleted, re-downloaded the current posted version to ensure i was working with a correct compiled copy. i'd place it in the plugins folder, and Mr. Norton, the (SOB) would obviously remove the file without notification to me.

anyhow, overriding that, and told to leave it alone. it works great as is...!!

yes, i figured the two win.xpl were not the same as you mentioned.

thanks again for all your support for everyone that posts a question to you. very admirable and highly respected, having your responses.

happy flying! ( and tennis adjudication...)

Dave