• Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About ronski

  • Rank

Profile Information

  • Gender
  • Location

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. 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.
  2. 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.
  3. 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; 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.
  4. 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.
  5. head over to microsoft, to check for registry errors and run the fix it program. the installer/uninstaller program may be faulty. see here; 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; may seem strange, but have you tried the drivers that are on the CD that came with the card.? Ron.
  6. 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; 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.