Redglyph

I've done a few tests including the two missions above, and it works fine now, I haven't had this issue since the 1.5.6.1340.230 update. Thanks! :)

Thanks for the tip! :) Just the edm file? I tried with the whole module and it works, but crashes with some features like the Sapphire radar. EDIT: Copying the edm file from beta is fine so far, flood lights are back and no problem. Thanks again!

Saw a similar post here, that may be the explanation. https://forums.eagle.ru/showthread.php?t=175255

DCS 2.0.5.1648.165 The red/white flood lights don't produce any light, even after this update (they do in 1.5.6), that's weird. Also, the red flood light knob turns the wrong way, but that's already reported in ticket #541.

So for you it's solved in 1.5.6? Strange... Are you sure?

Has this been reported? It's still the case in DCS 1.5.6.1340.230, which is probably an issue for everyone learning new aircraft, especially with foreign-labelled cockpits :)

I don't deny the Flogger was significant :) It's probably a bit of a psycho aircraft, for sure :D

Haha, can't believe this thread is back on the surface now, of all times. Go fly this Viggen, shoo! :D Anyway, on topic. At the risk of having a few flames, my personal opinion on the Mig-23 is that this was an awful aircraft on almost every level. It was unstable, unreliable, difficult to maintain and awkward to fight with. So definitely not this one. I have no idea on the Su-22. There's plenty of other interesting choices though, an F-117 would be something, so would be the F-4 (if that's not already in the works somewhere?). Or an F-16, which is dearly missed (even if supposedly planned for an uncertain future). Or, to stay on the continent, an Me-262!

There, a little update to fix some coordinates, and for the missing North Las Vegas - what would a Mig-21 do there, anyway? :D I'm a little divided on a few issues. The file only contains one entry for both RSBN and PRMG stations, which is not a huge deal, so what I did was - keep the first, already existing RSBN stations, even if their location seems a bit off (mainly the first channels around Las Vegas); - for the new ones (TTR for ex), I used the VORTAC, VOR/DME, or homer location for the ARC station, and the ILS localizer for the RSBN, and of course the ILS path for the PRMG part of the entry. Doing a separate entry for the PRMG location would require extra channels, I'm not sure it's worth it; - for North Las Vegas, where there is only an ILS, I used the coordinates of the localizer for the ARC station (again, it's no place for a Mig); - I haven't added a PRMG part for the other airports without ILS. It seems that in the Caucasus map, all entries have runway information, but here I left the same information another type of aircraft would get. On a slightly off-topic note, it would be nice to be able to change/add locations during a mission, or at least statically for a mission, to reflect the mobile nature of those stations. That is, after all, what caused a great deal of fear during cold war, all of a sudden those aircraft could strike from old / restored airstrips. Anyway, don't hesitate to post any discrepancy you may find, there's quite a few different files and numbers to get through, I may have slipped somewhere. :)

Ah OK. I'm not much in MP so I wasn't sure :D You shouldn't have any problem, I think I actually had the same question for a mod on the A-10C or the Mig-21bis (to rectify the incorrect mouse click bindings) and the conclusion was it was fine :) (EDIT: here)

The gauge highlighted in the start-up lesson is item #32, Figure 6 on page 24 (Bromstr), so that's the brake pressure manometer. (checked again, actually the highlight is all over the place) The correct gauge for the trim is just aft, it's item #25 on the same figure. Perhaps the confusion comes from there, I was quite puzzled in the cold start training lesson when I saw that. There are other little mistakes like "press start for 2 seconds", it's a switch, and sure enough if you click it back after 2 seconds the engine shuts down ;) Or missing "press spacebar", which makes you wait for a while before trying this one out. It's just WIP little issues, hopefully they won't stay as in the Mig-21bis :D

Temporary work-around here :)

It will be replaced by the original if you do a repair (if you're talking about the DCS_updater.exe in repair mode). On any DCS update, it will be detected as a non-original file and replaced, you can find your file back in the last _backup* directory under the DCS installation directory and merge it with the new one. Maybe you're talking about something else? It should not affect MP, nor will that modification be "detected" otherwise.

All the radio settings can only be bound to keyboard too. These are simply missing settings in the Mods\aircraft\AJS37\Input\joystick\default.lua file, you can copy them from the Mods\aircraft\AJS37\Input\keyboard\default.lua file. For instance, you can find this in the latter: {down = 3011, value_down = 1.0, cockpit_device_id = devices.TESTRADIO2, name = 'FR22 Push-to-talk', category = 'Radios'}, {down = 3011, value_down = 1.0, cockpit_device_id = devices.TESTRADIO, name = 'FR24 Push-to-talk', category = 'Radios'}, If you copy that at the right place in the former file, like this (in this case, at the beginning or anywhere in the same list joined to res.keyCommands), then the control get configurable for the joystick too: original local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") join(res.keyCommands,{ -- Autopilot {combos = {{key = 'J'}}, down = 3304, cockpit_device_id = devices.ENGINEPANEL, value_down = 1.0, name = 'Autothrottle mode AFK', category = 'Autopilot'}, [...] modified local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") join(res.keyCommands,{ {down = 3011, value_down = 1.0, cockpit_device_id = devices.TESTRADIO2, name = 'FR22 Push-to-talk', category = 'Radios'}, {down = 3011, value_down = 1.0, cockpit_device_id = devices.TESTRADIO, name = 'FR24 Push-to-talk', category = 'Radios'}, -- Autopilot {combos = {{key = 'J'}}, down = 3304, cockpit_device_id = devices.ENGINEPANEL, value_down = 1.0, name = 'Autothrottle mode AFK', category = 'Autopilot'}, [...]

Amazing feature ;) I'll have to watch my hands then. Sometimes I'm switching tasks or documents while DCS is booting up, that must be it. Good catch, ricktoberfest! And thanks to both of you for your help :)

Updated for 1.5.6. Now 2.0.4 and 1.5.6 are different, don't mix up the files!

Excellent! Thanks! :D That may well be the problem I had. Is that a known feature, or a known bug? I'm baffled!

Thanks for taking the time and effort to put all this together, it was very interesting! :)

Thanks! I have to change the antivirus / firewall soon, I'll see if that improves things. I suppose it's mostly DCS.exe and dcs_protect.exe that may trigger this error in case of problem. The fact it only happens once in a while seems to disqualify the registry method, reserved for permanent errors. If I do that (for all the aircraft...), I'll register them again and find myself in the same situation as now.

They're not in agreement. As you quoted, but you let the LANDING word in grey, the manual shows "relative position" (let's call it A) in navigation, and "flight path" (B) in letdown/landing, it's not confusing at all. Pilot's Flight Operating Instruction manual: (A) navigation, (B) letdown / landing. DCS behaviour: (A) navigation / letdown, (B) landing. So for example in DCS, if you change the course on the CCI/NPP, it will move the top needle on the FDI/KPP in navigation mode and in letdown mode, but not in landing. I can try and put this in a table.

Thanks for starting the discussion, it was an interesting topic! :) The terminology differs from one source to the next in this case, it seems, and there are some exotic elements as well, "directional needles", "command control pointer" or "bank/pitch director" are not standardized terminology. I think we're all just trying to find common ground here ;) That is from the previously mentioned document. If there is something "not quite", as you say, that's another difference in the DCS module. I haven't checked the letdown mode recently (shown as "proceed" in the English cockpit, for some obscure reason), so I just did and that's not entirely what I expected. Normally - meaning from this original manual - the KPP top needle (8 on the FDI figure) indicates the course deviation in navigation mode, and the relative position of the localizer in landing and letdown modes. The left needle (4 on the FDI figure) indicates the relative position of the glide path in landing and letdown modes, and is not specified in the navigation mode. What I observe in DCS is that the top needle shows the relative position of the localizer in letdown mode, and the left needle shows ... something else ... in letdown mode. The "K" course fault flag is set in both navigation and letdown, and the "G" glide path fault flag is set in letdown mode. But before saying it's wrong in DCS, I should probably admit it's quite possible that the functionality of those devices has varied during the model's lifetime, or depending on the "customer", although we'd expect the indicator's aspect to change too. It's also probable the translator made mistakes, the manual in question relates to the Mig-21bis, is in English (with Russian labels) and has some Arabic annotations and seals, it seems legit enough. The references to the radio navigation and landing systems are the same as the DCS manual, the same goes for the automatic flight control system. Yet the cockpit also shows some differences from the DCS cockpit, for example the battery gauges, or the magnetic declination indicator: that could not have been lost in translation. So LN's sources were obviously different, it could be interesting to ask them whether the specs of those indicators were also slightly different, or simply misinterpreted in either version. If the navigation system is not entirely correct, that doesn't really annoy me because they are not significant differences, but I know many people in the DCS community are keen to get any module as genuine as possible, which I perfectly understand, it adds to the perceived realism.

It seems I'll have to update the file with proper ILS information (affects horizontal guidance info on NPP and KPP in landing mode). Stay tuned ;)

I was talking about the KPP, not the NPP needle. The latter does move in navigation mode in the DCS module, indeed, not sure what to make of that. I see what you mean, in the DCS manual, the command pointer is called director too. They also mention that the item 8 discussed earlier is "an auxiliary PRMG needle", which sounds like it's only used in landing mode, whereas it actually works in landing/letdown mode OR in navigation mode, just differently. It seems fine in the DCS module though. As for the command pointer, perhaps they misread the manual, perhaps it's just a bug, who knows. The KPP course director - the top indicator of the KPP, item 8 in the right figure above, has two different behaviour, the one in navigation, and another one in landing/letdown mode, where it ignores the course set on the NPP and uses the runway alignment like a localizer needle would for an ILS - provided the localizer features horizontal guidance, of course, I've just tested one that doesn't and the needle is pretty useless in that mode. That's actually set in the MIG-21bis\Cockpit\Systems\R_NAV_data_Caucasus.lua and R_NAV_data_Nevada.lua files for the Mig-21bis, when the runway heading is provided, which seems to be the case for all airfields in the Caucasus file. The dots usually mark an approximate 2° deviation (hence about +/- 8° max), but I haven't verified whether it was the case here. Different times, different country, could be different.

Any news? This is happening more and more often these days, perhaps because I'm using DCS more often, not sure. It's much more frequent in 1.5 apparently, but that may just be random. Just had two occurrences when launching DCS right now. Could it be a timeout if DCS is trying to verify the module key online? 00010.881 ERROR EDCORE: LoadLibrary failed for Ka50.dll: (0) 00010.881 ERROR WorldPlugIns: Can't load plugin module Ka50.dll : 00015.428 ERROR EDCORE: LoadLibrary failed for M2KC_FM.dll: (0) 00015.428 ERROR WorldPlugIns: Can't load plugin module M2KC_FM.dll :

Any estimation when this will be fixed in 2.0?