TXHills

To add a bit to the confusion is that it is my impression (and I am aware that my set-up - screen size and position, use of wide view aspect = true, zoom percentage, etc influences what I see) is that compared to my RW perspective when I am on the visual GS (determined by PAPI, VASI, whatever) according to the sim it is not look quite right compared to what looks right based on my RW perspective. I have always attributed this to how things in a 2D world trying to mimic a 3D world end up looking but maybe you have discovered a more fundamental flaw that explains this incongruity. None the less I have always found it pretty amazing that $30 worth of software replicates the experience to the point that it is at least an enjoyable diversion - and precise or not, replicates to a great extent the real thing in spite of some aspects possibly being a bit skewed. I have always had the same VASI vs electronic GS difference and have updates turned off (now on Windows 8 and had already gotten the word that auto-updates were messing things up so never had updates turned on and never load updates). This has been true for my first (XP) sim computer, current systems running Windows 7 and now my (never updated) Win8 setup. Still seems odd that there was a change for you. Something else you did in those two weeks between then and now?

Well this is interesting. The first set of screen shots are what I am used to seeing - at my home (major) airport KSAT, the most-used Rwy 12R. As titled, they are On the PAPI, One Red above the PAPI and On the Electronic glide slope (all white on the PAPI). Exactly as I expected - see the approach plate which shows the visual and electronic glide slopes are not coincidental. http://skyvector.com/files/tpp/1312/pdf/00369IL12R.PDF Yesterday I was flying "Foggy Friday" at EasternHops (http://easternhops.com/ - fly with them sometime, they're good fun and Foggy Friday makes for some challenging landings - you don't have to fly with the group; the whole world is fogged in on their server on Fridays) and we landed at KBOS - where the approach plate shows that the visual and electronic glide slopes are not coincidental (http://skyvector.com/files/tpp/1312/pdf/00058IL22L.PDF) BUT - on approach you can see that there is almost perfect agreement. Displaced threshold, but this should have nothing to do with it since the touchdown points differ and are measured from the displaced threshold. THEN - off to KORD where Rwy 27R does not show a difference between the visual and electronic glide slopes (http://skyvector.com/files/tpp/1312/pdf/00166IL27R.PDF) but the pictures attached do - one showing on the PAPI, the other showing on the electronic GS. So in conclusion I guess, as amazed as the world might be about the revelation - Microsoft has not been completely accurate in depicting airports and their approaches - wow! Might there be other issues yet to be revealed with FSX?? None the less, I guess this shows that in some cases FSX does show you on the electronic glide slop but not on the visual glide slope - be that correct or not.

I'll give it a shot - guess after all these years I'm going to have to learn how to use the slew function in FSX :blink:

In my experience the glide slope puts you farther down the runway (therefore, is above the visual glide slope indicator glide slope) in FSX, consistent with most RW approaches. Not sure why you did not experience this before. I hand-fly my approaches and so I have had plenty of opportunity to see where I am with respect to the visual glide slope indicator system (PAPI, VASI, the occasional PVASI) - a good sampling of being on, above and below the electronic glide slope :rolleyes: . If you're flying by the rules (for commercial carriers, at least) then you are required to be at or above the glide slope in use. So - for the electronic glide slope you need to be at or above the center of the glide slope; for the visual, two red / two white (or the equivalent) or higher. However, once at minimums on the electronic glide slope - or presumably once you have visual contact with the runway (RW commercial carrier pilots please feel free to chime in on the opinion of a private pilot) you can revert to the visual guidance system and drop below the electronic glide slope as long as you are on or above the visual system glide slope. Back to your point - I believe you are now seeing things as you should. Not sure why this was not the case before.

We now have an updated version of Numpad Control - this one includes a script for entering speed for those aircraft equipped with an auto-throttle. Speeds can be entered as IAS or Mach number. The files are available here - http://www.mediafire.com/?b2oj1qm5at3b18i Numpad Control (NpC) allows you to control Com, Nav, ADF, Transponder, OBS and Autopilot settings in FSX using the keyboard number pad. Most entered values, such as radio frequencies, appear directly on the radio display as the digits are entered. No more 'fumbling with the mouse' to try to tune your radios, set you autopilot or your OBS heading. NpC requires a licensed version of FSUIPC4 and a keyboard equipped with a number pad. The zip file, NpC_v1.1.zip, contains 12 NpC LUA scripts, an instruction manual for configuring FSUIPC and a quick reference guide.

I have experimented with this (but only a little) - used FSRecorder to record the flight then used ezvid (http://www.ezvid.com/) to make the video and upload it to YouTube - the nice thing about this combination is that FSRecorder records the flight as an FSX flight (only viewable in FSX) but when you play it back (for recording for general viewing) the recorder (ezvid, in my case) records what you do during the playback phase. So - you can make the flight and then while playing it back you can show specific things, get specific views (I have TrackIR and the views you get are what you see on playback, so I can for example look out the side window and get that view during playback without the need to do that while I'm trying to fly the aircraft - same is true with outside views, tower views, etc). Here's my first attempt at this - a simple ILS approach (no narration at this point, just playing with the video part) - http://www.youtube.com/watch?v=G-JX4aobGx0&feature=em-upload_owner

We are interested to learn if / how well this works in non-default aircraft. Any feedback would be greatly appreciated.

Expanding on the GREAT work dazz did - here is a set of scripts that do some of the things being asked For Coms, Navs, ADF and transponder the codes appear in the radio display (not on the ribbon banner at the top) as they are entered Autopilot entry funcitions available - Altitude, vertical speed, heading (these do not appear until the entry is complete) OBS heading set (OBS1 and OBS2 available). Note that the heading bug is set using the heading set function associated with the autopilot Here's the link - http://www.mediafire...b2oj1qm5at3b18i Here's the Forum post regarding this - http://forum.avsim.net/topic/423405-setting-fsx-radios-obss-and-autopilot-using-the-keyboard-numberpad/

If you want to do this trough FSUIPC - see the configuration below. Click the key you want to use as your push to talk key, check 'Select for FS control' and other settings a shown below. I (successfully) configured the same button that does this as a compound button as I described earlier - in Mode 1 FSUIPC sends the Caps Lock key which activates TeamSpeak (I have TeamSpeak set to use the Caps Lock key as the PTT key so if FSX is not running I can still talk over TS by physically pushing Caps Lock. In Mode 2 FSUIPC controls in-plane radios via the settings shown here.

You can do it either way. I use the red button on the right side of the Saitek yoke to key the mic and have this set up through FSUIPC to send the talk signal to TeamSpeak (used by VATSIM indirectly, VFR Prop Hops and EasternHops among others as the primary online communication). Currently in FSX I have the radio keyed to transmit using the Tab key (and stop transmitting on release of the key) but by tomorrow I will have this set up through FSUIPC using compound programming so I can use the same yoke button for TeamSpeak (Mode switch on the yoke set to Mode 1) and in-plane radios (Mode switch set to Mode 2). The simple thing to start with is to go to FSX Buttons/Keys configuration (in the Multiplayer set - select with the drop down at the top of the screen) and set the keyboard key or controller button you want in the Start Transmit (or something to that effect) line and then do the same key/button for the Stop Transmit line where you will need to check the 'on button release' checkbox. BTW - is your FSUIPC a licensed version?

Working well - and a $5 tablet stand puts the keyboard at a good angle for easy access. Keyboard labeling not very fancy but effective.

Glad you found the offending device! One suggestion that I have seen related to this 'random assignment' problem is to copy your fsx.cfg file and save it as a back-up (something like fsx-cfg_yyyy-mm-dd.BAK so you know the date of the last saved it). Then, if things start acting weird you can simply delete the current fsx.cfg and copy the most recent back-up and rename it fsx.cfg. The problem with this is that you need to be diligent in updating your backup copy so that it has the most current configuration changes - but it is a valid suggestion and doesn't hurt to make the backup copy - you can decide if it is new enough to use or go through the steps of fixing whatever went awry depending on what, if any changes you might have made in the interim.

Agree Yep - seems to happen more often in Windows 8 (anecdotal reports). Check your Controls configuration - and be sure to check things that you think would NEVER have anything to do with the throttle (like yoke, joystick, rudder pedals) as weird and mysterious mapping of things that make absolutely no sense do occur - one of my favorites: Ailerons mapped to the throttle - makes for some very interesting take-offs. Is this new? (I assume so by the way your original post was phrased). Did you do anything between the time it worked and the time it stopped working correctly (add-ons, etc)?

I believe VATSIM also uses SquawkBox - but not sure if other servers do. FSCloud has a connection in "pre-Beta" that is acutually pretty slick - very simple to use, no 'sign up' (just give yourself you own name/handle and call sign) and you're on. Runs in 'Free Flight' mode like FSInn - but only capable of connecting to the FSCloud server. But, if you're looking to fly with other folks (especially those that don't what the hassle of FSInn) then this might be one solution. Does not support helicopters (yet). http://fscloud.net/

I checked the VATSIM site - nothing terribly new regarding this. One post from a couple of years ago might give you some ideas - http://forums.vatsim.net/viewtopic.php?f=43&t=59677 Likely that you have the new version of FSUIPC but just to be sure I thought I would mention it. Revo Uninstaller then re-install per http://forums.vatsim.net/viewtopic.php?t=20466 might work.

See http://forum.avsim.net/topic/417981-determining-active-runway/ for further discussion on the topic

I was going to add a caveat about that but there has been so much 'she knows, who said' (or some other mixed phrasing like that) that I decided to stay out of it. Has the jury come back on this? Seems like things change but I cannot say it is the truly up to date weather (maybe Microsoft is randomly generating old, stored weather :mad: )

Go to Weather at the opening screen or World | Weather from the menu bar and click 'Real-world weather (updated every 15 minutes)

This topic got my attention because I was unaware that TrackIR affected frame rates - well, I'm not a perfect idiot (no one is perfect) - I understand why it could but I was unaware that there was anything noticeable. So - yesterday I paid attention to my frame rates for a while (usually don't since I reliably get 32.2 to 32.9 locked at 33) - and low and behold I might have noticed a drop to ~ 31.5 if I moved my head quickly. The usual (instrument) scanning head movements did nothing. Looking out the side window seemed to make the most difference, causing a drop a couple of tenths below my usual. And, like Dan George, I usually stay out of the FPS discussions except to post that I basically ignore my frame rates and occasionally add that I locked mine at 33 because otherwise rates bounced around between 25 and 80 - and caused stutters- or should I say 'lack of smoothness'. The same philosophy as Henry and Antoine expressed. Somewhere I read from one of the Gurus of enhancing FSX performance (? *******) that the biggest performance killer was the user themselves and all of their add-on scenery and other goodies. I use REX because it enhances the weather effects and textures - weather being an important part of flying, fancy buildings etc. being not so important.

I cannot find anything about scroll wheel acceleration in the FSUIPC documents. Perhaps you can adjust this through your Windows mouse control panel. A friend of mine found a set of Lua scripts for FSUIPC that allows you to enter the frequency directly into Navs and Coms using the number pad on your keyboard. This is the original set of scripts he found: https://dl.dropboxusercontent.com/u/50535801/NumPadRadios-Original.zip He has been working (successfully) on expanding this to add several (IMHO) very valuable features. We are testing these now and I am re-writing the original readme file so that all of the instructions are included. Nonetheless the original version works well and so if your setup includes a keyboard with a number pad you are welcome to try it. If it works (it does in the default FSX aircraft but has not been tested in add-ons) e-mail me directly at [email protected] and I will send the updated versions as soon as they are out of 'beta testing'. As an FYI - the updated version - Allows you to see the numbers sequentially as you enter them, on the radio display that have selected (the original version does not change the frequency until you have entered all of the numbers) Has the capability to enter the autopilot altitude, vertical speed (+ or -) and heading Has the capability to enter the OBS1 and OBS2 cursor / card direction (also sets the HSI needle for aircraft with an HSI vs. standard VOR head)

Virtual cockpit? Every aircraft? Windowed or full screen mode?

... and progresses in alphabetical order, so information yankee is newer than information whiskey. When you get your weather briefing you are told which version the weather is that you have received - this is the same regardless of the source (FSS, ATC, ATIS, etc). Like the ATIS information states at the end, you should always 'advise on initial contact you have information xxxxx'.

Oh yea - January 1970. I was going to join then but they said I couldn't - lottery # 251

What I want to know is how did Russell Davis join this forum 43 years 8 months and 17 days ago. Clever!!

There is a way to adjust the trim effectiveness in the aircraft.cfg file. I have made this adjustment in several aircraft because the trim is too sensitive (nose slightly down - go one tick nose up on the trim - now nose slightly up - on tick down - back to nose slightly down attitude - rinse, repeat). I make my trim effectiveness 0.5 or 0.6 in most cases - It sounds like your trim is OK when you set it but it is changing back (?to neutral) by itself? There is a hot key you can set in FSX to center the rudder or the aileron trim but none for the elevator so that would not be it. Is it possible you are hitting the keyboard keys for trim adjustment (Num 7 and Num 1 are the FSX defaults)?