Soulflight

OK I got it solved:The Problem seems to be an everytime-there conflict between ASE and FSUIPC wind turbulence. As soon as I suppress wind turbulence in FSUIPC, its gone.But how do FSUIPC and ASE work together? If I tell FSUIPC to suppress effects, does it suppress ASE turbulence loaded into FSX as well? Since I changed that, my rides seem very smooth....

I see and thanks for your answer, the only problem is I have that issue with 2 soundpacks which were designed by CLS for FSX (as they have sound cones). The CLS DC-10 had that issue so I installed the FSX A300-600 sound by TSS on it (same engines), but its still there. Same applies to the PMDG 747-400X where I have installed the TSS FSX RR sound on.Since I have that issue with CLS sounds as well, its nothing neither TSS nor CLS support can help me with.

I am having that issue for quite a while now but now I decided to maybe find a solution for this. On some planes I have, the engine sound is still audible in external view with engines shut down, also its pretty much mis-mixed with engines running in idle, with some sound parts being annoyingly loud. Only way to fix this is to power the engines up and down a bit but this only works until the next view switch.The Problem appears with all CLS Planes, regardless of what soundpack I use, and with the PMDG 747 used with TSS' FSX soundpack.I once contacted CLS support on that one, but they just told me to update my sound card drivers. I already have the most recent ones and I run the realtek on-board sound of my ASUS M4A785-M. Since I also got this Problem with a PMDG plane, however, it does not seem to be a CLS problem.any ideas on this?thx in ADV

Forget my last post, 5 minutes after typing this my AP went to a 60 degree uncommanded turn again because of a 2 knot wind shift

I updated to Sp3 as soon as it was released, but I may have found a solution: the "rate of weather change in FSX" setting in ASE, I reduced it from 50 to 20 % and I am on a test flight right now. Until now the AP keeps track pretty good.

Not really, because ASE DWC mode proviedes the most accurate weather in FSX and is unusuable with the PMDG 747. PMDG blame FSX limitations for all their problems, while this may be correct considering the most realistic approach, I dont know why it does not work when using FSUIPC smoothing.I mean, we all hate FSX wind shifts and its not realistic when wind changes from 270/100 kts to 90/100 kts in one second, but I dont know why the 747 does not work with smoothing then. If you smooth out the wind to 1 knot or degree per sec, what else is there???

Not really, it is the same for me, but with much less wind. The banking gets more severe with time until the plane is in 90 degree angle or similar and crashes due to overstress. I'll try a flight in ASE normal mode....anyone noticed any kind of difference between DWC and normal?I already issued a support ticket and they just told me to deactivate all weather. Well, what I do know is that it is wind caused, so if I deactivate winds, I am sure its gone. But flying without winds is boring. ;)

Ok, just finished another testing flight, ASE DWC mode on, FSUIPC wind smoothing enabled and reg fix verified, it still goes crazy after some time at LNAV. I monitored the wind direction indicator and it only had a variance of about 5 degrees in total with a wind strength of some 15 knots, but it was enough to drive my FMC crazy.This is really starting to get to me, whats the use of being the most realistic aircraft addon designer if you have to completely disable weather to fly their products. Please, PMDG, tell me: is weather disabled when 747's are in the air in the RW???? I know FSX weather has its bugs in terms of wind shifts, but the smoothing out should do it, cant think of another way it is in real life.I spent around 50 $ on a plane which everyone is telling is a must have but it is completely unusuable to me.

Thanks!I just found out that the "setup path" key you mentioned is missing completely, I will enter it and see what happens.

thanks for the suggestion, I forgot to mention that I already did this with no effect. Does anybody know wether the utility works the same way for 32- and 64bit systems, maybe it was pointed to the wrong registry key.

Hi everyone,I know there is an official support forum from PMDG on this site, but since I do not feel very comfortable stating my real name in a public forum, which is required by their rules. ill post that here. (I still own a legitimate copy of the aircraft.)The Problem is already known to many I think: the 747 autopilot goes berserk in LNAV mode, banking until the bank angle warning goes off, and as soon as I deactivate the AP, the aircraft enters a steep climb and does barely respond to control input. Since I use fspassengers, this can get very frustrating.Now I use ASE with DWC mode and already searched this and variable other forums on that issue and in most places it is stated that FSUIPC wind smoothing should fix this. The reason why I start that topic now is because this hast no noticeable effect on the problem for me.So is it really impossible to use ASE DWC mode with the PMDG 747 even with wind smoothing on?Or are there any other ideas?thanks in advance

@ awf you have a pm

Anyone got something new on that problem? Since I thought the black screen is a sign of running out of video memory I swapped my video card with a friend, now I have a Club3d nvidia 550Ti with 3072 MB of VRAM (!). After I got that, I decided to give ENB another try.That should kill all lacks of video memory, I thought, but it does not: when using ENB the screen still goes black when trying to enter menus in FS. It also seems that as many people who do use ENB, only very few have these problems I have.

issue solved: shader optimization was off, sorry ;)

Hi there, I recently swapped my video card with a friend, and gave him my HD5770 for his GTX550Ti with 3072 MB RAM (goodbye OOM issues). However, I need someone who has a bit of experience with configuring the ENB Mod for FSX. I use the famous Nick's ENB settings for bloom and thats what I get: and here are the bloom settings I use, should be pretty subtle normally: [bLOOM]BloomPowerDay=8BloomFadeTime=400 BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=30BloomCurveDay=0BloomPowerNight=0BloomConstantNight=0 BloomCurveNight=0BloomScreenLevelNight=10BloomAdaptationScreenLevel=24BloomAdaptationMultiplier=100BloomAllowOversaturation=1BloomMaxLimit=100 I found out that with the Club3D 550Ti and recent drivers, bloom seems to be constantly running at the max limit value when in interior views. On external camera, all is normal (actually I dont see any bloom effect there)

Well, it has been a while and I am still trying to get ENB runnig correctly with FSX. like I mentioned in another post, für me it causes black screens after using menus even when the effect is disabled before by pressing SHIFT and F12. I wonder if the ENB Mod together with complex aircraft is overloading the graphics card or memory somehow. I switched from a GTS250 to a HD5770 with the same results, so the only suspect left is the video memory.TO the guys who got ENB to work on their systems: what cards do u have?

Seems FSX does not like the "narrow-tent" setting by ATI cards, when I change my AA mode, its gone.

I have accelleration installed and right now I just tried another complete removal of ALL traces of my previous video drivers (i mean all, completely with CCleaner and Driver Sweeper, where everything was completely gone!) but still I got those strange shadows:anyone else has an idea?why do I always have the most persistant problems -.-

Additionally, entering a FSX dialog after a long flight is almost certain to bring back the beloved d3d9.dll CTD to me. Is a modern 1GB card really that limited?I think I will just stick to playing minesweeper until 4GB cards get affordable.....

Thats what I were afraid of :( because getting a 2 GB card is not only expensive, I might have to replace my 500W PSU then, too. Looks like I'm in for some fun. :(

Ok a few facts after some trying:-removing the Overclocking completely does not change anything.-removing ENB Series does not solve it, however, without ENB it takes longer vor the texture errors to appear.-playing around with bufferpool sizes did not cause any differences so far.Is there anyone out there to who this thing makes sense?

I also use ENB Series but it does not change anything if i remove it. the strange thing is that before the black screen appears, the menu I was in is there two times, and you click on "ok" or "cancel" 2 times before it should close, but it does not....

since I got a HD5770 and use it with FSX, I'm having troubles with aircraft self shadowing. Either the area on the fuselage over the wings is showing a bright zone what looks like a reversed shadow effect or the whole plane flickers from "completely shadowed" to "normal" from time to time. When I still had my GTS250 installed I did not have this problem. My drivers were installed last week and therefore are the most recent.Anyone noticed something similar and is this maybe a driver setting?

-.- forget it, I still got black screens......

.....is it possible?The Space between the 2 INS-units is literally begging for the CS Weather Radar to be placed there!