XPACT

In the provided track it was more of a show off that it can even beat the video since it took exactly 15.509 seconds to finish 360 degree turn and it wasn't perfect by any means. I did pull more G's than I would like at the beginning of the turn but with my current setup, sadly, I don't have required precision. With better control, lower AOA hence lower maximum G's, you can do perfect circle with minimal speed loss (entry 750km/h and exit at around 650km/h) and do it in 16 seconds guaranteed because I managed to do 16.5 and saw many parts of the turn where I could improve it, at the end of the day it just requires a good setup and skill. https://www.youtube.com/watch?v=Npkd-gIalz4

Haha no @Ironhand I was refering to his comment forgot to quote it

I have no reason to lie about my achieved turn rate especially considering my bias towards Russian aircraft hehe As you said it is showing off competition so pilot is skilled and will pull high G's to acomplish it. In the video it is evident that he lost a lot of speed at exit so here you go, high speed high AOA lower speed at exit, I lost only 25m of altitude. Time taken depending on how you measure is between 15.5 - 16 seconds MiG29turnrate.trk

We don't know any info regarding these videos... altitude, fuel, speed. But obviously he is not carrying anything, probably has low amount of fuel and is doing full afterburner so with that little info we got I just tried doing "sustained" turn at 750km/h, 500m altitude, nothing on the wings and 1000kg of fuel, AOA was ≈15.5deg, ≈7.5g full turn was acomplished in ≈16.5 seconds and exit speed was around 690km/h and I lost around 15m of altitude in the process. Now with better skill (I wouldn't consider myself overly good) and equipment I think you can actually get scary close to the measured time in the video atleast in this configuration.

I Agree

Great post, MiG-29 definetly needs some developer love. There are many FF modules being worked on currently and I don't think they will check FC3 planes anytime soon but we will keep making noises here Only one thing I would add about cockpit lighting. It would be phenomelan if flood lights can be separate keybind from instrument lighting, of course brightness control would be nice but that is stepping into FF feature set I guess.

Exactly, it was a question to @draconus

I know it was working fine when I flew with MiG-29 in the past but that was quite some time ago, so I don't even know which update broke it in the first place.

Real question is why would radar switch to "continuous" illumination in HOJ firing mode as that's the only way how target aircraft RWR can detect lock, how does it precisely find target elevation and if it can why it isn't showed on the HUD then? Missile launch detection is different beast entirely and is sadly very simplified in DCS. Obviously ECM is implemented arcadishly and even tho it is true that ECM is hard topic in a sense of circuitry engineering, simulating various electronic warfare methods and dividing them into corresponding adequate timeline and aircrafts is possible, but main problem is that there's no way to get the data of how effective something should be at specific distances and various conditions, not to mention aircrafts of different eras facing each other (newer jammers could for example render older aircraft radars completely unusable at any distance). Then again that raises the question is it better to have simple system that is more or less arcadish like we have now but more or less equal for everyone or have realism orientated one with developers having final word on their effectivness in combat? I would choose second option simply from the fact that DCS shouldn't be about balance and multiplayer PVP it should try to as much as possible simulate old/modern combat vehicles and their systems. But I also know that there's a lot of folks here who will disagree with that.

Wrote it in FC3 bug thread but it seems pretty inactive. So I will repeat it here in the module subforum. MiG-29 A/G/S happens in both latest versions DCS 2.5.6.61527.3 Stable and DCS 2.5.6.61527.3 Open Beta Speed indicator (IAS) in cockpit is bugged for me, it always shows 1 instead of blank when under 1000 km/h so now speed reading is 1000 + current and if current speed exceeds 1000 needle just stops. HUD indicator is working properly.

MiG-29 A/G/S both latest versions DCS 2.5.6.61527.3 Stable and DCS 2.5.6.61527.3 Open Beta Speed indicator (IAS) in cockpit is bugged it always shows 1 instead of blank when under 1000 km/h so now speed reading is 1000 + current and if current speed exceeds 1000 needle just stops. HUD indicator is working properly.

I don't usually quote wikipedia as valid source of information but these are straight up facts. Second Chechen War "Ka-50 took part in the Russian Army's operations against separatists in the Chechen Republic during the Second Chechen War. In December 2000, a pair of production Ka-50s arrived to the area. With the Ka-50s was a Ka-29 to provide reconnaissance and target designation. On 6 January 2001, the Ka-50 used live weapons against a real enemy for the first time. On 9 January, at the entry into a mountain gorge in the area of a settlement named Komsomolskoye, a single Ka-50 accompanied by an Mi-24 used S-8 unguided rockets to destroy a warehouse full of ammunition belonging to Chechen insurgents. On 6 February, in the forest-covered mountain area to the south of the village of Tsentoroj, the strike group composed of two Ka-50s and the sole Ka-29 discovered and, from a range of 3 km, destroyed a fortified camp of insurgents using two "9K121 Vikhr" guided missiles. 14 February, saw a similar strike group carrying out a "hunting" mission in the area of Oak-Yurt and Hatun. In difficult conditions, pilots found and destroyed eight targets. These missions tested the type's airframe, as well as its on-board systems and armament. Its successful performance in difficult, mountainous terrain once again confirmed the usefulness of the many advanced features of the Ka-50's design, including its power and maneuverability." Andrey Fomin. "Kamov Warriors". Combat Aircraft, July 2005. Vol. 7, No. 1, pp. 64–73.

Not talking about helicopter turbines, there is really fighter jet mixed in when using external views like it is constantly flying somewhere around you. Best way to test is use F3 camera and wait a bit when the helicopter passes, you will clearly hear generic fighter jet sound soon after.

Works for me, both in the world and shkval screen Pictures provided are with 1.6 and 2.2 gamma settings when viewed from outside both single and multiple rockets And in last two pictures (shkval demo) you can clearly see lights in the sky and tree line on shkval screen but when they go out it's pitch black

Yes indeed the scale seems to be shifted, not sure how I didn't catch it immediately tho :doh: If you for example set QFE by airport instructions (or look at the briefing) it won't give you 0 altitude instead everything is shifted by X amount It is shifted for around +6.5mmHg :joystick: EDIT: Isn't Mozdok at altitude of around 135-140m? that would fit in perfectly with both QFE and QNH being off by +6.5mm?

Hmm not sure that I understand the issue, seems to work as expected for me, tho in my opinion black vertical line that shows current position should be thicker. These are with cockpit lights on, black line can be seen without lights also but it's even harder EDIT: also the barometric altimeter scale pressure (mmHg) to altitude (meters) is accurate since in these pictures difference in altitude should equal to around 70m and that is exactly the case

GGTharos I just love how confident you are that it's impossible since Russian radar in question is inferior to its American counterpart as like you developed both of them and did field testing... Not saying that it did happen but it wouldn't be the first time military technology didn't work out as planned and won't be the last either that is why it is always evolving and adapting. Also anyone who describes radar technology, electronic warfare or any aircraft sensor as "it's simple stuff you just need to pull this switch press this button voila" has no idea what he is talking about and that I guarantee. Almost all here can understand them on basic level and their usage but to really understand how it operates you need extensive knowledge on the topic even for the ones considered "simpler" in operation. Before people start bashing me I must say that I never worked on development of such systems but I am quite familiar with the topic from studying physics and my electrical engineering degree so I know thing or two. One more thing that was already mentioned, sadly DCS sensors send perfect data which almost never occurs in the real world but modeling such inaccurate data is probably too much work at this point and on top of it even if implemented would make many people angry because of the quasi randomness of it.

Fiddling with many ABRIS options I found out that if you try to change current date DCS will crash to desktop every time. Also worth noting is that ABRIS will also give you invalid input choices, it does the same for time setup but in that case if input is invalid it just resets to previous value. Not sure if that is intended but doesn't seem logical from programming standpoint to offer user to input something invalid in the first place :music_whistling: but maybe ABRIS software engineers don't share my opinion :D Btw ABRIS software/hardware failure in mission editor also doesn't trigger/work.

I hope BS3 will also add functionality to the cockpit since honestly almost all if not all switches should have proper function which is not the case and considering how complete Ka-50 is at the moment it should be achievable and finally called true full fidelity module, just my opinion, but sure those minor annoying things like vector characters on the HUD are priority to bump the overall quality feel

Oh well, lets hope they will work or at least show something in BS3 module

On my pictures it's the highest texture quality, anisotropic filtering x16, msaa x4

Many visible artifact for me also, other aircraft are fine. It is especially noticeable at night tho when zoomed in many of them disappear. MSAA is at x4 Steam screenshots are heavily compressed but nevertheless it can be seen easily. GPU is Vega 64 in case Nvidia users don't experience this EDIT: Now that I look at my pictures and ingame my cockpit lighting seems like 5300k cold white compared to videos on the youtube where it seems like it's 2400k incandescent lamp :huh: anyone else with this issue?

I know it's a minor thing but did they ever show any values? I like my gauges working especially when they are power related :joystick: :D

Oh don't get me started with Ka-50 they are unbearable, they break the immersion completely... Graphics team needs to wake up, it is better to have no reflections at all then fake baked in ones. Ok if they really want them in the game make it optional for all modules not just nit pick current popular ones.

As the title says jet is still powered on when all electric panel switches are off (not all systems but hud/displays/radio/lighting etc are still on) except if you pull canopy seal lever which from that moment starts behaving like battery on/off switch if the battery switch is left in off position. This doesn't happen on cold start you need to start the jet up and then set all power switches to off, it will still have power until you pull canopy seal lever. Only thing that comes to mind is if this is some kind of safety feature? Honestly seems more like a bug to me :music_whistling: EDIT: After more testing, canopy has to be closed and you don't have to actually start the jet, when the canopy is closed if you put battery to off, canopy seal lever starts switching battery on/off