Hiromachi

Yes. We're working on a less sophisticated rather screen picture, with less clutter presented on the screen. I'm not sure if it will come with this, most likely with a next, major update for the DCS. It's still WIP. Of course, its only temporal solution.

Maybe it is apples and oranges, maybe it is not. I would assume that like every other manual I've seen, Viggen documentation would have a separate section focusing on structural and flight limitations, not only indicating the speed limits but also reasons why they are there. For now all I've seen is just number - 1350 km/h at lower altitudes. But if someone can point to a specific page of manual where this is explained, it sure would be helpful. And sidenote, TLTeo, you are wrong in regard to MiG-21bis. Or half wrong. MiG-21bis flight characteristics manual indicates that there are two speed limits - Mach 2.1 in general and Vne of 1300 - 1350 km/h indicated at lower altitudes. Speed limit at low altitudes (up to around 10 km) based on instrument speed (indicated) is dictated by structural limitations of the engine. And it always was, be it for R-11F2-300, R-13-300 or R-25, all were unable to withstand airflow pressure (although at different speeds, for example R-11F2-300 was limited to 1100 - 1200 km/h). Especially the first stage of compressor, the blades and afterburner chamber which reaches thermal limit. The flameout we have in game is likely the best scenario pilot would expect. If engine was run for longer periods near the limit one could expect even a permanent damage. The Mach 2.1 speed limit on the other hand has nothing to do with airflow but with directional stability. Or lack of it at this speeds. In early tests MiG-21 exhibited directional instability over Mach 2.05 and would become uncontrollable to a significant degree. After MiG-21PFM when tail fin was enlarged, aircraft gained in that department and limit was lifted to 2.1, although I dont think any real life tests were specifically conducted to test the limit as credible sources (i.e. a number of pilots) exceeded that limit and pushed aircraft past Mach 2.2

As a matter of fact he is. If I'm not mistaken he has Master Degree in Aeronautics. So he has some qualifications to make claims ;)

So let me ask you this: What do you think should be happening and what do you base that on?

Yes, Im waiting for some artwork to be done to be able to show you. Hence the delay.

I fly in VR. And if I cant ID, than I hold until I get closer. Solution is not F10, solution is between the eyeballs.

It would do absolutely nothing to stop teamkills because we dont have any long range missiles. We have short range rear aspect IR missiles so adding ability for users to check whats around is not the way. The way to do it is to learn to ID targets. Personally I dont even see how one would be switching between F10 and F1 when in furball...

Because its not a casual server.

No, we were not doing well. People werent even interested in RED team in contributing. Someone was on SRS discussing the point of flying helo (or anything else) and capturing airfields, cause it will just roll the mission. Plus Alpen wasnt even doing GCI. He was driving Abrams near Fujairah.

So I was wondering what is the status on this issue. I had today another (its a common issue I see every flight vs the Viggen) damage model quirk. Managed to sneak behind Viggen and launched R-13M1 which detached his left wing and started smoke on him. Viggen disregarded that and proceeded to turn after another MiG-21, outturning him and launching a missile. In the meantime I put 1-2 rounds into Viggen fuselage, but that did not make Viggen abandon MiG. So I got behind Viggen again and launched R-60 into him which hit. He launched 2nd missile in the meantime. Finally I put some more rounds and he lost right wing: At this point he decided that its time to go home. And he flew back (you can see his smoke trail to the right of the center). Not sure if he made it since Tacview looses tracking ability after first missile hit:

I will forward this Tom, thank you for the report ;)

In reality this aircraft is not provided with with autopilot. As explained it was added for reasons above. And as such all inputs are negated. The only difference is that animation for rudder works and so you see rudder pedal movement. So the only issue here is the animation for rudder pedals. Nothing of the aerodynamics nature.

Cadillac of the skies ?

This isn't a bug. This module is provided with artificial simple auto pilot for users willing to familiarize themselves with the cockpit in flight or enjoy landscapes. Thus it takes all controls off the pilot hands, including the rudder.

Yes, Phase I which was scheduled for this year was comprised of shape changes. Phase II which is mostly focused on complete rework of the textures will take more time.

No. During pandemic it is hard to organize anything outside :/ But we're looking into that.

Phase 2 will focus on completely new textures. But that is something that requires going beyond drawings and pictures We would actually like to scan a MiG-21 cockpit.

Look up. If you see difference in position and shape of gunsight and mirror than yes, you see updated cockpit.

Thank you for the offer. I have ASP manual in Polish and Czech language. Just need time to review it in detail.

Ok Kow, will forward it to Dolphin. Thank you for reporting ;)

Dear K-51, I'd like to be added to the list as well. What is the average waiting time this days?

Those were my latest words Schmidtfire: https://forums.eagle.ru/showpost.php?p=4496974&postcount=41 I will be testing a few reported issues over the course of the weekend and will ask if there is any update on the radar issue.

Whats wrong with nukes ? :pilotfly:

Alright, I'm going to look into that and forward to Novak.

I've said in the other thread that we are preparing a development update for F4U Corsair and F8U Crusader. It will be released in a couple weeks so you can see the progress :)