flyco

Sounds like the sea-water is shorting something out in your PC.

Rad Alt shows height, not altitude. It may be OK for landing on a carrier or a perfectly flat plain, but not for normal approaches.

In and out of DCS. Very erratic and exagerated movements in both Windows control panel, in DCS Controls and while flying.

Thanks Sokol1, we are thinking along the same lines. Tthe only cause that I could think of for these symptoms is a faulty Hall sensor and magnet interaction. I just thought I would see if anyone had any other ideas before I dismantled the thing again.

I have a problem with my Warthog Thrustmaster Joystick. It began very shortly after I had replaced the main spring. All of the buttons operate OK, but the axis are very unstable. Any movement causes wild fluctuations in the axes outputs. The three possible sources as I see it are: a fault in the main board; an intermittent connection (possibly a damaged wire); or a displaced axes sensor. Before I either order a new board, or strip the stick down further to check on the wiring and axes sensor/magnet etc, I would welcome input from those more familiar with the device than I am. Can anyone throw any light on the most likely problem, or problems?

During the ME set-up, the JTAC reports that the target is in laser range and direct line of sight, when the target is assigned - in fact it won't let you select Laser unless it can. I also physically check that the JTAC can see the target, and that the range is less than 5 nm. Yes the JATAC does report Type 3 in my Mission, and Type 2 in the DCS Training Mission, but I do not know why.

Thank you both for your input. As I say The JTAC set-up is identical to that in the DCS Maverick-E Training Mission (other than names and frequencies, and I have added Invisible and Immortal) I have tried removing HARM from my mission, leaving just Cannon and Mav-E. The WEAPON is "Auto", and the Designation is "Laser", exactly as in the training mission. On contact the JTAC requests use of Maverick, but there is no option to request LASER ON. I am at a loss to understand it.

I am trying to use a Mav-E from the Hornet with a JTAC. I have copied the details from the ED practice mission to my mission. However, when I contact JTAC he gives me type 3 as opposed to a type 2 mission, which does not allow me to get Laser marking. The Hornet is loaded with HARM, Mav-E, and Cannon. The target is a Tunguska. Is the JTAC expecting me to use HARM first?

Why not put up two AWACs, operating on different frequencies. Since we don’t pay for the airframe hours or fuel, there is nothing to lose.

You need to set the Tanker speed according to the height it is at. I generally set the Tanker for the F/A-18 to cruise at around 250 kias. To get this set the Speed in the Mission Editor as follows: 30,000 ft. 400 Kts. - a bit too high for my comfort 25,000 ft. 375 kts. 20,000 ft. 350 kts 15,000 ft. 325 kts 10,000 ft. 300 kts For intermediate heights, change it by 5 kts per 1000 ft.

CG was only a problem when, while flying a simulated hydraulic failure in ‘manual’, you retracted the gear while overshooting - very exciting. Everyone who ever flew the Gnat will know what I mean and at least 99% of those will have done it!

The physics insists that there is a push if you move the basket in from its neutral position, and a pull if you move it out. I suspect that it is going to be only a few pounds, but it must exist, otherwise there would be nothing stopping it moving back and forth of its own volition. When trailing there is drag trying to extend it, balanced by a mechanical pull from the hose mechanism itself, trying to retract it.

Ah - happy days! I can still remember my first take-off, sitting in the front seat of a Gnat at RAF Valley. It was as though I was crammed into a goldfish bowl, and I clearly remember thinking “I am never going to be able to fly this”. Fortunately I did. Low level in the Welsh mountains was exhilarating!

I would support this suggestion. I routinely modded my .lua files to allow a simple On-Off switch to react in both directions. Unfortunately these are not universal, and because they are often updated as modules develop they need frequent changes.

So far as I could see, the probe and boom were touching, rather than ‘plugged in’ but there was some force holding them together.

Just found that you can refuel from a standard KC-130 (i.e. the one without drogues). Just position yourself at the appropriate spot under the boom, call 'Ready Contact', and the operator will plug in and fuel will flow. I was amazed - I was just testing all the tanker in our group's mission, when lo and behold! It's a lot easier that chasing that drogue off the wingtip. P.S don't tell DCS they may 'fix' it.

Probably best not to bomb while you're inverted then!

Yes and yes. The vortices are well outside the wingtips, and you can refuel from it.

Does anyone know of a simple guide to optimum height, speed and fuel usage for use when planning for different AI aircraft. Obviously those aircraft that I possess I can get reasonable estimates for, but when inserting an unknown aircraft in a mission any suggestions for how to chose a speed and estimate a range or endurance?

A very clear and concise one-pager. The only points I would make are: 1. Since the flight deck is at 9 degrees to the carrier's fore-and-aft line, should not the finals turn be started at 9 degrees past the beam? 2. I am not sure what the 290' marking at the threshold represents. 3. (I hesitate to put this one) the heights are given as agl. All very minor quibbles, I know. And thanks - a copy will go in my 'Info Folder'

It is possible to 'feel' the click, through the fingers, which is I suspect interpreted by the sensory system as a click.

Some months ago, I gave up using my switch driven USB input controllers, because of their randomly re-initialising during sorties. I had used them successfully for some months prior to this problem arising. At the time there was quite a lot of discussion in the Forum, with others experiencing very similar problems to those I had met. However, now I find that this problem has now disappeared. Does anyone know whether ED have changed the coding to remove this problem. It would be useful to know before I fully restore my cockpit with its many hard switches.

Very true, Druid When I did my RAF low-level training the rule of thumb was that at 250 ft you could see individual legs on the sheep. Solo students were allowed down to only 500 ft, where it was claimed that you could make out cow’s legs. When flying dual, a remark from the QFI, that he could see the rabbit’s legs was an indication that you were too low. As if I had time to look at animal feet at low level!!!

What would be useful, would be the ability, in the F-18, to reproduce the aircraft side-number on the instrument panel. I can usually remember my name and even my Callsign, but regularly have to refer to external view prior to rejoining for a Carrier approach.

Previously a Tunguska could only get up to 20,000ft, making knocking them out with an A-10 from 22,000ft+ fairly simple. However, suddenly they are lethal up to at least 23,000 ft. Is anyone experiencing the same, and does anyone know why?