IvanK

Just did some testing on Diskey's findings. Basically if you select the first digit as "T" it then allows you to tune any VOR or ILS station ...i.e any VHF navaid. the "T" representing the first digit as a 1. So tune whatever VOR or ILS you want then select the UHF selector to DF and the Nav selector lower down to DF and the HSI bearing pointer will give you mag bearing to the tuned VOR or ILS localiser station. No DME is available but bearing is. So in addition to the VOR stations Diskey labelled the following ILS stations are tuneable as well: ILS LOCALISERS Kutasi 109.75 Koblutei 111.50 Batumi 110.3 Min Vody 111.7 and 109.3 Nachlik 110.5 Beslan 110.5 Tiblisi (Lochini) 110.3 and 108.75 Tiblisi Vaziani 108.9 and 108.75 Great little "Easter egg" Now to play around with the "A" setting to see if it allows certain NDB's

The T and A positions are IRL I believe associated with HAVE QUICK and setting it up with the the cyphers etc. Not sure it should be working the way you describe but great find. :) The 2 and 3 are there just to select the first digit which in the UHF band can only be a 2 or a 3 .... for like 234Mhz and 305Mhz

Some detail from the Navy F5EN manual on "null tone" :

Interesting looking at the USAF Weapons Manual and the NAVY F5EN manual it says within limits that after radar lock the Missile Pipper is aligned with the radar line of site to indicate relative Target position ... pseudo TD box. We see this in game if locked from a manual lock. However if locked from DM mode the pipper remains in the centre of the reticle. I think it should again move to indicate radar LOS.

Though that inherently isn't as accurate as aligning on precise parking co ordinates.

A follow up from the USAF fighter weapons Review just 12 months later. very F4 Centric but discussion on the Very low amount smoke with the P and a change of thought on the cage versus uncage. The term "Combat Sage" refers to a USAF PACAF missile exploitation study/program

Easy its straight Trigonometry for your dive angle. I practiced by calculating the required Base Distance out (Allowing for both Turn radius and Aim Of Distance). Then in the Editor set a line of ships at exactly that distance out ahead of me on the base leg. This then ensured getting the correct dive angle. Whilst you are practicing notice where the target sits ref the canopy rail. You can then use this cur to help out on random targets.

Biggest Issue is Altimeter Lag. Using the Weapon manual to calculate depression works well in in the SIM IF you allow for the excessive Altimeter lag. Its around 300ft for 10-20 deg Dive angles and 410feet for 45 deg angles. Should only be in the order of 80-110ft. So say you are working out a 20deg Dive angle pass with a release altitude of 2500ft. work out the numbers for this then when you fly you need to pickle at 2800ft Indicated which results in a 2500ft Actual release altitude. ... there is quite a thread on this subject.

Great that there is some variation in Chem trails .... dont forget Coriolis as a factor.... Of course we know those nasty Chemtrailers turn them on and off at will !

Yes just a humble Gunsight

Interesting article from 1982 USAF Fighter Weapons Newsletter. Just posting here for interest

No not usually. In Fighter to Fighter A/A Tac use you get Distance only even with T/R. Some Airborne aircraft (Tankers) can if fitted also provide bearing. In General A/A TACAN only provides Distance

Spread is IMO excessive (same in F15). The Spec calls dispersion on the F5E gun system to be 8 mills. By inspection of Ground impacts in game it looks a whole lot larger than that. Even just watching the tracer versus reticle size its also evident. Reticle is 50mil diameter.

Runway Lighting logic is daft in DCS. Some airfields have Taxiway lighting on all the time with Rwy lighting off ! Certainly for Civil airfields Runway lighting should be ON during hours of Darkness. For Major airfields (even if subject to night curfew ops) it is an International requirement. In Daylight it should also be on as a function of Visibility. Anything below 1200m Viz should imo result in Runway lighting coming on regardless of Day or Night Ops. In addition there should be a means for player to ask for Runway lighting on at any time. In some night combat scenarios its logical to not have Runway lighting on all the time ... just when requested.

http://forums.eagle.ru/showthread.php?t=170967

Trying to Set up some Simple 1V1 type scenarios. Is there a way to have The player start with all Combat switches made? Specfically I want to start in the F5E with the Chaff and flare switches in the On position. At present you spawn with them off.

The specific F5E they chose to model dosent have VOR/ILS but many F5E in service are VOR/ILS equipped.

Either way the issue is a biggie that severely limits the F5E handling post missile launch. The fact that a similar issue exists with the Mirage2000C points to a fundamental FM type issue rather than a specific airframe type issue. Devs need to take a look at this. Both types can then benefit from the fix.

Ok once you apply the AOA correction I get 101mils . The end game AOA correction being -7 mils. (Chart A 20mils + Chart B 8mills - 35Mils correction). Anyway the single biggest error I believe is that caused by the huge (bugged) altimeter lag we are seeing.

Dont know but it works the way I described .... there is a test mission file around that lets you test it.

Looks pretty neat. ? note 1 are you are saying you need to -35mills correction to the displayed value ? So in the case of the MK82 45 deg pass 7000ft release at 500KIAS your chart value is 108mils ... is this sight setting or requires further correction ... like taking 35mills off to give a setting of 73mills. I recrunched all my 3 standard pass numbers. For the same 45 deg pass My Sight setting is 101mills but releasing at 7400ft as there is around 400ft alt lag at the moment.

Could be as its prevalent on the Mir2000C as well. The F5E becomes operationally limited from a handling point of view with just 1 x AIM9. Something somewhere is wrong.

After firing one AIM9 there is a significant roll couple that I believe is overdone. I dont believe the F5E should instantly become the handful it is as soon as one AIM9 is fired. Searching through the various manuals confirms my suspicion. The top refrence from the USN nATOPS for the F5N. The lower section from the USAF F5E Dash 1 Note the manuals say that the the Rudder and Aileron trim requirements are negligible. That certainly isn't the case aileron trim wise in the Belsimtek F5E

The single biggest error imo is caused by Altimeter lag. In the Belsimtek F5E it is around 3 x that of the aircraft. Using Book figures from the weapons manual and adding 300' of Alt lag works for 10Deg High Drag passes, 20 degree Low Drag passes. For 45 deg Low Drag passes using 400' Alt lag works.