Paco

Good job ED!

yes!! Please share the fix, please.

+1. Well said. Fix the basic stuff first, then worry about super carrier.

Bug fixed in latest patch, thank you.

Wasn't expecting a Hornet update after the dumpster fire of an update that was released. There's a lot of work to be done and I hope ED is trying to fix it. After buying the Hornet in EA and doing some thinking, I made the decision to not purchase a complex aircraft in EA again. Especially any module produced by ED. Previously, I bought modules to support ED, even ones I didn't want. No more. Their business model and customer base supports releasing half-baked products and then neglecting them for years, while they release more half-baked products. The data points are there, so you shouldn't be surprised. I assume most of us wouldn't support this type of business venture from a contractor working on our house but we accept in the DCS community. Releasing something in EA is not a license to let it sit for years, while you hide behind the, "well it's in early access...…", "...we plan this year...…" . ED has to regain lost trust among a portion of their customer base. I suspect this portion will grow in number. ED needs to put some trust points on the board and the clock is ticking.

If you can start it, you can fly it! Seriously, I want it hot started. Starting is like practicing bleeding.

I wish the Hoggitt exchange regarding development at ED was posted here. Although a fan of ED, I was (am) critical of the recent update and lack of progress on their EA modules. Having said that, after going to Hoggitt to read the updates there and the responses by Nick Grey, my confidence is somewhat buoyed. Honesty and transparency goes a long way. Hoping for a better 2020 and some finished modules.

Great post. Sad but true. Actions speak louder than words. As long as the majority of DCS customers exhibit addictive behavior and spend money for half-baked products, then there is no business incentive to finish modules in an even remotely timely manner...if at all. Wish it was different.

This is a good thread.

how about ED implement the feature of slewing the TPOD to a designated point?

I'll bite. I think the bigger problem is that we have modules that are in perpetual Beta, which drives people towards the Open Beta versus the stable version. ED could alleviate this problem by finishing modules in a timely manner instead of releasing more modules and leaving modules previously released in a half-finished state. Let me elaborate and please spare me the condescending lecture on what a Beta is. People are drawn to the OB because they want the latest and greatest. We as a community have grown accustomed to ED modules that stay in Beta for years. There is a healthy amount of cynicism in the community when ED announces yearly plans. ED has a credibility issue in this area. As a result we lean towards the OB because we know it will be years before a module comes out of Beta. So the gap between stable and OB grows larger and larger. As stated numerous times by DCS loyalists, "it's a Beta!!!!" Sure, but in reality, most DCS users are treating it as a stable since the gap between Beta and stable is growing and continues to grow. Not to go down a rabbit hole, but there is also dynamic of those who play DCS as an arcade game and those who want more of a simulator. The former are content with a buggy platform while the latter want finished products that accurately emulate reality in terms of systems and flight models. ED has to balance that spectrum and allocate resources according to the their business plan. While users must realize the bugs of a open beta, ED must also bear some responsibility. People are people, and they will lose patience. My humble suggestion and it is just a suggestion. ED should go on a "clean up stand down" for a specified period. Finish modules/projects on their plate before releasing anything else, with the intent of closing the gap between OB and stable. Get some credibility points on the board. If that's not an option due to business plan and financial constraints, then I support closing the MP to OB for the long term viability of this project. On a personal note, while I may sound harsh towards ED, I love the product and want the company to succeed. Overall this is a small bump in the road. Ready for spears.

It's a mission start issue. If there are triggers, flags or holds set at mission start they are not recognized. I can't believe more missions aren't hosed by this. Was reported as fixed but it's not.

WP hold at mission start This is still broken. ie not fixed as reported in the last update.

WP hold at mission start Still busted. :mad:

This bug broke all my missions. :-( I use the WP hold on mission start to phase in forces depending on certain triggers. Broke every one of them.

After the new mod, the ME and WP commands are all screwed up.

Bignewy, Did some more research using using a modded version your mission. I think it's a mission start issue, where DCS isn't recognizing hold (or any advanced WP function) at mission start. The "hold" at WP function isn't working at mission start but works after the mission is running. I can explain more if you like. Paco

Bignewy's modded mission Here it is. waypoint HOLDrev1.miz

Bignewy, Ran your mission, however the initial hold feature is still broken. I modded your mission, the BTR should hold at SP until flag 2 is activated via radio menu when playing as game master, but instead it just drives on. It does indeed hold at WP1 as you demonstrated, so I'm thinking the "hold" function doesn't activate at mission start for WP's with a hold at SP. Just a theory. I can do some more research to narrow down this bug. Thanks for the time. Trying to attach your mission that I modded. Paco

One of the many things that...…...

Sorry, typo......this feature is indeed broken in the new update. No hold function for WP's.

this feature is not busted in the new update. Hold at WP doesn't work. I bugged it. Ruined most of my missions

did some more trouble shooting. WP "hold" feature is definitely broken. Not a flag on/off issue. Doesn't matter if the mission was created before or after the update.

Seems the WP "hold" function is inop in the new update. Vehicle will not hold at a given WP. Sample mission attached. In this simple mission the enemy vehicle is supposed to hold at its first WP until flag 1 is true. It doesn't. Play mission as game master. Not sure what else is broke in the ME. Very frustrating ED. update trigger test.miz

Seems none of my hold at WP triggers are working in 2.5.6 Anyone else having this issue?