virgo47

What does it mean "not work"? I'm not sure what limits_6DOF is supposed to do, but from my experience, it does not allow tracking to the limits you put there - perhaps only a little bit if the original small numbers restrict the tracking too much. But it still allows placing the center of your head/camera within those limits - that is moving it around with key bindings.

Where the real manual meets the simulation, many DCS manuals fall a bit short and forget to mention things. I also think this should have been clearly stated somehow, otherwise it is confusing, it requires experiments, and even after those one still can ask "is this really how it should work?" In overall, the MiG-21bis is quite good actually, but I also couldn't find anything related to this simulation feature.

I tried it and it seemed that way, I just wanted to be sure. I'm probably mentally stuck on something here and I can't find the description in manual (at least not with the text search). On page 64 it says: Yet, if I trim the plane and bank it over 10 deg (e.g. 30 deg) and then just engage STABILIZE without holding my stick it does not stabilize the bank. That's what is confusing to me. To get what the manual says, I have to STABILIZE and then simulate not holding the stick with J although I didn't hold the stick at all in the first place. EDIT: I can speculate that the difference in roll axis is that J simulates the stick deflected and relieved of the pressure. It's difficult to imagine with a home setup with spingy joystick I guess. I can see J doing something subtle with the stick in the cockpit, so it's not the same as just leaving the stick in the middle position - which is "no pressure" for me, but perhaps not the same as "no pressure" in the real life cockpit?

I still don't quite get it... So J works only in stabilization mode, and it somehow keeps the attitude, just like it would if I engaged the stabilization mode without the hand on the stick? Does it mean I can do the same with pitch trim (the only one available) and then pressing the stabilization mode when the bank angle is what I want without having my hand on my stick at that time? (MiG-21 tends to unroll/unbank, so J helps me to keep the bank, in addition to the trimmed pitch... is that it?) And just to clarify, J is a simulator trick/assist then, not a real function of MiG-21, right?

Does it mean that SAU - Hold Attitude (J by default) is some kind of assist/cheat or combo, and not an actual switch/button in the cockpit? How exactly does it differ from SAU - Stabilize which is a light-button (LV53 in the manual, if I get it right)?

I've flown the ARC mission, I landed, even tried to go to the starting spot to get some conclusion - nothing. So I opened the mission file and I believe there is missing FLAG ON for flag 6 here: I checked some previous triggers (e.g. Turn towards... 4th from the end) and it has both OFF for 4 and ON for 5. The last trigger waits for the missing flag 6: Hopefully, I'd have the cockpit args in range, heading was definitely OK.

On other planes anything destructive happens after the third press of the Eject action - ideally everything necessary happens. On MiG-21 the first press jettisons canopy, which is quite strange - and I can't find anything about it in the manual either. Is it by design? If so, why is it different from other modules?

These two knobs move differently when activated with keyboard/buttons vs axis: With axis bindings (or mouse wheel) they move from ~8 to ~4 o'clock, with key/button bindings they start at 12h and end at 4h (end is the same). That is, for keys, they travel just the upper half. Strangely enough, the effect is not bound to the knob movement though. If I use keys/buttons, the light intensity goes from max (4h) to min (at 12h), but the moment I touch the knob with axis binding or use the mouse wheel on it, it immediately switches to the 8-4h range (any movement around 12h makes the effect go from 0 after key action to ~50% effect).

The title says it all. - brings the lights in, + decreases them. The other three Cockpit light sets seem to be OK.

Guys, please... I tried this mission after a year - and I decided to consult my own thread to see what the problem is. I remembered it vaguely, hoping to see the screenshot of the zone (because otherwise I'd have to stop the mission, go to editor, etc.). Great I reported it previously. Now where was I this year (#101 at the bottom)? I just wasn't sure whether I'm off totally, whether I need to go sideways or what... but after checking the screenshot in the OP I just pulled on a meter or two and it worked. The zone really is confusingly small. I'm glad you fixed the training mission #2, I really appreciate it, this one should be trivial to fix as well.

This is strange, I've tried my setup now and when "Command Sent" is in the log (that means I did something on the tablet), I can clearly see the effect in the DCS. I've checked your log and I don't see anything suspicious there. EDIT: Mostly, when I had problems like this, it was a DCS-BIOS stuff, but I'm not sure here, as you report the events work just fine as well (e.g. the icon reacts to the state of the game). Does the TP page update when you click in the cockpit?

What is the content of that dir where you run the command? (Use DIR command to see it.) If there is Munt.G_DCS-COINS sub-folder, go there (cd Munt.G_DCS-COINS) and try there again. That DCS-COINS.exe is there.

I can confirm the fix for this one, I had no problem finishing the mission this time. Thanks!

What does it mean? Is the purpose negated now? Does the option even do anything? I tried to find something about it, page 26 in the manual is obviously very old screenshot and doesn't cover it. Forum reports are various, some implying it perhaps doesn't do anything?

To clarify - I use no Reshade or anything - and it also seems to be affected by lighting conditions. I'm playing another training mission that starts with the rain and the same panel looks much better this time. Although some "ghosting" like stuff still appears it is much less annoying and very subtle this time. This picture is quite zoomed in - which makes it more obvious (and worse), but it's definitely more 3D this time and less about "sharpening" effect. I still think it looks artificial, but I just wanted to clarify why it may not be as obvious. It's light-dependent. (Some extreme bump mapping, perhaps?)

Thanks for the response. The problem with current execution is not only realism - but the resulting effect looks more like TV ghosting than anything realistic. Or like an outline in games such as Borderlands. It's really ugly.

My first example seems to be a very strong manifestation of some "engine" thing that can be seen also in good weather. Just today, without actually thinking of this problem, this is what I noticed when I was looking around the airport with a bit of zoom out: You may not see it at first, but it's pretty obvious when you accidentally focus and zoom at it - and it also depends on the clouds around the "seams". Instead of highlighting the lines I made circles around the points where three lines (seams) connect plus a few arrows to point out one of the seams. I have no idea whether this is a new phenomenon, but I haven't encountered it before the fog update (which I generally like except for the fog being global height, but hopefully they will fix that as well, but it may be completely unrelated).

Just to clarify - what is the source of your picture? Is it a real plane, just zoomed in? (Because I see some pixelation, I'm not sure.)

I generally like the new F-5 cockpit, but there was something that was bothering me about it and today I found out what it is. It seems like the textures are over-sharpened (or whatever else processing with similar effect) - especially around texts. I assume the text has some texture, perhaps it's etched or what, but look at it: The black contour lines around the text are clearly visible. And close up: This is even worse, it looks more like a cartoonish game. Many elements don't seem to suffer from this effect. E.g. the knobs seem to be OK, pedals are also fine, but the text is funny with the outlines. What do you think?

That's what I'm reporting - skipped triggers in the training mission for MB-339. It has nothing to do with server or MP, so no, I haven't tried. The training mission is faulty.

Recently, I was involved in scripting duties for a racing mission. You can try these missions online if you check "Black Angels" or "AirRace" in the server list - a helicopter and a warbird flavour is available. (Here you can also get the missions from your track file, but perhaps we will have a link as well.) Originally, the mission was full of triggers for each zone (there is a racing zone, kill zones and check zones you have to pass) and each player and it was also difficult to make it work for all clients independently. Imagine adding a new racer unit to a mission and setting all the triggers right. I said: "Hey, I can script a bit in Lua, I'll try to do a script for all these duties." The result is published here: https://github.com/virgo47/dcs-files/tree/main/mission-editing/scripts/air-race It supports both single and multi player, multiple players racing at the same time, and many other features. When you need a new racer, just add a group with a known (configurable) prefix. Add new killzones at will (with some prefix), or more checkzones that need to be passed. It also has a sub-second approximation, although the races script loop runs only once a second. And restart "voting". Altitude checks. Option to either kill unit or just softly disqualify it if it's out of bounds. And more. And I talk about all this in the following video: Merry Christmas to everyone and all the best to the New year!

This encryption is wrong on so many levels... The modding community is a strong point for DCS. Does it mean ED now doesn't care about it? Do they hide something? I've heard that the cockpit is virtually the same as before and doesn't warrant all those thousands of hours ED claims. I don't know, and ED does everything so we don't know. Many things for control tweaking are easier to discover in the Model Viewer. I just don't get it. Will we have some Model Viewer 3 supporting encrypted modules, or will DCS close more and more for us? Will we soon get to the point where we are not able to add the bindings that are missing in the modules (pick any)? Just extrapolating...

I was playing a MB-339 wet takeoff mission and decided to go up after the takeoff - and to my surprise I got this on the edge of the clouds: This is with a maximum zoom-out, but ht was pretty obvious, it looked like some sci-fi shield thing.

After a while, probably the first time after a few patches I got into an A2A mission, training mission. There was an Il-76 5 km ahead of me, and I had serious troubles to find it in the sights with zoom. It was partially a color/lighting thing, but I can't believe in real life I'd not see such a big thing when I looked at it directly. No simulator will ever be 100% realistic in this matter - the only question is how well it translates the reality to a screen (in my case 1440p). 2D screen is especially challenging as there is no stereoscopy, so if the colors blend, we're screwed. Of course, VR has its own set of challenges, there is a resolution-vs-visibility discussion for monitors, etc. It's not an easy problem. It is a matter of practice as well, especially when it comes to "spot" a moving dot. But when there is no dot to see, no shimmer, no movement, nothing, not even when you look straight at it, it's objectively not good.

It is described on the linked User file page: The panel default values are prepared for the cold setup, use the auxiliary RESET button in the top row to switch the panel switches to the "hot" setup. This does not change anything in DCS, only the Touch Portal button states. The thing is that when you enter the cockpit, not all values are sent to the DCS-BIOS->COINS->TouchPortal, so some of the buttons are stale. This RESET button simply flips between typical hot and cold touch portal presets - not for all buttons, only the typical ones (e.g. generator, battery, etc.). Most typical usage is to tap it once when you enter a hot/airborne aircraft - which is Reset Buttons to HOT.