Jump to content

L.A.M.

Frozen-Inactivity
  • Content Count

    10
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About L.A.M.

  • Birthday 09/10/1965

Flight Sim Profile

  • Commercial Member
    No
  • Virtual Airlines
    No
  1. Hello David, The ILS by itself gives the pilot vertical and lateral direction at the same time all the way down to the numbers on the runway while flying the approach either manually or using the AP. All the other types of approach procedures give you just lateral position and you must have the charts on hand for the vertical descent in order to avoid undershooting or overflying the runway. I believe that there are a very limited number of airports that have GPS approaches that work like an ILS and the last time I checked (a couples of years ago), they were in an experimental phase, so once this project is complete it will mean that every runway on every single airport will be able to have "ILS" procedure thanks to the GPS. FSX is well known for the misalignment between a plain vanilla ILS and its respective runway, some airports' ILS signals are dead on but other ones put you in the middle of nowhere. If your favorite FSX airports that you fly to and from all the time have such errors while flying the different approach procedures then is a good idea to browse AVSIM and download the airports that have been improved and/or corrected by the folks that master and know how to mess around with ADE and other tools available to make FSX much better.
  2. Hi Skynerk and all, From my limited experience all I can say is that the numbers on any runway like 26, 18, etc is just the heading on your compass assuming you keep it in line with your magnetic compass and properly calibrated but by no means they are precise, so assuming your are heading 270 and ATC tells to land on runway 8 guess what you have to do to reach runway 8 and as you turn final to runway 8 you'll see on your compass and HI that 8 is approaching the nose of your plane and then you align and land. The number on the runway are not precise but the numbers on your approach plates and airport and facilities directory are very precise and that's where you'll find out that runway 16 is 162 on your HI/compass and 18 in reality is 184, etc. Just browse the FAA website for airport and approach plates/procedures and you'll see the real numbers for your airport's runways. ILS is another story and it's a PRECISE approach compared to the non precise VOR, NDB and GPS approaches. If you check the approach plates, all of them will give you the exact heading that you are supposed to follow and in those plates you'll see the numbers 182, 243, etc.. ILS is a precise approach because it provides the precise vertical and horizontal position of your airplane while you are flying the approach so it's your duty and responsibility to keep those gauges dead center with a minor + or - deviation but believe me in real IFR you want to be dead center on those gauges/dials or LCD. At the moment some airports already offer GPS precision approaches but I'm not up to date on this information but is coming no doubt about that. Now the ILS is precise and it will take you dead center straight down the runway otherwise how will you do a CATII or CATIII or a 0/0 landing in your airplane? So while flying the ILS with your GPS make sure that the OBS letter are on or Nav but not GPS. FSX is not precise and ADE that can master it by dedicated guys like Ray Smith and all the great folks that burn their brains and eyes correcting runway headings and correcting ILS, VOR, NDB and what not that are installed on the airports surrounding areas that are needed to make the approach plates work right. I understand your issues but again from my limited experience they are totally 2 different things, ILS, NDB, VOR are made for flying. Runway headings are just that a general direction for you information while flying the an approach.
  3. Same thing happened to me and I had to look real close and only then I was able to see the difference on the split screen because the colors and shades were very close on both sides. Once I saw the difference then I began activating the other options just to see what they do and the difference was more noticeable. I think the default split screen is not vertical but runs in a diagonal line and you may want to choose the vertical split in the config. I believe this was the reason I had a hard time seeing the split screen the first time. In my case the left side had a light grayish blue sky while the right side of the monitor had nice blue sky because of sweetfx. The response above is right, I think it works only on single monitors and if you are using an external frame limiter you might want the limiter to point to the d3d9.dll provided by sweetfx and not the other "brand".
  4. Hi Luc, Maybe your textures and colors are close to the SweetFX initial settings so you won't notice much; however, if you activate the Split Screen option you'll notice the difference. Same thing with me, initially I didn't notice nothing until I activated the Split Screen only then I noticed that sweetfx was working. Once I could see the difference between the 2 then I activated the other options like technicolor and sepia just to have an idea what's going on with this injector, but haven't messed around with the individual components so far I haven't seen the need to do it and I"m happy with the defaults. You have to uncheck AA in FSX configuration file and enable AA in the video card, in other words hardware controlled instead of software. I'm using GURU3d because Skyrim's gives a flash of cyan when I switch cockpit views or activate the GPS or any of the consoles.
  5. Hello hocdaddy, WoAI's files contain the flight plan, airports and airplane information inside the zip file. When you run the installer you point the program to the location of the zip file and then the installer does the rest for you. Very simple just a couple of clicks and that's it. If you are using FSX then is up to you if you want to convert the flight plan to FSX or leave it as 2004 default format, just be aware that all your previously installed FSX traffic will go disappear. It all depends on the airline that you choose to download and the flight scheduling it may be or may not be at your airport at the time of your flight. You may pick a popular airline like Delta, American, Southwest, etc. and pick KLAX, KSEA to fly from/to and for sure you'll see some traffic coming and going on these airports if you choose some of the more well known airlines listed in WofAI. Good luck and enjoy the learning curve. Luis.
  6. It seems more like a screen refresh thing. It happens to me when closing the ATC (`) window or closing GPS (shift+3) and after switching screens (S) or views (A) but they get cleared after a few seconds or in the process of switching views. Is not major, just ignore them and before you know it they are gone later in the "flight".
  7. Hello IAF747, For starters you might want to google "FSX enb series" and just browse to the options. I believe there are about 2 or 3 options to handle the mood/ambient lighting of the FS. You may even try You Tube, there are a couple of videos that will show you what can be done by tweaking the different parameters. Probably with the right sky and land textures you won't need much of an ENB series and leave your monitor at the settings that are most comfortable to your eyes.
  8. Hello Braden, The addon that I've used is Nick's Light Fix V2 and it comes with large and small sizes and they look great from far away, specially if you are in major metro area with multiple airports or out in the middle of a cross country you can spot the airports right away. I don't know how tweaked your FSX.cfg file is but in may case for some reason all my airport's rotating beacons disapeared so hopefuly the same thing doesn't happen to you, for sure this issue has nothing to do with Nick's files. I've been toying with the following settings per Nick's suggestions but is not really necessary but it all depends on your taste. RUNWAY_LIGHTS_SURFACE_SCALAR=1.2 //adjust values to suit your scale RUNWAY_LIGHTS_VASI_SCALAR=1.2 RUNWAY_LIGHTS_APPROACH_SCALAR=1.2 RUNWAY_LIGHTS_STROBE_SCALAR=1.0 I hope this helps.
  9. I believe there are 2 versions of the FXAA PPIT tool or at least I was able to find 2 of them. Skyrim version comes with an install file and you choose on of the presets to install. You may view them at their web page. I choose preset 4 just for test purposes, but for some reason I found all of them kind of gloomy except preset 4, looks a little brighter. Skyrim also has the FPS limiter and it's much simpler and easier to install and configure than the one recommended by bojote in case you go that route to configure your fsx.cfg file. Assembla is the version I believe we are talking about here. For my taste so far this version didn't require any tweaking at all and the colors look much better than ENB or Skyrim. I haven't tested in all sorts of weather and the different landscapes in the world but initially it makes FSX look much better. I'm still playing around with it. My challenge right now is the FPS limiter and the FXAA tool working together since both use the same d3d9.dll file in the FSX folder. I found one solution were one dll gets renamed and the cfg file gets updated as well to reflect the name change but I haven't tried yet. But I still need to do more research on this one. So far looks like the Assembla FXAA tool is a keeper for me but YMMV.
  10. I had the same problem. Just download the latest update/version of DX9 from Microsoft. It's version © and once you install it copy the files again and that's it, run FSX again.
×
×
  • Create New...