Chris Wright

23 hours ago, scandinavian13 said:

Try now

yep that did it.

thanks for the heads-up.

g'day kyle...

Looks limited to P3Dv4 updates to the 600/700 at the moment

as mentioned on the following thread (which you've contributed to), kyprianos, tom and others (and indeed me although i didn't mention which version of p3d i was using in my contribution) are P3Dv3 users with the 403 problem - ie. it goes beyond just v4.

i have the same [PMDG2] log errors as kyprianos updating the -600/700.

with or without my a/v and firewall (where 'without' means temporarily uninstalled).

p3d licence, win7 pro, fully updated, located in west oz.

G'day Clayton...

I had a similar issue around the time of release.

Advice from support in response to the ticket I raised was that a reinstall was required (which fixed the problem for me).

hth.

Quote

...distribution to parts of Asia via S3 is not as robust as we would have believed.

We are working with Amazon to find a solution in order to increase our exposure and speed...

it's not just the northern hemisphere on this 'side  of the marble' - i'm downunder and downloading the most recent update to the Op Centre currently (which has been simulating dial-up speeds for the last 40 mins) and follows a flawed 744 update at similar excruciating speed over the weekend (which Paul has ben helping with through the support portal and determined will now require a complete reinstall to address following what may have been due to a timeout with one file in that update).

i have to say that a fix to speed will be most welcome robert! whatever (presumably) amazon changed, it compares with the original 1.1gb installer downloading in just a few mins at release time.

these and other rnp approaches to aerodromes in the region are maintained and published free on Jock McIntyre's vapap site: www.vapap.com

 

jock releases updates in line with the published DAP amendments.

 

hth.

noted and thanks for the follow-up kyle.

very timely as i had exactly this issue arise yesterday.

 

 

 

Entering a top of climb ISA or Temp outside of parameters will do this

 

i miskeyed the temp as a positive number, noted the error immediately and changed it to the correct figure but this would not address the waypoint eta calculations. i tried going all the way back to cold and dark to reset the error but the only way to fix it was to reload the sim (fsx). a bit of testing also showed that having put in the corrected value, saving the flight and then restarting fs and reloading the saved flight fixed the issue and ETAs calculated correctly.

 

i couldn't find a reference to this in the manual - is there a way of resetting/fixing the problem without reloading fs or is it a case of 'don't make any typos or you've no choice'?

i changed over from fs9 only recently and have the same issue (win7 64bit system, up to date, fsx gold, -400x updated to latest version).

 

however, the problem resolves itself on my sim by moving the Bank Limit Selector at least once (ie. the outer ring of the Heading Selector Knob) - i move it right and then back to the auto position each flight. it's marked up as a pre-taxi check and since discovering this odd 'fix' have had no problems with HDG selections in the 'air'.

 

hth!

a cheap do-it-yourself alternative to experiment with for the $-challenged...http://www.free-track.net/english/

no you don't need to send an email.use the link to the support portal in the post at the beginning of this thread.as noted above, it takes a while to open/load - be patient.if you aren't registered for the support portal, never fear it's free but some have had issues with dud activiation url's - see posts on page 1 of this thread.once registered and logged, recalling it takes an age for the page to load, create a ticket by following the links.hth

g'day no name...

It loads a blank page short of the PMDG logo on the top

it's a VERY slow page to load - it takes 65secs on this machine at work using ie7 for the page to load (about half that time on my machines at home using ie8.however, once it does load it is functional for the purpose.hth

g'day corey...i had the same problem (and followed the same advice).the link in the activation email appears to have some spurious characters:here's part of the emailed link "http://support.precisionmanuals.com:9996/Main..." - i deleted ":9996" from the full url in the email and it worked correctly.hth

robin (and others that took part)...that's a great event - run it annually! a bit of team rivalry is good and running on-line will almost certainly attract increasing participation and ATC coverage.dan...in answer to your query about a map, you want a tool such as vatspy ( http://www.metacraft.com/VATSpy/ )- it shows who's connected on vatsim, where they are, etc. it's not the only one out there but it's one of the latest.

my money's on ear wax which is also consistent with the greasy finger marks on the glassware several pages back. :(

...and as noted umpteen times, it happens in fs9 too so it isn't a simconnect issue!

...and it's not limited to fsx either, thre are references to fs9 users with this problem in this thread (and using add-ons other than pmdg and level d) - implies simconnect isn't the issue.

re: rob's suggestion to use active sky - if you have active sky advanced, you may still suffer from dodgy oat results - see this thread on the activesky forum which affects large number of asa users regardless of weather source or fs platform - http://forums1.avsim.net/index.php?showtopic=261770

gee stefan...perhaps you didn't ask the right question - see the last line of the following link which makes it clear manual activation can be arranged through the support service.http://ops.precisionmanuals.com/wiki/PMDG_Product_Activation

g'day maik...coffs' icao id was changed about 2 years ago (or thereabouts) to YCFS.if your airac is up to date, that should fix it for you.

So far only in the mountains

my fs9 report (early in this thread) was over water.

g'day jim...maybe a better question is in two parts '(a) have we enough here to conclude we have a problem with asa and ( b ) that it can be fixed?'speaking as a non-developer, the evidence seems persuasive for (a) - many have reported fsx above, i have reported fs9 above, not limited to pmdg add-ons, the latest report above is also with a default aircraft, restarting asa is one method reported as a work around. is this still too circumstantial or do we have the smoking gun here?!what does this mean then for ( b )?

i can also report my first experience of this problem just yesterday...fs9.1, asa (up to date), wilco/feelthere e-jet series (v 1.6), vista64 os (up to date), approx 3 hrs running the sim, on-line (vatsim) weather data.problem occured near waypoint ipkon (from memory) south of java, f380.completed crossing of oz with same setup and add-ons earlier in the day (on-line for around 6hrs) without issue.for info.

re: uac - it's that really useful 'feature' in vista that pops everytime you click on something, blink, or have a scratch, asking if you really want to do that!go google for 'turn off vista uac' and you'll find a gazillion tips on the net devoted to getting rid of it.then go to the other thread we've got going on your fs 9.1 woes here - http://forums1.avsim.net/index.php?showtopic=259286 which includes the 'turn off uac' suggestion again.

mike...it sounds to me like you need to start again.remove fs9 completely and remove the associated folders (do this using the uninstall utilities, don't just delete folders - you need the registry entries to be correctly removed).then:. if it's not disabled already, turn off vista's uac. install fs 9.0 from the disks running the setup proggie in 'run as administrator' (you must also be logged on your pc as a user account that has admin privileges).. once fs is installed and before you try and update it, run fs9 (again as 'run as administrator') and go through the full set up of database builds it does when first installed.. once you're in the sim, load the default flight at least once and then close the sim.. go to your fs9 folder and check that fs9.exe is indeed version 9.0 (this is saved in the properties info when you right clcik on the file with that name in explorer).. if it is 9.0, download the msfs 9.1 patch and make sure you copy it to four fs9 folder BEFORE you run it (the instructions say it should be in your fs9 root folder when you install).. run the patch as 'run as administrator'. when it's complete, run fs9 and let the database rebuild etc. and load the defo flight before closing the sim again.. check the fs9.exe file again and you should show the correct version (9.1...).you should now be good to go with adding your add-ons ('run as admin' when you install them).if you mess up any of this stuff, you can get duff registry entries and things get unpredictible.hth!