VOZzer

Hi everyone,I have a full version of VoxATC 6, running on Windows 7 64-Bit (FSX SP2).My problems are:1.) At East Midlands, after getting ATIS information, etc, I contact ground and tell them of my VFR flight intentions (with a flight plan loaded). After receiving my taxi instructions, (I'm told to taxi to "Runway 27 via Q and A"), nothing happens, even after acknowledging them. Interestingly, I'm not given a holding point, so naturally I assumed that I should taxi to the start of Runway 27 and hold. I am never transferred over to Tower even after I finish taxiing, nor do I get any sort of intelligible response from ATC after saying things like "G-LY, holding A runway 27 ready for departure". 2.) Speech Recognition. For some reason, to acknowledge an instruction, I must do the following:- Hold T down and speak, acknowledge the instruction- Release T(Nothing Happens)- Press T and immediately release TATC RespondPlease note, it is not a "stuck key" (it happens on all keyboards).IF anyone is wondering, the flight plan I'm using for all of these problems is a very simply VFR flight plan, EGNX -> Gamston via EGNE.Any help would be greatly appreciated.Cheers,VOZzer (Jack)

Right everyone, I have found the problem. I managed to pinpoint this issue to two pieces of scenery. Firstly, I downloaded some EGNF (Netherthorpe) Scenery awhile back. This was placed in my "addon-scenery" folder (it's the only entry in there at the moment). In FSX, when I enable/disable the "addon-scenery" entry in the Scenery Library, I toggle the glideslope problem on and off. Secondly, JustFlight's Traffic X seems to have some sort of play in this (cheers Jim!). Toggling "Traffic X Airport Facilities" on and off also toggles the glideslope/ILS capture issue. Therefore, it's EGNF and Traffic X that are the culprits. I have them disabled (for now) and everything is good. Cheers, VOZzer

Right, I can confirm that both 26L and 08R ILSs are present. Not only that, but they also have seperate identifiers and are correctly aligned with the runway. Clearly, it's not a file missing issue. The ILSs are definitely there. I absolutely cannot think what else is causing this issue.

Hiya CoolP, I have ADE, could you give me a quick guide on what to do? I have never really used it. What should I be looking for?

Hi CoolP, I get this problem all all ILS instrument equipped aircraft. It cannot just be the Level-D. Which files should I be looking at here?

Yeah it's UK2000 Gatwick. As I said though, it happened before I installed it too, so I doubt it's the scenery.

I can only get a singnal on 08R: The view from 27L is the same, but the only the Localiser ILS Magenta indicator appears. Also, the indicator that appears is for 08R, not 27L. I can summarise it like this: Landing 08R - Full ILS (Glideslope 08R + Localiser 08R) Landing 27L - Localiser Only (Localiser 08R) In other words, I can only ever get the signal for 08R. When I land on 27L, it only picks up half the signal for 08R. Cheers, VOZzer

Hiya CoolP, As I said, I know exactly how the RW ILS dual-frequencies work. I'm simply saying that no matter what, I can ONLY get a signal on ONE side of the ILS, no matter what. This makes landing on 27L quite difficult in IMC conditions. I'll prepare a screenshot...Cheers, VOZzer

Hi everyone, I am having severe issues with almost every runway that has the same ILS frequency on both sides. For example, at Gatwick, EGKK, the frequency is 110.90 on both sides. No matter what, I can ONLY ever get an ILS signal for 08R. Tuning 110.90 and CRS 260 for ILS26R will only result in the aircraft attempting to follow the ILS for 08R. This also happens at Heathrow EGLL. In other words, I can only get "one side of the ILS". I can confirm this because the ILS identifier is the same on both sides. After some Google searches, scenery seemed to be the issue. I had UK2000 Extreme Demo running at Gatwick, so I disabled that, and UTX, GEX, VFR Real Scenery... And so on, until I had disabled everything. No luck. In fact, I even recall having this issue before I installed half of the above scenery add-ons. Any help would be good. Cheers, VOZzer

Out of interest, what does wideviewaspect ACTUALLY do? Cheers Jan.

I think I tried this a few times, and it didn't seem to do anything (but all is fixed now so I can't really re-test).

Right! All fixed. For some reason, the 3072x768x32 resolution just suddenly appeared inside of FSX's display menu, from where it must be set (setting it in the .cfg file didn't work). To make a point, frequency can cause out of range errors; as my monitors won't work unless the frequency is set to 59Hz in the nVidia control panel, not 60Hz, it's just the way it works. I'd have to disagree about an "unstable system". It was custom built by Wired2Fire (an excellent company), and has worked fine for years. It runs everything I have with 75+ FPS, with the obvious exception of FSX (which I have now improved by running the 2D panel, which IMHO I currently prefer). It is perfectly, perfectly stable. Unstable implies frequent crashes, constant overheating temperatures; the first of which ONLY happens in the Matrox software and FSX (the latter of which is now 100% fixed). The Matrox software is just generally unreliable. It refuses to detect certain monitors when plugged into the Th2G box, it "sets" resolutions which it doesn't actually set (ie 3072x768 is actually 3084x1024). The software just generally crashes when I work through the GUI, sort've like FSX's alt-menu bar crashes; sudden and random. Thanks for all your help everyone, especially the advice regarding AA settings. I can now run AA at 16X, with ENB Mod, full Anisotropic filtering, and dense/very dense in the autogen settings, and get around 50FPS with my new setup. Cheers, VOZzer

Unfortunately, I cannot set up the Th2G from scratch, as the Matrox software doesn't work with my PC. It just crashes it every time.

Unfortunately; I have an even bigger problem now. I'm running two monitors: - One @ 1280x1024 (main monitor)- One @ 3072x768 (TH2G display) Basically, whilst all the monitors usually work fine, after entering full screen mode in FSX, all the monitors connected to the TH2G Unit give an "out of range" error. This problem is very recent, and has only surfaced today. There is an entry in my FSX.cfg file: [DISPLAY.Device.NVIDIA GeForce GTX 285.1]Mode=3072x768x32 Surely this has something to do with it? Also, there's also an entry in the FSX display options called "DISPLAY.Device.NVIDIA GeForce GTX 285.0". What's the difference between .0 and .1???

The PC is showing 6GB of installed RAM (as previously mentioned). I'll try disabling one, but it really isn't a suitable alternative to have one permanently disabled.