Big_Duke

This is the error message received in the Device Manager properties listing for my video card: "Windows has stopped this device because it has reported problems. (Code 43)" Pertinent info: WIN7-64 bit, SP1, Home Professional; Zotac 4GB Nvidia GeForce GTX 980 PCIe 3.0 card; ASRock Z97 OC Formula Mobo. The predominant solution I found on the internet is to uninstall the device using the WIN Device Manager and then use the rescan function to reinstall the video card. After rescanning, the Device Manager does recognize that the GTX 980 is present and changes the message to "This device cannot work properly until you restart your computer. (Code 14). This worked the first few times over several weeks, but now no longer does and the Device Manager reverts to reporting the Code 43 message as if I'm trapped in a maddening do-loop. I have also tried using System Restore with multiple, different restore points; several different versions of the video card driver; re-seating the card; and also moving the card to a different PCI slot. Also tried the Device Diagnostic tool from the Microsoft Support web page - still no joy. I'm beginning to think my card gave up the ghost, but before I spring for a new card, I wanted to check if anyone has heard of any other solutions to the Code 43 problem. The card is powered as the fans do work when the PC is powered on, but I can't use any other video card utilities to check the card as WIN keeps stopping the device from loading. I'd like to stop short of drastic solutions like reinstalling WIN7 if possible as I dread having to reinstall P3D and all my add ons after the Registry is zapped and replaced with a new one. I'd almost rather surrender and move to WIN10! Any ideas would be most appreciated. Thanks in advance!

If you look in your ...Scenery/World/Scenery directory, you'll see a bunch of traffic files beginning with <traffic_Ships......bgl>. Scroll around until you find the ones named <traffic_Ships_US_Lakes....bgl> and identify by name the ones you want to keep. The rest can be renamed to .bgl.passive or moved to another location outside the directory. Voila! You've got only the ship traffic you want.

If you go to the Boeing.com web site and search on "cost index", you'll find a very good explanatory article that defines cost index and gives examples of its use, especially for fuel conservation strategies.

Jon: Thanks for the informative posting; yep, I completely missed that thead. Good luck continuing the development and hope it comes to fruition soon!

Thanks, Ian and David, for your comments. Ian - Yes Foreflight could work, but becomes a rather expensive proposition at $175/yr just for US coverage. David - Any idea which product would incorporate SVS? I didn't see any mention in the B350i info which I assume is their upcoming flagship product.

I was just reading over at Aviation Week that Boeing and Airbus are beginning to delve into the synthetic vision arena with the somewhat tentative "goal" of incorporating SVS into the cockpit starting with new-build aircraft around 2020. That should give the devs some time to mull this one over and see how this might be included in whatever sim we might be using five years from now. I know it's down the road a piece, but it never hurts to start scratching out some thoughts/possible technical approaches to the topic.

I was just reading over at Aviation Week that Boeing and Airbus are beginning to delve into the synthetic vision arena with the somewhat tentative "goal" of incorporating SVS into the cockpit starting with new-build aircraft around 2020. That should give the devs some time to mull this one over and see how this might be included in whatever sim we might be using five years from now. I know it's down the road a piece, but it never hurts to start scratching out some thoughts/possible technical approaches to the topic.

Ric - glad it worked for you. As I replied over at Aerosoft, you might want to try editing your AI traffic files to divert some of the EDDT flights to EDDB. Right now, most AI programs have the majority of flights going to EDDT with only a small number going to EDDB.

Ric: See my reply over at the Aerosoft Forum. If you're using UTX Europe ver 2.0, you need to disable the repositioning of EDDB done by UTX.

This can be very perplexing. I, too, had some issues and reinstalled ASN. I'm running the SP1c 777, no SE, no SP1d, along with GEX/UTX, MT 5.4c, and no photo scenery. I flew a leg from KIAD (FlightBeam) to KLAX (FSDT) and the VAS held rock-solid around 2GB free the whole way. Then I flew a night leg from ORBI (stock) to EGSS (UK2K) and experienced a slow bleed of around 200MB VAS per flight hour, going from 2GB free VAS to 1GB free upon landing. I hadn't changed any settings. And then I saw another minor update had been made to the OC and installed it. After that, and again without changing any other settings, I flew a 9-hour flight from EGSS (UK2K) to KMEM (stock) and remarkably the free VAS remained constant at around 2GB the whole way! So, the only thing I had changed was installing the latest OC update. Very strange indeed.

I repeated my flight mentioned above (PANC-KORD w/777F) and this time had no issues with VAS, other than the normal VAS-sucking add-on airports - KORD by FSDT is much better than the Aerosoft/SimWings PANC. It doesn't release VAS back as well as other developers' airports. Now, before starting the flight I found my issue with ASN - somehow my cloud layers had jumped to 6 from my normal 4. I can't blame anything specific and might even have had a senior moment and changed it myself. Anyhow, the flight ran smooth, maintaining a stable 1.6GB free VAS all the way, then bumping down to a steady 1.3GB free VAS in the dense Chicago area. So, in my case, I can't explicitly blame ASN for my one-time VAS hiccup.

Will either of you two take this over to the HiFi ASN forum? I, too, noticed a strange VAS bleed issue the other day flying a relatively short leg from PANC to KORD. Where I'd normally maintain close to 2GB free VAS all the way with the 777F, this time I "bled" down to only about 600MB free VAS upon reaching the freight terminal at KORD (FSDT). Like Kyle, I wouldn't have normally associated this with ASN as I've had good luck with it. I haven't changed anything else in my system, so now I guess I'll have to look closer at ASN.

I would caution folks to temper their expectations a bit. If you read the article closely, it states: "To start, the things people will be able to do with HoloLens will likely be very basic. So don't expect to be able to pick up a virtual gun and play holographic Halo or see a holographic representation of your redesigned kitchen right off the bat." It isn't creating a virtual environment, but rather imposing simulated objects in your real environment. So you might be able to look at a model of a 787 in your living room, but unless you have a verrry looong living room, you won't be taking off to fly anywhere. Maybe later down stream, but with M$, who knows?

I hope there's some intrepid gamers out there willing to test drive WIN10 for us. After the WIN8/8.1 fiasco, there's no telling what WIN10 will do to FSX, Steam, P3D, and all the associated add-ons which tap into WIN services. With release next week, perhaps it's time for AVSIM to spin up the WIN10 Forum. And also check how AVSIM site functionality holds up under Spartan, the new web browser replacing IE. Hope springs eternal that most everything will go swimmingly!

I also posted over in the PMDG Forum that I,too, experienced the NGX VC shadows immediately after upgrading to Fixer v2.5 with the same effects noted above. But then I was unable to replicate the effect the next day on a different flight with the NGX. So I just assumed it was some artifact of the upgrade process. Anyway, it would be nice to have someone who consistently achieves the NGX VC shadows to post their Fixer settings.

This is a strange one. I, too, saw the same effect immediately after upgrading to DX10 Fixer v2.5 and fiddling with the legacy shadow settings as well as the settings to block the new sun glare effect from the later Nvidia drivers. But then I was unable to replicate the effect the next day after shutting down my PC for the night. So I wrote it off as a strange artifact of installation and the oft-quirky FSX. Perhaps someone will be able to discover the definitive Fixer settings to keep the VC shadows.

Well, I was surprised yesterday when flying the NGX and found I had VC cockpit shadows! I don't know if they resulted from the v2.5 update or my adding ForceVCShadowMap=1 to my fsx.cfg file. The shadows looked kind of generic if that's the right descriptor, like it was a generic shadow map rather than NGX-specific and they were bold and bright, and sometimes downright distracting. I'm guessing I need to fiddle with the shadow settings to fine tune it. Anyway, just my experience.

Are you using the EZdok camera? I had the same problem and I also use EZdok and I had to remember to re-run the EZCA Configurator after installing the 777 updates. Then I had the full external views back.

Some folks don't realize that the computer does remember everything you input, both from the keyboard and mouse. And it will execute them all when it's time! So, as Tom says, patience, Grasshopper.

Also keep in mind TOPCAT is not a fuel calculator; it only uses the weights (including fuel) for calculating takeoff and landing performance. Also, the PFPX OFP shown above indicates the trip average wind component as 0 Kts. Are you using the same weather source for planning as you use in FSX for flight? Unless you do, there will undoubtedly be a difference in fuel use. I have found the PFPX planning figures to be very close to FSX fuel consumption for both the 772 and 773, and have never come up short. Most times I'm actually a couple of thousand pounds over on arrival which is less than a 2% error.

Yes, either one will start both engines. "Ign L receives power from the respective ac transfer bus, while Ign R receives power from the standby ac bus and is also used for inflight starts on standby (battery) power so this system is required for dispatch." -from Bill Bulfer's 737NG Cockpit Companion. BTW highly recommended reading. Also, quite a few airlines use an alternating policy where on, say, even numbered days, you start with Ign L and on odd numbered days, you start with Ign R. This evens out wear and tear on the ignitors. It is unusual that you would use the "Both" position.

If there was a memory leak, it would leak for everyone. I'm on my third 300ER/SP1 flight now and free VAS is holding steady at 2.2GB available two hours in - totally stable and no fluctuation. Yes, the 777 and SP1 are VAS-heavy, but I've flown 80 flights, most in the 8-12 hour range with NO OOMs. Yes, I've flown into UK2K's EGLL as well as all FSDT's and Fly Tampa's sceneries without problem. As repeated numerous times, you can't have it all with FSX; choices and compromises need to be made. You'll never get all the scenery eye-candy you'd like, but that's understandable. The biggest offenders seem almost always to be Autogen, LOD, and AI traffic. I fly with Autogen set to sparse (1) which still gives plenty of it, and LOD set to 4.0 which satisfies my eyes (I'm concentrating on the runway during approach, not gawking at the far horizon), and I run MTX 5.4c at 50% traffic. I can still land at most complex airports with about 1.2GB free VAS.

Thanks, Kyle. I'll return to my dream and enjoy the bang-up job PMDG did implementing it on the NGX.

Seems AVSIM has temporarily disabled the Search function, so someone might be able to refresh my memory. I thought I saw some time ago that the 300ER would be equipped with a HGS. Was I dreaming? I'm not seeing anything in the FMC A/C Equipment sections.

I think a lot will depend on how the scenery developer builds the textures. My quick and dirty with the default Cessna, no AI, WX and LOD 4.5 and Autogen Normal, taking off from FSDT KJFK, Rwy 31L, head west to Manhattan w/Drzewiecki NYC loaded and fly north down the center of the island. I found using 4096 TML vice 2048 caused JFK to consume 159MB MORE VAS, but Drzewiecki NYC consumed 6.7MB LESS. Go figure.