DaveKay

I have an AMD 1100T, let the Asus M4A89GTD motherboard automatically do the initial overclock and got 3.9ghz right off the bat. Increased this to 4ghz without any issues. 3.7ghz on an 1055t as should be no problem at all! As already mentioned, depends on a decent motherboard with good voltage management etc… However, I found increasing the Northbridge & HT Link rendered better results than pushing the CUP speed to absolute limits! If you increase the HT link (default 2000mhz) to at least 3x the speed memory clock speed (3x800 for 1600memory) overall, things will be a lot snappier! I opted out getting the FX8350 due to so much of 'Bulldozer's' bad publicity (though I don't believe a lot of it) and would need to upgrade my mainboard too...an expense I'd rather not risk at this time...I'm quite satisfied with the performance of my current old defunct CPU! Increasing the Northbridge & HT Link... Cheers...DaveKay.

I thought I would give SweetFX another go after installing another profile from here …http://www.sim-outhouse.com/sohforums/showthread.php?73751-SweetFX-for-FSX/page2 (I’ve been using the FXAA tool for a while)… using the SweetFX configurator GUI. I seem to get the same effect using the FXAA tool with ‘only’ the ToneMap option turned on and making some adjustments giving the ‘illusion’ similar to that of an HDR effect…quite nice.. maybe this could be achieved via the graphic driver gamma and vibrance settings, though I must say SweetFX gives me a more satisfactory visual than the latter two methods. I recall a post from NickN at SimForums suggesting to turn off the EMB mod Anti-Aliasing option as this will cause stability problems, so maybe this might apply to SweetFX/FXAA too! I appear to be getting any performance ‘reduction’, but maybe attributed to that fact that my GPU is bottlenecked by my CPU (60% average usage in fact), thus leaving a lot of headroom for the GPU to do some extra processing such as this. I think I’ll test SweetFX for a while and see if it’s worth more tweaking time… just spent my hour quota I designated to reading my NGX manuals messing with this lol.

Just a short story to add...I purchased quite an expensive headset a couple of years ago, one of many I’ve owned over the years (from AKG, Beyerdynamic to Sennheiser all very good)... Had them a few weeks and accidentally sat on and broke them! I decided just to replace them with a cheap pair because I’m either ripping cord out the socket (or sitting on them)... Saw in my local shop a pair that ‘looked’ exactly identical, but a different brand costing much less. Did not think they sounded as good as the expensive ones and was not surprised. However, after a week or two I yet again wrenched the lead out...decided to dismantle them for repair and to my surprise the speakers inside were identical to the expensive ones!... soldered the wires back tested them and suddenly for no apparent reason they sounded as good as the expensive ones!!! At the moment I got myself the cheapest USB headset I could find for FSX... Cyber Acoustics AC-xxx range - speech recognition compliant, good reviews and work very well with Fs2crew... also usually check the frequency response on the packaging before buying somewhere around 20hz-20khz is good.

You’re welcome!

Try this!..... http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=16296 Regards..Davekay.

Funny enough seeing this post today …Beware of some of the ‘system wide’ tweaks… I spent till 3am this morning trying to resolve an application constantly crashing (Visual studio express)…turns out it was caused by disabling ‘UIAutomationCore.dll’ tweak mentioned on several FSX forums that’s supposed to reduce FSX from crashing!...was just about to-do a complete OS reinstall till I found after a considerable amount of time searching 100’s of MS support posts where I found ‘just one’ mentioning this file I forgot about…re-enabled it and bingo disabling this was the cause!!!!

I think that would be really cool…like the optional random equipment fault s...adds a little diversity!

Sure…http://www.orbxsystems.com/forum/topic/36537-fxaa-post-process-injection/Initially I followed instructions turning off antialiasing within NVidia control settings, but found leaving for FXAA to control looked terrible. I ended up turning off FXAA Antialiasing and kept NVidia Inspector settings as advised by ‘Tabs’, but not sure if this effects the other FXAA settings or if its independent of them!? However, I'm quite pleased with the way things look so far.The settings I’m currently using … Antialiasing = OFF (looks like 4x AA only) Sharpen = OFF (Seems to have no effect on my system!) HDR = ON, Power = 4, Radius = 3 Bloom = ON, All sliders = 5 Tone map = ON (all sliders kept default) Technicolor = ON (all sliders kept default) Sepia = OFF (for special effects only)I’m trying to get a good balance for daytime, dawn and dusk as settings that look ok at sunset, looks a little overexposed during day time, so deliberately kept setting low and subtle.I notice in the past there are a few folks on here with a good eye for achiving a realisitc look with textures etc. and maybe do the same using this!!!

Has anyone here tried FXAA Post Process Injection Tool? I have been testing it this weekend and managed to archive (in my opinion) a very nice viewing experience! However the default settings give a horrendous over exposed 1920s style screen which needs some adjustment through the provided GUI! I discovered it via the ORBX forum…http://www.assembla.com/spaces/fxaa-pp-inject/documents#I’m unable to gather a lot of info about this which appears to be more stable than the EMB mod.It works similar to the EMB mod (place ‘a d3d9.dll’ mod within the FSX root directory) plus some additional shaders...Apparently no performance loss at all and some claim it improves it, though I personally don’t see any!

I had the same problem. I think the REX spotlight.bmp(s) do work (sort of), but the intensity is too low to be visible!. Something I read from their forum. Using the higher intensity option ones I think work though I decided just to use the FSX default one in the end.Maybe a silly question, but have you checked ‘Landing Lights to illuminate Ground’ in the FSX Aircraft settings?Dave.

Hi. Did you set your text display DPI greater than >100% within the Windows control panel? If so, this can cause what you are experiencing with the load manager(s) and some cockpit display text side effects!

I have the Reality weather radar installed in the J41…a very nice little extra to play with (at first). However, more often than not… began to find it didn’t depict the conditions accurately, so I don’t’ even bother to turn it on anymore… I find it better to print a report from ‘Active Sky’ or I just wear a rain mac when the sky starts to look a bit moody!!!

Ah yes, I did wonder why this was the case though it opened and played ok in Golwave audio editor!...thanks for the explanation... Incidentally and at the risk of getting my head ‘bitten off’.. I resampled all the 44,100hz files to 22.050Hz and found slightly better performance especially with the J41 with a small top end reduction in audio quality (obviously).. Just thought I’d mention it in passing.

@Yitzhak LOL after 20 years of IT support, I’m begging to learn to check the obvious first too!... However,If it's still the dreaded ‘FSX’ graphic corruption… I would be re-checking the HIGHMEMFIX fix has been applied correctly syntax/spelling/iwithn the right FSX.CFG section etc. Have you already tried ‘Bojote' Altuve’ FSX.CFG auto config system (as stated in the PMDG 737NGX manual)… http://www.venetubo.com/fsx.htmlAlso maybe search and locate’ Bojote' in the root of these forums if not already done so… there are quite a few posts on this issue with various little remedies for different types video cards!

The NGX setup will/should install the correct VC runtimes *version and I think I recall a dialog stating this.Try reinstalling the NGX paying particular attention to that stage of the setup process to insure the correct VC runtimes gets installed alone with it. It is normal to have several versions of the VC runtimes and they should not be uninstalled as other applications that utilize them may have their own 'preferred (compatible) version. Applications that use the VC runtimes will check for a preferred set and if it can’t find it, will use the ‘best’ version it finds (but may cause errors). ...All the best