billythebassman

Is that the one from 2011 or is that the old one?

Sure... let's do that. We haven't done that before. I think the answer to that is very clear to those who are willing to hear it.

It's just that if Mag 3 has given up or abandoned this project, and they are still telling us to stop bothering them and just wait, I think we are entitled to know that.

May I ask the basis for your belief that the F-4U is ready? That would be an important statement if it were based on some verifiable evidence...otherwise more wishful thinking.

No we don't. That's why we're concerned. The facts are that these developers have said that this Corsair was "close to release" quite a few times over the past eight years. Are we asked to wait another four years and then be told the project wasn't feasible, or worse...told nothing. Let's keep in mind that this is a problem that takes about one minute to solve. Apparently they're not interested.

No one is suggesting a legal obligation to communicate with potential customers ...only the common courtesy to which everyone is entitled.

Yeah...that's probably it.

I have always wondered why some people seem to believe that they aren't entitled to anything. Is it a self esteem issue or just the sort of logic that refers to nine years of waiting as "zero" patience.

Yes, the project may take years to develop for all the reasons some have mentioned... posting some updated information takes about a minute. This topic is nine years old and 48 pages long. When was the last time the developers posted any information? The contempt is the non-communication.

Nope, I was patient in 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023 and two and a half months in 2024. I'll wait for the Hellcat... It is better on carriers and perhaps more iconic. I won't reward developers who show this kind of contempt for the community. This F4U-1 is the very last plane I would ever buy.

M3 is holding up an entire theater of operations in DCS while refusing to tell the community anything. Even if this addon is spectacular, I will not be buying it. Their showing this type of contempt for the community is inexcusable and should not be rewarded. But I think M3 has given up on the Corsair and has made the decision not to let us know that. I know I've given up on it too.

The only question that troubles me is How many other developers could have actually completed and released the Corsair during the past eight years, if this developer had not "marked the project as their territory" in 2015. My feeling is that eight years is far too long to have been "strung along" by this developer--the gamesmanship should end if they expect any sort of customer base.

No, the tease is what they've been doing with the Corsair since it was first announced in 2015. Eight years of "almost ready." Now they are literally teasing about a tease....ridiculous.

@f4l0 Thanks for the reply. Here is the export.lua file. Export.lua

Hi and Thanks for a great program! It’s working perfectly in MSFS controlling my HF8 haptic seat. But I can’t seem to get it to connect in DCS (ver 2.7.14). I have searched the forum but cannot seem to find my particular issue. The Seat handler shows “Force feed State: OK” but the Simconnect box in “Special Options” says “Status: X” in red letters. The “DCS Export Folder” is pointing to …\saved games\DCS\Scripts. I tried reinstalling all three modules of the legacy Simconnect download, but still no connection. I am unable to feel vibrations while on the runway ready for takeoff in DCS. “Test vibe-motors” sends vibration to the seat but nothing else seems to be connected correctly. I’m sure I am overlooking something, I just don’t know what it is. Any help will be appreciated. Thanks