[HOUNDS] CptTrips

So are rotary aircraft. Look, I know WWII stuff isn't the core focus. But look at Look at the ...other Russian built game and look at the ...other upcoming WWII game and there is obviously just as big and enthusiastic a market as anyone clamoring for an Apache or Kiowa. And I love those too. The WWII community has not grown in DCS because the company has made it pretty clear that they have little interest in them. That seems like a perfectly rational reaction. I'd like to see at least parity in interest, vision, resource allocation, and fan service for the WWII fans that they have shown the rotary fans. I think now, with one competitor abandoning the WWII genre inexplicably to go try and compete against them in jets products? (Oh that will work out well), and another potential competitor openly stating they are gunning to challenge DCS in the high fidelity space, I think now would be the perfect time to move into that WWII space before the new competitor can get dangerous. The best way to handle a potential adversary is to strangle them in the crib while they are still an infant. They best not let them get a foothold in the high fidelity space with an unserved Pacific WWII niche. Unserved niches are the breeding ground for competitors. And once established with momentum, they will become a much greater threat and much harder to defeat later. Ignore the potential competitor at your peril. If they can match your high-fidelity and beat your production cadence (which frankly won't be hard) then I think you have the potential for real future headache. And who is to say once they have established themself as a high-fidelity alternative to DCS, who is to say that long term they will only stick to WWII. Their product series title doesn't particularly restrict them to WWII. That is just the best unserved space they see to get a foothold in. That said, I don't have anything against those newcomers. I think their product is very interesting. The above is just trying to see the strategic terrain from ED's point of view. From customer's point of view, I wish them luck. If DCS won't serve the high-fidelity WWII market, eventually another competitor will. Whoever does first , gets my money. I'd still fly DCS for the whirly birds though. I think they can stand to relax on that market more than they can afford to ignore WWII. There are no, real potential rotary competitors that I see on the horizon.

Trying my hand at learning a little video skills. First attempts to just learn the basics of the editor and such. Thought I’d make some simple shorts to learn on. Take each of the DCS Warbirds and spotlight 3 or the top aces who were successful in that plane. Hope you enjoy. Feedback welcome. Cheers. Top 3 Aces of the F4U Corsair https://youtube.com/shorts/u0ZAmzljXuE?si=D7_y5pWAiyjSLaAV Top 3 Aces of the Spitfire Mk. IX https://youtube.com/shorts/Ubh4z8EGfaA?si=TV7HO1fsXCUp7VFs Top 3 Aces of the P=51D Mustang https://youtu.be/xzauroFbB9I?si=i7RUDQzB0-YTDML7

Very short trips. Often on a one-way ticket.

It'd be an incomprehensible crime if they didn't.

I was playing with this tool last night. Very nicely done. I don't think it gets enough attention. Thanks and cheers.

I've seen that happen alot If I spawn too near the IP or come in at an angle too extreme for it to get stabilized for a good run. It basically ran out of time to get within proper constraints for the drop before it reached the drop point. It is circling around to get lined up better for another run. Just as a test, try increasing the initial leg before the drop wp further out and make sure there is sufficient distance between the drop WP and the actual target triangle. Like at least 10 nm I think.

That's what I did in the sample mission I attached. Huey's aren't good again armor. I had two groups. A single Apache tasked with concentrating on the armor group. And a Client Huey group with door gunners to follow behind and let the door gunners mop up the supply trucks. Gave the huey some rockets too because...why not.

You could tweak a skeleton mission like this to your tastes. Cheers.Sample Convoy Attack.miz

You might start with some of these hints to avoid common pitfalls. https://www.reddit.com/r/hoggit/comments/s2n89h/sp_dcs_people_frustrated_with_the_ai_build/

That was the error from the original log I posted before I disabled CSAR. I've put it back to the original mission now. Seems logical to get that working first before changing more variables. Others hitting my server were experiencing the crash so that argues against it being my local game machine. I realized I neglected to add StopGapGUI. Lua to hooks. So I'll try that this morning as well as turn off pure scripts. Don't see how those would effect this problem, but first step is to get a proper test environment established. If that still doesn't help, then next logical step would be to see if you hitting my server can repro the behavior. I dunno why others haven't seen it. Maybe I just set it up wrong. Still verifying that. I do remember a lot of the event problems I heard rumor of seemed to coincide with the versions since they added Dynamic spawn. That's been fairly recent. If it's "timing related" as ChatGPT suggests, my machines might be slight faster or slightly slower, just enough to hit the unfortunate state. But, one step at a time. It's not vital I get this working. No worries. I just hate mysteries. Cheers.

I’m just thinking out load here so bear with me. I just want to document some ideas while they are fresh. I vaguely remember seeing some discussions of problems others were having with the DCS event system. I *think* one of the issues is that when a client dies, DCS swaps the client object into a static dead aircraft object. It is possible that by the time the event code executes that has happened and the initiator is not a Client object but now a static. And the static would not have the .getPlayerName method implemented. This bait and switch was causing all kinds of problems. Event initiators were not always the object you were expecting. That sounds a lot like this case because the error in the log was: 2025-02-12 03:43:17.517 ERROR SCRIPTING (Main): Error while handling event [string "--[[ 250114 CSAR 1.9.2 ..."]:496: attempt to call method 'getPlayerName' (a nil value) So I take that to mean the initiator object did NOT have the getPlayerName method implemented as expected by the time it reached the event handler. Possibly because the initiator object had already been swapped out to a static wreckage object. Looking at the recent Moose git hub fix diff that I suspected might be related to the same type of problem I noticed: {See image below} Note the clause they added. Looks to me they added a check to make sure that unit actually had the “.GetPlayerName” method implemented. (i.e. The method reference was nil or not.) I could not find the exact discussion I’m remembering, but here is a reference that looks like it has some similar issues and work-arounds. Event Handling Problems NOTE: When you test this, make sure you are testing against an actual Dedicated Server and not the server you can run from the client. I have seen those not perform exactly the same in all cases. (Thanks DCS.) So to some extend ChatGPT may have been referring to this as “timing issues” sometimes being involved in errors like this. So in some cases the initiator object might still be a client object, or might have already been switched to a static dead aircraft wreckage object by the time the event handler code executes. Or I could be full of it, but something to consider. $0.02.

Just a datapoint... I tried turning off the CSAR but I still get a crash. I ran locally on my game machine as SP and did not get a crash. Not sure what that implies. I will DM you shortly with the login. I'm setting it back to the original mission. It will be back up in a sec. Thanks.

I'll look into that. I'm currently looking at the log a littler closer to see if I can see another clue. You might try the autostart first. I didn't do a manual cold start. Not sure why that would matter. I didn't hear any CSAR message. The game locks the instant of impact. As a debugging test, would you mind logging into my server and trying my test case to see if you can repro it that way? That would eliminate my game machine from the equation. If so I will DM you the login info.

I'm got some more possible test cases to try but let me specify my test case so we can test the same canonical action. 1. Log onto a MP Dedicated Server running the mission. 2. Go straight to [Olf Orte] UH-1H and spawn. 3. Perform Autostart sequence. No ground crew rearm\refuel. 4. After started, take off climb a couple of hundred feet and intentionally nose into the dirt and explode. 5. Client crash. null