This sounds similar to the problem I have experienced - see http://www.tasoftware.co.uk/forum/index.php?topic=2217.0.  I have found a fix by placing a clean copy of UIAutomationCore.dll in the PLan-G folder.  You may want to try this.

Tim

I am not one to give up easily.  I reviewed the small detail of the error message when Plan-G crashed, and cross-referenced bits of it with other FSX error posts (not only Plan-G) in various forums.  The notorious UIAutomationCore.dll kept cropping up so, as a long shot, I tried dropping a 'clean' copy of this dll in the Plan-G directory.  Hey Presto! - I now have both build 50 and 51 running OK.

I don't know enough about what UIAutomationCore.dll does, or how Plan-G uses it - but perhaps a helpful result for other users who have problems with Plan-G to try?

Mike L

Tim

I had hoped that reinstalling build 50 would work but unfortunately not - the same error.

Tried your suggestion, Tim - sadly no luck  :(

Tim

I'm afraid this install just does not work for me.  I have tried the standard recovery techniques, uninstalling and re-installing (with Registry clean and reboot in between) but still to no avail.  Can you confirm, from the log file that I posted above, that the installation is completing OK? - it seems to be very short and doesn't give any clear statement that installation was completed OK.  Is there a known problem with 64-bit systems?

I had a closer look at the problem details from the "Plan-G3 has stopped working" dialog box (see below).  Although this code is largely beyond my understanding, I do wonder about the System.DllNotFoundException.  Could my system be missing some key dll which is being called by Plan-G?

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01:   plan-g3.exe
  Problem Signature 02:   3.0.2.51
  Problem Signature 03:   50d0decf
  Problem Signature 04:   UIAutomationTypes
  Problem Signature 05:   4.0.30319.17929
  Problem Signature 06:   4ffa7be8
  Problem Signature 07:   e
  Problem Signature 08:   0
  Problem Signature 09:   System.DllNotFoundException
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   2057
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Have just installed build 51 after previously uninstalling build 50.  Installation seemed too quick.  As soon as the program opens it crashes with the standard MS dialog box saying Plan-G has stopped working.

Nothing helpful in the log file - except that it looks as if installation didn't complete properly ...

20:56:37.7

---===+++===---

20:56:37.7 Starting Plan-G, build 3.0.2.51
20:56:37.7 OS is Microsoft Windows NT 6.1.7601 Service Pack 1
20:56:38.0 InitDataFolder
20:56:38.0 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\PlanG3_FSX.sdf
20:56:38.0 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\PlanG3_FS9.sdf
20:56:38.0 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\PlanG3_XPX.sdf
20:56:38.0 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\PlanG3_NAVI.sdf
20:56:38.0 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\UserWaypoints.sdf
20:56:38.1 Data Source = C:\Users\mike\Documents\Plan-G Files\Data\MEF.sdf

Thanks, Chuck - log file attached.  I am running build 46.

My X-Plane is 32-bit ver 10.10.  I decided to hold off installing a 64-bit version while it is still beta.

Now updated to build 50 and the X-Plane database seems to have been created OK.   ;D

And the log file is to be found where?

Tim

Trying to build an X-Plane 10 database - the process hangs at 20220 parking spaces and I have to shut down Plan-G via Task Manager.

Any suggestions?

Mike L

mikegogs

I reported the same problem in a separate thread which I strted just over a week ago (http://www.tasoftware.co.uk/forum/index.php?topic=228.0), and several of my regular online flying contacts have confirmed they have the same issue.  I believe it is related to the version of Plan-G - like you, I cannot see online traffic with 0.8.1.389, but online traffic is visible with the earlier version 0.8.0.380.

I'm not sure whether Tim sees this as a significant  problem in relation to his other priorities for the development of Plan-G.  I am happy using the 380 version.

Quote from: tim arnot on November 24, 2009, 03:23:32 PM
Is this connected with SimConnect or FSUIPC?

Tim - in my case (and I was one of Frank T's test session) it was with SimConnect.

Tim

Thanks - I got the local connection on to SimConnect.  But - back to my original question about IVAO traffic not showing up.  I did a test online with three other Plan-G / IVAO users this evening and it looks to be a version-related glitch.  The two users with 0.8.1 (I was one, Frank Turley the other) could not see the others (or indeed any IVAO traffic), but the two using 0.8.0 could.  I changed to 0.8.0 and - hey presto - the other traffic became visible.  Range was rather less than the settings suggested - around 20 nm, although set at 100 km.

Tim

Yes, traffic is visible in FSX.  I didn't check the View menu - will do next time.

Plan-G connects to FSX from my laptop (LAN) via SimConnect but, if I choose to run it on the FS machine instead, it connects via FSUIPC (that's another question - why not the same protocol in both cases?).  But regardless of whether Plan-G is running locally or over the LAN, it doesn't pick up the IVAO traffic - which was certainly within the range which I have specified.

Maybe something wrong with my configuration of 0.8.1 but it does not display other online (IVAO) traffic.  FSX AI traffic shows OK though.

Any suggestions?

Tom

I did read the download and installation instructions.  As stated above, I was under the impression that my laptop already had the correct version of .NET installed, in common with my other PCs.  When I ran into the problem described, I fired off my request to the forum, then thought to check the .NET version installed.  Tim's response appeared just as I realised my mistake.  I have acknowledged my carelessness already: having you gratuitously rub my nose in it is not a great welcome for a newcomer.