virgo47

I have the following input setup - up/down actions are on the up/down positions of the STECS K-switch: The actions in the red act as momentary actions only - I have to press and HOLD the button to keep the lever in that position. This doesn't seem right at all when the Flaps Up/Down works as a toggle. To clarify - JOY_BTON55 is NOT a middle position "button" it is a different physical button on the K-switch (middle button). If I press the Flaps Up/Down action in the Controls table, it goes there and stays there after the release - as there is no other action triggered by the release of the switch. Flap Stop works as expected. So does the Flaps Up/Down toggle. I found a similar thread from 2015 - but I'm not sure how relevant that is.

First - the good news - it doesn't break the mission. It just makes the leader vehicle look like it's driven by a drunk or what. The pathing is a bit of on the taxiway - I guess the shape of the airfield changed since this mission was created or what: Looking in the editor: This more or less follows the ideal path, but I suspect the vehicle should follow the taxiway. My suspicion that the shape of the taxiway changed slightly also stems from the briefing image, but I guess this doesn't need to be reworked because of it:

While the search is typed in and the focus is on the input, it does not work indeed. I just click with the mouse anywhere on the table and then it works fine. If the binding is in the result, it will jump to it. If it is not, it does nothing. That's how it works normally and it's fine. You have to click on the table first, because otherwise key presses add to the search. Sure, HOTAS buttons COULD work, but that would not be consistent. Always focus on the table first.

This is easy to check in the game itself. If it works in the game then the stuck mod/shift is not a culprit. Shift especially can cause this, but I don't use that, only mods on keys/buttons that return to the off position.

I wish I knew what (if anything) I did, but I'm sure if I had known something then, I'd have written it - as I passionately hate "I made it work!" kind of self-replies. But I don't remember anything in particular and it just went away after another patch. Currently, I don't have such a problem with the latest OB/MT.

I was confused by my bindings for L-39 radar altimeter RALT knob setting (bug for r-alt warning sound) until I double-checked that LEFT means CW and RIGHT means CCW. This is totally counterintuitive - why the left-right is the direction of the bottom of the knob? I'd expect it to be the TOP of the knob. Red arrows show the current action that corresponds to the direction of the RALT bug, CCW (currently labelled - misleadingly - right) lowering the dangerous altitude indication: As it is a rotary, it would be better to use classic CW and CCW names - so I'd suggest that the current "left" is relabeled as "CW" and the current "right" as "CCW". Applies to both C and ZA variants.

Good to know this still doesn't work, I wanted to revisit the map with a trial, but it seems it would be a waste of time. I'm puzzled, how this issue is so hard to solve for ED. Is it just ignored, or it is so hard to trace the problem? Their shop shows confusing info when this map is trialled, I just don't understand how it can be so unreliable for so long.

This is not MiG-15 specific, I encountered the same issue with Yak-52, but I see it as a control bug. I have a 3-way switch for the gear lever with each position mapped. But when I flip the position quicker, the lever in the cockpit stays in the middle: Technically, the middle position "button' on the lever is generated by the "Boolean" function in VKB config software (virtual button when none of the up/down positions is on), but I this is of no consequence - as demonstrated by the very reliable action in the Controls itself. It's very responsive there. Also, I thought it had something to do with the "pulse" action of the buttons - as I have it set to 50ms pulse instead of press-n-hold to avoid undesirable cockpit changes when I forget the lever in the "wrong" position before the mission. I nearly stopped writing this report - but to my surprise, this bug is present with normal button action as well. I even tried to map up-neutral-down to keys 4-5-6 and went from 4 (up) through 5 (quickly) to 6 (and held it) - and the handle still stayed in the middle position. Simply put, until the plane doesn't do "its thing" in the middle position, it ignores any presses towards the extreme positions. This makes mapping the middle position on the lever itself counter-intuitive. I FEEL what I did. But the plane DIDN'T do it. There should be some kind of queuing for these actions. I the up/down comes after the neutral, it should be executed.

Touch Portal 4.0 got out recently and it has a few interesting improvements that can be handy for multi-page "pages" (or panels, let's say). It can export multiple pages at once and on import it asks what to do with conflicting value ids (unfortunately, for now it asks for each of them, instead of something like "ignore/reuse for all"). But it's not all bells and whistles. While built-in actions seem to work, COINS action seems to not work properly - as it is not possible to drag'n'drop them into On Pressed/On Event canvases anymore. Also, existing actions don't show the value as a select box anymore: Funny that "everything works" - but nothing can be changed. I asked on the TP Discord as well, but I have no info yet. Not sure whether the plugin needs to be rebuilt for 4.0 or what. I'll let you know when/if TP guy(s) tell me more.

I found this nearly furious about "multiplayer only MiG-15 canopy close bug"... and it turned out I just activated the airconditioning (right-hand valve) before the canopy. Silly me. It's great this thread exists.

When the Taxi training mission starts, the MiG-15 plane is on the edge of the concrete and grass - I believe it also affects the initial required RPM for taxiing: Cockpit view: And the map - with some strange lines: The rest of the mission is OK, the pathing is fine, no misalignments visible and the final parking spot is not on the edge, but more normal.

I can confirm the markers sounding as I land, good fix (the range is higher, but that is another problem for another OB, we hope ;-)) and I could also follow the car which is pathed properly and - this was the first time I finished the mission! It's great to see also this kind of fixes for vintage modules. Thank you very much for your care!

If you mean Il-76, then look at the manual Su-33 from page 139 on. Just a few snippets: This is about your distance from the tanker - obviously, green is good. Additional signals are: No idea about the S-3.

I've just had a similar problem. Landed the Su-33 in the training mission and wanted to see it from the outside. No luck, the track replay didn't budge. I restarted the game, loaded the same track and... F2 started to work. Annoying. Something gets stuck when the track is saved and replayed in the same DCS session. Using any of the views from the actual mission is just replayed as well, it does not allow subsequent changes in the view. (Also, avoid Fly Again button if you want reliable track, it seems to remember the first flight. Always go back to the mission selection and start the mission afresh. But that's another story.)

My question exactly. I was surprised the NWS on Su-33 works with the switch off/closed... but the label says "откл(ючить) упр(авление) колесом" which is "disable wheel steering" (more or less). So yes, the switch in Su-33 seems to be there to DISABLE it. Hence ON for disable. Of course, this is just my deduction, no real experience with Su-33.

Great! If needed I can add more info, as I eventually grabbed MiG-15 "as-is" just days later in that incredible sale back then.

That's how I understand it too, thanks. Talking about how Caucasus-specific markers are... I don't know whether Western planes have anything similar, but F-15C makes no sound over the same beacons, so I guess not. I guess it's an Eastern standard helping with landing, on Nevada and PG map there are no NDBs and no markers (so it seems). There are some in Syria, though. You can clearly hear the marker tone when landing to Damascus from the east (over the NDB).

Technically, I'm not sure how the marker signal is triggered - but if I understand the plane/manual correctly, it is a different receiver (MRP-56P), separate from (and/or additional to) NDB system. Marker transmitters just happen to be placed with the outer/inner NDB beacons. If both are available, they both send a sound, just different. Demonstration video: That said, I haven't heard a marker on the ground yet - but this may be a concrete NDB/marker/aerodrome thing.

Ouch, my bad. I didn't manage to read the Su-27 manual that much. I'm behind with all the manuals despite trying hard. So the line is actually right, I just looked at all the wrong places. Sorry and thanks!

BTW: Su-25T mission starts in the evening 7:45:00 on 14/02/2012, it's not totally dark, but it works really well. Of course, the ideal mission would: have the gates more as a guide with "close enough" working just fine voicovers could be cut by the action mentioned at the end (space, A-G mode, etc.) But that's probably unrealistic. About the K mentioned for full cannon, the line is similar, but not identical to the Su-25T mission. Su-25T has this weapon status panel: I'm not sure whether Su-27 should indicate it as well and it is some kind of regress, but the line says so - except the status panel is left from HDD, not HUD.

If I remember, the comment comes with the additional green-smoke targets. I've replayed your track and you missed many of the gates. Su-27 switches the waypoints just fine, but these old missions are pretty adamant when it comes to the gates. There are many lines you missed, e.g. the one about a low gate when you fly over the first ridge, and many other explanation lines on the way to the target.

Has anyone noticed that gates in training missions have spotting dots as well? Is it a feature or a bug? I think it's a bit distractive - and actually doesn't help with spotting the gate against the sun/bright clouds anyway. I guess the gate is just another plane for DCS.

I'd actually pay for FC4. I like full-fidelity modules, but I also like to have so much fun in a single package. I don't need massive visual or flight model revamps, I'd rather have bug fixes and function polishing and some more capabilities such as dropping single bombs or firing less unguided rockets... that is if the planes can do it (would be strange if not when Eastern trainer like L-39 can). Sure, I'd like to have newer Su-27 variants, but I know it's not possible - so I actually don't care. Not nearly as much as I care about the maintenance of existing modules.

I suspect these two controls should be the same - one on buttons and the other on an axis - but they both remember a different value for the vertical radar elevation. Is that normal or is it a bug? What I mean is, when I push the buttons (which, annoyingly and to my surprise, needs to be done repetitively) it goes to some position, let's say -13 (down). Then I move the axis, it starts in the middle, and I can move it up (e.g. 15). Then when I press the buttons, the elevation immediately goes to the "button" position (-13) and starts from there. That doesn't seem right. Or are there really two sets of different controls in the real Su-27 which remember different elevations? I assume these two (buttons and the axis) should be just two ways to control the same thing, or not?

This is just a reuse of Su-25T gun mission (or the other way around?) but the Su-27 happens way too late - in the morning, instead of in the night. All the voiceover remarks about the cockpit lights, darkness and flares sound ridiculous in such a setup. There is also a misleading line about K showing for cannon ammo full, this works for Su-25T gun panel, but not for the HUDs, here both planes show 4 for full.