ScAvenger001

Yeah, I'm not getting any warnings whatsoever, for SARH or IR missiles.

The mig21 reads as "UK" which probably means "unknown." The mig29 reads as "29" and the flanker reads as "27". No other NATO plane can distinguish these two radars, so I assume this is an error.

I've received no missile launch warnings despite dogfighting all day. RWR and D2M are both on.

Thanks for hosting this, Bunyap! And thanks also for posting the raw data, this is really interesting. What does "gate release" mean?

Here's my shot at it. Beginner's luck entirely: this was my very first attempt at the mission, and while I got closer individual hits on other attempts, this was definitely my best average. ScAvenger001BombingEntry.zip

There's an odd blue triangle in GG76. At more distant zoom levels it's still a triangle but it's "river blue" and seems like an oddly geometric reservoir attached to that river. At closer zoom levels it disappears.

I'll second that it seems to no longer shows a physical line in f10.

Sometimes we like to close a mission by doing a "synchronized ejection" but in 1.5 whoever's hosting can't see any pilots other than his own. The aircraft go through the ejection sequence, but no pilots or parachutes are spawned. The clients all report being able to see all ejected pilots properly.

Yes, after the aircraft had impacted the ground.

According to jones, who took the screenshot: RurouniJones: "DCS 1.5 BUG: Radar locking onto a dead plane. Plane was dead long before radar found it. Was able to stay locked on for a very long time." RurouniJones: It locked on as if it were a live plane RurouniJones: I moveda round, tried unlocking it, radar on/off RurouniJones: Still showed up RurouniJones: Just as if it were a live plane RurouniJones: I never saw that plane on the radar while it was flying

Visibility problems with aircraft in weather where the cockpits are visible when they shouldn't be.

A screenshot

They're way more tinted now than they used to be. They went from "strongly tinted" to "basically opaque." Here's a 1.2 pic and a 1.5 pic for comparison. No mods used for either cockpit. You can tell in the latter shot that the overhead window is almost flat black, you can barely see the rotor blade through it and around the edges it's entirely opaque.

BUBByBe4kWY Some eye candy as the SAMs of DCS 1.5 (and their victims) show off some new smoke effects. Unit visibility has been set to max, so it's even possible to spot the missiles after their rockets have burned out. Give it a try!

Sure thing :)

I think we're saying the same thing, that my losing connection to the server is non-indicative. But I really don't think the server crashed ate the capture, because the "restart" message displayed for everyone and it happened 30 seconds after the capture. That said, my understanding is that the capture event would be recorded more or less immediately? Rewatching the video, the capture message appears at 04:27, the "mission restart" message appears at 04:53, the huey's clock stops ticking (presumably due to the mission being closed server-side and the simulation halting) at 04:59, and the recording ends (due to the game closing itself) at 05:21. Since the capture message is apparent to the other clients, the server must still be alive at that point, and I'm pretty sure the restart message is also triggered server-side so it's very probably still kicking at that point as well. Also, oddly, it gave me a "welcome back" message when I initially landed at the still-red FARP. In any case, there's more than 30 seconds between the capture and the mission end. Here's how it went, and then you'll know everything I do:

When the mission changed, DCS crashed to the main menu for me. So, "kicked out" but that's just as likely to be a problem on my end. PAK6 intel report listed the FARP still as red after the restart. When we sent another strike package to the FARP the respawned ground units attacked our A10s. The FARP was definitely red after the restart.

This wasn't a crash, it gave a "mission restarting" message and everything, it was just ten minutes early and didn't record the FARP capture.

a) I wasn't looking at the web map, and as a huey pilot the FARP wasn't visible to me on the f10. I'm going entirely by the message that said "INTEL REPORT: (Our forces have captured Kutaisi_Tblisi-Lochini FARP!)" after I dropped troops. b) This capture was immediately before the too-soon mission restart, so I don't think it was something the admins interfered with manually. Also, it was when bluefor had been pushed back to the three airports around Tblisi and nothing else, if it had been related to a general reset of the war this FARP would have gone to blue regardless and so would a bunch of other things. Pretty sure the Kutaisi/Tblisi FARP is originally owned by blue. I have a shadowplay recording of the whole thing, so I can provide screenshots if you want them. I can do screenshots of the time bug too.

Some bugs encountered last night: 1st, it shorted us ten minutes on the mission restart. It said "15 minutes remaining" and then restarted the mission 4m30s later. 2nd. About a minute before the mission restart, I dropped troops at the Kutaisi/Tblisi FARP for blue and got the capture message, but when the server came back up the FARP was still red. Having spent an hour cruising from Vaz and waiting for the strikers to clear the area, this was most irritating.

We played around with this last weekend and had a lot of fun, since it generates enemies we don't usually face. I made a video: Not shown: P-51 bomber escorts, and us failing hilariously to stop attacks on our airbase.

Non Start Holo = Cold Start Helo, maybe?

I played around with this a bit and it seemed pretty fun. You might want to look into making your triggers a bit more robust. For example, it seems like sometimes the "explosion" action doesn't necessarily kill the speedboat that triggered it. This means that sometimes there are speedboats just idling next to the destroyer, chilling while they wait for the next bomb-boat to arrive. This is easy to fix, just have the explosion trigger also delete the boat that set it off. As another example, it seems like Rentz isn't meant to survive since the second half of the mission only starts after it dies, but the mission assumes that the AI will set off enough explosion triggers to kill it. Further, since each wave of kamikazes is spawned by the previous wave reaching the explosion trigger, if one of the boats misses its date with destiny (e.g. the AI gets confused, or is destroyed by something else like a suicidal huey) then the later waves don't appear and Rentz survives. Great for the sailors, less great for the mission logic. One solution to this might be to have the Rentz explode of its own accord on a timed trigger, which doesn't seem unreasonable with the number of fires onboard. Also, spawning the later kamikaze waves might work better if their trigger criteria includes a timer as well as an [OR] to the current trigger criteria. Looking forward to more Huey action!

After some sleuthing, their IP turns out to be 208.94.240.34:10308. So far, knowing this hasn't done me any good. It seems like Joe's Datacenter might be rejecting the connection for some reason. If you're able to connect with that IP, please let me know.