virgo47

I use Touch Portal with DSC-COINS plugin as a poor man's control panel. Matric can be used for similar purposes but I don't have experience with that. I like it, it's flexible per plane and gives me more control with visual feedback. Of course it's not VR friendly. Example panel:

I absolutely agree with your last sentence. As for the context switching (I'm a developer too) - it is a thing, no questions about that. But we're not talking a month here, we're talking months, even years. That is beyond the context switching of a developer. This is about the priorities of the company, perhaps they are spread thin, I don't know. I'm not saying they would not like to do it, but they leave many bugs unattended and focus on new stuff instead. There will always be some ratio of bugs vs new features (modules, whatever). The question is how long the bugs are there, how many, etc. As a customer, I don't like the current ratio, but it is what it is.

Welcome to the forums. Please, provide at least a screenshot, what module we're talking about and any other possibly useful info. When the question is very general, nobody can help. (For screenshot, pressing Print Screen should be enough, the file then should appear in your Saved Games/<dcs-directory>/ScreenShots.) Some modules have some binding options missing for some devices - this is super annoying, but fixable - although I totally agree that a new user encountering this is not the best scenario ("look at this mod" or "check this Lua file" should not be the first advice any new user should hear).

That's not the same. That means waiting for ED to refresh the module. There is no incentive for them to refresh older modules based on the demand from users. Currently, they don't even bother to systematically fix the bugs that crop up in some modules from update to update. Also, sadly, BS3 was not trialable, so if one had BS2 and wanted to upgrade to BS3 just to see what was fixed, there was no way to do it. (Granted, the upgrade price was reasonable.)

I can only assume that TM Warthog, being a replica, is also ergonomic - but focused on A-10C. Can you use it for other planes? Sure. Does it have so many buttons as STECS grips? No. I'd say that the main killer feature of this throttle is configurable detents. Nice things are easily adjustable throttle tension (can be done any time you want quickly) and module customization (although you will only do that once). VKB does not seem to like normal switches (there is just one toggle metal switch) and prefers buttons - this shows on the STEM base module. STECS is a universal throttle with unique configurable detents, TDC on the thumb (has its pros and cons, for many mostly cons), many, many buttons/hats/actions, less metal than the competition. It performs great. It's not perfect. Probably none throttle suits all the needs of every person and every plane. Yes, STECS is comfortable. Very comfortable. Even the seemingly overcrowded front of the throttle is easy to use.

I was thinking about "modules" like this. I'd also buy a module called "L-39 bugfixes"... However, ED is not very transparent about what is sold in what quantities at this time, so how would I know whether it even makes sense? Perhaps then something like a donation effort with the goal amount where it would make sense to start something with such dedicated money. Currently, there is no way how one can "vote with their money" on priorities. It's still their business and the topics/options would have to come from their side anyway. As for subscription, I don't agree with it either. But ED must do something about overall quality and care for older modules as well - as we will only get more and more modules and if all of them get worse over time after "finished" it will likely bring some sour feelings. Not to mention many people can be put off by simple things like missing bindings (not actual bindings, but even actions in controls) for some planes/devices, buggy bindings (e.g. toggle is not toggle or bindings doing nothing or other things), buggy training lessons, etc. This all sounds trivial for long-term users and they know how to overcome it - or enjoy the plane otherwise - but I know it can be off-putting. And most of these bugs are pretty cheap. But instead of fixing them in the next version after being reported, they often take well over a year(s). And with fewer people put off by things like that, they could make more money. Speculation perhaps, but quality is important.

I don't own L-39C to test it myself. I know the knowledge can get lost - I'm not sure if the team still has the SMEs that worked on this or, ideally, notes in the code. I nearly asked on Matt Guthmiller's YouTube channel about it, but it felt a bit silly really (what if it broke one of his L-39 for whatever reason). But if you/the team can't get non-contradictory sources, I believe most people would be just as happy if it is fixed in the manual.

@Flappie Just to add one more source, taken from 1991/1992 Flight Manual L-39C Serial No 931529, I've got just some pure-image scan PDF without page indication (p31 in reader): Arguably, it's not totally clear and as a programmer I'd have a few questions about it, just to be sure. (This is a slightly modified L-39C judging from the pictures, e.g. knots instead of km/h speed indicator, but the changes are minimal, no changes in warning/caution lights, and I doubt this affects how this engine-related mechanism works.) Now, again, it can be an error from some other sources, but it really made me thinking what sources were used for the original implementation. Again, the nosewheel and engine shutdown with 730 light is also mentioned, currently not implemented.

That sounds pretty clear then... although so does the engine manual I mentioned, so there seems to be some contradiction on the ground (not in flight). God knows how and why it was implemented originally, whether intentional or not - perhaps there are some comments in the code. In any case, there is a discrepancy between the module behavior and the manual. And the engine does not stop after touchdown with 730 light on.

Perhaps there are some mechanics for the Kola map, no idea. But the list of fixes is really underwhelming.

Did uninstalling some of your mods help? If so, which ones? I encountered this thread when my game regularly crashed on restarting one of the Su-25T Instant Action missions (easy CAS). I'm not sure it's mission-related, but it seems it crashes the game mostly when I ask the mission restart in the outside view (F2 or after I crash and the view is outside already). As for mods: I suspected the Barthek's Caucasus redone mod originally, but uninstalling that one didn't help. I've got a few seriously low-profile mods + DCS-BIOS - and while DCS BIOS does show some errors in the log, it does so consistently (so to say), not only when the DCS crash occurs. As a side note, a crash related to mods... isn't this still kind of a DCS problem that it doesn't catch exceptions (or whatever the equivalent is) at the "extension points" and - if totally unrecoverable - at least clearly logs it that way in the log? Suspicious logs are attached. As a side note 2 - it would help us as well if the log was not polluted by various other warnings and errors, often graphics/shader related... if something is normal, don't report it as warning. And if something is a warning, fix it, or if possible, suggest a remedy, perhaps even in the log. (Sounds overly simple, I know, but as of know, there is no way to tell whether I can do something about a warning or an error.) dcs.log dcs.log.old

Eh? ... Shouldn't this be an English forum?

I don't have a 3D printer (yet) and somehow I manage. The worst part is the resistance... it should be progressively higher away from the center, not like now that it kinda "snaps" and then it moves easily. Yeah, I exaggerate a bit - but really, only a bit. I also use curves for TDC in DCS, but that's another problem, because in DCS you need some minimal value (around 10) to get the TDC moving. So to make it move slowly from the get-go (right after you move it off center) you need to add user curve with a steep step at the start, then a smoother one later, and also probably some saturation as the max speed of TDC is often too fast (at least in FC3). All that said, it's not worse than the TDC on the TWCS... but it's not that much better really. (Index vs thumb issue aside, one can really train it for the thumb.)

I've used it for 7 months and I understand all those points mentioned in the OP. I don't need to mount it, but I also wondered about the screw hole under the USB connector, although you can unplug and plug it... Now the main points: OTS - it's far from perfect, but to my surprise, I got used to the thumb. But I wish it was easier to move from the center and progressively harder towards the ends. This one is kinda harder to start moving and then it goes easily runaway. This is even more so when moving the thumb "sideways" (physically up/down, but logically I map this to side, of course) - because there is even less control in that thumb move. Back and forth (up/down logically) is fine, plenty of control in the muscles. But the move action is way too loose. And with that, I don't even use OTS press to lock, for that I use one of the front triggers, so I don't accidentally move the OTS. And please, VKB, give us some dish shape. This cone is not bad, but it's far from good. Just for fun I tried the rubberized red button from WEAPON SELECT and it was MUCH better. (But of course it doesn't cover the hole and I miss the piece on WEAPON SELECT position.) Detents are great, I use mostly one, but I have one "universal" IDLE+AB combo, still reasonable amount of throttle is left, as I mounted the IDLE as low as possible and also used narrower V detent. I didn't like low (regular) L detent for idle, because it's easy to overcome, and "large" L detent is extremely difficult to overcome in idle configuration, as it goes really against the springed rollers. I'll not try it, but I don't believe it wouldn't break eventually after many cycles. Large V works much better as IDLE for me, and the throttle can start lower than with the L shape. Three detents seem silly to me, not with these quite wide detents (W and L both take 18-19% of the throttle range). I'd welcome some subtle version of W, something that doesn't push the throttle away and the center notch is just a small groove, just to feel it and hold the throttle with minimal force. This would be a great detent that would not have to be configured and great for things like "nominal power". I use DCS curves to set the actual AB position for planes where the physical AB doesn't match the logical one. No problem. You're using even less friction than me. I had problems on the top end, especially the right grip is heavy. I'd also like to use less friction, but it is what it is and this throttle must be pretty tight. Not sure what can be done about it mechanically, perhaps some counterweight, but for that there is no room - otherwise the unit would have to be much higher, I guess. Overall? I also like it. I only talked about the points from OP, so I'll not open "grip encoder-vs-axis" problems and other possible improvements as there are plenty and it would be a different product. We'll see what VKB comes with. I wish they'd give us more grip options in the future (e.g. the right one with OTS on the index finger or the left one with axes options).

I've noticed that some 3rd party dev maps are not available for trial - will this be the case for Kola as well? I guess it's ultimately the decision of the dev, but I don't understand it with terrains in particular, because if one likes the plane, they can enjoy it for 14 days and then exploit this after 6 months again, but with the terrain, if one likes it, it's probably more likely they will not wait 6 months to enjoy it again. Doubly so if they need it for some online play.

Ergonomics is a lot of things. What this throttle does - it does well. I like it under my hand. Everything is easily within reach. But there are some drawbacks - which I'm sure every throttle has - just different ones: Encoders on the left grip are great, but configured as axes they are not adequate substitutes for real axes. Especially the encoder under the ring finger is difficult to operate, some axes (perhaps self-centering?) would work better there. The thumbwheel is precise, but the placement and spiky finish is not the best... rubberized wheel (like on the grip encoders) would be much better. There is no substitute for any rudder axis if you're upgrading from a throttle where you had one. And OTS on the thumb is a thing to consider. I have no problem with the thumb position now, but a better hat/dish would help with the control. Feeling and action (including the press action) could also be better, but I guess these are in the price range (I can't compare). These are all ergonomics things as well... That said, it's a solid product. And what it does, it does really comfortably.

I posted the first two parts of my review trilogy previously, and finally, I got to the last one. This one focuses on detents and various configuration customizations, including quite extensive examples in VKB DevCfg. Let's call it "first impressions after 7 months" in the context of this thread.

I guess it will also be simplified. It can't just be FF module without a clickable cockpit. So it will likely be "electric switch on, one engine on, other one, flaps..." and you're good to go. For better or worse, that's how it should be with FC-style module. I've spent hours in cold cockpits, no problem with that. But I like this option as well. So there will not be tons of arcane keybinds really. On the other hand, I also like that mod for clickable FC3 (not quite working with 2.9 though) - because it is not NON-clickability, but simplicity, which is the main feature of FC3. Plus, there was a great idea in one video of FC-style WW2 birds... I don't think it's that bad. Not because I don't like spending hours and hours in cold cockpits. But just to have some options - not to mention the unit price of these.

I'm glad... probably, but also confused. I'm glad that FC style is not dead. I'm confused about the choice of modules... Immediately the first thing that comes to my mind is negative - the FF modules will not be cared for that much more and their future is in FC-style. I hope that is not true (as I own all three) but it's a strange choice at least. It makes some logic though, you've got the know-how about those modules. I guess it will be an upgrade, which means paid... no prob as long there is a good upgrade from FC3 as a package. I expect this, this part is mostly done right by ED. And yes, Kola... I fly so little on other maps, but whether I buy it or not (eventually I will), Kola seems a great choice from the start. Something similar. Something cold-war-ish, although it never happened. But it still might, you never know. And it's distinct.

Thanks for the info and for the method, I'll add that to my palette. It's a bummer it is so complicated and unsearchable. But it's possible. (Half an hour later before I actually pressed submit.) But this left me wondering that DCS-BIOS guys must know it already and perhaps have such a database. Old dcs-bios repo wasn't helpful as it only defined seven indicator lamps, but I found this treasure - and it contains: C_101:defineIndicatorLight("CC_FRONT_WARN_AOA", 167, "Warning, Caution and IndicatorLights", "C-101CC FRONT Warning Panel AOA/STALL Lamp (yellow)") Now how they got from this to this piece of JSON that is available in their release... "CC_FRONT_WARN_AOA": { "category": "Warning, Caution and IndicatorLights", "control_type": "led", "description": "C-101CC FRONT Warning Panel AOA/STALL Lamp (yellow)", "identifier": "CC_FRONT_WARN_AOA", "inputs": [ ], "outputs": [ { "address": 14182, "address_mask_identifier": "C_101_CC_FRONT_WARN_AOA_AM", "address_mask_shift_identifier": "C_101_CC_FRONT_WARN_AOA", "description": "0 if light is off, 1 if light is on", "mask": 4, "max_value": 1, "shift_by": 2, "suffix": "", "type": "integer" } ] ...is a mystery to me. Also, I don't see any relation between the address and mask and the original 167 - so I guess there is none. But at least they have it all sorted out in their sources, which is great. That's the "database" I needed! (I assume, someone did all the digging in the Modelviewer, or even knew how to read some of the binary files.)

Hello guys, I know this is more a mission editing question, but it's C-101 specific because I'm lost in those lua files. I want to check whether some warning/caution light, let's say AVIS.PERD. is on. I wanted to use X: COCKPIT ARGUMENT IN RANGE, but I can't find the argument. When I want something like that for, let's say, L-39, I go to L-39C/Cockpit/mainpanel_init.lua and find the section there with a line such as RV_5_2_DangerRALT_index.arg_number = 397. For C-101 I can't find this. Specific mainpanel_init.lua files are very short, and mainpanel_init_common.lua is longer, but still doesn't contain what I'm looking for. I grepped the whole directory for "warn", "caut", and more, but couldn't find anything in non-binary files. I know it can be obtained, as DCS-BIOS sends the status to Touch Portal plugin (DCS-COINS), but DCS-BIOS definition didn't help me much. Please, where is it? What am I missing?

I investigated the issue with the very first training mission (C-101FA-Lesson-01-Start-Up-V4.miz) not proceeding when waiting for the throttle STOP position and it seems the problem is that the range of throttle argument was changed (or the mission changed, because it worked back in 2022). Originally, the step waits for X: COCKPIT ARGUMENT IN RANGE with ARGUMENT 5 and value min/max both -0.4. Argument is OK, as it is also used for the previous check of THROTTLE being completely advanced. I tried to lower the minus number (towards zero), but no luck, so I tried 0-0.1 (positive) and this worked. It does not trigger in the IDLE and correctly triggers in the STOP position. The fixed trigger: Ignore the time since flag condition, which I also changed, I wish all TIME SINCE FLAG were 1 (except when something really long is happening, e.g. engine revving up or so), so I can faster repeat the mission, it's more user-friendly.

Thanks for the info Rudel, I'm looking forward to more fun with the plane. It's not a device issue, I just used throttle detent virtual buttons to trigger it, but I also checked with keys and all do toggle. So I guess you always had the throttle on the right side or the detent, then you toggle it the right way and it looks good. But when I pressed any of the R...+Home combinations, it always happily toggled: Reported and rereported here: Now I'm going to look at the training mission why it gets stuck on the throttle step and also whether it can be sped up by not waiting for the whole sound. I remember (quite fondly actually, but my memory is generally bad ) spending some hours with these tutorials back when I was trialling the plane in 2022 and I was impressed compared to many other stock tutorials. But man, are they long and slow. This is OK until you want to repeat them after some stoppage. So I made an unlucky choice for my "good-night" mission.

BTW: This could probably be merged with Or the other way around. The other thread also has a more descriptive name.

I returned to the C-101 after a year and a half, now actually owning the module... I'm quite surprised there is little activity in this thread. So I'm just asking: Are the developers still active on this plane? I got the first tutorial mission stuck at step 7, I don't remember such an experience back in Aug 2022. I guess the plane flies, but having throttle STOP and IDLE actions acting as toggle kinda put me off very quickly, especially after seeing it reported back in Jun 2023.