Post by aeromexico - HJG on Jul 13, 2015 19:44:10 GMT
Hi, thanks Tony, I will see into it immediately since right now I am in the process of saving all my files and software into another HD.
I just did a check, it is not present in my system since I am not admitting anymore Windows updates due to the same reason, Microsoft pushing people to buy Windows 10 and installing crap without any information on it.
Post by Nathan Ford - HJG on Jul 27, 2015 9:08:37 GMT
Eduardo, how have things been going? Can I make a suggestion? Run FS9 in windowed full screen but close down core 0 on your CPU in the FS9.exe
To do this start up fs9 and wait until it loads the create a flight menu. Now hit ctrl alt del and open up the task manager. Find FS9.exe and right click then select "Affinity". Remove the tick from core 0 but keep the ticks on the other cores. Now close the task manager. Now carry on with fs9 and see if you get better FPS.
Windows runs a lot of its processes on core 0 and if FS9 has to compete with these processes, it can degrade FPS. I do this every time I start FS9 and get locked 50fps on nearly everything. If I find my FPS are down, I realise straight away that I forgot to close core 0. If you have 6 cores, you could look on the task manager usage graph and see if windows is hammering any other of your cores then close that one too in fs9.exe if you want, but always close core 0 for FS9.
A quick note too, only close the core for the FS9.exe, leave the others. Your drop in FPS may be a result of a windows update utilising windows during fs9 more than before.
Also, if you are using REX or Active Sky, you may want to think about running it on core 0 and the last core. I have a 4 core machine so I run FS9.exe on core 1, 2 and 3 (unchecking core 0) and run Active Sky on core 0 and 3 (unchecking core 1 and 2). With your 6 core CPU run FS9 on 1, 2, 3, 4 and 5 (unchecking 0) and run REX/Active Sky.exe on core 0 and 5 (unchecking 1, 2, 3 and 4). This will allow a different core to run the weather freeing up the others for FS9.
Post by aeromexico - HJG on Jul 31, 2015 3:01:09 GMT
Nathan hello, thanks for the input!, effectively I did notice that it was better to run FS9 on the rest of the cores and disable Core 0 from the affinity list. I do not own REX nor AS but FSrealWX lite, yes it does make a difference, considering that I do have FS9 patched with the 4GB thing. As for my antialiasing dilemma, I am currently on driver 301.42 I think, and it is working nicely, my setup is on 16xS with super sampling 8X, now I am getting 58-60FPS solid in climbs and cruise while on detailed airports and weather around 30 FPS minimum, I do not know what is happening but the sim seems to run nicely now even if get occasional sutters specially from weather updating in departures and arrivals. also what I have done to improve the situation a bit is to change my monitor resolution from 1680x1050X32 to 1680x1124, this seems to have helped a bit to make it more fluent. I am satisfied with this result thou I had this quality at 8xS previously, perhaps in the future I might be able to find a proper solution and make sure this does not happen again. In the mean time I appreciate the input of everybody who took the time to answer.
Post by Nathan Ford - HJG on Aug 1, 2015 12:23:04 GMT
One last thing, you have been installing and uninstalling a lot of drivers. After you have uninstalled the driver from remove programs, are you running DDU (Display Driver Uninstaller) by GURU3D in Windows Safe Mode before installing the next driver? If not, I would highly recommend Googling it, creating a restore point, uninstalling your latest driver, running DDU in "Windows Safe Mode", then and only then reinstalling the driver.
Each time you uninstall a video driver, it leaves files and registry entries behind so it never truly uninstalls properly. DDU will clean everything out so that you have a clean video driver install. You will have to re-enter the nVidia inspector setting afterwards as they will go too.
Post by aeromexico - HJG on Aug 4, 2015 7:51:05 GMT
Nathan hi, yes I have done all of this now, and yes the picture is very clear, of course I am still running the 16xS setting and wonder how on earth I had the same or even better quality on 8xs?, one thing is... I did re-adjust my Monitor setting and it seems to have made a difference, also I discarded ALL of the files on the TEMP folder where FS9.cfg is located, it removed a lot of blurriness from the sim, how can it be?, dunno.... but it sure works. Yes I always use DDU, nice little gadget for cleaning everything I'd say. I have had my 560 since Dec 2012 might be coming the time to change to something more powerful since I do intend to run P3D in the enar future.
Post by Tony Madge - HJG on Aug 11, 2015 5:04:31 GMT
Hi Nathan, well I did the trick off putting FS9 on the other three cores and not "0" no difference, I tried the other stuff again no difference, I seem to be hung around 35-40 fps and busy areas mid to high 20's I have a lot of intensive graphics going on with scenery and weather etc so I am happy with it though, it looks ok and I live with the odd FS9 stutter I have put Windows 10 on another partition so I am going to slowly load FS9 on there, big job though
AMD Phenom II X4 965 o/c 3.80GHz Gigabyte GA-MA770T-UD3P Motherboard Corsair Dominator 8GB DDR3 XMS3 PC2-1600C9 Ram GEforce GTX 560TI 1200Mb DDR5 Ram 3x SATA hard drives Arctic Cooling Freezer Pro CPU Cooler OCZ 700w ModXStream Pro PSU
A few things to keep in mind with using NVidia Inspector: 1) never use the driver setting window, but do any tweaks through Inspector itself only! 2) never change the default profile ever either through Inspector or the driver settings window, it can brake stuff!
A few pointers: with AA, supersampling is 4 times as resource demanding as multisampling, also I saw FXAA is on, both FS2004 and FSX are too old to support that, so turn it off. Unless you are running a 4 or 8k monitor it's useless to go higher on AA than 4, 8 if you really wanna go gung ho on it 4xS is quite ok for 1080p monitors. Also, with transparency AA make sure to have the same type of AA setting as the main one, so if the main AA is multisampling, so should the transparency one be, and either the same or half (or power of 2) setting (as an example, if AA is 4xS, transparency should be either 4 or 2, if 8 then it can be 8,4,2, etc., but keep in mind that the xS modes are combined multi and supersampling ones, so use multi in that case).
Extension limit is OpenGL stuff only, keep it off. Threaded optimization: Intel or AMD Hyperthreading related. Not to use with OpenGL - turn this off since FS2004/FSX isn't a program which can utilize this correctly. Tripple buffering: You turn this on if VSync is on
Post by Nathan Ford - HJG on Sept 13, 2015 12:55:55 GMT
That's stange Tony, you are running a similar sort of rig that I had prior to my last update and I used to get a steady 50fps. I also run Razor Cortex as it closes down a few un-needed processes, I wonder if that was the difference. I did notice every time I forgot to drop core 0 though. I did have twice the ram it too.
Will have a think about it. Might be a little bit though as my wife and I are approaching the one year anniversary of our beautiful daughter passing away four days after her eighteenth birthday And are both a bit off the rails atm.