I just use the ILS function by being in NAV mode and pressing 1 on my keyboard to bring up the crosshairs. Pete, I do not use the flight planner for an ILS. If a runway has an ILS at each end then unique identifiers would have to be assigned. For example, the ILS at Batumi might have an identifier such as IBAT (In the real world, this is how ILS are identified e.g the identifier for Runway 28L in KSFO, is ISFO). Implement a unique identifier for each ILS which displays on the HUD. For aircraft where it is not possible to tune an ILS frquency and set a front course (such as the F-15C), then perhaps a Navigation Menu should be implemented so that you can select the airport, then select the runway and then the ILS for that runway.ģ. This is the standard real world implementation.Ģ. Survey all ILS serving all runways in DCS and ensure that their glideslope is 3 degrees, the GPI (glideslope point of intercept) is 1000 feet from the threshold and the TCH (threshold crossing height) is 50 feet. This is a suggestion on how the ILS implementation might be improved in the Flaming Cliffs F-15 and other aircraft where an ILS frequency cannot be tuned on an ILS receiver.ġ. F-15 landing-No Saitek Rudders - W key k F-15 landing-With Saitek k My current rudder axis setting is attached to the first post on this thread. As you can see directional control is very difficult. The nosewheel steering is not deflected either. On landing, I apply brakes using the toe brakes and try to keep the aircraft straight with rudder. The second track is with the Saitek Combat rudder pedals plugged in. If you bring up the control inputs display with RCtrl+Enter you can see there are no rudder or aileron inputs on the rollout and brakes are applied symmetrically. As you can see with only the brakes applied and no rudder input the aircraft veers off to the left and off the runway with only the W key pressed. On landing, I apply brakes using the W key only with no rudder inputs at all. The first track is with the Saitek Combat rudder pedals unplugged. Here are two tracks which illustrate the problem using DCS 1.5.2 The Mirage does not exhibit this problem under identical conditions. From these tests I can conclude there is something in the F15 which either applies asymmetrical braking or some other type of lateral input which causes the divergence. If you watch the control inputs on roll out (Right Ctrl+Enter), when you press and hold the W key, both brakes are applied in a symmetrical fashion and there is no rudder input at all.Ĥ. Veer from centreline at about 100 knots and off the runway into the dirt.ģ. F15, landing on centreline - nosewheel on at about 135 knots. Dead straight and does not veer from centreline.Ģ. Mirage, landing on centreline - nosewheel on at about 135 knots. Used the W key for brakes which applies brakes perfectly symmetrically (this is an assumption on my part) on both wheels (Right Ctrl+Enter to verify brake application)ġ. Mirage 2000 and F15, both landing at Groom.ģ. No wind or cloud or turbulence in mission.Ģ. Questions about SimConnect can be posted in the SimConnect forum.Īny other question that is not specific to an aspect of development or tool can be posted in the General chat forum.īy following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.OK, so I disconnected my rudder pedals and did some tests:ġ. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |