jordanal

I would like to request the same - very much appreciated of this effort, but the after-flows would conflict with my FS2crew efforts. Thanks again!

I couldn't find a specific forum support thread so I'll mention it here. Is the list of recent forum topics both on the Avsim front page and the list at the top of the forums broke (missing many topics)? There seems to be a bunch of topics that never make it to the list - almost as if the entire "Commercial Forums" section or more, is being ignored. Specifically, PMDG's recent updates by RSR this weekend were never on the list, let alone any other PMDG topics. Yes, I have been logged-in while noting this issue. I think the 'recent topics lists' may need some attention. Thanks.

Thanks Capt. Rob - great update and the P3D licensing correlation to recent "unflattering attention" makes perfect sense now that I think about it. Good update, sir.

Capt. Rob (or Ryan), Assuming for a second that it's primarily the technical part of the PMDG dev-team that has been dealing with SP1, has management (Rob) by chance had any progress (hopefully in parallel with the elongated SP1 efforts) to deploying the 777 and eventually the NGX for P3D v2? I guess I'm wondering if any/all P3D effort was sidetracked as well by SP1? Is there any chance someone on the beta team is looking at SP1 in P3Dv2 while development is still ongoing? Thanks for any news you might have on this front.

No, the AI flocking is simply a side affect of continuous time injection (syncing). His issue sounds like a time-zone file problem, which I know FSRT changes/updates as well. Maybe it's outdated?

I'm going to throw in some legacy FS time-sync knowledge that may not be widely known anymore - yes, possibly lost to previous FS ages/versions. The long-standing issue pertains specifically to those who have/use AI aircraft in their Sims (FS2002/2004/FSX). Whether the time is synced by FSRT or FSUIPC, or others, the micro time-correction they issue into the sim can and will cause AI aircraft to group (flock) into and around airports - especially Mega airports with large AI fleets. You may notice on some occasions what appears to an invasion of AI aircraft inbound to your current airport. This is caused by the time-sync process stuttering the AI engine. To the best of my knowledge, this issue was never addressed by any time-sync utility (and I've owned/used most of them over the years). Corrected time-zone files don't seem to be an issue, but messing with the internal FS clock can have unpredictable results.

Sorry all, the jpg's are gone and I've performed a thorough search of my local backups to no avail. Unless someone else saved the article, including the jpgs, there's not much more I can do.

Agreed, posting at 0016 April 1, it almost definitely a joke (at this point); he does something tricky every year. But knowing Capt. Rob's high level of humor, I wonder if he's using a little reverse psychology. Didn't he post in one of his recent updates that he had something new in-store for us? What if the weather radar joke today is actually released with the 300/sp1? Then this announcement will have served two purposes today (joke and future real announcement) and I can hear him laughing now, and again when the 300/sp1 is released - he'll post a big 'ol large "Gotcha!" then as well.

Is that Capt. Rob posing with his personal flightsim rig at the top of the article? LOL... :lol: OK, I give up, Capt. What's the toilet paper for? :LMAO: I too thought it was a decent article (overview), especially given the circumstances...

^^^^^^^^^^^ Exactly what Zeljko said - no better logger, tracker, critique (all in one) program. Been using it for over 10 years.

If it helps, I use Thomas Molitor's "Flightsim Flight Keeper" for not only logging and in-flight analysis, but it is very usefull for displaying scenery maps as well. I run FSFK on a WideFS (second PC) and when you zoom in to the current airport in it's map, you can see all the taxiway details and other AI as well. Makes getting around a big airports a snap. Best of all, it has a scenery scanning utility that scans all your actual FS airports/AFCADs and that is what is actually presented in the maps - kind of like what MakeRwys does for Radar Contact, etc. http://www.flightkeeper.net/Gallery.html

Just don't give the Apache and Linux gurus the root password!

Does anyone happen to have the recent KMCO patches and somehow willing to share? :Praying: I purchased the scenery from SimMarket yesterday not knowing the stupid Taxi2Gate domain is down/unavailable. I've searched the iFlySimX forums for an alternate link to no avail. These guys are getting on my nerves - first we had to wait 4 months for the MMMX crash-detection issues to be resolved, now they can't keep their website registered. :angry: Later: A kind soul has already helped - thanks.

I've always used the in-flight map display included with FS Flight Keeper (FSFK). Full FSUIPC/WideFS integration running on my Client PC. The live map uses data collected by a scenery scanning utility so it shows the exact scenery data you use in FS (i.e. AFCAD data) which is very useful for taxing at the larger airports. It also depicts all my AI traffic (both on the ground and in the air). Not nearly as nice as a Google Satellite background but it does come with basic topo ground textures. Thomas Molitare keeps it quit up-to-date supporting the newest aircraft as they come along for logging and events. This program has served me very well for almost 10 years.

@Meshman, Do you honestly think I sat there punching the submit button three times? The forum server was throwing an actual error and I simply hit the browser refresh icon twice, in an attempt to get back to the forum. I've already submitted my very own request to have the duplicate posts removed. So just move along and don't concern yourself with other people's troubles.

The long anticipated patch update (v1.008) has been released for the Q400. Not only does it include a truck-load of fixes, but also enables turbulence. http://majesticsoftware.com/forums/discussion/1094/majestic-software-q400-update-version-1-008-released V/r,

FlyTampa P3Dv2 status/info support thread here: http://www.flytampa.org/forum/viewtopic.php?f=1&t=6459 In addition, St. Maarten v1.7 is being released. For the latest Dubai, Montreal, and Tampa P3Dv2 installers, send your registration details to Support(AT)FlyTampa.com and they will e-mail you new download-links.

From the PMDG 772 aircraft.cfg file... [WEIGHT_AND_BALANCE] // ** DO NOT EDIT ** reference_datum_position = 0.00, 0, 0.0 // REF : Model 87.8ft to nose empty_weight_CG_position = -6.10, 0, 1.29 // Boeing WBM 1053+92.5in BA empty_weight = 344224.0 // Basic operating (line) max_gross_weight = 768000.0 // Max taxi weight max_takeoff_weight = 766000.0 max_zerofuel_weight = 461000.0 max_landing_weight = 492000.0

Capt. Rob - is it reasonable to assume the NGX SP2 might be somewhere between the 773 and 744? Presumably to include some T7 functionality? Thanks,

Yes, exactly and 195lbs if you plan to fly the T7. Here is a little something I wrote-up a while back for the NGX - read the entire thread first before tweaking. http://forum.avsim.net/topic/417842-topcat-pfpx-737ngx-weights-how-to/

Correct, 175 for the NGX and 195 for the T7. This becomes important on the NGX and TopCat for example, if you wish to distribute the payload in the FMC according to the values shown in the TopCat Payload distribution page, after it's exported from PFPX. Abviously we are still waiting fot PMDG T7 in Topcat at this time. But, Christian does have an acrtion-item on his to-do list to make the weights part of the PFPX aicrfaft profiles vice the current method of a single Prefernce for the entire PFPX program. This will negate the need to change the weight prefence every time we switch aircraft.

I must admit, as much as I love my PMDG gear, the P3D V2 Blogs have certainly peeked my interest for the first time. I will certainly be watching the reviews for further consideration - PMDG or no PMDG...

Excellent find - thanks for the heads-up!

I followed Umberto's guidance he posted here: http://www.fsdreamteam.com/forum/index.php?topic=9092.msg72855#msg72855 Basically copy everything, including the door code/name/position fields from 2L to notepad, then copied all 1L fields into the 2L fields, then from Notepad, copied the old 2L info, back to 1L.

A tweak I found on the FSDT forum is to swap the door settings between L1 and L2 in the GSX aircraft profile. Doing this essentially makes L2 "the main exit". FSDT did not indicate they were going to change/swap it as part of the default profile - not sure why....