TurbofanDude

it seemed to be FsCopilot/FsInn not working in my situation

Hi there. This is pretty much it. Recently, after I changed a few windows features, I went to fly and saw that my Ariane 737 wasn't loading its activation. Figuring it was just on the fritz again, I went to fly the Wilco 737. Same thing, gauges did not initialize. Both of them require external .dlls to function that don't seem to be loading. I tried removing other addons, fixing the dll.xml file, repairing Flight Sim. All that. I also changed the settings back to the way they were, nothing. (the features ones). When I restored FSX, they worked for a while, then after restarting the computer, they had the same issue again. Now, I cannot for the life of me figure it out, but for now, no flying.Windows 7 Ultimate 64bitIntel i7 Quadcore, 3.07GhZNVidia GTX470 4GB8GB DDR3 RAMFSX AccelerationCollin

14, simming since about 12

add the line HIGHMEMFIX=1 under your [GRAPHICS] section in the fsx.cfg. Fixed it for me.

At this point, I'd do FSX and the new system. Your specs are too low to get the WOW FSX! feeling, but with an upgrade and a few addons, it's 100X better. I remember using an addon ground texture addon in FS9 and it still wasn't as good as FSX default. Run at around 20FPS on medium high graphics and it's visually much more attractive.My system specs:Intel i7 Quadcore stock 3.07 GhZNVidia GTX470 4GB8GB RamWindows 7 64 bit UltimateCollinGood luck to yOU!

Fellow simmers, I've recently purchased a new custom computer, and it seems that my sound isn't quite right yet. The exact problem is as follows: Flight Simulator plays most sounds correctly, but on certain sounds (both addon and default), when it's supposed to loop, it pops loudly, then loops. I get around it by using another sound set sometimes, but when the "popping" is coming from a sound embedded in the planes gauges, it's hard to get around. I've adjusted the sound quality, my settings are more than reasonable for my cpu, tried limiting the framerate, tried updating sound card drivers, used different drivers, changed surround settings on the cpu, tried bufferpools, and searched 20+ forums for help. I've rebuilt the shaders, fsc.cfg folder, logbook.bin, and I've defragged the computer and cleaned the computer of registry errors or corrupt anything. I miss my new soundset! As well, I've tried deleting the sound fader entry in the fsx.cfg and adjusting the actual sound file to many different formats. Even my computer tech support guy can't figure it out. PLEASE HELP ME! Recentlty I tried different varations of the "[bufferpools]\RejectThreshold=98304" fsx.cfg mod and I tried using a higher zoom. Nothing. One more bit of info, it only happens with certain sounds, and that's it. It's not random. Sounds that don't pop now almost certainly won't next time I fly (knock on wood, Thanks in advance, Collin Biedenkapp System Specs: Windows 7 64bit Vidia GTX 470 4GB Logitech X540 Surround Sound Speakers 8GB DDR3 Ram FSX Acceleration Intel i7 Quadcore stock at 3.07 Ghz Asus p6x58d-e Motherboard

Please read my post to the bottom. Thanks, but ******* came up with most of this, I just summarized his and added a bit of my own knowledge and time to it.Collin (with two L's, :) It may in fact be due to your graphics card, your drivers, your FSX version, your addons or anything. I seem to have more issues with power hungry addons. Your computer may just be more compatible with things. At least now you know that if it happens, you can fix it. As well, I summarized a lot of *******'s ideas about this (like the HIGHMEMFIX=1) and that and I added a bit of my own knowledge and time. I will be testing with the REX weather engine and much higher settings to see if it stays stable or now. Either way, Good luck!Collin

I know, I was just summarizing what fixed it for me. I should have been ,ore specific. A few other things seem to cause trouble on my system and I thought I'd try to add to the existing knowledge base and summarize all I've read and learned. I only take credit for what I've done, which is not using the REX engine for now (until I can test), reducing water settings (from a friend of mine)I wasn't trying to steal *******'s ideas, instead add to them.As well, like before, the newest drivers did indeed have problems on my system in a similar way, bu more with alt-tabbing instead.CollinATTENTION ALL! A lot of this is from the other post by Ryan. I was just backing his ideas up and adding a little information for the people that his idea didn't quite fix if for. A good chunk of this is just me copying from the other post to back it up and summarize it.I will be testing with bringing my settings back up and using the REX weather, and if my test prove successful, I'll report back. If not, I'll identify the issues.If anybody else has any other information or troubles they would like to add or need help with, please post it on the stickied post or here.

Hello all,After hours and hours of testing, like 20 settings, and numerous phone calls and emails to nvidia and microsoft, here it is:The problem: (from the other post)"Issue #4: The “skeleton plane” issue - loss of textures and geometry on the external model and VC. This is the issue that’s going to have the most discussion…I want to put forth a new theory we’ve developed on this over the past week or so:I was talking to one of our new programmers about this issue and we stumbled upon something quite interesting. I was mentioning to him how some users seem to have success in resolving the issue via lowering the Windows sound quality setting. This sparked the realization that something all the aircraft we’ve heard of this issue happening with (which includes the Level-D 767, the Captain Sim aircraft, the Flight 1 Super 80, and now most recently the Flight Sim Labs Concorde X) have in common is custom sounds that are generated through an external processor dll and not by the FSX audio engine. We believe that most addons have used a very similar method code-wise for playing these custom sounds back, one which predates the modern Windows OSes and Direct X versions by nearly 10 years. I remembered back to issues we’ve seen in the past with sound crackling while using the 747 and MD-11. Sound crackling is usually the result of something called direct procedure call (DPC) latency. DPC is the method Windows uses to stream real time events like audio and graphics processing across the system bus. High DPC latency backlogs these events and can produce audio and visual artifacts. The proverbial lightbulb went off and we asked ourselves “What if the sound is somehow overloading the bus and this affects the graphics subsystem too?”Acting on this hunch, I’ve had several people who see the issue try disabling the PMDGSounds.dll gauge and then flying to see if the problem occurs. Doing this results in none of the custom panel sounds playing back, just the engines (which sound via the FSX audio engine) but it provides something of a way to test for the effect of the gauge. We’ve had some very promising results from the couple of people who’ve tried it. Both users also have the Flightsim Labs Concorde X and I had them disable that aircraft’s sound gauge as well - it is likely identical to the PMDG gauge since the same person, Lefteris Kalamaras, wrote both of them. Both people reported that they were able to complete numerous long flights without any major issues and that in the case of the Concorde, both were able to see the external model for the first time without it almost instantly disappearing/corrupting upon loading the sim. My theory (I will readily admit I don’t know for sure on this) is that the Concorde may be loading more custom sounds than the 747 or MD-11 do, and this explains why the issue is more prevalent there than it is with the PMDG products.Now, that said, we are not convinced this is all of the story – one of the testers told me he did see a piece of the 747-400 VC (the floor) disappear even with the sound dll disabled – it did not however cause a CTD or any further corruption in the visual model. What this tells us is that we are undoubtedly at least on the right track with this idea that the issue is caused at the root by the system bus getting overloaded with real time data streams. Only certain systems seem to be susceptible to it as well, including systems with much higher specs than some that don’t see the issue, which further complicates pinning anything down. I’ve tried in vain to make it happen on my own system and I can’t, even when running just about every crazy maxed out addon I can throw at it.We’re providing this information in the hopes that it sparks ideas among the whole community (other developers and knowledgeable simmers alike) on this issue – it’s clear that this affects everyone and that this is going to be a problem for almost anyone making complex aircraft for FSX. If the clues we are publishing here can lead to a solution, we will share this information with all developers in order that the entire community benefits from this discovery. Clearly this problem affects more developers than just PMDG, so a solution will benefit everyone."The Fix:Turn your settings down, make sure to reduce the water quality to at least low 2X. Disable/discontinue use of the REX 2.0 weather engine, reduce your computer's sound quality to 3 settings from the bottom.Use *******'s fix:"add the following lines to their corresponding sections your FSX.cfg (located in the C:\Users\YOUR USER NAME\AppData\Roaming\Microsoft\FSX folder)[GRAPHICS]SHADER_CACHE_VERSION=1 // it 're-builds' the Shader Cache (good to do on every fsx.cfg change) just enter a random number (versioning)HIGHMEMFIX=1STALE_BUFFER_THRESHOLD=2147483647 // (2048 megabytes)[Display]TEXTURE_BANDWIDTH_MULT=400 // Default is 40 (made 10x faster so we dont end up filling the stale buffer which is also used by the sound card)[sOUND]SOUND=1SOUND_QUALITY=2SOUND_LOD=0and as well follow this adviceForce VSYNC to OFF on your Video CardLet The Application control Antialiasing and Anisotropic Filtering (set them to application controlled in the nVidia control panel) Make sure you use MultiSampling AA, and not SuperSampling or Combined.if you use the evil nHancer, set Aniso there to OFF (it will still work), seems to be a bug with nHancer.If you use dualview or Clone mode, DISABLE it, make sure you ONLY use one monitor when doing the tests.Set pre-render frames to 0Finally, go back with your Nvidia drivers to 197.71 or the oldest your card will support.. I've yet to see a performance change in new drivers, but old ones restore compatibility. MY system:Windows 7 Ultimate 64bitIntel i7 Quadcore overclocked to 3.07 GhZ8GB DDR3 RAMNvidia GTX 470 4GB driver version 197.71Collin BiedenkappALL USERS WHO TRY THIS PLEASE REPORT BACK!

I experience this issue with another addon or default and it seems partially video card driver related with me. I tried *******'s trick, and it seems successful so far. I don't quite know yet, but I'll report back ina few days with more info.UPDATE:As well, it seems that reducing your settings helps out too, as it's reducing system load. I ran FSX for 3.5 hours last night, and I was alt-tabbing and flying on and off for that whole time with not so much as a twinge visually. Thanks *******!My system specs:Windows 7 Ultimate 64bitIntel i7 Quadcore overclocked to 3.07 GhZNVidia GTX 470 with 197.71 drivers installedFSX Acceleration8BG DDR3 Ram

BTW: The gauges: Here is all I meant by that: The picture I took from the real plane and an earlier picture of your plane show black backgrounds and the new one shows blue. I didn't know the brightness had the great of an effect on it! (I'M NOT SAYING YOU'RE WRONG! I am going to buy the NGX no matter what!

Alright, in this order,1:I did not know that about the gauges, (you learn something new everyday. The planes I've been on they all seemed black. Cool! I couldn't imagine how you'd have it wrong. I figured it was an model difference or carrier option or something)2:I get it, the wide angle, and it's since been adjusted3:Awesome, I prefer the dials!4:That is insanely realistic. I can't believe how close you guys got this to real!1:OK. That's probably a huge framerate killer,2:Yea, that makes sense -> no cabin3:SWEET! I love opening them sometimes!4:Awesome. The other -CENSORED- 737 I use doesn't have it. :( I can'tYes I know I'm ridiculously picky, but I was just wondering. I am absolutely anal about having it as close to perfect as I can!

OK, while looking at the insane preview pictures of the NGX, I noticed a few things.Concerns1:The gauge backgrounds are blue. Is there a way to change them back to black like many -700s are? And of course, blue gauges means the colors are going to be a tad different. Like the engine started on light being yellow not amber. (I've seen a preview somewhere else that had black gauges, which leads me to believe you can)2:The object (?) above the window lock/unlock handle seems quite large compared to the -700? Is that different for the -800, and -900 models?3:The fuel gauge isn't the round dial-like gauge I'm used to. Is there a way to turn it back the round one?4:Some gauges have random switches (like a wierd one thrown in middle of something else?QUESTIONS:1:Will there be a virtual cabin?2:will the flightdeck door open? (animated)3:Will the windows open?4:Will your FMC have updatable airacs?Thanks in Advance,Collin Biedenkapp

Actually, I thought the same way until about 5 different people told me it really is as good as people say it is! It's worth a try! (I just bought it for my 2500$ computer, that ought to tell you what I think of it)

I only see this issue when using addon textures (photo-real ground scenery or REX or anything) and only on one older FS9 plane that was made into an FSX plane. That is the {BLANK} 737 (I know Im not supposed to use other companies name here) The cockpit dissappears, and slowly the screen becomes just black on the bottom and white on the top.

I'll fix those (they're just texures)

I would like to see it work with the multipanel as well

I truly can barely tell the difference. That's as real as it gets right there!

That looks amazing

Yeah, and at the rate PMDG is going, that's about on par! FSPAX gives you the ability to do belly landings! Thats why it worked!Is there still going to be something of a virtual cabin? (I've been looking forward to flying the WHOLE airplane, not the flight attendents bay like the Ariane 737!)Also, what about the Flight Deck Door? Will it function?Collin Biedenkapp,Soon to be proud supporter! (Awaiting NGX)

I have the seat belt sign and the flight attendent call sounds. Email me at TurbofanDude@gmail.com