November 2, 20169 yr Just a head's up that installing ChasePlane corrupted my exe.xml file in P3D, which required some minor hand editing to correct. Presumably, the faulty syntax error occurred when the installation routine was disabling EZDok and inserting the ChasePlane.exe into the exe.xml file. The syntax error affected the ActiveSky 2016 entry. I post this just in case other users experienced anything similar. Wayne KlocknerUnited Virtual
November 2, 20169 yr Commercial Member Just a head's up that installing ChasePlane corrupted my exe.xml file in P3D, which required some minor hand editing to correct. Presumably, the faulty syntax error occurred when the installation routine was disabling EZDok and inserting the ChasePlane.exe into the exe.xml file. The syntax error affected the ActiveSky 2016 entry. I post this just in case other users experienced anything similar. Hi, Can you provide us the original file so that we can experiment with it? Thanks! Keven Menard Technical Director, //42.
November 5, 20169 yr I had the same issue Keven along with my joystick disconnect issue. It also caused Couatl not to launch as well as an error with Active Sky.
November 5, 20169 yr Same issue here. There was an orphan "</Launch.Addon>" line that screwed up the xml parser.
November 5, 20169 yr Author Same issue here. There was an orphan "</Launch.Addon>" line that screwed up the xml parser. Exactly. Keven, I've already edited the file so that everything works now. Wayne KlocknerUnited Virtual
November 5, 20169 yr Commercial Member Thank you guys, I forwarded the thread to responsable authorities! Should be fixed in no time! Keven Menard Technical Director, //42.
November 6, 20169 yr Hello guys, If you can reproduce the issue could you please send me your initial EXE.xml before ChasePlane modify it? Thanks Michaël Villeneuve-Normand Co-Founder and Developer, OldProp.
November 6, 20169 yr Do you still need the exe.xml file with the reported issue? Roy Asus Maximus Hero VIII, I7 6700K @4.8Ghz, Corsair H110I GTX, 2X8Gb Corsair Dominator @2400Ghz, Asus GTX1070, W10 on M.2, 2x 480GB SSD Corsair, EVGA NEX750G, 6X HSAP fan, Corsair Strafe RGB Silent, Corsair M65 RGB, Asus PG278Q
November 6, 20169 yr Do you still need the exe.xml file with the reported issue? Yes the version before chaseplane touch it. Michaël Villeneuve-Normand Co-Founder and Developer, OldProp.
November 7, 20169 yr Sorry, I thought you meant the file after CP install Roy Asus Maximus Hero VIII, I7 6700K @4.8Ghz, Corsair H110I GTX, 2X8Gb Corsair Dominator @2400Ghz, Asus GTX1070, W10 on M.2, 2x 480GB SSD Corsair, EVGA NEX750G, 6X HSAP fan, Corsair Strafe RGB Silent, Corsair M65 RGB, Asus PG278Q
November 8, 20169 yr Commercial Member We have pushed an update for the exe.xml corruption. Thank you for your patience and reports Keven Menard Technical Director, //42.
November 9, 20169 yr Thank you but how do i fix my exe.xml? Roy Asus Maximus Hero VIII, I7 6700K @4.8Ghz, Corsair H110I GTX, 2X8Gb Corsair Dominator @2400Ghz, Asus GTX1070, W10 on M.2, 2x 480GB SSD Corsair, EVGA NEX750G, 6X HSAP fan, Corsair Strafe RGB Silent, Corsair M65 RGB, Asus PG278Q
November 9, 20169 yr Commercial Member Roy, You can restore the backup file from your %appdata%\Lockheed Martin\Prepar3D v3 folder Keven Menard Technical Director, //42.
November 10, 20169 yr Thank you Keven Roy Asus Maximus Hero VIII, I7 6700K @4.8Ghz, Corsair H110I GTX, 2X8Gb Corsair Dominator @2400Ghz, Asus GTX1070, W10 on M.2, 2x 480GB SSD Corsair, EVGA NEX750G, 6X HSAP fan, Corsair Strafe RGB Silent, Corsair M65 RGB, Asus PG278Q
Archived
This topic is now archived and is closed to further replies.