MrExplosion

Because there is often a misunderstanding about the usage of AFN-2 I have attached this PDF. For simple direction finding AFN-2 could be used in conjunction with FuG16ZY. Frequency band for FuG16 is 38-42 MHz. But for bad weather approaches AFN-2 was the display device for FuG125. This also required a different antenna than what we have modeled in DCS. Frequency band for FuG125 is 30-33 MHz. Quote from https://en.wikipedia.org/wiki/Luftwaffe_radio_equipment_of_World_War_II Hope this helps clear up the topic. Führungs-und-Navigationsverfahren_Januar45.pdf

But ILS should not be working. It should be purely direction finding and we need the proper beacons usable in ME.

The AFN-2 is a display device that can take input from a variety of sources. The German warbirds have a FuG16ZY radio built in. The Z in the name stands for Zielflug, roughly translatable to direction finding. So in our warbirds the device was used to home in on a beacon and find your airfield that way. The AFN-2 was also used as a display device for an early ILS but for that to work it required different radio to supply the input to the AFN-2 and that radio was only used in warbirds specially outfitted for bad weather ops. Our warbirds in DCS don't have that radio as you can tell by the missing antennas on the model as well. It is possible right now to place ILS beacons by editing some LUA files or by flying on maps that supply the ILS beacons and get the AFN-2 working for the ILS approach. It SHOULD be possible though, to place a FuG16Z beacon unit in the mission editor and home in on that with the AFN-2.

I hope the delay for the patch scheduled today is due to this bug finally making it to the top of the prio listing.

No, it doesn't. The AFN-2 is a display device that can take input from a variety of sources. The German warbirds have a FuG16ZY radio built in. The Z in the name stands for Zielflug, roughly translatable to direction finding. So in our warbirds the device was used to home in on a beacon and find your airfield that way. The AFN-2 was also used as a display device for an early ILS but for that to work it required different radio to supply the input to the AFN-2 and that radio was only used in warbirds specially outfitted for bad weather ops. Our warbirds in DCS don't have that radio as you can tell by the missing antennas on the model as well. It is possible right now to place ILS beacons by editing some LUA files and get the AFN-2 working for the ILS approach. It SHOULD be possible though, to place a FuG16Z beacon unit in the mission editor and home in on that with the AFN-2.

Can I WSO in an F14 or F4 if I am out of lives? Will I loose lives if I WSO and the pilot f*cks it up?^^

Open: \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-4E\Input\F-4E-Pilot\keyboard\default.lua Add the following lines below this comment at the top of the file and you can bind Aspect and Radar mode to your Hotas. Disable Jester via the normal menu and you are good to go. (WSO binds until Jester is better) knob('[WSO] Target Aspect', { 'Tail', 'Aft', 'Forward', 'Nose', 'Wide' }, nil, device_commands.RADAR_WSO_ASPECT_KNOB, device_commands.RADAR_WSO_ASPECT_KNOB_INC_DEC, device_commands.RADAR_WSO_ASPECT_KNOB_NEXT, device_commands.RADAR_WSO_ASPECT_KNOB_AXIS, bind_templates.radar_panel(), { category = categories.wso_temp }), knob('[WSO] Radar Mode', { 'BST', 'Radar', 'Map', 'Air-Ground', 'Beacon', 'TV' }, nil, device_commands.RADAR_Mode_Knob_RIO, device_commands.RADAR_Mode_Knob_RIO_INC_DEC, device_commands.RADAR_Mode_Knob_RIO_NEXT, device_commands.RADAR_Mode_Knob_RIO_AXIS, bind_templates.radar_panel(), { category = categories.wso_temp }),

Allied Propaganda confirmed.

It's not that easy by far. 150 Octane wasn't used as widely as you think.

Thank you for summarizing the current status quo. Great job! As long as there are no known cheats that evil minded users could employ to take advantage of gunsight mods being excluded from IC I am all for trying this!

Pls also check for the Anton. It's broken there as well, even tho I dont have a track rn. Thx

Yes, I just wonder if damage dealt is realistically modelled. Germans kept that ammo throughout the war, so if ballistics was bad they probably had other reasons to use it.

You can check page 8 and following to get detailed measurements of velocity / kinetic energy at different distances and compare that to the in game results. Handbuch der Flugzeug Bordwaffenmunition 1936-1945.pdf

Yes, on Saturdays every 2 weeks usually. Join the discord to keep updated.

You don't even realize it is totally necessary to "block this behind IC"? Spotting is a skill. Trying to level the ground for all resolutions is a good thing per se, but this script just takes all the skill out of it.

Tested this yesterday on VR with my G2 headset. Imo it looks terrible - contacts render as giant bricks and will stay bricks until really close, making it impossible to ID. Also take all the skill out of spotting. Pls add this to IC asap.

Why would you make the FuG16 optional? What would it have instead?

Stunning work mate! Can't wait to use it

Sorry, misunderstood your initial question. Main difference between mV and Vz: mV is designed to detonate the bomb really shortly after impact - basically while it is still in motion (up to 0.5 seconds of delay) and Vz is used for a longer delay of 20 seconds or longer. These are the basic definitions. I am not familiar with all the details involved tho. If you want to know more you can read the original documentation here: http://michaelhiske.de/Wehrmacht/Luft/Luft/LDV_4200/SERIE_1/Blatt_04_1943.HTM

In general you would use m.V. setting whenever you dont want the bomb to detonate directly upon impact but a little bit later. For example a SC 50 with Zünder 15 in m.V. would detonate 0,05 seconds after impact on a 4-story building making it detonate in the basement rendering the whole building unusable.

Thanks for providing this. I hope Ugra will put in the necessary changes to correctly model Luftwaffe airfield lightings. The document you provided updated Sicherheitsbefehl Nr. 10 from January '42 and was then further updated in Taktischer Einzelhinweis Nr. 17 in May '44. I provided the Sicherheitsbefehl Nr. 10 for download here and will also be able to provide Taktischer Einzelhinweis Nr. 17 by the end of the month. It would be great if Ugra could provide a means for mission devs to turn the lights on or off via scripting. So @MAESTR0pls get in touch so we can get night lighting in correctly. I would greatly appreciate. SicherheitsbefehlNr10.pdf

Do you have a contact who I can message daily to get some priority onto these plans?

Nice skins! Hope someone from ED reads this and makes this happen