All Activity

You are free to think that "In combat missions, the carrier does not orbit, but sails like the carrier in Ace Combat. In war, you never know what will happen next, so you have to deal with it flexibly, and launch/recovery is not always done in a safe area where a diversion airfield can be set up. This is the way real carrier operations should be." And I do not deny those who like that type of mission, and I do not want such missions to become impossible to create. However, if this topic is a wish topic for people who want to realize more realistic carrier operations, posting such opinions goes against the purpose of the topic. Aircraft and carriers are very expensive military assets, so they are operated in places where threats are absolutely not allowed to approach under any circumstances. If an aircraft carrier, which is the pride of America, were to be sunk by carelessly operating in an area where threats are expected, the disappointment and dismay of the American people in the U.S. military would be incomparable to the national feelings that arose as a result of the Vietnam War. But when you think about it, carrier operations in the Pacific War were very risky. Even the Japanese Navy's attack on Pearl Harbor was a strange event, with nearly 200 aircraft launched at once in the open sea with no alternative airfields. I can't help but wonder if they didn't plan carefully enough because it was the early days of carrier operations, or if it was actually a US Navy plane with Japanese markings that was launched from a US Navy aircraft carrier (which may be why there were no US aircraft carriers anchored at Pearl Harbor at the time). And I suspect that the current conservative US carrier operations, which are determined to "never let US soldiers die," were built on the accumulation of such experience. Oh, sorry. I've digressed, but that's why merging with cyclic ops is inevitable in order to avoid posting incorrect opinions. If this is not done, it would be unreasonable to complain that wishes in the same context are intentionally split up, making the number of wishers appear small and difficult to realize.

A decidedly more practical and useful idea than the monthly 'all automatic AAR wish' thread.

Here is a clip for your viewing pleasures (I was LSO spectating). After event, crashed 3 clients + server. https://www.twitch.tv/indynavy/clip/AlluringTenuousCockroachKAPOW-1IsqC1IXKqM0Qb6w

First, something like this would be an option, just like the IFLOLS for the SCM. If you don't want it, take a ten-twenty second jaunt through the settings, and turn it off. Some people have a hard time seeing the lights at all. Sure, you can probably see them just fine in VR, or with a high enough resolution screen and GPU... but not everyone has that... actually... for that matter... I'd be willing to bet money that at least 40% or more of the community is running the game with a computer that can run it at OK settings, and using lower-end controls. If my estimate is correct, then this option would likely help a fairly significant portion of the community, which in turn leads to better investment into DCS, which means more money spent on modules, etc. A small bit of development time to make AAR a little easier... and ED will reap the rewards. I can only see this as an absolute win.

Still having no luck with this after update.

Yeah. The Huey shouldn't do a loop when you take your hands off the controls. LOL (I've had that happen a few times. Like ... WTAF... restart the mission and it doesn't happen) Also, the FFB. If hydraulics go out, them controls should get heavy. Cyclic and even moreso collective -- and FFB collectives exist. To quote ChatGPT, "now that Immersion’s FFB patents have expired, the sim industry has zero excuse not to support force feedback as a first-class feature. It’s ridiculous that we’re still stuck with half-baked or inconsistent FFB in 2025"

If I switch to the new pod on the ground will it break the mission?

Current build for this date, big patch came out earlier this week that changed scripting stuff. I flew up to hotel and placed the cargo on the helipad down the road from Hotel and nothing/nada/zip/zilch et al. I used auto unhook, maybe that was the issue?

Would’ve been great to know about these changes that would effect our servers ahead of time… our Group flight night was a fail tonight due to this new “safeguard”.

Hydraulics are the only reason helo controls feel as light as they do. Those hydraulics go out and you start feeling the forces on them rotors, cyclic and collective. Now that FFB is becoming more common (I personally have an old Logitech G940 ... check ebay, seriously. 80usd total after troubleshooting) -- including FFB collectives (wish i had one) -- this really needs to be addressed. It's my understanding that you feel it in the collective more than the cyclic. But FFB is very important for proper feel, and the only reason we flight simmers haven't been enjoying it like racing simmers have (where it's considered pretty essential) is patents idiocy. Now that THAT is over, we can expect FFB to become as common in flying sims as it is in racing sims. And ALL the modules need work on that level. Step up please. Thanks. FFB is back and growing and will soon be considered essential for flight simming just as it is for racing. To quote ChatGPT, "now that Immersion’s FFB patents have expired, the sim industry has zero excuse not to support force feedback as a first-class feature. It’s ridiculous that we’re still stuck with half-baked or inconsistent FFB in 2025 ..."

Doesn't work well with mapping in voiceattack. Had every function in the old menu fully mapped using only the W, S, A and D keys, including changing speeds and elevation. Can't figure this one out fully. Especially the new search functions.

Please add keybinds for all the George functions available in the AI menu.

where EXACTLY do I put the OH-6a WEAPON MOD files ? (( OH-6A Weapons & Attachments Mod v2.01 *Updated for OH-6A v1.5*)) i tried putting the Weapons folder into the OH-6A \Mods\airplane\0H-6A\weapons folder and put the Entry.LUA file copying over the existing Entry.lua file BUT that was not working where do they go then ? Thanks

DCS Carrier LSO grading crashes clients and server. To reproduce, simply do a trap that gives a core DCS LSO grading, preferribly one with an OK wire. 2 different clients and 1 server logs `dcs.log` and the server crash dump(`dcs.log-20250724-234009-server.zip`) happened at the same time. Clients can crashe the server. This was in F/A-18C, but reports are coming from other communities with the same crash, as well as F4U Corsair. dcs.log-20250724-213933.zip dcs.log-20250724-234009-server.zip dcs.log

I like its overall functionality better. So I wish to use the Sniper over the LITENING.

As I said in the other subforum where you posted this, ADD A TRACKFILE. That will narrow down what you could be doing wrong. Currently it's a complete guessing game.

For me PiP mode is a gimmick that adds unessesary complexity Lack of a wide fov in tv mode makes it less usefull for loitering overtop targets for CAS. This something rl pilots have said litening 2 is better at. Except of course without the degraded image there is no incentive to use sniper over litening except maybe or a2a or if you really want multi target track.

Which carrier (Essex carrier has a problem with all users currently and is acknowledged) and are you using Tobi eyetracking (which currently is causing an issue with all carriers, which is reported, but not sure if it's acknowledged)

I've stopped flying the Kiowa as this just creates all sorts of eye strain for me. Unfortunately this doesn't appear to have been recognized officially as an issue - so I'm wondering if it's 'correct as is' and will receive no attention. That's a real pity - I had looked forward for years for this module, and would love to fly it more.

It's not a "problem with the external drive" per se, it's the fact that it IS an external drive which is almost always going to mean it is (much) slow transferring data to your motherboard.

A bit of a problem with Mission 7 - Steel Rain: Enroute to a midflight tasking, it says "Mission failed. Your wingman died. Retry the mission" Looks like my wingman didn't die. He just never took off, shut down his engine right after I had taken off, and pretty exactly 30 minutes later was despawned, which seems to count as "killed". Until that point, I didn't even realize that he wasn't somewhere on my tail, because his voice overs played without a hitch. As a general rule, failing a mission for a wingman getting killed can be pretty annoying, DCS wingmen being what they are, unless their aircraft are crucial for triggers (didn't seem to be the case here, at least not yet). Also, please for the love of whatever is holy to you, do NOT end missions for players. I can find the "Quit" button just fine on my own. At this stage, I don't want to fly the exact same mission again, so I'm going to skip it, but maybe I could have seen what was in store at the next tasking if the rug hadn't been pulled from under my feet. Otherwise, I'm really enjoying the campaign, which just makes it more annoying to fail a mission for no fault of my own, and not getting to see where it would have led.

that's not the issue. that's the cause, the issue is George goes into voice loop instead of the process being killed when power is cut

Hello. Since some months ago, maybe april I have a problem with DCS. Because I didn't use DCS often the last months I don't know when exactly. The problem is when I use multiple screens (3xwinwing displays) for MFDs all my system goes extreme slow. When I enter in DCS main menu, DCS and all system is near to freeze. Every click or key takes 1 or more minutes to respond. I don't see excesive resources consume in windows task manager. At first I thought it was a problem with winwing APP but today I am trying export MFDs editing the Monitorsetup LUAs and the problem appears too. Before around March-April I was using my screems without problems and I didn't change grafics cards neither other main component. I will try to uninstall a reshader app but I don't think it was the cause. Someone else reports issues of this kind in the last 4-6 months? Thanks in advance for your tips and sorry for english is not my language.