All Activity

Take Flight Events: Operation CHAOS THEORY & Server Raid Come fly with us during our next event "Operation CHAOS THEORY - Mission 1: Steel Glimmer" next Friday August 29th at 2300 UTC. Quick Synopsis Below. More Details and sign-ups are on the Take Flight Discord. https://discord.gg/takeflightdcs This Sunday at 2030 UTC will be our normal weekly event hours but will be a server raid on Gray Flag instead. Overview: In the aftermath of cascading global crises—economic collapse, famine, and the disintegration of international trade—regional conflicts have erupted into open warfare. Syria and Turkey imploded almost simultaneously: the Democratic Syrian State (DSS) rose from a military-backed secession in Syria, while in eastern Turkey, a Soviet-armed separatist faction declared itself the East Turkish Concordiat (ETC). NATO’s credibility was shattered when the ETC seized Incirlik Air Base with cutting-edge Russian armor, and now only heroic resistance in Hatay keeps the region from collapsing entirely. With Incirlik lost, NATO’s foothold depends on seizing and holding Latakia Harbor before enemy reinforcements arrive. Armored task force CHISEL will push from Hatay, but the route is heavily defended by DSS armor, SAMs, and SHORAD. NATO is deploying aircraft in three packages to support CHISEL's push. VULTURE Package must provide close escort and protect CHISEL through hostile fortified terrain, and direct CHISEL's movement. PUMA Package is responsible for suppressing enemy air defenses threatening VULTURE and performing airstrikes in support of CHISEL's advance. MADCAT Package is responsible for maintaining air superiority, blocking DSS aircraft from the southeast and ETC fighters from the northeast, should any intercede. Success demands speed, coordination, and precise inter-flight cooperation. Good hunting. Please note that this group is led by a group of flight enthusiasts, and none of us claim to be experts!

MiG-29A Fulcrum Intro video now live We just released the MiG-29A Introduction video for our upcoming DCS: MiG-29A Fulcrum. Also known as project 9-12A, this Soviet light fighter was designed in the 1970s, and entered service in 1983. This episode reviews the Fulcrum’s design and mission and its key features such as twin RD-33 engines, automatic slats, an all-moving tailplane, and 9G capability combined with high angle-of-attack flight. Paired with the Helmet-Mounted Sight and R-73 high off-boresight air-to-air missile, the Fulcrum is a deadly opponent in a dogfight. This video also reviews the planned weapons for our MiG-29A which includes the R-60, R-60M, R-73, R-27R/T, and R-27ER/ET air-to-air missiles and GSh-30-1 cannon. Our Fulcrum can also employ unguided air-to-ground weapons such as bombs and rockets. Although considered a 4th generation fighter, the P-12A does not include multifunction displays, but rather a HUD repeater screen, ‘steam’ gauges, and limited Hand-On Throttle and Stick (HOTAS) functions. Despite this, the MiG-29A is a deadly opponent in Beyond Visual Range (BVR) combat when armed with long-range R-27ER and ET missiles, and when operated by skilled pilots. Keep an eye out for the next chapters where we learn the steps to bring a cold and dark Fulcrum to life, taxi to the runway, and take off. Development Progress Development progress on the DCS: MiG-29A Fulcrum continues with much of the work focused on completing aircraft systems, the damage model, data transfer cartridge (DTC), skins, content, and bug fixing and tuning. We are also working on a large set of default controller input assignments to support several popular sticks and throttles. A 1st person pilot will also be available at launch; an often requested feature from VR pilots. It will also include ground equipment such as engine, intake, pitot, and louvre covers. We’ve been taking good note of the many MiG-29A skin requests you have made. At launch, we will provide the Soviet Union and Russia, East Germany, Poland, Kazakhstan, North Korea, and Syria. Many more are in the works and will be coming soon. Additional external modelling tasks being worked on, including highly detailed missile and bomb pylons and external fuel tanks. A version of the NS430 navigation system is also being developed for the DCS: MiG-29A as a separate download, and both English and Cyrilic cockpit and HUD options will be available at launch. Bye Phant

HIMARSы от currenthill в момент перезарядки остаются визуально разряженными (без крышки) и ракета визуально отображается только в момент очередного пуска (по аналогии с другой техникой, она должна появиться и только через некоторое время выстрел)

Bye Phant

Use this chart.

I think my super is arriving a bit sooner than expected... like tomorrow. I need some pointers are how to get the most out of this with as few mistakes as possible i dont have unlimited time. Everything was lined up and I was going to just follow the tallymouse setup for DCS but It looks like at least a good part of that is invalid now due to the new pixmax play software. 1) Do I use the new pixmax play or is that a waist of time? It sounds like it has some advantages but overall is worse... I dont recall anyone saying it was better overall. So im confused about this. 2) If using the latest PP software is indeed a poor starting point Do I use the version from tallymouse guide or is there a later version that is better? If I should be using the version from tallymouse or one that is compatible with his guide can you please link it? 3) is there some other route I should be following to get the best dcs experience out of this using DFR. Is there a guide for this route. I really really want to avoid another VR1 mess I watched that thing get developed for a year and a half and 2 months before it arrived I had a plan figured out and by the time it arrived software was updating and nothing worked, eyetracking was not great, open xr didnt work, steam was better but didnt support eyetracking which wasnt working well anyhow. I see that trying to repeat is self now but this time Im thankfully not the first and there is actually a functional community support on the forum here because more than 3 people own one. That larger community is more important than you might imagine at first... a never discussed pro. Thanks!

I'd say Mirage F1. It's more primitive than the M2000 but the same philosophy is already there. Plus, the upcoming F-1M will be similar to the M2000 avionics wise. Performance, naturally, will not.

Ok, first off, the game manual is early access too. I'm currently updating it, and will have all corrected numbers once I get the final numbers from the programmers Secondly, use the manuals dated 1 December 1952 or 1 June 1946. Finally, I was told to change the wall placard values to these:

Who said they won't?

Yes , but the airframes used in tests, sometimes pylons were removed, indicating "clean." No, use the one dated 1 December 1952 or 1 June 1946. Pay attention to the revised pages. Sometimes the new pages are in front of the PDF, instead of actually replacing the pages. Changes are noted by "delete" or thick black lines down the margins of changed paragraph sections.

just occurred to me to check the bios for hyper threading and turn it off. made no difference.

Does anybody knows if the mig29 is able to single drop a bomb in CCIP / CCRP ? For example I have a rack of 6 FAB 100 can I drop single by single or only once all. thanks for the help !

"At launch, we will provide the Soviet Union and Russia, East Germany, Poland, Kazakhstan, North Korea, and Syria. Many more are in the works and will be coming soon."

I don't think the devs are using discord as a platform right now, but it looks really awesome!

Most of us feel (probably) that multi-player is what makes DCS what it is. Countless squadrons make their own missions, host servers, etc. But it baffles me that campaigns are single player only. It makes no sense. With more and more multi-crew aircraft coming every year, or the simple joy of flying with a human wingman, you can't do it in a story driven campaign. I for one, and my friends would all buy campaigns if we could fly together. A Tomcat campaign should be able to be flown with a human RIO, and same for the Phantom. Upcoming C-130 Campaigns should be able to be flown with 3 people. Apache and Hind Campaigns with a gunner, etc. Campaigns like the Blue Nosed Bastards should have an option to replace an AI wingman with a human. It would add more sales. Pilots buy campaigns, GIB's buy campaigns, fun for all. I recently watched a campaign reveal video that said it wasn't possible because of triggers and such. It works for multi-player mission makers, work around it. If a RIO needs to have voice lines, have an AI wingman's RIO say them instead of your RIO. Just an example. Anyway, I think an opportunity is missed here. I know I would buy campaigns if I could fly them with (a) friend(s).

The DCS WebGUI app communicates with the DCS dedicated server via HTTP POST requests to /encryptedRequest. On the dedicated server, these POST requests are handled by a built-in HTTP server listening on :8088 (or whatever port configured via webgui_port in autoexec.cfg). This works well when accessing the WebGUI in a browser to communicate with a local dedicated server. Unfortunately, the URL is hard-coded into WebGUI/js/app.js as http://127.0.0.1:8088/encryptedRequest, which fails when providing access to the WebGUI via an HTTP reverse proxy. Supporting reverse proxy use would facilitate providing configurable, secure access to the WebGUI on dedicated servers without handing out the server account login credentials. This has come up in the forums a couple of times [1, 2, 3, 4]. Screenshot of the WebGUI issue with and unmodified WebGUI/js/app.js file: This issue is relatively straightforward to fix by removing the hard-coded URL from WebGUI/js/app.js and setting up the encryption key for non-local use with the following three search and replace operations: Search: dynamicUrl:"http://127.0.0.1\\:8088/encryptedRequest" Replace: dynamicUrl:"encryptedRequest" Search: "http://".concat(e.address,":").concat(e.port,"/encryptedRequest") Replace: window.location.protocol=="file:"?"http://".concat(e.address,":").concat(e.port,"/encryptedRequest"):"encryptedRequest" Search: if(e.url.includes("file:///")||e.url.includes("localhost")) Replace: if(true) Or alternatively via a single sed invocation: sed 's,dynamicUrl:"http://127.0.0.1\\\\:8088/encryptedRequest",dynamicUrl:"encryptedRequest",' app.js.orig \ | sed 's,if(e.url.includes("file:///")||e.url.includes("localhost")),if(true),' \ | sed 's;"http://".concat(e.address,":").concat(e.port,"/encryptedRequest");window.location.protocol==="file:"?"http://".concat(e.address,":").concat(e.port,"/encryptedRequest"):"encryptedRequest";' >app.js.fixed These minimal changes will enable use of the WebGUI via a reverse proxy, without affecting local WebGUI use (will work as before).

Understood - but this is my point - the manuals and reference material don’t match so I’m asking to see if there is a definitive answer yet. We don’t know if Mag3 based their model off that manual do we?

Are you sure? I understand that there is overlap of devs from SA map and Kola map, and SA has Razbam strictly as a publisher, but as I understood Kola, Orbx are actual developer on it. Not confident in my understanding so don't take it as for sure being correct, but that was what I thought.

Super. Small remarks that can simply be eliminated. 1. Ladder is retracted only for engine starting and equipment check. After that, the technician, making sure that everything is working properly, descends from the stepladder. 2. LE flaps are extended only at combined with TE flaps.

dcs.log DxDiag0822251515.txt just occurred to me to check the bios for hyper threading and turn it off.

I had several QPro's but was never able to get past setup as they were trying to force me to register as a business account. I think the image will be much better than that of the PSVR2. I had a good PSVR2 and was able to turn down the brightness to where mura was no longer readily visible. The DP connection is certainly better than fiddling with the Quest Link cable. The problems with the PSVR2 are narrow sweet spot and glare. Other than that it has great HMD tracking and controllers seemed to track reliably. Problem with the QPro will be unpredictable mandatory software updates and that Meta can brick a QP at any time for any reason and there is no recourse. Another possible issue is that there might be a block on registration for a given QPro ID# so it would be best to buy one that is returnable for refund.

This looks really cool. As I understand it, the TV seekers issue has not yet been resolved?

I noticed that the controller setup seems to be missing some controls, as shown in Chuck's guide for the KA-50. I've taken a screenshot and attached it on what I am referring to. I also noticed that there is no listing of the base of the Warthog Throttle. It's almost like an entire page may be missing. nullAnyone have suggestions on what should be completed?