All Activity

They reduced the F4U’s speed by about 7 knots in the latest update. Hopefully, this is just one step in a longer process to fine-tune its performance. I'm also hoping we see a credible Zero AI soon—especially since the real Zero was significantly slower than even the slightly slowed Corsair we have now.

not much happening here or on the discord...................silence = death

I don't even dare to imagine what would be the size of that map

Hello, I already bought East Afghanistan and can't express my joy with that map as the decision of ED to provide high details on part which is considered valueable for the player and give them access to the rest of the map! What I can't quite figureout yet with Iraq map is having it again split on regions North and South would that be the case if I purchase the available North Iraq? Would I have Norther part in high resolution and South in lower or would I have access only to the Norther part and later must buy Southern part as well? P.S. can't wait for Syria map to be on sale once again!

Mission 4 problem. I input the lat/long mentioned for Golf in the kneeboards and nothing is there via the flir. Searched all around with the flir, nothing to be seen. Way point is designated a target steer point. Flir contrast, etc. adjusted. Only mod installed is tacview. I see plenty of ground and roads, but no buildings, etc. of any kind anywhere for miles around. Ideas? Broken in an update? Edit: The lat/long info. in the briefing sheet for Golf is wrong, by a large distance. Very frustrating. I got these from a flir of a youtube video of the mission and they are correct N 35 14 19 E 39 19 06 Elevation 1306 The briefing lists N 35 34 17 E 39 19 05 No elevation given.

Hi all, Firstly, thanks for this fix Taz, it's such a great QoL change for multiplayer. Unfortunately this is preventing me from using my communication menu via the binds I've set on my HOTAS and I'm not sure how to fix it. The mod is installed, or enabled, via OvGME. I have binds set for opening the command menu, cycling between the next or previous items, and selecting an item. The bind to open the command menu works fine, but once the menu is open I am unable to cycle between or select any items. The text remains white instead of turning yellow when you are cycling through the list. nullI'm using the dial on the VKB STECS ATEM. It is not an axis, and registers as buttons. You can twist it left or right, depress it, and click it fwd, aft, left and right (it's basically a dpad. I had a look through the lua file to see if there was anything in there I can edit to fix this but haven't been able to figure it out. At the end of the day it's not a dealbreaker, I might set some binds on my keyboard other than backslash and the F buttons to see if that works. Cheersnull

So, I know I'm super late to the party on this mod, but I just got it today, and it's fantastic, other than in VR, the head position is like a foot and a half too far to the right, relatively speaking. Does anyone know how I can adjust this? Recentering using the hotkey doesn't fix it. I know there's probably just something I haven't learned yet about how to move the camera position

I would very much like to know what manual as well, I'd like to acquire it if it's just available on Amazon. Also, do we have a solid release date yet?

IMO the problem is they've been conditioned for it, because that's how simulators have been handling it for decades.

I've spent a lot of time in the past combing through bug reports to get to a place where I could enjoy DCS. I'm retired USAF aircrew and after that career I spent another 20+ years doing software development. I even developed software solutions for FSX and P3D a long time ago. It occured to me to use an LLM AI to comb though the data not only from these forums, but to also use it analyzing simulated flight test data derived from monitoring the CPU, RAM and GPU sensors. I spent about a month in my spare time training an AI to become a simulation test data analyst. I was pleasantly surprised by how much faster problems could be tracked down in the hardware and also to tune or retune DCS (like after an update). The end result is I can determine issues almost as fast or faster than spending time waiting and wading through the forums for clues as to what is wrong. In fact, the AI has developed a "mental" picture of how DCS operates. I'm now spending a lot of time flying with instrumentation on the hardware running DCS so if something goes wrong a solution is no longer hours and days (in some cases) to get the sim and hardware back in a stable state. Is there anyone else here that has done that? And if so would they be interesting in sharing their experiences in doing so? Maybe the discussion would help others who are struggling to get the sim to work for them?

The screenshot above shows a destroyed Su-15, not a Yak-28.

Гув контейнеры не очень хорошо работают с подвижной меткой прицела. Пулемёты показывают ошибочную точку попадания (и одну и ту же для якб, гшг), гранатомёт не имеет подвижной метки. Это оружие должно работать с прицелом или нет в реальности?

Bumping since we have currenthill now making in-house units.

It would be handy if as a Developer option, a tick box or similar could be added somewhere on main screen or somewhere, where for this map a “Combat” or “Training” switch could be made, whereby cones, balloons could be removed for the whole map, or reinstated. Training keeps them where they are, and should the flyer wish, he/she can practice proper avoidance and routing. Combat removes them, (rightly so!), and routings and low level runs can be used as would be.

It seems like most in this thread lack the IQ to understand this nuance, and can only think in absolute terms.

With the anticipated release of the MiG-29, Could we possibly see an updated 3D Model and Pilot model for the L-39?

The only reason the liveries are bloated at all is because they have unnecessarily large resolutions, often 4k or 2k.

Thank you. I noticed the addition for choosing the custom cockpit but I didn't realize I had to rename some folders.

Had a chance to watch this. It's the same issue everyone is having. Oil coolers not open enough, and you cooked the engine. Here's the NTSB preliminary report Oil temp was in the high blue zone, practically touching red line for the majority of the first lap. It was so close to the red line that I was unable to tell whether is was red lined or not. Maybe half the needle width was in the red, and the other half in the blue. You possibly accumulated damage here. Your oil coolers were open about 25%, and the inter coolers open a little more than that for the entire flight. You never touched them again for the entirety of the track file, after initially setting them. This likely indicates that oil temperature was not part of your instrument scan. Solution: Open the oil coolers more, about 50% or so and it will keep the needle in the mid blue range. If you see your needle the in the high blue and your oil coolers can be opened more, open them. You can even get the needle in the lower blue range. Intercooler flaps don't need to be open when not using blower. You can leave them fully closed here without consequence and eliminate the associated drag. You were not using blower, which is correct. No harm leaving the intercooler flaps open, but your engine just works a tiny bit harder to overcome the unnecessary drag. First two takeoffs: You pushed MP too high and heard the engine knocking sound, thereby accumulating damage. You reacted quickly though, and pulled MP back, which bought you some time, but the damage had already been done. Your RPM and MP changes were quick and abrupt at times, causing the needles to briefly overshoot their limits. Be smooth. Count 2-3 full seconds between the endpoints of any control when you are adjusting it. One the 2nd landing, you oil temp was a tad lower, but still in the high blue zone near the red, noticeably not touching the red line. Again, oil flaps need to be open more. 3rd takeoff: Oil temp was too close to red for a comfortable takeoff attempt. Don't forget to look at the gauge before takeoff and wait until it cools down a little. Much better on the takeoff throttle here. No knocking noise heard, but shortly after takeoff, the oil warmed up just slightly and touched the red line, and that was the end of your engine. In the current model, there's no buffer. It acts as an instantaneous trigger. Great patterns and landings though! If you do the exact same flight with only two corrections, everything will be fine: 1. Oil flaps open 50% or more. 2. Do not exceed 2700 RPM, 54 MP on takeoffs. When on the deck, push your RPM to maximum before opening the throttle. There were times you opened throttle to 50+ MP, but RPM lever was still pulled back from the last landing, and then you pushed RPM up. The order is backwards and puts additional stress on the engine because you are trying to take bigger bites out of the air with high MP. Flatten that blade pitch, then throttle up. Other recommendation: Your entire 3 flights were done on the main fuel tank. Make sure fuel selector is on reserve tank for takeoffs and landings. This will bite you in the future. When on main tank, as soon as your fuel gauge hits 50 gallons, engine will quit and you'll have to quickly switch to reserve. You don't want to have to do this when low and slow, ready to touch down. Cheers!

J-10CE cockpit, very close to JF *wink* *wink*

CVW-1 VMFA-312 F/A-18 Skin pack WIP

I am pretty sure they come back if you connect the device and rescan though.

The dual SD-10 pylon loadout is ~6.16 (0.00150390623 * 4096), which includes both missiles and the pylon. Each missile itself in that loadout is ~2.64 (0.00064453124 * 4096) and that value is subtracted from the dual pylon loadout when the missile is fired. Same for the single SD-10 loadout which has a total drag value of ~2.64 (0.00064453124 * 4096) while the missile itself is 2.2. The drag for dual SD-10 loadouts are high but aren't that high. For reference, the AIM-120 LAU-115 2xLAU-127 dual pylons has a drag roughly of 8.027.

null