virgo47

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.

I'm not sure this is the same, perhaps it's particular options dependent, but I've got an example of ships appearing, inflating and shrinking in Syria:

I'm talking only about the ships inflating and shrinking; I thought you said to Tippis that it is only a map issue. I didn't notice any flickering and random stuff yet.

OK, I also mixed the issues in this thread with this. My video of the same, also Syria, but from heights, it's more obvious: But that's all from me in this thread...

From the L-39 manual - element 1: The whole handle was turning previously, because that is the actual control - the distance bar on the sight is only an indicator. Both turned previously.

That's the reason why I thought it didn't work at all... not only the distance bar, but the twisty element on the throttle doesn't move either - that's where I was checking, not the HUD. Thanks, Flappie, always nice to hear from you. So to summarize: buttons don't work at all the axis seems to work on the HUD, so hopefully, it works properly in the action while in gyro mode, etc. graphics element in the cockpit don't work - that is the twist on the throttle and the distance wheel indicator on the gunsight.

My options.lua: options.lua

I noticed ships "growing" in one video showing OB 2.9 and it was quite distractive - that was the Marianas. Later I saw it myself in Free Flight mission for Yak-52 near Haifa - that is Syria map. Ships appear, then they grow as you close in - but not realistically, they really inflate - and then they shrink as you fly away. My DCS was repaired after OB 2.9 update. My LOD is set to 1, I can try again without DLSS whether that is an issue, although I doubt it.

I don't mind when the bugs appear, especially in OB, I understand they will not play all the missions and try all the features of all the modules. I'm not sure they have some kind of automation for it - if it is even possible. So I understand bugs in OB, especially after a big change like 2.9. I just hope they will not join the suit of many other long-standing bugs. Hopefully, this is considered a high priority as it should. But sometimes I'm not sure whether some modules are not low-priority as a whole... I like flying a couple of older modules and they often feel a bit abandoned.