[HOUNDS] CptTrips

Save often with iterative backups. It's easy to brick you mission file if you go one too many routes. $0.02.

So many bugs here. I didn't see this one right off. MT. Keep getting MFD images overlaying each other. Is this already a known issue?

Sorry, I was just being a goof. Not sure of the answer to your question. You might see if something called Skynet could help. Its a script to simulate a networked coordinated IADS. Maybe that could be adapted to you needs. https://github.com/walder/Skynet-IADS Though sounds like you have a simpler solution.

DCS ground AI can be both Thanos and Forest Gump at the same time.

So would it be safe to delete those spans so I could save more units with road routes? A shame to hobble designers for something the AI doesn't even use. [Edit] I don't see ED updating Lua versions. Who knows what chaos that would unleash in everything written up to now.

Possibly, but sounds risky for average customers to have to go muck around in the internals of the file. The correct answer is to fix the ME so it doesn't brick files.

It's mind-boggling self-sabotage. M3 gets it. It's why they are not going to repeat the same mistake. I'm starting to lean your direction. I am now thinking I might can justify buying the Corsair. M3 is being smart. I'll have to think more before buying the F6F.

Bloating a mission file is one thing, but bricking a mission is unforgivable. If it hadn't been for the 3rd party web editor, I would have lost a lot of work. I wonder how they are able to open it. Oh, they are problem not using Lua. So can that data be deleted without harm? Does that bloat get transferred over to anyone playing on a MP server even if it has no use in gameplay? Ick. If it could be culled safely, that would be a nice little util feature for the DWE.

But what about WWII being a niche? What about the development costs? OMG. Ahhh. Then pulling all the modern objects out of the ME and selling an Modern Ware Asset Pack instead would be no problem then, right? That wouldn't hurt business at all, right? It is a slap in the face of the customer. It is the clearest signal you can send to potential customers that WWII is considered a second class citizen of the DCS ecosystem. That the members of the WWII community have to be nickel-and-dimed in ways the CW and modern war players aren't. I own the stupid thing so I am not arguing for self interest. I think ED is shooting themselves in the foot. They are being pennywise but pound foolish. More importantly they are stifling the possible growth of the WWII DCS community. Making WWII fans pay for things the other genre do not telegraphs to them that WWII players are second class citizens in the DCS ecosystem. M3 gets it. Maybe they could explain to ED why it would have been bad business to sell customers a 60$ Corsair and then turn around and charge them for a separate asset pack. "Would you like a steering wheel and tires to go with that Ferrari you just bought, sir?"

Well that's a step in the right direction. At least they get it.

Wait. Wut? It isn't even needed? Then editor should purge that. When I drop a road wp I've always been impressed on how fast it calculated it. Doesn't sound like worth bricking missions for something not needed. It might take an extra 2 seconds to open the mission.

There is going to be a separate Pacific WW2 Asset Pack? Separate from the WWII Asset Pack I already bought? Not just added to? Is that going to be a free pack?

That is a very interesting idea. Thanks. I'll think that one over. In my case, yes, they are late activated templates that I spawn copies of. I should be able to change the formation. I'll experiment with that.

What do you think would happen to your business if you took all modern war AI\static assets out of the base game and put them into a Modern War Asset Pack that players had to buy to put them on their map or play on a server that had? Would that help your business, or hurt your business? If you admit that would hurt your business, explain to me why the WWII Asset Pack doesn't. If you claim that wouldn't hurt your business, do it and prove me wrong.

How is that different that every other modern AI\static item I can plop on the map in the ME? Did those not have any production costs? Why do I not have to buy a Modern War Asset Pack? You just have all those items in the ME as part of the base game. Why don't you give the finger to those guys? I understand you guys had some additional costs when you first took over the WWII kickstarter project but that was YEARS ago. You're just shooting yourselves in foot. You're going to lose a lot of sales on much more expensive modules and maps because you are trying to nickle-and-dime players on a asset pack. How would you feel if you just bought a Ferrari and the salesman said, "Wonderful. Now, would you also like to buy a steering wheel and tires to go with that? Those are extra."

Here is a copy of his broken one that I deleted a few groups with the Web Editor. On my machine, I can open it, but adding one more ground group with a long on-road wp and try and save it gives the error. I'd love to find a fix for this too. (See attached.) Test4.miz

Yes. Modern platforms wouldn't make any money either if they put no effort into it.

It's a hack, but maybe you could play around with popping off a small explosion near the spawned unit. Play around with the load and distance and position of the bang to see if you can get the level of damage you want. $0.02.

They'd be fools not to do that with the Corsair and F6F launch. Folding the WWII asset pack into the base game would clearly signal that ED sees WWII as a first class citizen of their ecosystem and not just some side thing that they don't want to contaminate their base game with but will sorta pretend to support a little on the side as long as you pay extra. ED really needs to give WWII some love for a while. Wags himself admitted they are starting to run out of modern stuff that would be compelling yet feasible for security reasons. WWII is still an largely untapped market for them. There is a large cohort of dedicated WWII players out there that have not yet been lured into the DCS ecosystem. Green fields. There is plenty of documentation out there for WWII stuff and avoids all the security friction. Airframes are fundamentally simpler (no complex computers or radar) and can be developed quicker. Once those new WWII customers have been won over, who knows what else they might buy on a summer sale. ED just needs to show they give a flip and will take WWII as seriously seriously as they do the other period genre. And it needs to be done with actions. Talk is cheap.

I ran into that. A couple of suggestions... I use a free github account to store off a version of my scripts every day so I never risk losing too much work. I also save obsessively so I realized right after I added the last unit that caused that. I was able to use the DCS Web Editor to open it up and delete that last group I placed. I could then reopen it in the native ME again. https://discord.gg/MYqwPmd6 What that means is you've reached the limit ground units with on-road routes. I haven't found a way around it. [Edit] Mine was on Cyprus too. Don't know if that is related.

I'll keep an open mind. But if the supporting units are sparse and only promises that "someday" you will get a lot more, then I'll wait a year or two and get the Corsair F6F on summer sale. Since ETO is much further along, I still think it would have been better to flesh that out more and fold the WW2 Asset Pack into the purchase of WWII maps.

Fine. Allow me to rephrase. Which is something to consider. I would want to know if that is still the case when they ask me to buy the next $50 Corsair or F6F. (But I'll wager you a beer that the Corsair and F6F will be more than $50.)

Which is something to consider. I would want to know if that is still the case when they ask me to buy the next $70 Corsair or F6F.

Makes me wonder if there is going to be a PTO Asset Pack that you have to buy separately as well.

Wished they had fleshed out ETO more before diverting off the PTO. Better to complete one task before starting another one to be partially implemented.