Fred Solli Posted September 1, 2012 Share Posted September 1, 2012 A small problem occured in the FSX version of the newest FTX Central. When choosing "FTX Scenery Insertion Points" I get an error saying "FTXConfigurator" has stopped working. Problem details says: Problem Event Name: CLR20r3 Problem Signature01: ftxconfigurator.exe Problem Signature02: 8.2.0.0 Problem Signature03: 4e4b9e53 Problem Signature04: mscorlib Problem Signature05: 4.0.0.0 Problem Signature06: 4ee9d7cd Problem Signature07: 3fdb Problem Signature08: 106 Problem Signature09: System.IO.FileNotFoundException etc.. When closing the error message I get the window to set instertion points and it is working. P3D version is working perfectly. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 1, 2012 Share Posted September 1, 2012 Hi Fred, I assume this only happens with the Library insert feature? Applying NA or Oceania shows no errors? Link to comment Share on other sites More sharing options...
Fred Solli Posted September 1, 2012 Author Share Posted September 1, 2012 Yes, no problem switching between the areas. Only when I choose insertion point in the menu. Sent from my GT-P1000 using Tapatalk 2 Link to comment Share on other sites More sharing options...
Fred Solli Posted September 1, 2012 Author Share Posted September 1, 2012 Sorry, seems like this error comes when changing areas as well. Link to comment Share on other sites More sharing options...
Fred Solli Posted September 1, 2012 Author Share Posted September 1, 2012 And it will not put in the areas for ORBX scenery at all. No matter where FTX central is set I have default scenery. Do bad. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 1, 2012 Share Posted September 1, 2012 Can you give us a screenshot of the error message? Can you try running FTXConfigurator located in the scripts folder. It is a silent operation, but should make ORBX entries in the scenery.cfg file. Link to comment Share on other sites More sharing options...
Fred Solli Posted September 1, 2012 Author Share Posted September 1, 2012 Tried to run FTXConfigurator from the script folder with similar result. FTX changes default.xml and AutogenDescriptions.spb, but no changes to the scenery.cfg file. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 2, 2012 Share Posted September 2, 2012 Hi Fred, so FTX Central for P3D performs with no errors? Also, could you please scroll down on that error screen and post an image of that. I want to see if there is a missing file or something similar. Thanks Link to comment Share on other sites More sharing options...
Fred Solli Posted September 2, 2012 Author Share Posted September 2, 2012 FTX Central is working perfectly on P3D. No problems whatsoever. Here is the rest Link to comment Share on other sites More sharing options...
gandy Posted September 2, 2012 Share Posted September 2, 2012 Im also getting this on fsx, just updated the libs today for fsx and p3d i did when it was released. Link to comment Share on other sites More sharing options...
Fred Solli Posted September 3, 2012 Author Share Posted September 3, 2012 Thanks Paul. I was feeling a bit alone here. Not good to here you have the same problem, but then it may be consistent for some. Link to comment Share on other sites More sharing options...
gandy Posted September 3, 2012 Share Posted September 3, 2012 I dont know if its related to this error but ive had some random elevation issues in pnw ( i don't get out of pwn much ), today i noticed it at Ocean Shores ( runway/taxiways was sunk and the ground around it was higher ), was doing some low flying around the bay in a EC135, I landed where i planed to land at western then loaded direct in to Ocean Shows and the issue was gone. My pc is on its last legs so it could be that. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 3, 2012 Share Posted September 3, 2012 Hi Fred & Paul, I am not sure why you are receiving that error message. I might need to get someone else to help out here. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 3, 2012 Share Posted September 3, 2012 OK, I think i know what's happening, your FTXConfigurator.exe is a different version (P3D version in fact), so right-clicking the file and selecting properties, your version should be 8.1.0.3 if it's 8.2.0.0, then you have the P3D version. Here is the FSX version FTXConfigurator.zip Drop it into the ORBX\Scripts and ORBX\Scripts\FTXCentral\Work folders. Hope that fixes things. Link to comment Share on other sites More sharing options...
gandy Posted September 3, 2012 Share Posted September 3, 2012 Yep mine is the p3d version, 8.2.0.0. Thanks for the correct version Ed Link to comment Share on other sites More sharing options...
Fred Solli Posted September 3, 2012 Author Share Posted September 3, 2012 Still having the same error message, after replacing to correct file. Link to comment Share on other sites More sharing options...
gandy Posted September 3, 2012 Share Posted September 3, 2012 Make sure you copy it to both folders Freds for me it was E:\Microsoft Flight Simulator X\ORBX\Scripts and E:\Microsoft Flight Simulator X\ORBX\Scripts\FTXCentral\Work I only put it in one at first and got the error but when i read Ed's post again it worked a charm Link to comment Share on other sites More sharing options...
Fred Solli Posted September 3, 2012 Author Share Posted September 3, 2012 I'll try it out tomorrow. Sent from my GT-P1000 using Tapatalk 2 Link to comment Share on other sites More sharing options...
Fred Solli Posted September 4, 2012 Author Share Posted September 4, 2012 That did the trick. Everything is in working order now. Thanks Ed for fixing this. Link to comment Share on other sites More sharing options...
Ed Correia Posted September 4, 2012 Share Posted September 4, 2012 No worries guys, glad you are back up and running. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.