**MiG-21 Changelog 5/2/2016**

[BadHabit]

Allowed? Oh dear.

 

If you want a 100% consistent and up to date changelog; go to our bugtracker. Generally expect any fix that is marked as resolved there to be available within the next two releases.

 

We don't have the time to accurately track every fix and into which branch they were released.

 

Nobody wants to be pain in the ass Cobra.

DCS has a big variant so far of Modules, all of them piece of art and the Mig is no exception, it's the one we enjoy and have big interest in.

The bugtracker is a good tool but is also (my opinion) a mess. We need that changelog posted in every update in the ED's Update page like Razbram is doing.

I am not complaining about the Mig being slowly fixed step to step. It's something i believe everyone understand and respect, that the workload is huge.

Having no time to write and post the changes is no excuse sorry. We are customers and we deserve the update on our browsers.

It's a first come first served business and the Mig-21 is your first so don't leave it behind :thumbup:

[Harle]

Allowed? Oh dear.

 

If you want a 100% consistent and up to date changelog; go to our bugtracker.

Generally expect any fix that is marked as resolved there to be available within the next two releases.

 

We don't have the time to accurately track every fix and into which branch they were released.

 

No one was asking for meticulous accurate reports on current progress.

I just want to see Mig-21 section in changelogs. Because when I don't I tend to think "No fixes for Mig-21?! WTF have LN been doing when other guys were fixing their planes?!"

This is the only A/C I care for.

Most generic and concise notes would suffice for the changelog.

[probad]

We are customers and we deserve the update on our browsers.

Damn, who put you in charge here?

 

Convenience is as convenient as your routine, so:

-Dedicated pilots keep up to date with the bugtracker because it's part of their routine.

-Forum regulars like changes posted in the forums because that's their routine.

-Offline players want it delivered right into the client because the client is the only thing part of their routine (just for example, all the people suddenly popping up asking about the aileron booster when it was already documented on the forums).

 

These are all different interest groups and it is LN's prerogative to choose who to cater to. You don't speak for all of us, and you are not the only customer LN has.

Edited March 12, 2016 by probad

[BadHabit]

These are all different interest groups and it is LN's prerogative to choose who to cater to, you don't speak for all of us and you are not the only customer LN has.

 

I don't understand why you are defending and who. And i don't like your attitude but i am going to skip that and no fight here.

I am not speaking for anyone i am speaking my opinion and i can use my words as i see fit.

I am asking for changelog updates and i am rightful to do that. It is a product, i paid, i see changes and i want the changes to be shown in public.

[Harle]

You don't speak for all of us

 

2 against 1

You seem to be a minority so far.

[probad]

okay i had issue with you trying to push your desire through under the guise of representing the entire mig-21 playerbase.

 

because there are customers like me who are okay with the current system and would rather like ln to spend their time more on actually working on the software than making my life more convenient.

 

2 against 1

You seem to be a minority so far.

there's always going to be forumer interest majority on the forums, who would have thought???

but dcs: mig-21 is bigger than just the forums.

Edited March 12, 2016 by probad

[Harle]

okay i had issue with you trying to push your desire through under the guise of representing the entire mig-21 playerbase.

 

because there are customers like me who are okay with the current system and would rather like ln to spend their time more on actually working on the software than making my life more convenient.

 

 

there's always going to be forumer interest majority on the forums, who would have thought???

but dcs: mig-21 is bigger than just the forums.

 

But sir, would you like the devs to get pissed on for failing to do the work that they actually did but forgot or neglected to notify about it having been done?

[probad]

i see it as my responsibility to learn about the plane i fly. discovering changes variously through testing or the bugtracker is no different than doing research in books or the manual.

 

in fact i feel the process of discovery only serves to enrich my experience.

 

that is my own outlook on it and you are welcome to yours as well. but what i want to express is that i feel the choice should be left up to leatherneck, not up to some kind of democratic process. i actually couldn't care less if leatherneck wants to deliver patchnotes to forum, or if even they deliver it straight to the client, what matters is that it is leatherneck's choice to do it.

 

i don't want democratic process because i bought and support leatherneck, because i like their work and philosophies; i did not pay for or care for the opinions of this community.

Edited March 12, 2016 by probad

[Harle]

in fact i feel the process of discovery only serves to enrich my experience.

 

Suit yourself. If you enjoy discovering broken systems so much.

[gospadin]

The one thing that's missing (IMO) is an "official" confirmation of bugs having been resolved as of a particular publicly-available version of the simulator.

 

When the issues in the public tracker get resolved today, there's a comment like "fixed locally, should be in 1.5.4 or 1.5.5 release."

 

What I think most of your users/testers/enthusiasts would appreciate is if developers could post a confirmation message after an ED update, saying "Confirmed fixed with ED's 1.5.3.51171.34 beta release" or similar.

 

Making sure the tracking comes full-circle, instead of ending with "fixed internally" as it seems to do today, would help clear up a lot of the confusion around the public tracker.

 

thx!

--gos

 

(At work, we use a "fixed pending validation" state to indicate it's fixed internally and has been released, but we don't actually mark a bug resolved until a public release that includes the fix has been validated by our test team and/or end users)

[EEch]

For some reason i can't set engine power above 80% so i can't use afterburner, anybody know why?!

[BFBunny]

You need to turn afterburner on. There is a switch nr throttles nr apu switch. Set to up.

Edited March 12, 2016 by BFBunny

[EEch]

You need to turn afterburner on. There is a switch nr throttles nr apu switch. Set to up.

 

Thanks for answer but it's not work (try both up and down). Look like throttle just don't move above Maximal.

Edited March 12, 2016 by EEch
none

[probad]

pls delete

Edited March 12, 2016 by probad
offtopic

[NeilWillis]

Have you got the axis set up for the throttle working correctly? Open the settings, then controls, go to the MiG-21Bis, select Axis Commands in the drop down menu, then select the axis for the throttle under the correct controller column.

 

Click on the axis tune button, then just see if you have full travel on the curve. I'd select the slider option, and then adjust the dead zone so the two red dots just meet at the baseline when the throttle is wide open, but not in the afterburner detent position.

 

That way, you will go to full military power when the throttle is at the stop, and then it will go into afterburner when you proceed into the afterburner detent.

[BadHabit]

Have you got the axis set up for the throttle working correctly? Open the settings, then controls, go to the MiG-21Bis, select Axis Commands in the drop down menu, then select the axis for the throttle under the correct controller column.

 

Click on the axis tune button, then just see if you have full travel on the curve. I'd select the slider option, and then adjust the dead zone so the two red dots just meet at the baseline when the throttle is wide open, but not in the afterburner detent position.

 

That way, you will go to full military power when the throttle is at the stop, and then it will go into afterburner when you proceed into the afterburner detent.

Guys you are off topic. PlZ post at the proper subforum.

[NeilWillis]

Guys you are off topic. PlZ post at the proper subforum.

 

Hard to answer the question in a different forum to one in which the question was asked. Maybe you'd have been better suggesting this earlier, or simply asking a moderator to move them all?

 

Just a thought.

[BadHabit]

Just delete

[iggi]

i have problem with afterburner too i only get 80% power and when i press F2 my scenery is blurry and that happend after last update 1.5.3. Any help pls?

[Art-J]

Blurry scenery is most likely caused by "depth of field" in game options. It might've been reset after last update. Turn it off again.

 

As for the afterburner, it seems to be bugged for some players - If You use keyboard to operate throttle, You have to wait for the official fix.

[iggi]

ok i turned off depth of field and that worked out and thank you :) Yes i use keyboard :( i hope they will fix it. And i see some other things dont work but i will wait next update and i hope they will fix it. Thx Art-J.

[simapajik]

What MiG-21 actually works? radar does not work, flares are not working very bad .. bad .. .. module is useless to fight the non-use .. prefer to move to another module .. which will also work. improving DCS = return to the working version 1.2.16. More and more errors.

[Nooch]

And flood lights still haven't been implemented if I'm not mistaken...

Edited May 5, 2016 by Nooch

[sideshow]

I don't have any engine sound on external views since the last Open Alpha update. In F10 view it show's my engine at 0% and no sound. However, the engine sound works inside the cockpit. Anyone else having this issue?

[Art-J]

^ All of us. It's a known issue in 2.0.2. Wait for the fix, or fly in 1.5.3 instead.