Banzaiib

TTI = 15 or 16 seconds is when it SHOULD go pitbull, but that's not how it works right now because the current missile API cannot support that logic. Right now it's using an older version of the AIM-120 guidance logic and goes pitbull at a specified range 11.5 miles (18.5km)... NOT time to impact. Again, this is confirmed many times by Heatblur.

11.5 miles (18.5km) at 1500 mph is about 27 seconds... 11.5 miles at 2000 mph is about 21 seconds 11.5 miles at 2500 mph is about 17 seconds Even at 2500 mph closing speed, it only travels 3.5 miles in 5 seconds... the missile goes active long before that range. moral of the story is, you have to be REALLY high up and REALLY fast toward the missile to have it go active less than 5 seconds before impact... if anything, it gives too much warning right now. (unless my math is way off... haven't had coffee yet this morning) Again, this is all with the current functionality we have... this is not how the missile worked IRL. That will come with the new missile API updates confirmed many times by Heatblur.

~11.5 miles based on the lua value (18,500m if i remember correctly) but, that is because they have not completed the new missile API (missile guidance / realism update). After that it should be roughly 15 seconds to impact.

100% and with how well (or not well) Jester works, I'd rather not have their dev efforts put into an AI. I'd rather they fully focus on the module itself.

bruh, that's software development in general. Being a fan of DCS means being really REALLY patient and just enjoying what you have now.

100% agree. It would be a massive letdown not to get JHMCS in the 15E, and not just for the 9x, especially since the A-10ii is going to get it too. The JHMCS A-G capabilities are game changers.

Just hold the power button for 10 seconds or unplug it from the wall. It'll exit much faster.

skin files can be MASSIVE... i need more than 16 gigs of ram just to work on part of the tomcat skin... that kind of makes them less multiplayer friendly in terms of rapid sharing

so they have no impact on the FM, but you'd have to completely redo the FM? not sure if i track with you on that... now you've decided not to do it at all because it's time and effort and money to deliver something that you've given to us for free of charge... except that's not at all what's going on here. WE paid for a product to contain certain features and we rightly expect to get them. I'm on the losing end of this argument (and have before, just look at my warning %), I know... but there's also a list (long but distinguished... little TOP GUN humor there) of features promised not getting delivered on for other modules, which makes this just a straw breaking the camel's back. the 14 is a wonderful module... don't get me wrong. By far better than anything ED's ever done... but that attitude gets me firey.

except for that time you said you were doing the glove vanes... granted, that's a while ago... it's tough to keep track of everything https://forums.eagle.ru/showpost.php?p=3983072&postcount=8 and I wouldn't say the 14A is free of charge. You promised it before I bought, which means it's part of what I bought... so in a way, I paid for it. Your post implies like you're doing us all a favor, and this is the problem with pre-paying for software that hasn't been finished. You are fulfilling your part of the contract, not doing us all a favor.

personally, I welcome the wave after wave of A-6s throwing themselves at the rampaging kill bots... you see, they have a pre-set kill limit...

Glove vanes... duh! :)

This bug persists post-08-19-2020 patch.

Same. And he refuses to put it back into TWS for what seems like an eternity, but is probably 2 minutes (maybe related to the track memory?) Jester also is switching to pulse mode while STT locked with a missile in the air even when that option is turned off in the settings, or at least calling out that he is...

As a self-proclaimed audiophile, the F-18 sounds could be better, but they're also pretty damned good, compared to that in-cockpit display footage. It's gotta be a difficult thing for a sound engineer to master all the sounds, given that he's probably never flown an F-18 before... <shrug> Looking forward to the update.

That's a good point. I'll test more this evening with different altitudes if possible. I was shot at by both S-300 and SA-15, the SA-15 from about 5 miles and only about 1000 ft AGL up to about 7,000 ft AGL... and got no launch warning, only lock... even when the radar was clearly within the sensor limits. edit: quick test at lunch, SA-2 and SA-11 both give lock and launch warnings. Will test SA-15 and amraams later tonight. Edit: i guess i was wrong. sorry. After more testing, all seems fine.

I will make tracks tonight specifically for this purpose. My tracks from last night are very large.

2020/08/13 - Haven't flown the J-11 in a while, but did last night, and I and several other J-11 guys were complaining that we were not getting missile launch warnings, both from SAMs and AA missiles. Amraams were killing us with zero warning (TWS launched), and SAMs like SA-15 and S-300 were clearly firing at us and only giving lock warnings, no angry beeping when missiles launched. This also occurred on the SU-33 and Su-27.

version 2.5.6.52437 Last night in multiplayer on several of the best known servers, I was not getting missile launch warnings at all in the Su-27, J-11, or Su-33. TWS launched amraams gave no warning at all. S-300 and SA-15 only gave lock warnings, no missile launch beeping when they fired at me. the tracks I have are massive. Will try to make smaller ones this evening.

Mover and other SMEs on this topic have said that the G-limit is super low, regardless of air-frame. The reclined seat is a 2 edged sword, when you need to look behind you at 8g, you might not like it anymore... as many have complained. that aside, the g-limit / blackout is really low, but i've heard that g-warm-up might be a thing modeled in DCS. I'd like to know this definitively... as sometimes I can pull a lot more g than others... especially toward the end of a mission...

Are you sure he's switching to RWS? and TWS-A is not just auto-adjusting the width of the scan zone?

big changes coming for missile guidance... new API is in the pipe, very soon, but ED time frames are not always ideal :)

Truly Agile development doesn't really concern itself with deadlines. They deliver products and product features internally on a regular basis (2 - 4 week sprints), but that doesn't mean we'll see them in production / beta releases. And new dependencies and requirements are often discovered mid-sprint. Projected time lines are based on known requirements now, but things you discover along the way often affect dev time, hence delays. HB is pretty smart not to put out very many firm dates, in my opinion. They're doing things that have never been done before, so i am quite sure they have an "agile" development team... which means, it's done when it's done, and it'll be awesome.

"Realism AND fun" there... i fixed that for you.