Soulflight

OK, I can carefully say that maybe my OC was too high, I lowered it to 3,8 Ghz and after an 8 hour flight with the CS767-200 with landing in LA as well as a few test runs in densely populated areas, the problem never occured so far. I guess it was the "load line calibration" setting....for ppl who know what im talking about: my M4A785-M Board has the problem that on high overclocks which are harmless in terms of CPU temp, the capaciators next to the CPU start overheating which causes a brief CPU performance drop visible in CoreTemp. Playing around with the LoadLine-Setting helps to get the voltage it needs to the CPU, but also causes these drops more often. The LoadLineCalibration manages the transitions between idle mode and load to prevent voltage spikes. TO get the 3,9 Ghz stable, I had to lower the LLC setting from standard 51 % to 32%, which was stable anywhere except FSX obiously.Now what happens when you close an FSX dialog in densely populated areas? Right: the CPU usage shoots from idle to orbit. Thats where the blackscreens and crashes happen.Since I stabilized my OC at 3,8 Ghz with therefore reduced voltage and LLC on standard setting, FSX seems to run stable even after long range flights. (I frequently take off at night, switch FMC on and go to sleep to land at morning. ;) )The performance drop of using 100 Mhz less is not really noticeable, and since it is summer, maybe its more healthy that way too. ;) For the same reason you enter the ambient temp on the FMC for your takeoff thrust.

Alright im currently test running with clock reduced to 3,8 Ghz.I had BufferPool=0 before, which really gave me good FPS but now im running the RejectThreshold Value for testing, it does not change anything I noticed.It happens with all planes.

Hmm, I have to say I do not really have performance problems, clouds are set to 70 miles distance with 3 layers maximum in Active Sky, World of AI traffic is set to 70 %. Autogen is set to 1500 Trees and 3000 Buildings maximum and my minimum FPS are around 10, but 15-30 most of the time. I have some Addons like UTX and GEX, they are all updated to the most recent version. my overclock is stable and I can easily run prime95 for 12 hours.So do I really have to reduce graphics details after spending so much time and effort to get a decent machine running? :(

The older of you may remember my very persistant CTD Problem, which is solved now.The other one still remains: I havent flown in densely populated areas for a while, and now I noticed its still there. This happens when I exit an FS menu (looking up something on the chart for example) and want to get back to the sim, the screen goes black! The sim runs, I can hear sounds and change my mouse cursor to pan-view-control, but I dont see a damn thing anymore. ALT+ENTER just makes the window around the black screen disappear but nothing changes. Only way out: Alt+Tab and exiting FS; which is really annoying when it happens after a long flight while trying to look up an ILS freq in map view with FS Passengers.Things I have done so far, mostly because of trying to solve the earlier CTD problem:-HIGHMEMFIX and uiautomationcore fix applied-changed various poolsize and bufferpool entries-changed the video card from a GTS250 1 GB to a HD5770 1GB I had available, I uninstalled the nvidia drivers with driver sweeper before, obviously its not video card or driver related.-refreshed shaders by changing version in FSX.CFGas well as a few others i dont remember now.system specs: Phenom II X4 965 @ 3,9 Ghz, 8 GB RAM, Radeon HD5770 1GB, WIn7 64bit, FSX Acceleration.any ideas? except for not entering menus in flight anymore.....

The RejectThreshold thing helped for most of the time, thanks.Anyways one more question: since this video mode is so great, does anyone know how to reduce the blurriness in ENB Mod? Because the screen in FSX looks good, but very blurry with this antialiasing setting and ENB on. As far as I know the reduced sharpness was done on purpose for the games ENB was originally designed for, but although the color correction and bloom looks great, the blurry image give it a kind of comic style look when used with the AA setting mentioned above. Any ideas? thx ;)

Hi,I recently tried to improve the AA Quality in my FSX, because the recommended 8xSQ setting made cockpit screens and small text quite unreadable when used with the ENB Series Mod.Somewhere I found a tip to use the AA Mode "AA_MODE_METHOD_SUPERVCAA_64x_4v12" in nhancer instead. And I must say I am really impressed by the AA Quality while all gauges stay readable, also, this seems to increase performance quite a bit.However there is one issue: in areas with higher autogen (especially trees) I get flashing artifacts like polygons originating from trees and buildings for a short time. There are no performance problems and the sim runs stable, but this is kind of annoying.My suspicion is, that this AA setting is just too much for my rather-weak GTS250 card, or has anyone an idea how to get rid of these errors? Otherwise that setting has to wait for the next upgrade....My System specs: Phenom II X4 965 @ 3,9 Ghz, 8 GB RAM, nvidia GTS250 1GB, Win7 64bit, FSX AccelerationI run the sim with bufferpools=o if thats something useful.....

OK, I did that, but no changes, with the default soundpack, it only occurs in the internal view. Jugded by the sound files i'd say its the internal whine_2-Sound that comes out way to loud after pausing the sim in internal view or switching from external to internal.

Well, IÄm sure someone posted this before but I cannot find the thread now. I fly the CLS DC-10 alot, because I like the DC-10 and there is no other one out there.However, there is a sound mix problem with this bird: on low engine power settings, some idle sound of the engines get extremely loud and sound somehow broken. that only vanishes when pushing the engines up to about 60 % and back but is back when changing external and internal views or pausing the sim.....I tried to use another soundpack but the problem persists, seems to be a CLS issue.

Tried to revert all settings coming from nivida inspector and using default AA only -no luck......

Clean-reinstalled the driver , version 266.58 with no difference.....setting that slider to medium is probably all that I have left, although it reminds me in good old 32bit, 1 GB of RAM-Days......:blink:EDIT: distance set to medium, crash after 15 minutes in-game when trying to view the map.

Ok, I'll try to clean-install my drivers, but I have trouble finding a cleaner program that is compatible with WIn7 64bit.Anyways, forget what I said about the 707, I just had the same crash when having a Wilco 737 parked at KJFK for about one hour and then returned and opened a menu, again: crash.So the crash happens when using ENB mod in densely populated areas.Could that be too much for my video card?

the new nvidia installers does this automatically as far as I know. Correct me if im wrong. :( I know ;) well, I can definitely tell you now, that die ENB Mod causes the crash. right now im in-flight with the CS 707 and it runs rock stable without ENB. There is still one thing I forgot: my test flights to see if the crash happens were all made with this plane, because its the most demanding thing I have installed, to see if it works. So there is a possibility that the CS 707 does not work well with the ENB Mod. Ill check on that....

are you sure this will help? I mean, I can do this, in the end, the Problem will be gone. But it will be gone if its an OOM issue as well as it will be if its a broken addon, because the memory load drops without addons.

As I already mentioned in this post, I get crashes after 5 till 30 minutes in-flight, I originally thought they were related to my ENB-Mod, but it seems when testing it without I just have been lucky.Here is the error message from Win7, sorry its in german: Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14Name des fehlerhaften Moduls: d3d9.dll, Version: 1.0.0.1, Zeitstempel: 0x48751493Ausnahmecode: 0xc0000005Fehleroffset: 0x00006d1cID des fehlerhaften Prozesses: 0xbc8Startzeit der fehlerhaften Anwendung: 0x01cc1d227d76a55aPfad der fehlerhaften Anwendung: S:\FSX\fsx.exePfad des fehlerhaften Moduls: S:\FSX\d3d9.dllBerichtskennung: 9f136128-891b-11e0-84f7-0050ba493fe4 This happens faster when I only use 4 GB of Memory instead of 8 GB, which would point to an OOM-issue, I have many addons, but shouldnt 8 GB be enough? Should I really consider co for a new MoBo which supports 16 GB max??? I don't think so......I tried all possible things in my FSX.CFG without sucess, here it is, I removed some entries that are not relevant: [bufferPools]//RejectThreshold=131072 <-------- (thats because of boyotes auto tweak, however the sim runs much smoother with PoolSize=0 then with RejectThreshold enabled, I tried other pool values without sucess)PoolSize=0[VirtualCopilot]VirtualCopilotActive=0[sOUND]AmbientUI=0AmbientUIMusicVolume=-6.000000PrimaryDevice={7FA56862-A712-459F-A1A3-3BC764A3AEF2}SOUND=1SOUND_LOD=0SOUND_QUALITY=2UISound=1VoiceDevice={7FA56862-A712-459F-A1A3-3BC764A3AEF2}SOUND_FADER1=0.390000SOUND_FADER2=0.610000SOUND_FADER3=0.500000SOUND_FADER4=0.500000AmbientUIMusic=FSX01[slewTextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2[AContain]LabelColor=FFFF0000LabelDelay=1000ShowLabelAirline=0ShowLabelAirlineAndFlightNumber=0ShowLabelAirspeed=0ShowLabelAltitude=1ShowLabelContainerId=0ShowLabelDistance=1ShowLabelFlightPlan=0ShowLabelHeading=0ShowLabelManufacturer=1ShowLabelModel=1ShowLabelTailNumber=0ShowLabels=0ShowUserLabel=0[DISPLAY.Device.NVIDIA GeForce GTS 250.0]Anisotropic=1Mode=1280x1024x32[ATC]AutoOpenAirTrafficWindow=1COMM_MSG_AI_ATC_COLOR=FFFF7840COMM_MSG_ATC_AI_COLOR=FF00FF00COMM_MSG_ATC_USER_COLOR=FFB6FFB6COMM_MSG_NONE_COLOR=FFFFFFFFCOMM_MSG_USER_ATC_COLOR=FFFFD21BPilotVoice=0ShowATCText=1UsePilotVoice=1[TextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2WindDirectionAndSpeed=1,6[AccelerationPack]ControlsFirstRun=0HomePageFirstRun=0[iNTERNATIONAL]ASLAT=2ASLON=1MEASURE=0[CONTROLS]Controls_Current=StandardControls_Default=StandardKBDAIL=64KBDELEV=64KBDRUD=38[FACILITIES]CITY=COUNTRY=GTL_BUTTON=1336STATE=[TextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1FuelPercentage=2,4GForce=2,3Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2WindDirectionAndSpeed=1,6[PointOfInterestSystem]CycleSetting=0[GRAPHICS]AC_SELF_SHADOW=1AIRCRAFT_REFLECTIONS=1AIRCRAFT_SHADOWS=1ALLOW_SHADER_30=1COCKPIT_HIGH_LOD=1D3D10=0EFFECTS_QUALITY=2GROUND_SHADOWS=0HIGHMEMFIX=1IMAGE_QUALITY=0LANDING_LIGHTS=1NUM_LIGHTS=8See_Self=1TEXTURE_MAX_LOAD=1024TEXTURE_QUALITY=3Text_Scroll=1SHADER_CACHE_PRIMED_10=1693500674SHADER_CACHE_PRIMED=1693500674SHADER_CACHE_VERSION=2[TrafficManager]AIRPORT_SCENERY_DENSITY=3AirlineDensity=100FreewayDensity=20GADensity=75IFROnly=0LeisureBoatsDensity=100ShipsAndFerriesDensity=100[DynamicHeadMovement]HeadMoveTimeConstant=1.000000LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000MaxHeadAngle=5.000000MaxHeadOffset=0.300000RollAccelOnHeadLat=0.010000RollAccelOnHeadRoll=0.100000YawAccelOnHeadLat=-0.100000[REALISM]AllowEngineDamage=TrueAutoCoord=TrueAutoTrim=FalseCrashDetection=TrueCrashTolerance=1.000000CrashWithDyn=FalseGEffect=TrueGeneral=1.000000GyroDrift=TrueGyroEffect=1.000000ManualLights=TruePFactor=1.000000RealMixture=TrueStressDamage=TrueTorque=1.000000TrueAirspeed=FalseUnlimitedFuel=False[Weather]AdjustForMagVarInDialog=1CLOUD_COVERAGE_DENSITY=8CLOUD_DRAW_DISTANCE=4DETAILED_CLOUDS=1DisableTurbulence=0DownloadWindsAloft=1DynamicWeather=2MaxGustRampSpeed=200MaxGustTime=500MaxVarRampSpeed=75MaxVarTime=50MinGustRampSpeed=1MinGustTime=10MinVarRampSpeed=10MinVarTime=5THERMAL_VISUALS=0TurbulenceScale=1.000000WeatherGraphDataInDialog=0WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WindshieldPrecipitationEffects=1[Misc]Com_Rate=7[Main]HideMenuFullscreen=1HideMenuNormal=0SimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscUser Objects=Airplane, HelicopterProcSpeed=10063PerfBucket=7Location=124,110,1156,876,\\.\DISPLAY1Maximized=1[TextInfo.2]FrameRate=1,1FuelPercentage=1,4GForce=1,3LockedFrameRate=1,2[uSERINTERFACE]Map_Orientation=2PAUSE_ON_LOST_FOCUS=0PROMPT_ON_EXIT=1PageID=1SHOW_MISSION_CAPTIONS=0SITUATION=FLIGHTS\OTHER\FLTSIMOpenATCOnCreate=1DisplayFuelAsWeight=0ShowAllACPaintSchemes=1SelectAircraftManufacturer=AlleSelectAircraftPublisher=AlleSelectAircraftType=Alle[sIM]SYSCLOCK=1[Display]ActiveWindowTitleBackGroundColor=0,28,140,64ActiveWindowTitleTextColor=255,255,255BLOOM_EFFECTS=0ChangeTime=4.000000InfoBrakesEnable=TrueInfoLowerLeftBackGroundColor=255,0,0,128InfoLowerLeftTextColor=255,255,255InfoLowerRightBackGroundColor=255,0,0,128InfoLowerRightTextColor=255,255,255InfoOverspeedEnable=TrueInfoParkingBrakesEnable=TrueInfoPauseEnable=TrueInfoSlewEnable=TrueInfoStallEnable=TrueInfoUpperRightBackGroundColor=0,0,0,0InfoUpperRightTextColor=255,0,0NonActiveWindowTitleBackGroundColor=24,33,87,64NonActiveWindowTitleTextColor=255,255,255SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=70TextureMaxLoad=30TransitionTime=4.000000UPPER_FRAMERATE_LIMIT=0WideViewAspect=False[JOBSCHEDULER]AffinityMask=14[slewTextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2[PANELS]DEFAULT_VIEW=0IMAGE_QUALITY=1PANEL_MASKING=1PANEL_OPACITY=100PANEL_STRETCHING=1QUICKTIPS=0UNITS_OF_MEASURE=0[sTARTUP]DEMO=0LoadWindow=1SHOW_OPENING_SCREEN=1STARTUP_DEMO=0[slewTextInfo.2]FrameRate=1,1LockedFrameRate=1,2[TERRAIN]AUTOGEN_DENSITY=5DETAIL_TEXTURE=1LOD_RADIUS=4.500000MESH_COMPLEXITY=100MESH_RESOLUTION=25SWAP_WAIT_TIMEOUT=2TEXTURE_RESOLUTION=29WATER_EFFECTS=7TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=4500[sCENERY]DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=5LENSFLARE=1MAX_ASYNC_BATCHING_JOBS=2SmallPartRejectRadius=4.0[FlightPlanMap]LineWidth=2SHOW_AIRPORTS=1SHOW_VORS=1SHOW_NDBS=1SHOW_APPROACHES=1SHOW_INTERSECTIONS=1SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=1SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1show_waypoints=1show_airways=1show_markers=1show_volume_boundaries=1show_ac_twr=1[MAPVIEW_MAP]SHOW_AIRPORTS=1SHOW_VORS=1SHOW_NDBS=1SHOW_APPROACHES=1SHOW_INTERSECTIONS=0SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=1SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1show_flight_history=1[MULTIPLAYER]condAccoutPassword=0 My system specs are as follows: 4,0 Ghz Phenom II X4 965, 8 GB DDR2 1066 RAM CL5, nvidia GTS250 1GB driver version 266.58 (I have changed that, no sucess), Win7 64bit, FSX with Acceleration.Here is whatI did so far:-changed bufferpool values and experimented with them.-tested my ram for instability, actually found one, solved it, but still got the crash.-reworked ENB settings as seen in the thread mentioned above, actually I got these crashes before I even installed this mod.-tried 3 different nvidia drivers-uiautomationcore.dll is applied-completely reworked my overclock to assure its stable.-highmemfix is there, as you can see, as well as the fsx-exe is verified to have the largeadresshardware-option set.Tha fact that it happens in high-density areas like NYC with UTX and GEX points to an OOM issue as well, but since I do not have any performance problems on my rig, am I really required to lower my settings? How much RAM does FSX use max on a 64bit system with highmemfix set?Any Ideas?thx in advance....

Thx for all the responses. Yes, my config basically was nicks although I changed some values at the beginning but now I changed my logic in doing so, because what might cause such a crash is probably activating a function in ENB that is already present in FSX, like AA and AF, I'll try that change now.About UseEffect=0, thats what I tried 2 days ago with no sucess, the other values for AA and AF were still on then however.EDIT:no sucess, moving this issue to the CTD section.....

no, my GTS250 runs on stock clocks, only my CPU is a Phenom II 965 brought to 4 Ghz via multiplier so everything else on my system runs on default speed.

Well it didn't happen to me without the ENB mod, and I tried 3 different nvidia drivers. I already noticed the crash does happen faster when I only have 4 Gigs of RAM installed (about 5 minutes) than with 8 GB (about one hour). But its not happening when I rename the ENB dll and fly without it.menu dll uiautomationcore was already taken care of a long time ago. ;)

I dont know this for sure and mine is a CTD issue. But I noticed I am forcing AF in the specs and I have no screen size listed there, maybe this does change something.....

Lucky you. :Applause:so? You either have a 32bit OS, a different version of ENB or an ATI card or I am doing something wrong here.........:rolleyes:heres my enbsettings.ini: [PROXY]EnableProxyLibrary=0InitProxyFunctions=0ProxyLibrary=[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1BugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=enbseries2.ini[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0EnableDepthOfField=0[iNPUT]KeyUseEffect=123KeyBloom=120KeyOcclusion=121KeyReflection=122KeyCombination=16KeyScreenshot=44KeyShadow=119KeyWater=118KeyShowFPS=106[REFLECTION]ReflectionPower=60ChromePower=60UseCurrentFrameReflection=1ReflectionQuality=1ReflectionSourceSpecular=50ReflectionSourceTFactor=50UseAdditiveReflection=1ReflectionDepthBias=0UseLowResReflection=1ReflectionSinglePass=1UseEnvBump=0EnvBumpAmount=100EnvBumpOffset=100ReflectionFlip=0[bLOOM]BloomPowerDay=7BloomFadeTime=400BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=30BloomCurveDay=0BloomPowerNight=30BloomConstantNight=0 BloomCurveNight=9BloomScreenLevelNight=12BloomAdaptationScreenLevel=80BloomAdaptationMultiplier=100BloomAllowOversaturation=1BloomMaxLimit=100[sSAO]UseFilter=1OcclusionQuality=2FilterQuality=1DarkeningLevel=15BrighteningLevel=20 IlluminationLevel=20 AdditiveIlluminationLevel=25UseAmbientOcclusion=1UseIndirectLighting=1FadeDistance=50UseForAlphaTest=0UseForAlphaBlend=0[colorCORRECTION]DarkeningAmountDay=25ScreenLevelDay=50ScreenLevelNight=12DarkeningAmountNight=-80GammaCurveDay=-2GammaCurveNight=10ColorSaturationDay=1ColorSaturationNight=-3UsePaletteTexture=0[WATER]UseWaterDeep=0WaterDeepness=20WaterQuality=0[sHADOW]ShadowFadeStart=40ShadowFadeEnd=80ShadowAmountDay=50ShadowAmountNight=40ShadowScreenLevelDay=40ShadowScreenLevelNight=30ShadowQuality=1UseShadowFilter=0FilterQuality=2ShadowBlurRange=30[ENGINE]ForceAnisotropicFiltering=1MaxAnisotropy=8ForceDisplayRefreshRate=1DisplayRefreshRateHz=75[MOTIONBLUR]MotionBlurQuality=1MotionBlurVelocity=0MotionBlurRotation=0[PERPIXELLIGHTING]SpecularColorMin=0SpecularColorMax=100SpecularColorMultiplier=100SpecularGlossinessMin=0SpecularGlossinessMax=100SpecularGlossinessMultiplier=100[DEPTHOFFIELD]DOFQuality=2DOFNumberOfPasses=1DOFFocusRange=50DOFBlurinessRange=10

Hi there,I used the ENB Mod to compensate my turned off FSX Bloom effects, which improved performance quite a lot since I only fly in DX9-Mode. However, my FSX crashes with a d3d9.dll-error when entering or exiting menu screens after a while. (I noticed this changed depending on how much RAM I have installed, with 8 GB this was a vicious thing that happened after half an hour flying, with only 4 GB it happened after a few minutes.)After a week of tweaking, testing and swearing....I have ruled out any other cause for this crash except for the ENB Mod, which is really a pity because I liked these effects and spent day on good values giving my nights a higher contrast and making stars and cities look better while the rest is still very dark.I read about an issue with highmemfix=1 when using ENB-Mod, but since I found that topic via google, I just ask in a new one if there were any progresses in fixing this.thanks in advance.

That Registry thing worked! Thanks everyone!

OK since my last posting about this topic was a bit complicated, maybe someone is able to help when I get more specific. Basically my problem is, that with addon planes that use external dlls, this sections in the panels are missing.-The FSX dialog box when loading such an addon plane for the first time does not appear.I mean this one, example taken from Active Sky's Xgauge:-FSX therefore blocks digitally unsigned gauges.My addons were all installed with administrator rights as well I FSX is run as admin, I globally turned off DEP via console command and UAC is at the lowest level Windows allowed me.I use Windows 7 x64.Does really no one have any ideas? :(

To specify my problem: is there any option, setting or configuration that can prevent FSX from showing the digital Signature Dialog that appears when selecting an addon plane for the first time?

Hi there,after I renewed my FSX.cfg because of some other problems which are gone now, my FSX stopped adding the dll's needed for some addons (mostly planes) automatically to the "trusted" section. The popup you normally get, which asks whether you want to add this file to the trusted list, simply does not appear and most complex planes get loaded with lots auf gauges or in some cases (CLS 747) with the entire VC missing.I am running win7 64bit and FSX with administrator rights.any ideas about this really strange problem?thanks in advance....