kjng

create a batch file put in this line start/affinity a "b" "c" where a represents a hex value of which cores to be used, like the affinitymask setting in the fsx.cfg BUT the value has to be hexadecimal here b is the title, leave it blank c is the exact path of your active sky exe file example given start/affinity 8 "" "c:\AS2012\AS2012_Exec.exe" will start as2012 solely on core 4 on a 4 core processor with ht disabled regards, Markus

You could use parameters to define the affinity of a started application

The video memory is handled by the video driver, fsx has nothing to do with it. It looks like the gtx 680 is the card to have with fsx, benchmarks show an extreme performance with ssaa. I will wait for ivy and build a new rig

I know what eyefinity is and I know what great load that resolution would put on any gpu in heavy weather. I guess "Your Dudeness" does not.I like the big lebowski too and I know what I am talking about ;)

dude, you're talking about a resolution of 5760x1080, go figure... I don't know if this still stands with modern ATI cards.With my Nvidia card I am using heavy AA modes to get rid of very bad shimmering (that TrackIR reveals) the ATI cards don't seem to have in the first place.I guess if you know exactly what you're doing you can be quite happy with an ATI card.

To make it short, if you're happy with FS9 stay with it, don't even start wasting your money on fsx.

There's evidence that if you run an SSD without ahci you will lose one of its biggest advantages (4K threaded performance), but it seems you're right about trim.

Make sure you activate ahci for the sata controller within the bios or trim won't work

I also consider buying either fs2crew or mce. I want to use voice recognition for RC4 ATC communication.I read mce has a part for that, too bad fs2crew has not. Is something like this planned for fs2crew too?

you should also check your ram mit memtest86

kepler maybe delayed due to problems with the pcie 3.0 interface

Lars you could run this tool during your test runshttp://forum.avsim.net/topic/360449-dx-explorer-excellent-tool-for-in-depth-analysis/It would give you even more information on what's going on, dx calls etc.Regards,Markus

Can you give us a sane reason why you are trying to do this?anyway, you could try to restrict as2012 local network access thus breaking the link to simconnect

For anyone interested whats happening beneath the hood of fsx look herehttp://forum.avsim.net/topic/360449-dx-explorer-excellent-tool-for-in-depth-analysis/Regards,Markus

Hi fellow simmers,inspired by Word Not Allowed's effort to pinpoint a problem with his clouds by offering comparison screenshots,I started to search for a tool that we all could use for a much more detailed under the hood analysis of a certain situation, so maybe we could find solutions togetherand make the sim better for all of us!To make it short, I've found something that will show you in detail everything that's happening on your screen.The name of the tool is DX Explorer, kudos to Matt Stentiford the developer!You get all possible information like the number of triangles, DX calls, draw calls, used textures, used version of pixel and vertex shaders, you can fiddle around with the draw modes, render states and so much more.This is a definitive must have for anyone interested in the technique behind the simulator and guess what it's free too!some screenswireframe draw modePixel Shader Version displayStats displaywhere to get:http://www.sandboxso...net/dxexplorer/how to use:I think it does no mess with anything but you use it at your own risk!extract or run the installerrun the applicationBrowse for your "fsx.exe" (lower middle section)open advanced options (bottom left corner)check proxy dll and press "copy dll"There's a brief explanation of how to use it within the directory.I think a helpful advice is to be patient, it will not always interact with the first few clicks.