Pizzicato

I'm on the same page. I'm definitely way more excited about a better DCS than a bigger DCS.

100% agree. They just need to make a call to MakePlaneGoFaster(2.05, 40000) in the code. Every fool knows that. :thumbup:

I suspect you're got a better chance of getting your questions answered in the Mission Editing sub-forum: https://forums.eagle.ru/forumdisplay.php?f=210

Yes. The last couple of patches broke a lot of stuff and caused a lot of angst in the community. ED are shifting to a less frequent patch cycle so they can (hopefully) do a better job with their internal testing before releasing content to the wider community. The specific link that Speed-of-Heat was looking for is this one from BigNewy: https://forums.eagle.ru/showpost.php?p=4388369&postcount=1767

I rarely ever fly at night, but I figured I'd give it a go after hearing mutterings about the improved night lighting in the latest 2.5.6 beta. Wow. I took the Hornet up over the Caucasus and was blown away. Even starting up on the ramp, taxiing out after a couple of other Hornets, and then taking off and gently climbing out over Tbilisi was absolutely stunning. Night and day (no pun intended) from the previous nighttime implementations in DCS. Things ramped up even further when my wingman and I got into a dogfight with a pair of Fulcrums. The glow of the aircraft afterburners and missile exhausts was really immersive, and the burning of falling aircraft and their burning remains on the ground was pretty damn amazing. I'm not a fan of the current super-hazy, washed out daytime lighting, but the nighttime lighting is stunning. It's all going to look pretty damn good when everything's all dialed in. Great job on this ED. :thumbup:

"Hey! What's that Ka-27 doing there?" :D

https://forums.eagle.ru/showthread.php?t=114030

Thanks for responding, Majinbot. I'm not sure how that relates to my question, though. I understand the concept of Events and Event Handlers, but I'm not clear on is how the function Handler:onEvent(event) definition works: As far as I can tell, Handler is initially declared as a generic Lua table. In the next line, however, it's being used as an EventHandler to capture the Event Table from a DCS event in the parameter named event. I looked the SSE page you referenced, but that doesn't have any reference to the onEvent() method call that's being used as part of the function definition. Where is that coming from, and how does it "know" to catch a DCS event? Apologies if I'm being super-dense, but I really want to wrap my head around this.

Very naive question, but where is the function onEvent defined? Is that a MOOSE function, or an embedded DCS function? Is there any documentation I can reference around it?

Just a lazy +1 here. Just flew a 7 AM Hornet mission in the summer Caucasus and could barely see the HUD or DDIs. The environment was super washed out and low-contrast, too - almost like a super-bright haze or fog.

Thanks for keeping us all in the loop, Kate. I'm loving the Hornet, and looking forward to the on going development. :thumbup:

Nobody said it was just you. They just said that other people aren't having that issue, so it's probably not coming from ED's end (unless they're deliberately targeting you for especially slow downloads). That being the case, it maybe something to do with your ISP.

IR is due for a major update, but it's a monstrous task that's going to involve revisiting every single asset in the game in order to provide them with accurate, dynamic IR signatures. It's in ED's plans, but who knows when it'll actually make it into a build.

Just did the Persian Gulf Cold Start mission, then returned to the carrier (versus landing at Al Dhafra per the flight plan). That was pretty damned amazing. Great work, ED. :thumbup:

The absolute last thing that ED needs at the moment is yet another distracting thread of work to spread them even thinner and take them away from improving the core of the sim and finishing their existing modules.:doh:

https://forums.eagle.ru/showpost.php?p=4298458&postcount=649

Just wanted to add my own thanks. I'm particularly grateful for Kate's increased presence in the community. It's great to hear more in the way of direct, honest communication from the very top of ED. :thumbup:

+1 I just discovered the posts from Nick and Kate off the back of watching a random YouTube video that happened to mention them. They were hugely informative and valuable, and directly addressed a good number of the questions that repeatedly come up on these forums. Kate's post about predicted timelines was especially helpful and appreciated:

Can't speak for the OP, but I've deleted FXO and Metashaders and ensured that SSLR is off, and my framerates are still horrendous. DCS was silky smooth for me in 2.5.5, but it's pretty much unplayable in 2.5.6. The difference is absolutely massive.

It isn't. It's part of the lighting update, but the patch notes don't go into exhaustive detail on the specifics.

I think there's almost zero chance of that. That business model is pretty much dead for niche genres, and ED moved away from it years ago. My guess is that they're chasing the War Thunder crowd - frictionless entry into a lightweight, metagame-driven, free-to-play arcade-like flying game. That's where the money is, and I'd be really surprised if ED didn't go that route. My only real concern is that DCS will gradually fall to the wayside if MAC takes off and becomes the more profitable and easily-serviced experience. We shall see, though.

Disappointing for sure, but these things happen. No big deal. Thanks for the heads up. :thumbup:

THIS! It's insanely immersion-breaking when your wingmen can spot enemies at 400nm with a radar that only displays contacts out to 160nm. It's especially annoying when this suggests that the enemy AI can see you and your flight at similarly extreme distances. Accurate/realistic/just-plain-plausible AI sensor-usage is definitely one of the bigger issues to address in the current engine.

Yes! :thumbup:

I do. :) I'm also totally uninterested in MP, so that side of things doesn't really impact me either, luckily.