Tarres

It would be great that these commands were added in the joystick Lua to make the warthog 2/3 positions switches work. File attached with some examples. bf-109 2pos.lua

Thanks! So the bug is only the “always clean” answer and the Wurzburg “no animation and lack of Fire Control ability”.

In the screenshots both radars are in “default/fixed position”. Both have arguments and implemented animations but for now both are “static”, only difference is that Wurzbug seems to work in full 360º for the IA planes as a EWR, or as a 360º EWR (ranges seem ok) for a Tactical Commander in F10.

I know that it’s not perfect, but if you use the system inside their freq. range and in ww2 maps, the system works better than before 2.7

AFN-2 is not designed to made IFR flights. It´s more of a kind of "early blind landing system" with a very short range. AFN-2 works within the frequencies of the FUG-16. ILS frequencies are outside the FUG-16 limits. AFN-2 must be set to one of the FUG-16 presets except "I" preset (I don´t know if Y fighter is modeled or WIP, so I avoid "I" preset for my tests). As you said, the Y system works with the "I" preset. This is not modeled for now. In the "I" preset you talk in the "I" preset but you don´t hear anything, because the answer is made though the "II" preset. For this resason The Y-Fighter is not the leader. Works for me. Attached mission file. Edit, on a side note, I think that the "yellow lamp indicator" wasn´t installed in the AFN-2 fitted on fighters. Edit 2: You can talk and receive AFN-2 indications with the switch in the Y ZF. YZF as IRL, preset "I" and YZF position, is not modeled. YZF provides indications for the afn2 in the 2, square and triangle positions. afn2 test caucasus.miz

The AFN-2 is a very short range system, is more a kind of “a very primitive blind landing system”. In the ME set the afn frequency coupled with the preset that you set to your home airfield. Later I will try to make some test with the power. The needle only moves when receive signal, so if used with an ATC freq, it only moves when the ATC is answering. Definitely the AFN mustn’t work with NDB, ILS or similar outside the freq band. This is a bug that remains in the modern maps. I will try later. Sorry for my English

Yes, in maps with ndb, and ils (modern maps) works as you said. I’ve only use warbirds with Channel and Normandy maps. So it works better than in pre 27/05

Yes, it seems that now works as the system sholud.

Update: After 27/5 patch, AFN2 works as intented in the Channel Map in the 109K and both 190.

Tested in The Channel map with an Opel Blitz broadcasting in the 38.75mhz. with ATC. When ATC answers, the AFN2 marks distance and bearing. AFN2 working as intented with the FUG16 set at "HOMING" in both tests.

Update: .- using a modern EWR works as intended for blue or red colaitions. Only bug is the information given to the german planes in Imperial. This is related to the WIP "German class" in the sounds lua file. .- using a german EWR (FREYA, with the rotation bug take into account) or EWR/FC (Wurzbug), answer is always: "CLEAN". Workarund for missions: use modern EWR. Due to the bug of the max range (120km instead of 400km) in the modern EWR, there is no Uber-EWR problem if you use the modern EWR for now.

This point seems solved in the 05/20/21 patch.

SS-1 TEL not reassuming route until R-17 impact. Attached mission. Two TEL´s: one shoots at near minimun range, second to nearly maximun range. Each TEL in different groups. Until the second R-17 impact (max range), neither of the MAZ reassume route. Time to "fold launch system and reassume" is the same. So it´s related to the time of flight of the R-17. Test1.miz

In english, the tooltips definitions for the SPU-9 are missing; the tooltip shows the definition code. In spanish, tooltips work as intended for the SPU-9 showing the description instead of the definition code. Image attached showing "Cockpit generic..." instead of "Main/backup Intercom Switch" like in the L-39

Yes. All of yours points are correct. I suspect that the lack of rotation is one of the points related to the "azimuth bug" in the Freya. The Würzbug doesn´t rotate BUT I see a clean 360º picture in the F10 with fog of war enabled. Setting an old caped EWR from LOMAC, the 55G6, it provides indications when you request picture. I suspect that the code for the German EWR are WIP, and for the Fire direction Wurzbug it´s for now only an EWR. We´ve got correct search ranges in the WW2 EWR (azimuth bug aside) but lack of "information as requested by the player", In the "modern" EWR, we´ve got caped search and detection ranges but provides information when you request it.

Forget to add that GCI always respond "Clean" when player request picture.

I think that the options related to these options in the ME are WIP: AFN-2: listening and distance working but no azimuth. Allied BS1206/A1271 not working. Thanks in advance.

Setting a Freya with a PU Maschinen33 facing north In Normandy, near the coastline so no obstructions in LOS. Heading 0. Range it´s OK, around 160km for an airplane traveling at 6000m/18000ft (B17G). Only detects airplanes in the 340-20 aziumth sector. No rotation. Seems that detection it´s on a fixed cone of around 35/40 degrees linked to the heading of the object. Wurzbug: seems to work 360º, with coorect range but without any animation. KduG40 fire direction works as intended with proper range and animation. Attached test files. Freya test.miz Freya and Wurzbung test.miz

Some beacons are defined in the beacons.lua in Hz instead of Mhz. Attached file with corrected frequencies. beacons.lua

+10000000

+1. Not only for the 39.

It has been reported in their mantishub. When the airplane reaches its designed “trimmed speed” at around 700-800 TAS, the SAU Recovery and Stab recovery work as designed. So yes, the problem is about the 0 pitch and the 0 m/s.

Try this: {down = device_commands.Button_14,cockpit_device_id = devices.RSBN_5,value_down = 0.0,up = device_commands.Button_14,cockpit_device_id = devices.RSBN_5, value_up = 0.1 ,name = _('RSBN Mode Switch - GLIDE PATH/NAVIGATION'),category = {_('RSBN-5 Control Panel'), _('Only Front Cockpit')}}, {down = device_commands.Button_14,cockpit_device_id = devices.RSBN_5,value_down = 0.2, up = device_commands.Button_14,cockpit_device_id = devices.RSBN_5, value_up = 0.1,name = _('RSBN Mode Switch - LANDING/NAVIGATION'),category = {_('RSBN-5 Control Panel'), _('Only Front Cockpit')}},

+1

Same here. It seems that the SAU RECOVERY, stabilizes the plane at 0º pitch, no at 0 m/s.