All Activity

Why do you think so?

Сталь, алюминий, бакелит и пластик покрашенный одной и той же черной масляной краской выглядят по разному потому что дают разную реакцию на свет - отражение, поглощение, у пластика подповерхностное рассеивание. Physics Based Rendering не просто так так называется. Иногда ходожники забывают о разнице реальных материалов прототипа и бросают один материал игрового движка на поверхности из разных металлов. Например бывает бросают 1 рафмет на приборку(которая из листа алюминия) и безели и циферблаты приборов(из стали). Когда это правится, кабина становится "живее" и "объемнее" при тех же текстурах что были.

On September 12, 1988, a group of MiG-23MLD from the 120th Fighter Aviation Regiment took off to strike targets in the Kunar River valley east of Asadabad. The Pakistanis were showing increasing activity, and the pilots repeatedly reported "visual contact" with F-16s escorting the strike groups from their side. The tension was literally hanging in the air, which erupted that day into an open clash. Gathering over a prominent landmark (Surubi Lake), the group headed toward the border. Two pairs of cover had gone ahead there in advance: the targets were right at the border strip, which is why two pairs of cover were assigned. Over the mountain range 50 km northwest of the attack site, the patrol zone was occupied by fighters of the commander, Lieutenant Colonel Sergey Bunin, and his political officer, Major Nikolay Golosienko, while Major Semyon Petkov and Senior Lieutenant Vladimir Danchenkov were located 40 km to the south. However, the F-16s, attracted by their appearance, were already in the air: from the Kamra base, a pair of fighters led by Lieutenant Khalid Mahmud from the 14th Squadron of the Pakistan Air Force took off, following the MiGs on a parallel course. Within minutes, they were informed from the ground that a column of aircraft had appeared in the air — a strike group was approaching the target. Over Kunar, it turned north, taking a combat course along the border. When the strike group formed a column to approach the target, it was only a few kilometers from the border, which the enemy took advantage of. The cover had gone quite far, and nothing prevented Khalid from reaching the middle of the stretched-out target. The closest to him was a MiG-23MLD (board number 55) of Captain Sergey Privalov, the outermost in the bearing of the second flight. Emerging 13 km from him out of thick clouds, Khalid heard his radiation warning station beep: the MiGs loitering a few minutes away were turning toward him. This was not part of the Pakistani pilot's plan. He began to maneuver, hastily firing two AIM-9L missiles from a half-roll with a 135° bank and exited the fight upside down 1500 m from the attacked MiGs. One missile went far off to the side, but the second Sidewinder exploded over Privalov's plane, showering it with fragments. The shock was severe; the pilot felt a strong impact, even his feet were knocked off the pedals. A large fragment entered the rear cockpit compartment half a meter from his head, the others slashed the flap and left wing panel, piercing the fuel tank box. A whitish trail of fuel trailed behind the plane, but after the initial shock, the pilot confirmed the plane was not on fire, remained airborne, and responded to controls. Both pairs of cover rushed to the scene at full afterburner, and shouts and curses rose on the radio. The Pakistani pilot faced serious trouble — the firing range of the R-24R missiles was enough to hit him even before the border, and on the ground, someone even shouted: "Let me shoot him down!" However, the score could not be evened — the command post ordered everyone to urgently withdraw, fearing a fight over a remote area where the situation was unfavorable: the enemy could bring in new forces, and the MiGs had limited fuel reserves. The Pakistanis had all the advantages here, from numerical superiority to tactical situation, and an open clash with a neighboring state on the eve of the long-awaited ceasefire was undesirable. After dropping bombs, Privalov turned homeward, followed by the rest of the group. Bunin and Golosienko closed the formation, and then a pair of F-16s appeared again from behind. The Pakistanis followed, intending to shoot down the MiGs in pursuit, but they could not catch up: setting their wings to maximum sweep, they accelerated to the speed of sound on afterburner (although with an external tank there was a limit of M=0.8). Approaching Bagram, the damaged MiG was allowed to go ahead to land first. It had almost no fuel left: judging by the fuel gauge, the plane had already lost 1200 liters of kerosene. Leaving a wet trail on the concrete, the fighter taxied to the parking area, where the leak stopped immediately after the engine was shut down — the fuel was gone. Petkov, who landed next, got out of the plane and angrily slammed his helmet on the concrete: "Damn them..! I had that bastard in my sights!". Source: "The Hot Sky of Afghanistan" Viktor Markovsky

To add, I enjoy the Gazelle a lot, and it would be a shame for it to go away. After the resignation of most, if not all, of the Polychop developers, I don't think the future of Polychop's modules are guaranteed, especially the Gazelle, when it comes to them being supported and updated. ED needs to make sure that Polychop (Sven) maintains this module and clarifies that he'll do so.

What resolution do you run your headset at, and are you using quadviews? I have to admit that I have not read or remember your other posts about jittering. Also - this might be a far stretch but I found this about jittering and Pimax AND Quadviews in MSFS 2024: https://forums.flightsimulator.com/t/image-shake-when-foveated-rendering-other-that-0-50-and-eye-tracking-enabled-on-pimax-crystal-og-wrong-resolution-division-when-fov-ren-scale-slider-introduced-in-su4/737911 Probably not the same thing. But, if you want, take a look at it.

I am glad you enjoy it. Fingers have been crossed!

Hello everyone, this is Shaft, from Myself Dynamic! As an active participant in the gazelle community, a day one fan of this historical module (one of the first 3rd party module) in DCS, and a livery creator for Polychop, I must say I'm 100% with what was written by @peeter It is not because the gazelle is a "niche" module that Polcyhop can act like if it doesn't matter, and we really need to get people at ED involved in this. There are guidelines, rules, commitment toward costumers, and some basic criteria are just not met by Polychop right now. We know for sure that not a single resource is dedicated to the gazelle, and this is a reality for over a year and a half almost.. There is a long list of easy fix that is just lying there and no one cares about it... Please, someone have to make it right. For the sake of the gazelle, and the credibility of both Polychop (and by them, ED...) Take care all

I already lost my favourite aircraft, the Mirage-2000 and now i'm loosing my favourite helicopter. It really breaks my heart to see what's happening to DCS. I hope this situation gets resolved soon.

Hey Avalanche, thank you very much. Sounds promising, I will have a look at it.

@BIGNEWY SSAO OFF does not work. I have turned SSAO off, other things ON/OFF - all kinds of variations. It doesn't matter. The SSAO "solution" I think first spread on Reddit, but in reality it is not an solution. Maybe it lowers the visibility for some, but not for me and others. How much testing has the developers put into this instead of repeating the "solution"? In Eagle Dynamics defense I don't think they are to blame for it either. It is a Quad views problem - but likely in combination with other things. The only thing that reduces the problem (for me at least) is turning sharpening in DCS graphic settings down. It does not go away totally but it becomes more playable. Certain scenarios and lighting conditions makes it more or less visible. I thought I got rid of it after turning down sharpening, but then - new tried a new terrain, new lighting conditions and there it was again... Also having a very small foveated region makes it more pronounced I think. For the record, my visible sqaure is not as dark as the original poster here. It is more bright. Also, other screen shots I have seen of this, in DCS Forums and elsewhere have brighter squares than in the first post here. Now, in MSFS 2024, Quadviews was implemented some time ago. And there they have discovered the exact same problem. And it is not just a Pimax Quadviews problem, but people using static quad views with Quest 3 and even HP Reverb G2 sees it too when activating Quadviews. I have also seen people with Varjo headsets reporting this. See this thread: https://forums.flightsimulator.com/t/quad-views-brightness-difference-in-clouds/715212/14 That thread started in April, but the problem still persists even in the latest beta for Update 4. Hopefully ED will look into it, and see what they can do on their part. SSAO OFF does not solve it. Certainly not for everyone. Never hurts to try, but we have to keep it real. My suggestions for those who are bothered with it: 1. Try increasing the Foveated rendering area 2. Try increasing the Transition thickness area Both of this will decrease perfomance so not an ideal solution. But perhaps play around with it and see what is tolerable. 3. Turn down sharpening in DCS Settings. Can give a negative impact with image clarity compared to what you are used to. But again, what is worse? Big square outline or loose some sharpness? I tried lowering sharpness in Tally Mouse Quadviews companion app too, but that didn't seem to have such an impact. Though I am not sure. So in summary - SSAO OFF is not the solution. This is not just a DCS problem - it is there in MSFS 2024 too when using quad views. This is not just a Pimax problem. Quest, HP Reverb and Varjo users reports the same thing. Certain lighting situations makes it more visible.

*cries quietly in trying to get stable, reliable, simming with DCS and the horrific afterthought that is Meta's idea of PCVR with it's Link software* Note to those who want to get VR - get something where the designers actually have at least 1% of a clue what PCVR is about and how people actually use their headsets.

В ИЛ-2 ещё замечательный эффект капель на фонаре, когда в облака залетаешь

I’ve been spending a lot of time in the CH47 recently and one thing that has stood out is how good the physics of the sling load cables is (at least when connected to a heavy object). Why can’t we have that for the SC’s arresting wires?

Nice! looks like recorded in VR?

Hmm you know that there isn't a AC-130 - there will be a C-130J Super Hercules at launch and later a MC-130J Commando II - but for now no AC-130

Hello in M01 it happened to me that during the enroute to the BFM training area Saint dives from 15000ft down to the deck (600 ft msl or so). After a while he climbs up again to 15k ft. During the climb he reports "speed and angels right". Restarted the Mission because I lost visual because of this unexpected descent and it happened again.

@OmasRachE If you haven't come across this already, you might find it interesting.

Something probably changed in the map which in turn altered the AI behaviour. Thanks for reporting this, possibly parking spot numbering was altered. Should be an easy fix.

РСЗО БМ-21-1 "Град" 122-мм (Россия). Рассматриваем, читаем характеристики. Смотреть видео.

The more I get into the mission building process, the more I wish they make it happen. Even that other sim is way more immersive when it comes to use radios and for me this is the biggest weakness of DCS.

Das JTAC Script hatte ich komplett vergessen ich werd Alt Danke dir Yurgon, denke das ist genau, was Jonny sucht .)

Adding the ability to add/remove hard point and suppressor using the rearm/refuel menu

No big deal, someone took the time to tell me. If you like to learn more about BVR engagements or other fighter tactics I can highly recomend joining a virtual squadron. There are many out there from the most casual bunch of sim pilots up to hardcore milsim dudes. And every one I got to know till now is very kind and supportive. It will boost your learning process like hell.

Ребят такой вопрос а при работающем gnirehtet шлем вообще должен пинговаться?