The combination of Prepar3D, It's Your Plane (By Robert Cezar) and Plan-G by Tim are simply the best combination of Flight Simulator tools one can buy and use (of course Plan-G is free and anyone using it should donate to Tim).  With P3D running on a host and IYP/Plan-G running on a client they make for a fantastic learning/operational experience.

Assuming you installed Plan-G to \TA Software:

\TA Software\Plan-G_log.txt

Have you "Shared" \ProgramData on the host machine?

If not:

Right click on the \ProgramData folder on the host
Click properties
Click the sharing tab
Click the Share Button
Add or select users that are allowed to access that folder, for example "Everyone" and allow read/write access to the folder
Click Share
It takes a few moments for all items in the folder to be "Shared"

Hi Peter and Tim.

I think I have finally pounded into my hard head what I was misinterpreting with the DEM versus the manual.

When I defined the waypoint at Scafell Pike I expected the DEM display to immediately update with that terrain being showed.  Apparently Plan-G does not update the DEM display until you define the next waypoint beyond that (At least that is what I observed conducting several waypoint tests, I hope I am correct on that?).  If that is indeed the case I would suggest adding something about that to the manual so that dense people like me won't get into trouble.

Also I was neglecting to add my flight altitude to each of the waypoints along the way which showed me plowing into Scafell Pike until I added the flight altitude to each waypoint and defined the next waypoint.

I love Plan-G.

Thanks for the reply Peter.  Very informative and I appreciate you taking the time to work with me.

I guess my tiles are ok then since they are the same size as yours.  I cannot figure out for the life of me why my Terrain DEM display is so different than yours (see attached screen shot).  I have examined it very carefully to make sure it conforms to your figure in the manual.  Now that I feel better about the terrain files I will look even closer to see what I am probably doing wrong.

My Keswick waypoint is at 54.6026992797852 & -3.13316345214844

Pretty close to each other.

I should mention that I lived in SouthWest Colorado for several years and am very, very familiar with the elevations etc. there.  Many 11,000 foot peaks and low valleys there. Plan-G, DEM etc. are right on the money and work perfectly showing correct elevations of peaks etc. in that area.

Don't get me wrong Peter,  I certainly have no complaints of any kind about the manual.   It is excellent.   I just got stuck on these points and wanted to clear them up for my own education.  I considered a few payware flight planners and I thought Plan-G was better than all of them.  I sent Tim a couple of donations to help out.

I suspect I am on the track of the problem.  In looking at the flight plan tutorial I noticed that my DEM display is not even close to the displayed figure (Figure 79) in the manual.  I downloaded the DEM files from NOAA as described in the manual.  I suspect there is some problem with the downloaded files.  I placed them in \TA Software\Plan-G v2\DEM folder.  But I find that the file sizes are somewhat less than what the NOAA site says they should be after extraction.  I have downloaded and extracted them several times as zip, gz or tgz files.  They are always 101,250 kb and 126,563 kb after extraction instead of the 103,680 kb and 129,600 kb that the NOAA site says they should be.  I have tried qzip, winzip, jzip and all of them extract to the same incorrect size.  If I look at the compressed files, they are the correct size. 

I'm stumped on this one but I suspect the DEM files are the problem I am having with the Elevations/Altitudes described earlier.

I did exactly what the manual said to do, Page 70, step 6 "Right click on the name Keswick shown on the map and complete the user waypoint dialogue box".  So I expected that my elevations would be reasonably close to what was shown in the manual.  So the "Problem" is that perhaps the manual should indicate that "your displayed elevations may vary somewhat from the elevations shown in this manual".  Remember I am reading the manual word for word so I would expect that I see the same results as the manual when I follow the instructions.  The manual says click on the name Keswick so I did!

I seem to have run into another problem in the manual, which seems to be inconsistent.

Page 71, step 10.  This paragraph indicates that I should be seeing terrain altitudes of 2605, 2994 and 3959 feet respectively on the DEM.  When I move the cursor on to the DEM display (refer to attached screenshot) and on to the first highpoint at 17.8 miles it indicates an altitude of 994 feet instead of the 2605 that the manual appears to be using.  When I moved to the next higher point at 23.8 miles the DEM display indicates 2110 feet as opposed to the manual indicating 2994.  The final point in the manual (which I presume would be the last ridge, so to speak, of the DEM display) indicates 3959 feet, whereas I see 1890 at 24.8 miles.

I checked options to make sure that I have runway dimensions set to feet, which I presume would apply to altitude also.  Perhaps I am totally misinterpreting the manual as opposed to the DEM display.  Right clicking at various points between 18-26 miles of the plan seems to indicate discrepancies between the manual and what is shown for the altitude along those points.

Hopefully, I am simply misinterpreting what I am seeing on the screen as opposed to the manual and need to be corrected.

I really like Plan-G and have spent a lot of time with it and reading the manual very carefully.

On page 69 of the Plan-G manual,step eight of the tutorial states "In FS, you have already selected PARKING 1 - RAMP GA SMALL".

I did not find anything in the previous steps on that page to say that I should start FSX, select a Cessna 172 and go to EGNC, PARKING 1 - RAMP GA SMALL" prior to starting the tutorial.

I find this a little confusing, should I have previously started FSX and selected EGNC etc. prior to starting that tutorial?  Or, is this just an omission in the manual?

I am trying to go "by the book" and read the Plan-G manual carefully.

Other than this minor problem I have found the manual to be quite good.

you got it!!!!  I missed it completely that I should have put an IP address in there instead of a path to FSX.

Simconnect working fine now.  Wonderful program Tim.

Thanks again for all your help.  Hopefully this thread will be a help to others having trouble with Simconnect.

John

Hi Tim

I have FSX all reinstalled and everything working again, a VERY long job.  I started out with FSUIPC/WIDEFS on Plan-G which works fine.

I wanted to use Simconnect.xml instead of FSUIPC/WIDEFS with Plan-G. so I then uninstalled Plan-G so I had a clean install of Plan-G to work with.  I restarted Plan-G setting it up to use SimConnect instead of FSUIPC/WIDEFS.  Still no joy, when I click Connect in Plan-G I get a time out error with no connection.

The paths setup in Plan-G are correct (Z:\FSX, Z:\Users\xxxx\AppData\Roaming\Microsoft\FSX).  Plan-G builds the databases just fine so it is seeing FSX on the FSX computer.  I setup Plan-G to use Simconnect, IPV-4, Z:\FSX, Port 15300 (See attached SimConnect.xml file).  The Simconnect.xml file is located in the FSX.cfg folder on the FSX computer.  I presume I do not need a Simconnect.xml file on the client computer?  Plan-G is installed only on the client computer and not on the FSX computer.

I added the code in the lower part of the .xml file, the original code that existed in the SimConnect.xml file is in the top.  I tried changing the port from 15300 in the lower code to 15400 and vice versa with no difference.  I changed the port number in Plan-G each time I modified the port number in the SimConnect.xml file, exited Plan-G and restarted FSX on the FSX computer then restarted Plan-G on the client computer.

Obviously I still do not have something setup correctly.

Thanks Tim.

I have the "Gold" version which includes Acceleration so that should not be a problem.  I will probably start the uninstall process tomorrow.  I'll deal with the simconnect thing after I have rebuilt everything.

Thanks for the sympathy, I am NOT looking forward to this!

I'll let you know after it is all done.

That seems to have fixed the problem. 

I went to File > Options > Traffic - Unchecked Aircraft Moving and Show Trail.  Exited Plan-G and restarted.  Seems to be working ok.  I also use Super Traffic Board from FlyingWSimulations (I am a beta tester for him) as well as Ultimate Traffic 2, MyTrafficX and REX.  They are used across the network from the same client PC that Plan-G is on.  Perhaps there is some interaction between one or more of them with Plan-G causing the crash cured by turning off the Traffic?

I use a simconnect.xml on them as well with no problems.  I could not get Plan-G to work on simconnect.xml so had to fall back on FSUIPC and WideFS for the time being.  I had modified the simconnect.xml contained in the user folder to use the code from the manual but I am not doing something right.  Everytime I modified it to include the code from the Plan-G manual all of my other programs (REX, SuperTrafficBoard etc.) stopped working on the network.  When I took out that code everything worked ok again so I am messing up some place in it.  I am attaching the .xml file, if you can look at it I would appreciate knowing what I am doing wrong.  It was originally .xml but I renamed the file to .txt so that the forum would allow me to upload it.  The upper part of the simconnect is the original code that worked with my other utility (STB), the lower part is what I added for Plan-G.

I changed from KSEA to KJFK on FSX and Plan-G followed nicely but when I used the mouse wheel to zoom in the display I got the error attached.  I just clicked Yes and Plan-G went right on working.

I am planning to uninstall FSX and all of my addons and re-install in a \FSX folder to make life a bit easier.  A massive job since I have an incredible amount of scenery, aircraft, utilities, airports etc. to re-install but I think its for the better.

Thanks for the help, donation coming very shortly.

John

I disabled the weather in options.  WideFS and FSUIPC show connected.  2-5 seconds after I click on connect Plan-G crashes.

log attached again.

I finally wound up copying the database files from the \TA Software\Plan-g\Data folder on the FSX machine over to the client.

For some reason I cannot get Windows 7 to allow me access to the \Program Files (x86)\Microsoft Games\Microsoft Flight Simulator folder.  I have been able to share any other folder on that computer with any other computer on the network but not the Program Files folder.  I have tried many times to set sharing - permissions - advanced sharing to allow access to that folder from a client to the FSX computer but have never been successful.

I guess I will just live with copying the databases from the TA Software folder over to the client and run them from there.

I ran Plan-G and all seemed normal.  When I clicked on Connect, Plan-G displayed a map for the airport I was at (KSEA) and then a couple of seconds after that Plan-G crashed.  It now crashes within 10 seconds after I start Plan-G.

Log file(s) attached.  I deleted the first attached log file and started Plan-G again which crashed after about 5 seconds after I started it.  The second attachment is that log file.