jordanal

But if you read this thread on the PFPX forum, it would appear Navigraph is ready to support PFPX and just waiting for the 'word'. It makes me think that the AS Navdata deal is to simply state, it is 'also' now supported. It wouldn't panic just yet about which NavData product will or will not be supported - I think both in the end. http://www.topcatsim...msg4963#msg4963 FWIW, I've been a loyal FSBuild user and supporter for the better part of a decade and by all indications, PFPX will blow the socks off FSBuild. I think it's the main reason Ernie stopped future developemnt of the FSBuild series - just my humble observation, though...

I thought there was a MS DX9 or OS patch a long-while back that basically limited the footprint GPU VRAM has in the VAS array? I know DX10 does not have any GPU VRAM mapped to the VAS which is why VAS goes down when switching to DX10 mode in FSX. On top of that, I could've sworn some FSX DX9 users tested the specific affects of today's GPU's with large amounts of VRAM and could not make it show any appreciable difference in the amount of VAS consumed as shown ProcExp, including various settings of the VRAM limiter available to the fsx.cfg. In the last years, I've jumped from a GPU with 1, 1.2, 1.5, and 2.0GB of VRAM and the amount of VAS consumed by FSX has not changed significanly. So, my current understaning is that VRAM in DX9 will consume some amount of VAS but it's not a 1:1 ratio and capped at some extent.

I too am hoping PMDG is or will make a concensious effort to manage and/or reduce the VAS footprint required to run the T7 as compared to previous PMDG products. The VAS limit situation is becoming everyone's problem and needs to be well managed by ALL third party developers. If it turns-out to use much more VAS than the NGX, it will be a problem for many of us, I guarantee it.

I don't think so. IIRC, the CH TQ doesn't have the necessary toggle-switches at the bottom of the lever travel, below the idle detent. It's these toggle switches that cause the LUA script to reverse the lever calibration logic.

I've been using the first LUA reverse script mentioned above for the past year or so and it works really, really well on my Saitek TQ. I pull the throttle levers back to idle just before landing and then upon touchdown, pop the levers down onto the built-in lever-switches below the idle-detent to activate the LUA script and deploy the reversers. After confirming 'REV' above the N1 guages, just start pushing the levers forward and watch the N1 pickup speed - no need to go full reverse on the levers anymore as long as my speedbrakes deploy as scheduled. You get much more finite control to smoothly slow down the aircraft with less reverse thrust. After reaching about 80 or 70kts IAS, I pop the throttle levers back-down to the idle detent - with just a tiny bit of seperation so the LUA script is sure to see both idle detent events. It took me a few moments to figure out it was this idle detent event (from reverse) that stows reversers and the "REV" indicators dissapear above the N1 guages. Although I haven't tried it as it's been a long time since I've flown the Queen or the MD-11, the latest LUA script version above was fixed to work with up to 4 levers simultaneously. I give this LUA script my full/best endorsement possible. If you have the full FSUIPC with calibrations on the Saitek TQ's, do yourself a favor and give this a chance. It's better than having a built-in reverser zone below the idle detent like some of the older TQ's. Kudos to the LUA script author - job well done!

Thanks. Yea, I knew the FO/PNF handles it, and it works fine as far as dusk/dawn goes. The thought came to mind however using the new FSDreamTeam Vancouver Intl yesterday with very low-vis, crappy weather and I was trying to order my FO to turn on the dang Logo light - but he just wouldn't listen - good help is so hard to find these days, LOL...

Bryan, I'm a bit curious to know; did a voice command phrase such as "Select Logo Light <on/off>" not get included becuase it was not available in the PMDG SDK? Or, was it a FS2Crew issue? If a variation of the command already exists, I've never been able to figure it out. Thanks for your insight.

Thanks Jakub, not a bad idea actually. Although I'm not sure about refunding any remaining funds - LOL... But that kind of brings up a second thought - what if the gift VISA/AE/MC card doesn't have enough funds on it for the T7, for example. If necessary, does the PMDG on-line store allow a purchases to be spread across multiple cards?

My lovely wife keeps nagging me (why does Walter from Jeff Dunham's act come to mind when I say it like that, LOL) about what I want for Christmas. Of course foremost on my wish list is something new from PMDG (777, DC-6, etc...). I don't seee it on the PMDG store-front but I thought I'd ask anyway - does PMDG offer any kind of gift-certificates that can be purchased by our better-halves and then used for current or upcoming PMDG products?

I'm not sure if it's the exact same situation, but I was getting these CTD errors after properly closing FSX for the longest time. I tried all kinds of different tips and tricks to resolve the issue. I FINALLY solved it with one very simple solution about two months ago and have not had a repeat occurrance since. I appearently had a slightly different variant of the uiautomationcore.dll file copied to the root of my FSX folder to fix the original menu crashing issue also common to FSX. Apperently, there are several different variants of the Vista file and only one of them is the proper dll. Once I replaced it with another version found from a link on this forum (sorry, I can't find it now), my problem was solved. No more CTD's when propely closing FSX. My appologies if this is not the case with regard to this thread - wanted to pass it along just in case.

Ha, this is quite ironic. I just reported this exact issue in the Navigraph FMC Bug Report forum yesterday. I have seen this exact SEAVU lockup, and sometimes CTD, for at least the past several cycles. All other KLAX STARs work without issue. Please, if you see this same problem add your observation to the report in the Navigraph forum so it might get fixed. http://forum.navigra...?g=posts&t=3622

It's a corrupt or mipped cirrus_overcast03.bmp texture. Opus offers a few alternatives to correct the problem in their official forums, I think.

I own all the latest versions of the ImaginSim sceneries for FSX and I can honestly say, the latest updates to KSJC and KCLT are now two of the worst performing airports I own. They now tank at around 8 FPS. I normally enjoy ImagineSim (for the most part) but I cannot understand why multiple copies of old AFCADs would be includ in the update-zip files without any installaton instructions. I too will be dumping the SP1 patches and turning back to the original 2008 installations.

Excellent FT stuff as usual. Thought it worthy to dedicate my inaugural OMDB fligth with a departure from another FT airport (LGAV - Athens). Photo album can be seen here... http://s1178.beta.photobucket.com/user/jordanal/media/LGAV%20to%20OMDG%20Rebooted/2012-11-9_16-57-16-928.jpg.html?sort=2&o=0#/user/jordanal/media/LGAV%20to%20OMDG%20Rebooted/2012-11-9_16-57-16-928.jpg.html?sort=2&o=0&_suid=1352518320741033786987142936764

AES 2.25 was just posted and it includes the FSX version of Dubai-rebooted.

Yea, it's pretty sweet. I like how you open up the top of the box and the first thing you notice is two calibration certificates! I work in the I.T./server industry and I don't think I've ever seen that before. Two other points. 1) I had to send the EVGA GTX680 SC Sig2 GPU back as it was a bad card (pixiliating and crashing after using it for a short while. Decided to just keep using my GTX570 for now. 2) I was surprised how 'warm' the U3011 gets from both the front and top of the screen. Not an issue really, but noticeable.

Yea, it's pretty damn cool! The first thing you notice going from a 24" to a 30" is all the desktop icons which used to take-up half the screen now fit in two vertical rows. The picture is very, very sharp - I'm using the DipslayPort jack with a confirmed resolution of 2560x1600/60Hz. Now using the GTX680 after cleaning and reinstalling the 306.97 WHQL driver and the latest NV Inspector app. I imported the same FSX Inspector profile I had been using - 8xS/2GSS (and all of Word Not Allowed's other settings). I fired up FSX for the first time (after adjusting the fsx.cfg) with the PMDG 738NGX sitting in front of Terminal A at FlyTampa's KBOS with Opus weather being injected and pretty dusk sunset scene. Mind you, I run a full onslaught of hand-config/installed commercial AI at 100%, (using all of AIG's FP's), and 10% vehicle traffic. All other sliders are pretty much maxed, except AG which I keep at Dense and Water at 2x-Low. One thing I would like to point out is how different the NGX VC looked going from a 16x9 to a 16x10 panel. For example, I had always dropped the yoke height (clicking on top of the yoke) so I could see the PFD and the ND as soon as I switched into the VC for the first time at the beginning of each flight. Not any more - the aspect display change causes the viewpoint to be somewhat higher and maybe a bit closer, so the yoke looks to be in a much more realistic position by deafult and the PFD and ND are closer and larger. I was genually surprised and pleased how much of difference the change in Aspect ratio changed/corrected this view! With my original Inspector settings driving the 24" 1920x1280 display, I would usually see around 22 to 25 FPS (shift-z) at this scene at KBOS as I quickly panned around the NGX in locked-spot view. When I first loaded up this new montor and GPU with the same Inspetor settings, I found my FPS's had tanked to around 8 or 9 FPS. This really didn't surprise me though as I thought it might happen with the higher 2560x1600 resolution. I had recalled reading on here somewhere during my procurement research, that someone else had to drop the AA level as well due to the change in resolution. I changed the Inspector AA from 8xS/2GSS to 4xMS/2GSS, keeping all other Inspector settings the same. Now my FPS have returned to the previous 22 to 25 level experienced before the upgrade. Loading up the same scene again at KBOS, I really could not tell a difference at the level of AA change, especially in the VC or exterior locked spot view. It looked the same to me. So, no change in FPS with the new hardware (as can be fully expected) while maintaining my current level of scene quality - but man, this display is huge, crisp, clear, and the colors look remarkably sharper/different as well. Especially while looking at many of the AI liveries I've collected over the years. That was all I had time to do last night before dinner and presenting/explaining my upgrade to the wife like a car salesman or something, LOL. Of course she pretended to be genually interested, just as any good spouse of a FS-nut should be, right? LOL... But honestly, even she remarked at not only the size of the montior, but difference in display characteristics. No, the 'exact' price still hasn't come up, whew.... LOL...

Holy crap... OK, I guess it was worth it. :good:

Yea, GPU upgrades over the recent years have not been really fruitfull as far FPS goes. Two reasons why I chose to upgrade now, with respect to the U3011 monitor. 1) Any of the GTX6xx series cards are designed to support the higher native resolution 2560x1600. But I chose the 680 because, 2) I wanted all the horse-power I could get for the best AA/AF at this high resolution. According to the HDMI 1.4 resolution spec, it now defines the new "4K Display" (4096x2160) which is the new high-end stardard for bleeding-edge video and home entertainment systems (something else for us to blow our money on). You can see the comparision and read about it here - http://www.hdmi.org/...dmi_1_4/4K.aspx Clearly, the U3011 montior only suppprts HDMI 1.3 (1920x1280 - a.k.a 1080p). Only the DVI-D and Dipslay-Port jacks support 2560x1600. But, appearently the GTX6-series cards do in fact support the new HDMI 1.4 "4K Display" standard on the HDMI and Display-Port outputs only, but not on the DVI output - I wonder what the max Digital Resolution of the DVI ouptut is? Surely not the lower VGA limit of only 2048x1536. You can read it on the Nvida specs page "Maximum Digitial Resolution" and specifically Note 4 at the bottom of the page - http://www.geforce.c.../specifications I guess I'll use the DisplayPort jacks and cable between the two just to be sure I'm getting 2560x1600 out of both devices.

Ahha (to answer my own question) - according to the online documentation (setting the maximum resolution) for the monitor, it would appear only the DVI-D and DisplayPort connetors carry the full 2560x1600 resolution. The HDMI connector only carries 1920x1200. http://support.dell....imal Resolution

BTW, althought the monitor has no audio, is the HDMI connection preferred over DVI in any way? I know HDMI is preferred for TV's, but I wasn't sure about computers these days. Thanks...

Oh what the hell - if I don't spend it, my wife will. A monitor this nice just deserves a matching GPU - and they're on sale too! My wife would be proud, LOL... :rolleyes: EVGA GeForce GTX 680 SC Signature2/Dual Fan/2048MB GDDR5 (02G-P4-2687-KR)

He he he, well, when you decide to "man-up" (LOL), let me know how that works out for 'ya (telling your wife the cost) and then I'll consider it! LOL.. :Chicken:

Thanks guys, I am looking forward to it. I just told the wife about it - but, I didn't mention how much it costs though (yet)... :Whistle:

I have been using a Samsung 24" TN monitor for my FS rig for years. I got an unexpected bonus from work recently and decided to blow it on something I wanted for a change, instead of benefiting the entire family (man, do I feel guilty now, LOL...) or putting away in savings as has been customary during this recent economy. Ssshhh - I haven't told my wife yet.... Anyway, after reading around the forums and a few PC magazine reviews, I chose to indulge myself with the Dell U3011 30" IPS panel. Coupled with my GTX570 and my TrackIR5, I'm hoping it will be a nice upgrade for most of my big-iron flying in the VC and all the add-on goodies fully displayed at 2560x1600. Can't wait - it arrives Tuesday.