Brisse

Thrust vector control helps the missile turn at a very high angle of attack which helps point the nose of the missile so that the seeker can stay on target. It's the sum of the gimbal limit and the angle of attack that matters, not just the gimbal limit on it's own.

Они сказали, что они загружены Cy-27 только с P-73, потому что это тяжело решать ее с полным снаряжения. Сy-27 является более опасным, и каждый знает, что. And by the way, this is the English part of the forums :)

No. It will update automatically next time you launch the sim (1.5.1 open beta).

No words from any devs. I wonder if they left the office thinking that they had uploaded the update, but forgot to do so? :)

Single engine fighters usually have higher reliability requirements on the engines which is taken into consideration both when constructing the engine and when maintaining it. It's not uncommon to see zero mishap rates for single engine fighter these days.

Not a bug. The update is not live yet. There's already another thread on this subject.

It's convenient that they share anti ship missiles with the Viggen :)

Naah. I think they would have mentioned in todays newsletter of they were to release today. I'm guessing next week...

We can't say that for sure yet. There are often fixes that aren't mentioned in the changelog.

Instant buy. Let's hope they can make something out of this :)

I don't think it's live yet, as mine isn't updating either. They often post the change-log early and then update later so let's just have some patience.

"Updated Magic II and Super 530D performance." http://www.digitalcombatsimulator.com/en/news/2015-12-11_DCS-1.5.2/

Hahaha! That sure lightened up the mood :)

Add weight and drag to that and you will be able to make some calculations yes. It's pretty basic rocket science. Ever played Kerbal Space Program? :)

I'll chime in and try to answer that. Missiles in DCS are using an advanced flight model. They are not scripted to reach a certain fixed speed or anything like that. The missile has weight, drag, lift and thrust etc... and the physical forces are simulated in real time. Under these circumstances the answer to your question is obviously YES, the speed of the launch platform affects the missile in a manner that is realistic. It has to follow the laws of physics.

Actually, some of the stuff RadeonPro does will permanently mess with your driver, even after it is shut down. That's why it's so dangerous to use with the newer drivers. The only way to make sure RadeonPro has no influence is to uninstall it, then uninstall the driver with a tool called DDU, and then make a fresh install of the latest driver. AMD marketing department like us to believe it is completely new, but that's not really true. It's just another update to the old driver, but with some new features and a new UI. Otherwise it is just the usual bug fixing and optimization that we have seen between different versions of Catalyst previously. Feel free to try old versions if you want. I suggest you use DDU to uninstall the current driver first. The AMD uninstaller does not do a great job which has caused me problems many times in the past.

That could be caused by RadeonPro. Sounds like you have the adaptive v-sync option enabled. That would result in v-sync being off as long as the framerate is under 60, which it is permanently in your case since you are limiting framerate using FRTC. You mean you want to go back to a driver that was released while RadeonPro were still being developed? That's a bad idea, because the drivers have become much better since then, with major improvements in functionality, stability and performance. To be honest, the AMD graphics driver was pretty crappy back then. Sadly no, but I don't see much use for RadeonPro any longer. The only useful feature I can think of is adaptive v-sync. Personally I don't need that since I have a freesync compatible monitor now, so I don't have any use for RadeonPro whatsoever. I which they would add adaptive v-sync in their driver like nvidia did. It would be nice for those still running fixed refresh rate monitors.

Impossible, because the 530D doesn't exist in any of the public versions of DCS yet.

That is so far from the truth, but I guess you are talking about a specific time period? If we look at all time periods I can count five or six fully simulated dogfighters, depending on if you count the MiG-21bis or not.

Wow! Good work. I've been looking for this but found very little. Most of the stuff out there on the internet is about the PS 46/A used in the JA, which is completely different.

So NWS is switched on/off automatically based on speed? Is it possible to switch it manually?

Looking good. The reason that some people get upset I think is due to having wrong expectations. Simulators from the 90's and 00's had missiles that didn't follow the laws of physics and therefore they performed too well. That has influenced people's expectations of what missiles can do.

It has an entry in the steam database since a while back. Maybe 2016 is the year we have all been waiting for? https://steamdb.info/app/411950/subs/ I bet sith knows more, but he's under NDA... :music_whistling:

Wouldn't GMTI require a doppler radar?

Just a quick tip Gunnergolly: RadeonPro is sadly not up to date. Development stopped a long time ago, which means it doesn't support current AMD graphics drivers. It could lead to incompatibility issues, and cause more harm than it's worth. As for v-sync at half refresh rate, just turn on v-sync and then set the framerate control to any framerate between half and just under native refresh rate. The result is the same as if you would have a v-sync half refresh option enabled. It's just not as intuitive.