News:

Plan-G has over 1700 followers on FACEBOOK! Click HERE and add your support

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - psimester

#1
Plan-G / Re: Snippets losing NDB frequencies
February 07, 2021, 05:17:29 PM
Thanks, Tim. This is a really great piece of software!  :)
#2
Plan-G / Snippets losing NDB frequencies
February 07, 2021, 03:13:34 PM
Hi. Apologies if I've missed this in a previous topic, but I've searched and not found an answer. I'm using v3.2.2.167 with FSX and have recently started using snippets.

If I save a complete flight plan which includes NDBs and then reload it, the NDB names and frequencies show in the Description column of the Flight Plan window. However, if I delete the origin airport and save the remainder of the flight as a snippet, reloading the snippet causes the NDBs to become 'merely' waypoints with nothing showing in the Description column.

This is frustrating me as I obviously want to use snippets to save time, but after loading a snippet I'm actually having to delete each NDB waypoint and then add it back in to get the frequencies to show - which somewhat defeats the purpose.

Can anyone confirm whether or not I'm missing something? I've used Plan-G for years and love the software, so this is really frustrating! :'(

#3
Very many thanks, Tim. This is a great bit of software!!
#4
Plan-G / Aircraft Profile missing decimal point
May 24, 2020, 04:53:17 PM
Hi, I see this issue was raised a couple of years ago but there appears to be no 'reply' facility to the post, so I apologise for starting a new post on the subject.

I'm using v3.2.2.167 on Windows 10 English setting, and attempting to create Aircraft Profiles. Whilst the v3 Manual and a couple of Profiles I've downloaded show the decimal point (for example in Econ. Fuel and Perf. Fuel), I'm unable to get the decimal point to register when I create a Profile myself.

As no-one else appears to have raised this issue I'm not sure if there's something in a setting somewhere that can cause this, a peculiar effect of a type of keyboard, or whether it simply doesn't bother anyone else  :D

Does anyone have experience of this problem and, more importantly, is there a workaround?