virgo47

Today is getting better and better. Great news, I hoped it had been just a hiccup and everything would be OK in the end. Thanks for the clarification. I install both from COINS, so I'll be fine.

I still don't understand this - is this related only to the new versions of DCS-BIOS and/or DCS-COINS? There is a single file for both L-39C and L-39ZA planes (either L-39ZA.json in DCS-BIOS or L-39ZA.pp) and both planes work fine in version 2, I use one unified custom TP page with both and I'm very happy having this extension of the controls. Now I'm confused whether I should stick to DCS-COINS version 2.2202.02 and not update in the future or what. What is the problem and can someone with the L-39 Albatros module (like me) help in any way to fix it?

I was using L-39 just fine with DCS-COINS version 2. What does the exclusion mean to the future? Will COINS be unusable now with that or can I somehow add the plane there later?

Great info, I didn't realize (or forgot) that while the arms are ready above 310 km/h, guns in particular require 400 km/h. The "deblock" button is interesting though. It can't be mapped with a key/joystick bind, which is probably a bug (definitely a missing feature), but it can be mapped using anything that goes over DCS-BIOS (for cockpit panels), e.g. DCS-COINS plugin for Touch Portal Android application. I was afraid the button has to be pressed - like RSBN tune button, for instance - but luckily, this one works as a toggle every time you press it. This also means that there is no indication of the deblock state, sans the AoA light itself when in the situation where it would likely be alight. (And yes, I was shooting down transport plane as well. )

Thank you guys very much, the answers came so fast. There is definitely a lot to desire - although I'm in a position where I don't know the current capabilities. But this cockpit setup stuff shows just how awkward it is now. Instead of somehow saying "RSBN Navigation to 20" I need to know it's 1 at the start and repeat the click 19 times. But the same solution will not work for mission where the plane doesn't start with RSBN set to 1 - that is, even in the same mission if I change the plane from flying to hot start on the runway (imagine scenario I want some other RSBN channel there). I was afraid it will come to this. I didn't see noticeable difference hence I didn't try to clone it many a times there. But this is semi-usable, because, again, when I move the plane, I have to reconsider the initial position of the RMI - which is ridiculous. That doesn't take away from your answer, of course, I appreciate that. I'll probably just instruct myself via a message to set RMI. Or use first WP when convenient. Interesting info, thanks - but RMI goes round and round - so I can't imagine getting to any known (e.g. end) position anyway. But I'll think about this when/if working with some non-continuous rotary knobs. At least I know that in the current state of things I don't need to chase this chimera of how to set RMI precisely to a known value, which is also a good thing.

Hello Recently I've created various landing scenarios for my practice, but it was very annoying that I need to set everything in the cockpit again and again. It would be great if the plane started with the same setting like "hot" for the target aerodrome, I'm not sure whether such a shortcut exists. However, I started to experiment with triggers and go most of the stuff I needed. I love the OPTIONS_ADD_COMMAND_CODES_TO_TOOLTIP=true setting, very useful - although first I thought it does not work until I found out it works on the right side of the Controls table, not on the left where it shows the original description. In my case, I fly L-39, I managed to disable arms, click 19x on RSBN to set channel 20, etc. I'd like to learn to do the same in script eventually, because cloning something for 20+ clicks is indeed ridiculous. Funny that some clicks are COCKPIT PERFORM CLICKABLE ACTION (like RSBN channels) and some are SET COMMAND WITH VALUE (switching radio channel) - but it’s easy to recognize which is which (based on the presence of the device id). It’s cumbersome, but it works, no problem there. What puzzles me is how to set RMI course selector which is on a rotary knob. Controls say “cockpit id: 25, pressed: 3004” both for CW and CCW rotation, I tried to add COCKPIT PERFORM CLICKABLE ACTION (because there is device id) but I have no idea whether this works, what the value does, etc. I tried values from -1 to 1… but I don’t see any difference on the RMI course. Not even in units of degrees. How can one set such an instrument in a Mission Editor? BTW: I never made Prepare mission work for me and this plane (manual is also half-clear on this), not to mention it moves the time as well, so the trigger way is much better. If someone knows how to do it in DO SCRIPT, even better. I’m at the beginning of the scripting road and most materials are about other units, dynamic missions, etc. I couldn’t find anything about setting single player cockpit. It’s probably out there but buried under more advanced stuff. Thanks

So, with the values of light intensity knob coming to the TP I could display it ("Update Button text each cycle" event), but sliders do not seem usable at this moment. There are a few issues: TP has no On Event for sliders - so the visual update of the slider seems not possible. The actions provided for the slider are quite limited. These are mostly very specific actions - or I can set a value 0-100. So I tried that. I thought I can create some global event when the value is changed and update the value in DCS. But currently I'm in a dead end with an event like this: I'm not sure how to listen for ANY change - this is obviously more a TP related question, maybe when I don't provide any value, it listens to any change, but I doubt it. I have no idea how to even try that. But even after the calculation of the final value, I have only two options for the DCS action - increase or decrease the value by 3200. I'd need an action to set it precisely. This is perhaps something that DCS-COINS can help with. Now with all these limitations - most of them on the TP part (e.g. "any change" event and no way to set the slider based on other event) I'm not going to do this. Even using it for buttons (two or multi-state) is a big benefit already and I'm going to tune the setup for these first.

OK, that one was easy, I forgot the DCS-COINS setup already because of the DCS-BIOS experiments. Perfect that there is auto-detect + way to override it. I tried it and definitely saw some actions in dcs-coins -v output when clicking the cockpit of TF-51D. Thanks. I removed the # characters and ... well, it was actually success after I figured out which line is the right one. That can be tricky, but that's probably because I just start with it. E.g. that FRONT_INST_LIGHT_INTENS is NOT a control knob - and that's also why it had only output section. That is in fact the actual light intensity. Not the knob position, but what pilot can see in cockpit. Cool. The knob was the line with FRONT_INST_LIGHTS_CON - and it worked like a charm. I didn't create any meaningful widget for it yet, I just wanted to debug it quickly, but I'll try later. I thought so, thanks for the confirmation. It makes sense with the previous paragraph as well - when I have a knob, it needs to have both input and output. Pure output is something I can't control directly (e.g. actual light), but can be a combination of factors (e.g. switch ON + intensity knob turned). Yes, I saw this already - although understandably didn't get through the whole thread (it also takes time + experiments to let all the info sink). That is that Lua console, which is not the same like your dcs-coins -v output, which - again - is really great to figure out what should be available in TP via your plugin. DCS-BIOS level will take some time, but no worry. I'll write when I know more. Great strides today, thank you very much.

I suspected P-51D may support TF-51D, but it is not automatically installed like other modules - it probably relies on P-51D module being bought. I don't know how to install it manually (just adding the JSON from DCS-BIOS is enough?), but for now this is lower on my priority list. Talking about the sliders - I want to ask about the ignored items, whether I understand it correctly. The line from the PP file related to my slider experiment was this: FRONT_INST_LIGHT_INTENS|front_inst_light_intens|FRONT Instrument Lights Intensity|0|0|#Max65535#|0 Does the # character anywhere on the line mean the line is ignored? Also - in DCS-BIOS JSON, the entry for FRONT_INST_LIGHT_INTENS has outputs, but empty inputs array - that probably means it only works one way. Sorry for lame question, input/output is from which perspective - from DCS's point of view? Finally about the missing events for one switch - I installed DCS-BIOS separately on my other DCS installation and tried to see what it does, but after a few hours here and there I couldn't figure out whether DCS-BIOS has anything similar to your debug output - which is very useful. There is this Lua console, but it doesn't show the events as they are emitted, then there is DCS-BIOS.log, but that one is only full of lines like "Util.lua: value 334646.000000 is too large for address 12862 mask 65535" and nothing else. I'll probably ask on the DCS forums for Home Cockpits eventually, but I'll try a few more stabs at it before that.

I've noticed an interesting problem while extending my L-39 setup. There is a switch defined by this line in PP file: FRONT_BOMB_REL_SEL|front_bomb_rel_sel|FRONT Missile/Bomb Release Selector Switch, PORT(Left)/STARB-BOTH(Right for Missiles/Both)|4|0|OffOn|OFF Now, it works when I call the action from TP, but the events do not work. Even stranger - when I flip the switch in the cockpit, it only works one way (to ON position) - and only once. I ran the verbose debug... and there was no action at all when I flipped the switch back and forth. There is only one line: Event: mgdc_l-39za_st_front_bomb_rel_sel [ON] And this one only after I set the switch via TP first, not when I change it in the cockpit afterwards. EDIT: Affects only L-39C, works fine in ZA. Any idea what is the problem? Is it DCS-BIOS related or DCS itself?

I'd love to see the NG version - but let's be real here. L-39NG is a different plane from L-39. It seems L-59 and L-159 are actually more similar to L-39 than NG. I'd rather see L-39/59/159 variant with Western avionics, although you can go for C-101 to get the same aircraft class. Also, L-59 and L-159 have both around 80pcs produced each... NG has 5 prototypes produced, so it seems. That hardly attracts any DCS development. I doubt the NG variant will ever be part of this module. It's too different from the L-39 original, it's not really used, and it's also too new for that I guess. I'd rather see a refresh of the L-39 module as it is with the fixes for the bugs we already know about.

Hello I totally fell in love with this solution and have been experimenting with switches for L-39 for a few evenings (slow progress though nothing publishable yet). I also noticed the published FC3 panels and was curious how they work - because FC3 actions/events are very poor compared to full-blown module. But these are different, they are keyboard based, which is OK - although it means you have to redefine it if some of the default keybinds are changed. This is the strength of those low-level actions - but I guess there are no such actions available for these kinds of models, right? I'm wondering about the free clickable TF-51D - I noticed there is nothing installed for it, no action section, nothing. Is this somehow tied to the full version of P-51D? Of course, one can support it via keyboard emulation again, but it seems strange - as it is fully clickable cockpit. In L-39 I also hit the wall was when I wanted to use a slider to control something like light intensity (rheostat). I can convert the 0-100 range to that of DCS (e.g. by multiplying the number by 655), but I can't find any actual action to set the rheostat value. There is something like FRONT_INST_LIGHT_INTENS in DCS-BIOS JSON for L-39, but I can't see it in Touch Portal. Does anyone know whether/how it's possible? In overall, I'm just at the beginning, but this is very nice alternative not only to Steam Deck, but also to HW buttons (e.g. like VKB NXT modules and similar). Sure, these are more tactile - but the tablet is much more flexible and programmable + can show stuff much better as well. Even when it can't do some things (yet?)... whatever, now I can do at least something on the tablet - so I'm better off in any case! Thanks @xoomigo for DCS-COINS, it is really a great improvement providing many options.

Minor manual bug on p29: Start switch This is a three-position toggle switch marked NORMAL and VENTILACIÓN (CRANK). The switch is two position - at least in game.

@gulredrel You were right, if I really do not touch the ignition switch at all, everything checks, bulb is off and nothing wrong happens. I definitely didn't start it with the electricity on, but probably checked the switch when it was mentioned. I left it in OFF, but it still started the ignition. If there is a way how to reset the ignition, I'll probably learn it eventually, now I'll just stay away from the switch even when the plane is cold. I tried again: If the switch is touched in the Step 8 of the interior inspection list (turned ON and then OFF), the Ignition Lamp goes on when the battery is turned on (step 1 of the before start list), later goes off when GPU is turned ON, and then goes on again when that Bus Tie Switch is turned ON. Is that realistic? Does that IGNITION switch really toggle something when cold and then it works even when the switch is in OFF position before any power is applied?

I'm following the first training mission and during second list (Before Start), step 9, Ignition Lamp is on even when not pushed. Ignition switch is definitely not in the Cont Ign position. Pressing the lamp does not change anything, it still is on and stays on after release. Is it normal or can some other stuff cause this situation? EDIT: I tracked it to the Bus Tie Switch - when ON, the Ignition lamp is always on as well. Marker lamps are off, unless pressed (check works fine for those). There is also another side-effect - the N2 needle tries to go up, so the starter actually does something. If I put the throttle into IDLE, it starts the engine.

I'm just testing C-101EB (not sure how this affects CC): HOT MIC RX Volume - PULL and PUSH actions are reversed when using keyboard or joystick buttons. PUSH pulls the volume knob out and PULL pushes it down. That is PUSH works like right mouse button in the cockpit (which pulls the knob up) and PULL works like the left mouse button. This applies to rear cockpit as well. The same applies to other volumes TAC, INT, MK (Marker beacon), UHF, VHF and VOR. For HOT MIC TALK Breaker PULL/PUSH - both actions do the same, they toggle. None of them is reliable to get the breaker into the described position. Should either be clearly marked as PUSH/PULL toggle, or work one way only for each. I hope I understand meaning of push and pull correctly in the cockpit and it's not some confusing slang or what. It seems like you can simply switch the description for the actions for the first problem.

ED fixed it, thanks!

@Rudel_chw I understand that, that's why I mentioned "assist" function ("cheat"). The thing is, I was a few minutes into the first tutorial, just checking the things - and I had to restart it. In DCS I still don't reliably know what click does what, when to drag, when to click, what cycles, etc (even in C-101 left/right clicks are not direction-wise consistent for each switch) - so it's good idea to try it in a new plane. The handle is a single click operation. Of course, I'll try to avoid it like the plague now, but it's prohibitively easy to activate. Thank you for the link, it is interesting, but way above my trials at this moment.

I tried the Emergency landing gear handle - and it can't be reset on ground when cold either. Is it possible to give us at least some assist function to fix this?

I am IT by trade as well. Programmer - and my family asks me to fix their computers... obviously. I actually like downloading manuals even before buying the products - sure, DCS costs nothing (except 100MB on the disk), but this seems like a cheap shot at a quality appearance, wasted opportunity that should cost little to nothing really. It should have been automated.

Thanks for the info, I know that now. I'm just pointing out that there is readily google-able obsolete manual which only leads to confusion. It's on the same list as other airplanes, etc. It's good that it's also offline, of course. But I doubt I'm the only one mislead by the offered download. Many people go online first before looking into their folders on disk.

Hello ED! For months I was wondering why you don't update the User Manual, because I've been working with this until now: https://www.digitalcombatsimulator.com/en/downloads/documentation/dcs_user_manual/ This is what I get to when I google the DCS manual, the filename even says 2020, but it's obviously old. Today I accidentally found the manual in DCSWorld/Doc folder (~40MB version with much more up-to-date screenshots). Please, can you do something with that download page? It's confusing and I can't believe it's difficult to update it or obsolete it somehow. I wonder how many other people work with that ancient manual. Cheers

I tried takeoff/landing on Soganlug airfield with various winds, and got totally confused by its ATC. For example, I took off on 14, expected to be navigated back and land on 14, but Soganlug ATC said: "Fly heading 312 for 12, QFE..., runway 32, ..." As the airfield was just behind me on ~320 deg, it was strange. How can I fly 312 for 12 km and then land on runway 32?! It all makes sense if I actually believe the ATC, just flip the named runway (14/32), then it all makes sense and it also navigates properly to go upwind on landing. So I suggest - fix the ATC messages to say the right runway number. Just exchange them. I tried this in L-39C and Su-25T, so I guess it's not plane specific. I'm on updated OpenBeta.

It's a silly test, nothing critical, but it bothers me as well. Probably easy to fix the lights - and this would be the best part of the fix. The test switch change to spring-loaded would require removing the OFF binding as well. Too bad this has probably no priority. But it would make the plane virtually perfect (in the scope it is modeled)!

1. I'm still not sure about saturation, it may be dead-end experiment, currently I'm flying L-39C, so I have no conclusion on it. Perhaps I'll need 100% saturation at least for taxiing. It might have been a stupid idea. The "phenomena" I mentioned is not about sync of HOTAS - which I actually like - it seems to be some auto-calibration process during the first few moves. It's like the pedals are overly sensitive and saturated way before you reach any of the sides. But after a few moves, they calibrate somehow and try to cover the whole distance properly (still too sensitive in the center for my taste, but that is another problem). These first few moments may cause feeling of over-saturation. In order to fix this calibration issue, I pause the game, go full left-right on the pedals couple of times, and it fixes it. I don't use any TM software, only the default Windows 11 drivers, I don't know whether that would fix it, but at this moment this is fine with me. It's just the thing I have to do when I start the game/the first flight. It's OK.