Thanks Tim,

I don't think "Program Files (x86)" is dangerous as long as it is not under C: which has special restrictions indeed. I never had any issues with this with previous versions of Plan-G. Moreover, the Client is able to build the database, which is quite strange indeed, it's just the Flightsim PC which stalls.

I'll have a closer look into the issue when I find more time and report here, if I find anything worth reporting.

Thanks and kind regards, Michael

First, thanks for taking care.

scenery.cfg is attached, however, there might have been some activations/de-activations in-between. The contents as such shouldn't have changed though (as far as I recall).

One additional info: I was able to rebuild the scenery database on a Client laptop without any issues based on the same Prepar3d3 installation (networked) (and the same version of Plan-G 3.1.3 - 113).

Kind regards, Michael

Hi,

after I could not rebuild the database, I deinstalled 3.1.3 including all user documents and AppData files and made a completely new installation. Administrator right it set. I am still unable to build the database for Prepar3d3. However, I can build the database for Prepar3d2.5 which is still on my system. When I try to build the Prepar3d3 database, the build stops within a second and that's it.

Log file is attached, but seems to give no hint.

This is under an up to date Windows 10. I double-checked the paths are correct.

And idea what could go wrong?

Thanks and kind regards, Michael

I set the IPs for my machines under Windows network/adater settings on the respective machines, which did work as well. I feel a bit uneasy messing with the router.

Kind regards, Michael

I just wanted to ask for this very same feature when a search provided this contribution. I would find it very helpful if the airport diagrams could be overlaid over the main map when zooming in or at least having the aircraft moving within the separate airport diagram.

Thanks for considering and
kind regards, Michael

Hi

they are hidden under

C:\Users\$Your Profile$\Documents\Plan-G Files\Data

Kind regards,
Michael

Exactly the same with P3D2.1 here. Transferred the data from the main PC, which worked, although I'd be happy to be able to create the database over the network again.

Otherwise  things are really great.

Kind regards, Michael

Hi,

I am not an expert, but as far as I see your simconnect.xml looks fine and similar to mine.

No you don't need another simconnect library, at least I didn't. I used PlanG with Prepar3d1.4 before and only had to copy simconnect.xml from the Prepar3d1.4 config directory into the Prepar3d2.1 config directory, and PlanG was up and running on the laptop immediately.

Hope you get it running, too,
kind regards, Michael

Hi,

yes. it works remotely via Simconnect. I had it working in 2.0 before and did not change anything, it just worked (after restoring the simconnect.xml file).

Maybe you need another simconnect library? I have several of them installed, not sure which one Plan G actually uses. I read older Simconnect versions are part of the P3D2.1 SDK.

This is the GPS aspect. I did not yet try flight planning, though.

Kind regards, Michael

This case can be considered as solved. I deleted (actually shifted) several folders in advance of installing the patch, as suggested by LM. I returned several files afterwards, but forgot simconnect.xml. Now all is fine, and Plan-G is working again.

I tried and even bought several flight planners/moving maps, but found nothing better for VFR than Plan-G. Maybe, Skydemon would be, but this is expensive subscription based - a no-go for me.

Thanks, Tim, for that gem.

Michael

Hi,

after installing the recent Prepar3d 2.1 patch from LM, which went flawlessly, Plan-G does no longer work for me ("stops working") as soon as I try to connect to the simulator. This is over a Network/Simconnect. It has been working until the patch.

This is with Plan-G3 3.0.4.59, the most recent version does not work at all (like I mentioned in another thread). I even tried the obsolete Plan-G 2 giving the same issue.

Windows error protocol first states a "null reference exception" in .Net and next an error in an unknown module of Plan-G3.

Is this only me or does anyone else have this issue?

Now I am completely lost in heaven.  :(

Thanks and kind regards, Michael

Hi Russell,

I am afraid, the .net issue is only one of several ones causing this message. Here's one more experience: After installation on my main machine failed, I tried the networked laptop, which I use most of the time anyway for running Plan G. This is still on .net 4.0 (there was no need to upgrade) and it's able to run Plan G 3.07.71 indeed.

Perhaps you can find a solution in one of the other threads?

Kind regards, Michael

Excellent news, Russ, which got you another little donation.

Kind regards, Michael

Reginald,

I can. Just look for the Programs and Functions Icon in the Control Panel. There you will find Microsoft .net Framework 4.5.1. Right clicking gives you the Option to change/uninstall it.

Afterwards make a Google search for .net framework 4.0. Microsoft has the older versions archived (entry 01).

http://www.microsoft.com/de-de/download/details.aspx?id=17718

This should do it.

Personally I would like to see another solution as some other programs require the most recent .net Version (if I recall right, it's suggested for Prepar3d v2, too).

Kind regards, Michael

Hi,

I get the same error after installing 3.0.7.71.
---------------------------------------------------------------
Anwendung: Plan-G3.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.
Ausnahmeinformationen: System.TypeInitializationException
Stapel:
   bei Plan_G3.App..ctor()
   bei Plan_G3._Main.Main()
---------------------------------------------------------------
(read: exception error)

I installed .net 4.5.1 a few days ago, and for a reason, as another program required it. I am not really inclined to de-install it for 4.0. There should be a better solution.

Any idea what I can do? As a temporary fix, I returned to 3.0.4, which works.

Thanks for any help and
kind regards, Michael