tgibson_new

PS. If you pay for V2 now, a V3 upgrade will either be free or 5 euros, the author hasn't decided.

It appears that the current v3 release is a Beta, and will probably expire. Version 2 Pro is limited freeware, with a payment required to unlock all its features (i.e. get a registration key). The features added by paying: These advantages are given with registered version: flight planner load editor weather finder better weather display for FSX and Prepar3D loading past weather loading and saving of weather data FSrealWX as client on a further computer more features are developed…. direct wind control You can activate FSrealWX by buying a key. From: http://wiki.fsrealwx.net/doku.php?id=en:fsrealwx:differences_between_unregistered_and_registered_version Hope this helps,

Hi, You don't need to actually delete gauges. In the panel.cfg file you will see lines like: gauge00= with gauge info after that. To inactivate that gauge, just edit by adding //: //gauge00= That way you can inactivate and reactivate gauges easily. Save the file after each edit, and then reload the plane.

First check if you have inactivated them in FS2004. Try pressing Ctrl K to toggle them. If that didn't change anything you can press Ctrl K again. If you changed this to something else use those keys instead. Then make sure they are plugged into active USB ports. Try a memory stick in them to test them. Then go to the FS2004 Options/Controls/Sensitivities/Joystick/Advanced and checked the settings of your yoke and pedals. First make sure that your devices are listed at all. The sensitivities of my yoke are halfway for ailerons and elevators, and all the way right for the throttle. The null zones are about 1/4 to the right for ailerons and elevators, and all the way left for throttle. Finally, try calibrating them using Options/Controls/Calibrate Joystick Hope this helps,

Filename and download location?

One good way to reset ATC is to go to the Map, change your heading by one degree, and click OK.

Another possibility is a corrupt magdec.bgl file. Have you replaced that at some point with an addon version?

If you are talking about the Real World weather download option built into FS9, there is no solution at the moment, because it appears it is happening to everyone and thus nothing you can do yourself. You'll just have to wait until it starts working again, if ever.

There is an old freeware version, FSrealWX Lite, which works if you keep the download distance below 150 NM. It can be downloaded from places like freedownloadmanager. Do a web search for "download" and the program name.

Thanks, Karol, I appreciate that. Manfred and I are working towards an FS2004 release of his Generic GCA which uses your Synthetic ILS. I'm sorry to hear that you are having computer problems and hope you are back up and running soon.

One more thing. The ILS localizer needle does not work properly in FS2004 - it only moves to the right. The reason is that the command rnor does not work properly in FS2004. If you cannot read what I wrote, the command name it is r n o r, which is supposed to normalize radian values. So here's the fix, and it's surprisingly easy. 1. Open the zzDAT37.xml file in a text editor. 2. Do a search for rnor 3. Replace rnor with rddg dnor dgrd Keep the spaces around the words. Karol actually did this in a number of other locations, but looks like he missed this one. I found this out on this old thread, thanks Rob! https://www.avsim.com/forums/topic/72598-xml-function-rnor-bug/ Hope this helps,

Seems to work for me in a quick test.

These are the other problem variables I can find. I do not know if they are needed or not, because I do not know what FSX is using as the "default" units for these variables in the original gauge. I am assuming that the (L:ApprOffsetDistance) variable uses nmiles as units, since none of them have units in the original gauge. Note that I do not know if the gauge will work with these changes - it might rely on these errors. :) (L:MkReciprocal) to (L:MkReciprocal,enum) (L:ApprOffsetDistance) to (L:ApprOffsetDistance,nmiles) (more than one) (L:OffsetDistance) to (L:OffsetDistance,nmiles) (more than one) Hope this helps,

Hi all, I have found why you cannot select a runway end in FS2004 - the L: variables are missing units. BACKUP the zzDAT37.xml file by copying and pasting it back into the same folder. 1. Open zzDAT37.xml in any text editor. 2. Do a search for RwyEndSelect 3. If you find this: (L:RwyEndSelect) change it to this: (L:RwyEndSelect,enum) There are 4 places that need to be changed. Don't change any other variation. Save the file - you won't be able to if you have FS running and that panel loaded - choose another plane that doesn't load that gauge before saving. After that you can select the runway end. There are a few other L: variables that Karol left off the units from, see below.

When you purchased EZ Landmark you should have received a support email address. Email that or the main Abacus email address.

The assignments have occasionally reverted to default for me as well, but only quite rarely. I don't know why it happens. I do not have a plane that does this, though.

I would suggest the C-47 by Manfred Jahn as the best model for FS9. https://www.flightsim.com/vbfs/fslib.php?searchid=64466693 I also suggest replacement flight dynamics from DC-3 Airways. Scroll down to the FS2004 section: http://www.dc3airways.com/our_fleet/dc3_fleet.htm Hope this helps,

Hi, I didn't realize those search links were session specific. Just do a search here for: sidney schwartz update and that will list the 3 texture updates that fix many of the blurries issues. And there are a couple more done by someone else; I don't know if these have overlap with the first three. Do a search for: sidney schwarz Hope this helps,

Some files to investigate: https://www.flightsim.com/vbfs/fslib.php?searchid=58643043 https://www.flightsim.com/vbfs/fslib.php?searchid=58643167

Crashes due to ground textures might be due to lack of mipmaps, other than that I don't know. I know that a missing custom terrain texture, or one not in DXT1 format with mipmaps can cause a crash. DXTBmp can convert a DXT file into a 24 bit image, and then any paint program can reduce that to 256 colors.

We have found that sometimes it can be a bad texture file (typically of a library object) that can cause this as well. Typically, if you spin around in slew mode and suddenly the ground textures blur out, the object with the bad texture has just appeared on your screen. I can usually get things to sharpen up again by going to full screen mode and then back to windowed mode. But as soon as that object appears again on the screen, back to blurry. We have also found that a common problem is small textures (smaller than 64x64 pixels, but I'm not sure of the actual threshold) in DXT format can cause these problems. Converting this small texture file to 256 colors (usually not a problem for such small textures) cures this. Hope this helps,

http://simviation.com/hjg/downloads.htm Scroll down to the panel links. Hope this helps,

And don't forget that in System 7 and later when you use Add Area to add a new scenery layer, after clicking OK you have to click in the white area of the box remaining on the screen for the box to clear and the scenery area to be added.