ronski

I remember some AA issues with 2004. Not 100% sure, but it may have been a Nvidia control issue. The profile for 2004 was never quite right, but it didn't affect everyone. Or it simply got corrupted somehow. something you could try. Open Nvidia control panel, manage 3D settings, select program settings and find FS 2004. Make a note of recommended settings, either from Inspector setup or known correct settings. Delete this profile. close control panel. At this point, you may have to delete any Inspector setup as well. Next, go back into control panel and create a new program setting by selecting 'Add'. you may have to browse for FS 2004 if it's no longer listed. set up using known settings. Once done, start Fs and try first to enable AA in game. If it works then continue to setup inspector to the recommended settings, remembering to disable in game AA. Note, after run of FS, sometimes the inspector settings do not hold first time. Go back and check. This worked for some people, not all, but worth a try. Ron.

Go into NVidia control panel. look at the arrangement of your monitors, and note the numbers, ie 1-4 If any monitor is to the left of monitor 1, Change it. move the monitor to the far right of 1. Then try to move the required window in fsx to monitor 4. Yes, it will seem strange, if your actual physical monitor is below and left. You will have to move through your other monitors. Reason; some add on programs do not recognise negative values when it comes to resolutions in extended mode. If you think about it, monitor 1. starts with zero ( 0 ) top left, and ends with 1980, or if triple screens, 5800 or so. any monitor to the right starts at the next pixel, ie. 1981. and so on. Any monitor to the left will have a negative value. ie. -1980 Some programs, not all, do not like this negative value and will either freeze or stay black. All of this is in control panel and has nothing to do with actual position of your monitors. hope this helps, Ron.

If your instrument panel appears too close in the VC mode, you need to change a setting in your .cfg file. wide view aspect = true. default is 'false' change to 'true' and the instrument view will move back properly. (C:\Users\YOUR ACCOUNT NAME\AppData\Roaming\Microsoft\FSX\fsx.CFG) As for the stretching effect, this is a result of 'aspect ratio' and zoom. The result of projecting a 3D image on a flat screen, even with a single monitor, this can be seen at far corners if you move a round instrument there, but hardly noticeable. we used to run around 3800 x 1200 for triple screens. ( 3-1 approx. ). with high resolution wide screen monitors these days, that ratio has increased to over 6-1 and is the primary cause of the stretching effect at far right and left. Yes, there are some who claim to fix it, you would have to search. A really good video on this effect is here; https://www.youtube.com/watch?v=qjbCFNSofpk I prefer to run at a lower resolution, around 5040 x 1200 as a max. with bezel correction, most use 6000 or so and the effect is very noticeable. So, change the wide wiew apect setting, =true, start with 1.0 zoom and go from there. hope this helps, Ron.

OK, so I dribbled off topic. :unsure: My point was, I Agree with the OP. If we look at all the benchmarking graphs published, it's easy to think that one thing is 4 times faster than another, an example here; http://www.tomshardware.com/charts/cpu-charts-2012/-02-Cinebench-11.5,3143.html The fastest Intel chip appears to be 4 times faster than the AMD phenom 2 @ 3.4gig way down the list. Same thing happens when comparing an old GTX 9800 with the new GTX 780. The colored fancy graphs show it to be 4-5 times faster, but in reality, Not so...Hmmmm. I have FSX on an old phenom2 @ 3.4 with a GTX 9800, and have just completed a new Intel Haswell system overclocked to 4.2, superfast 2400 memory and a GTX780. Very expensive. If you believe the graphs etc. we could all be forgiven for thinking it would be at least 4 times faster. No where near it, :huh: a decent improvement of course, and better scenery settings, but barely 10-15 fps, This leads to a lot of frustrated users paying big money for very little gain. It's the marketing machine to keep us buying the latest ( and not so greatest ) computers.

fair comment, i tried to simplify it. remember that the card get's it information through the PCI bus on the motherboard. here's the long version. PCIe 3.0 removes the requirement 2.0 has for 8b/10b encoding, and instead uses a technique called "scrambling" that applies a known binary polynomial to a data stream in a feedback topology. Because the scrambling polynomial is known, the data can be recovered by running it through a feedback topology using the inverse polynomial. and also uses a 128b/130b encoding scheme, reducing the overhead to approximately 1.5% ((130-128)/130), as opposed to the 20% overhead of 8b/10b encoding used by PCIe 2.0. PCIe 3.0's 8 GT/s bit rate effectively delivers double PCIe 2.0 bandwidth. :blink:

Just shoving a new video card into a four year old system is simply not going to work as it should. The 7 ( and 6 I think ) series have PCI-3.0 and that made it possible to reduce the number of cores, reduce heat and volt requirements, allow turbo boosting, etc, etc.etc, bla, bla. Fancy colored graphs will show how many points faster it is than it's predecessors. But, without that extra bandwidth.......all for very little. If the motherboard does not have PCI-3.0 slots , the card will operate much like the old one. These days, with the rapid change, we must match all the components. Now with the new 4K video format ( Awesome!! ) we're looking at 4 times the resolution of true high definition. All those that bought anything less than a Titan, running 4K, are going to be complaining. and on it goes. Oh the fun. :Party:

Not really hard to believe, it's the same card, same chipset, with very mild higher clock. Just a later series. Good old marketing companies are making a fortune. the only real upgrade since the 400 series is the 780 and the Titan which use the newer 110 cuda cores.

Hi larry, If the instrument panel appears too close in 3D mode, go into the .cfg file and change; wide view aspect = false. change to, wide view aspect = true. Ron.

head over to microsoft, to check for registry errors and run the fix it program. the installer/uninstaller program may be faulty. see here; http://support.microsoft.com/mats/Program_Install_and_Uninstall/en-us just click on the 'fix it' button, see if they can sort it. Is there any way to reverse changes made by CCcleaner, just in case something was removed that shouldn't have? I don't use it, but I use Revo uninstaller, as it can reverse any changes. here; http://www.revouninstaller.com/revo_uninstaller_free_download.html may seem strange, but have you tried the drivers that are on the CD that came with the card.? Ron.

Hi there, Try this next, That atiumdag.dll is part of the ATI directX drivers, I don't know which DirectX download you tried but you should be able to use the update for DX9 etc. even if your card supports newer DX 10 or 11, here; http://www.microsoft.com/en-us/download/details.aspx?id=35 Next, Go into device manager, view, and select show all devices/ or show hidden devices. Check for errors and also multiple listings of the video card. If you find multiple entries for video card, delete them all and reboot, windows will either install the drivers or ask you to do it. Or, if only one and has an error, what does the error say? Next. have you considered a system restore? at least to get you back to workable situation. was there a problem with the old drivers? you know what they say; 'if it ain't broke....... Ron.

If your looking at overclocking, Nick has put together a great guide here; he does though, say you must use a Haswell rated power supply, something you may want to research, some do, some don't. I have a system for only FSX, when not flying it gets turned off, so I have no need for sleep mode. http://www.simforums.com/Forums/haswell-48ghz-on-air-building-a-haswell-system_topic46180&SID=1694759c93456ac28zzze98c8f72e8704513889.html You didn't mention what motherboard.? good luck, Ron.

Also make sure that the PSU you have, is rated for that Haswell chip, the Haswell has a new power saving feature in sleep mode, which reduces voltage to very low levels that previous PSU's could not do. If you have C-states enabled, then the power will shut down if not designed for the haswell. Check for haswell rated PSU's on it's web site. You can of course still use an old one, but you must disable C-states in the BIOS. ( or don't let it sleep ) something to be aware of. Ron.

You could also consider this if you have money to burn, NEC also have released something similar,

There are some places, here; http://flyawaysimulation.com/downloads/97/fsx-panels-gauges/20/ or here; http://www.friendlypanels.com/ If you search for FSX 2D panels, you might find some one who has done what you need. I have used panelstudio before and it is really quite easy to do, you can start with any default panel and simply add the 'pop up' ones in. Ron.

You could also just create your own, www.fspanelstudio.com Ron.

Hi Rushad, what on earth were you thinking, going from a high end graphics card, to a very low end card. you have to understand the sequence numbers of Nvidia cards, ie. the first number is the series, ie, 200, 400,500,600, the second number is the performance of the card, being 10 through to 80. ( ok lets not go to the dual 90 series ) 10 being the lowest and 80 being the highest. Your 280 was the highest and supported high end graphics, the 610, even though a later model was a piece of rubbish when using FSX as it is a very low end card, and hardly suited to any form of graphics or gaming. Anything with 50 or 60 attached , ie 660 or 550 are mid range performance cards. Anything with 70 or 80 attached, ie. 680 or 580, or now 780, are high performance cards. this applies to all series of cards, whether 200 through to 700, the higher the second number the better the card. Rod is correct, the 660 will maybe give slightly better performance at a lower cost, but it is still a mid range card, a 680 would be a much better upgrade. It all comes down to what you can afford, Ron.

Hi Mike, some of the missions are locked and prevent you from changing aircraft etc. Most missions are in 3D view, but yes, the Lear is in 2D. So, Try this when selecting a mission, make sure to check the box, 'Enable changes in selected mission' (no rewards given). Then, when it starts, press Alt, from menu, go to aircraft, >change aircraft,> select the same one and see if it loads the modified panel.cfg file. I can't try this myself as I'm away from home, but it's worth a shot. Ron. ps. thanks for the correction Frank, I was never good at fractions. :drinks:

Hi Mike, The mini panel is the four or two stand alone gauges that appear when you cycle through the views. ('w' key) most work OK, but some need to be reduced. As Jonabird points out, this only happens with the new ultra wide resolutions, as the gauge bitmap cannot stretch across such a wide screen. Go into your main FSX folder and look for 'Gauges' here you will find the mini panels, open in notepad. scroll down and you will see something like this; [minipanel100] position =7 size_mm=600,100 window_size=0.9, 0.2 the window size is the one that needs to be reduced by 1/3, so change it and then save. window_size= 0.3, 0.2 Ron D.

Hi Mike, Did you remember to apply the fixes to the mini panels as well? Here is a possible workaround; 1. Start the flight with say, the lear jet that's giving the problem, 2. Using the 'W' key on your keyboard, cycle through the views untill you get 'no instruments', ie full panel,> mini panel, > then view only. Stay on view only. 3. Go to the menu, (press alt ), select aircraft, then change aircraft, select the same one, ie, lear jet and OK. should be, when you return, the flashing curser will be gone. 4. From menu, go to views, select new view, instrument panel, then drag the new instrument view to your 4th monitor. 5. If the curser returns, repeat steps 1 - 3. This works sometimes with that horrible spinning thing. Ron D. :unsure:

Maybe next try to calibrate your monitors, using the black test here, http://www.lagom.nl/lcd-test/black.php something from Nick himself, http://www.simforums.com/forums/night-gamma-i-think-question_topic37205.html Ron.

One thing I remember, In Inspector settings, Under Antialaising, make sure gamma corrrection is set to 'off' Ron.

Hi Eddie, a couple of more things to check. 1.Make sure you are using the Dual link DVI cable that came with the TH2GO to connect to the video card. and that the green light on the unit is in fact on. Try a different usb port, don't share a port with controllers unless it's got it's own power. In fact try unplugging your yokes etc. to test. not enough power can cause problems. 2. Press alt + enter to see if it works in full screen mode. 3. The display mode you have is different from mine, and it's warning you that it's not appropriate for your set up. I have something like 60hz ( input 59 ). Even though Matrox recommend this, some monitors do not like 50hz. mine do not. Change the display mode. see pic

Hi Eddie, Go into FSX options >Display settings, make sure you select the new wide resolution you chose when setting it up in Matrox. ie, something like 5760 x 1080 x 32 have a quick look in Device manager, expand monitors, it should read Matrox TH2GO etc. not Generic plug and play. This was an early problem that Matrox claimed to have fixed, but worth checking. Nearly there, Ron.

Hi gb, that could be the one, too many different resolutions. But you can create custom resolutions etc. The point is, lower the resolution and aspect ratio to reduce the distortion, something to try out. I will have another look to see if that is in fact what I have. Just lower the resolution for the horizontal and see if it makes a difference :rolleyes: Ron.

Hi Eddie, Have you considered a system restore, as you can't get into windows normally, try this. Start windows in 'safe mode with command prompt', by tapping F8 key when starting. If asked, select administrator account. When the black cmd window opens, type in rstrui.exe. and then press enter. This should open your system restore window, and from here you can turn back to an earlier time before the mess started. You could also run the system file checker tool from the cmd window, Type in sfc /scannow ( note space after sfc ) and press enter, this will scan your operating system files and replace any corrupted ones with original windows files. takes a little time and may ask for the windows install disk, If you don't have it, just make a note of the file it wants to replace, and continue. You may also want to check that it's not some Malware causing the issue, search for and download Malwarebytes, it's free, but I'm not sure if it will install in safe mode. If it does, then run full system scan in safe mode. Ron.