zaelu

A. Multiplayer is small now because of lack of support. Single player is meaningless in the future. This point of yours (A) is like advocating for no food in a country plagued with famine because the people are skinny anyway. Let me put this in another way: Say DCS World has a market of 1 million people and 99% are "single player". If ED wants DCS to grow to 10 million people those 9 million missing are in multiplayer market. B. You confuse fairness with balance and symmetry or you are advocating cheating. C. If it would be like you say you wouldn't have people freaking out and asking for thread lock etc because someone asks for this feature to be default OFF and not default ON. Do you understand the difference? There is no need to explain it to you. Simply if it is the same... and you don't want to cheat and it's useless anyway (as it should) then it should be equal to you isn't it? But it isn't. You want it On for a reason. Exploiting. There can't be any other reason than this as it is a feature that: a) was never ever on the plane b ) it is suppose to be rubbish anyway c) if it glitches offers unwanted advantage only in Multiplayer as in singleplayer is plain useless. D: Mig21 is incapacitated in Ground attack role by some factors in DCS (ASP not fixed, Damage from unguided rockets and bombs not real, etc). But this doesn't mean all should carry nukes. The nukes on it are forbidden on most serious servers. Why? Because they are disabled by default. And the Mission Creator simple does not put them available on an airbase and voila! you can't take them no matter what. But for D2M is the other way around. The mission designer has to disable it manually for all the mirages in the mission. Same for other planes. You can't fix an evil with another evil. If MWS on A10C works not as on spec we have to have D2M on Mirage... where is the logic in that? I repeat. If it's useless and the same for you and you don't want to exploit it then it should be the same for you to have this option default disabled and you can enable it as much as you want for your awesome single player missions or servers. If is the same! Is it the same for you? If you want to talk about weak arguments the argument that "was promised" is weak. If a feature for such still secret plane was promised and then was discovered not to be real... should we still implemented and ruin the plane? Then why build those plane differently from each other? Let's all have F15C and call them Mirage or Huey if we like.

If is such a little trivial thing and same for you... Why not make it default "disabled"? I mean. Enduro14 can go to servers that have it enabled and Esac_mirmidon can simply check the box to enable it. Seriously. Would it be the same for you guys? Because if yes... then lets kindly ask Zeus when he has time to make it like that.

That's like proving god does not exists with a picture. :megalol: Also the argument of TomCatMucDe that other modules are not realistically depicted so this one should do the same, is weak. How about we should not ask more than FC3 level since we have half of the DCS planes at that level? The problem with this debate is that it just dances around the main point. Multiplayer fairness. The rest is BS. You can mod M2KC to carry anything even the so called Nukes from Mig21. It's not an issue. Having people cheering at this system with hearts pumping of emotion on how "cool" they will be in multiplayer with something unreal and arcade like but certain they will not be called cheaters is an issue. Game changer, game changer, game changer cried the folks, remember? Why would someone playing a single player mission be so excited about some system beeping unrealistically that an enemy F15C launched an AIM-9 from almost 12 O'clock?? What's the heroism? You can toggle radio assist and have Betty screaming missile 12 O'Clock high at you. Seriously. I consider this a pure lie or at least self-lie. You are fooling yourself. People want the edge on multiplayer and if the edge is a feature that would be called Arcade or Cheat normally, but being justified by some convoluted logic suddenly is fair and to be accepted. This system will never be used where supposedly it niches. Avoiding manpads. No... it will be mostly be activated in multiplayer to offer a bit of hope in dodging enemy missiles. Stop pretending otherwise, nobody cares you dodge a SAM launch you visually missed in mission 27 of some campaign. And every time the system will be bugged by an update that will push it out of it's limitations its fan users will secretly cheer. But here... they try to act "realistically gentlemen". For me. This is a cheat. Like auto rudder and take off assist, etc. It should be default OFF not ON. Sorry to break your "I feel good about myself bubble". Merry Christmas!

Thank you!

Thank You const!! I use earbuds and that accidental bang bang bang bang bang is beyond any Christmas fun.

Thank you! Is it compatible with Integrity Check? edit It is! Super!

Very rarely an update deletes configuration inside game folder that are not compatible with what is saved in DCS/Config/Input forder from User Folder/Saved Games. And what is saved there it doesn't ever been deleted by the game. Example for A-10C Also the game does come with such configs for main joysticks/hotas. here: So I don't see the relation with reality of this problem.

I use (Opentrack 2.30 release) the default or almost default but with an PS3 camera and a IR LED arrangement similar to TrackIR clip Pro. http://imgur.com/a/fx9Q4

For me this doesn't look more real. There is good work in it but it breaks the spell some how. The trees and the noise1 textures in particular. The trees are bigger and more realistic than Starways thinner choice but they don't look like belonging in the game at all wile Starway's although thinner and breaking the idea of a true forest kind of blends better while still retaining a bit of usefulness in hiding troops or helicopters. The noise1 textures are very well done while looked in Photoshop but in game... somehow they become lifeless patterns.

Oh... sad to hear then. Yes I have them added not with scripts but with ME.

For me it works. You scared me. My entire squadron mission is based on this. :D

:D 14.9GB. But I think I don't have really a lot of them.

The duration might be OK. There are some moments during the mission when is silence (after talking with the tower and waiting for the double needle to reach 121), or maybe after turning to 121 when some of the info might be passed. The waypoint 2 can be selected early. It helps but at the final stage the workload can be reduced by it being already selected.. My main problems I think were related with the dash line and the square that can be confusing now because they are not very clear what they show, when and when the go haywire. Also not maintaining 6000 feet and then 3000 feet.

I managed to do it "cleanly" without getting lost. I changed the DEST waypoint to 02 before the actual moment of instruction because at that point usually I was handful. There are instructions about the altitude at some point but I observed them only at reviewing the movie file and not during the lesson. Cause I think is a bit of overload.

I thought it was one of the 2 subjects of this thread, release and precision. So I understand that the precision might be affected by the radar antenna behavior as described above?

If everything was so perfect then all the un-documented modifications on Mig21 FM since launch were what? The dev climbed in the cockpit with different mood in that day? Or maybe the truth is that DCS Mig21 is a lot of work and maybe some of it is still to be done? Here are some wise words (bolded by me):

Thank you for this SkateZilla!! :thumbup:

Thanks for the Skin folder Tip Rudel_chw!! 15GB of free space :D

I don't understand. And why if the range is to big the bombs are released carelessly when the pilot presses the trigger? You can squeeze the trigger when the cue first appears on the HUD or immediately before it passes the FPM... it will drop the bombs anyway when the trigger switch is pressed. Shouldn't it just abort the launch if that is the case?

I want to create a separate thread for this mission maybe others have different feedback on it. After trying the mission several times I managed to reach the airfield and land but only after getting terrible lost over the sea. After thinking about it I found some solutions for the minuses of the mission. First. It needs another mission for a normal visual landing with all the information explained. Where you should start your approach. What distance. What altitude. In the ILS landing mission you only say "keep this altitude". Not even... Hey look you are at 6800feet this should be your starting approach altitude and start descending when you are at x distance from beacon. What sink rate. Yes the Mirage is very smart and can make those for you if you just "activate chevrons" (kidding) but as a pilot you need to know these values anyway and they are not included in the current manual. Speed. When to reduce from 280 to 230 and what should be the touch down speed at current weight? Landing the Mirage currently is such a guess work. 230 is the speed when the gear lever is flashing. 120 is the rotate speed in the manual at take off so maybe 140 should be minimum for landing and when heavy the airplane hits hard even at 190. A lot of trial and error that shouldn't be necessary. Also in the milk is very hard to follow instructions when they are many and superimposed with the tower. Also instructions are not clear. The dash line is not pointing... it's tilted but has no pointing end or it's not described. The square doesn't stay on top it moves over the dash line. Also the square sometimes is misleading because it seems it tries to suggest hard turns instead of small adjustments and acts differently (has no triangles). All in all the mission is OK but because it's the first and only landing you get to train it's looking more like a dare than a lesson.

I had the same with Mk82 and I switched to GBU because CCRP is useless anyway for now.

Yes I know... we were 2 Mirage2000C yesterday and we had some targets to activate via F10 menus and we couldn't do it after take off with none of the 3 available radios. VUHF, UHF and Simple \ Radio.

The program is still Open Source AFAIK so you can download the code... check it then compile it for yourself. P.S. I used avast on many PC years ago but now is just garbage... for me (always trying to sell something more, false positives until you lose faith).

I tried your edit and it works but if I chose ground commander first the F10 radio becomes invisible the F10 men is not active and after I join Su25 it remains inactive. If I join Su25 from start it s active and correct. Also. The bug is present only in Single Player. In multiplayer I encounter a bigger problem with the radio being completely inactive via keyboard (only if the unit has a clickable ptt radio button you can make it show) and the external views messed up and not working (I think this is a new bug introduced with latest update and reported but it becomes a mess when mixed with the one in this thread. For example radio is available only on the ground and once you took off radio does not work as the external views are not working. So to activate some units via F10 menu after take off is impossible.

How is that briefing generated? It shows only one of Maykop frequencies. 254MHz is a valid one but not the only one. And is 125 not 127.