Rinz1er

Hey did this ever get pushed? I was flying with that livery yesterday and noticed the glare again.

How do you know the missile is going active at those times? And also, what missile are you using?

Great response btw!

I just did an ACLS landing the other day. Had no issues with autothrottle. Remember that your gear, flaps need to be down and DLC needs to be on. The throttle also must not be on idle for it to engage.

So this makes sense if you are saying that the aim54C in IRL doesn't abide by the target size switch and has more authority of itself. And therefore, is unlike the aim54A, which the WCS and more specifically the target size switch was originally designed for and had more functionality. Though this would make the aim54C different than the other active guided DCS missiles(AIM120 and SD10) where the target size switch option reduces it's go-active distance as expected. If this is the intention and as close to IRL as possible then yeah, there is no-op needed to fix this functionality and I will shut up about it.

Yeah I feel like we haven't gotten any significant tomcat content in several patches. What is going on?

Edited the post above to include the specifying missile as the AIM54C-Mk47. This can also be found in the TacView. Thanks!

Thank you to @Callsign JoNay for assisting in testing this. Two tomcats flying at each other. Taking a AIM54C-MK47 shot at ~60nm with the target switch settings in the following profile. 1st launch -> Target Size Switch "Normal" 2nd launch -> Target Size Switch "Small" 3rd launch -> Target Size Switch "Large" When the launched-on F14 flares, it signifies the RWR is warning of an active guided missile. When the launching F14 flares, it signifies when the TID ticker starts flashing. What we found was that the TID ticker flashed at different times directly related to the setting of the Target Size Switch. For example, when the Target Size Switch was set to "small", the TID ticker would begin flashing <15s. When the Target Size Switch was set to "large", the TID ticker would begin flashing at >20s. However, no matter the Target Size Switch setting the missile ALWAYS went active at ~7nm. This is a bit different than the AI defending ALWAYS at ~10nm which may be why some folks saw improvements in their PVP engagements over their PVE engagements. TLDR: Nothing has changed with the Target Size Switch recently. It is still non-functioning in changing the go-active distance of the missile. It only seem to affect the TID ticker. Attached the TacView of this encounter for your viewing pleasure. Tacview-20230124-202744-DCS-51st_Syria_Training_Map-48.zip.acmi

I have definitely not found this to be true.

Will the F14 and Viggen be updated to use this new code framework?

Can you provide any update on this?

This. The no target size functionality with the AIM54C, the omniscient AI, and the strange AIM54 guidance when notched (the pitch up and seemingly inability to reacquire even when out of notch) has all really put this missile in a bad place. I hope that both HB and ED will get this stuff fixed so that it can renew my interest in flying the F14...

just had this happen again from sa-5. Had nails warnings but no launch warnings. Minute later I was dead

I think this is what I experienced as well in

Diesel, how you doing man? Though this is only a problem with the super carrier. Get in a RIO slot on a non super carrier and you can avoid the CTD, or atleast wait for the pilot to get off the super carrier deck as a temporary workaround.

Okay so I have been trying to figure out a repro case since the two times it happened initially to no avail. I am chalking it up to some obscure transient occurrence. Continue on gents! Sorry for wasting y'all time! I will update this thread again if I ever figure out what caused it.

I am not sure as it was an MP server. I suspect that it has something to do with Jammer being on though. I will try to get some repro cases tonight and post a track.

Had it happen last night in an MP server with the Jammer turned on against an SA-5. I also had it happen again against a Hawk launch with the jammer turned off except for that one I got a launch indication when it was just 5 miles from hitting me and it had been in the air for 1 minute already. I will try to get a track of this tonight and post it.

Deka seems to not use the "go_active_by_default = 1"...They instead use "active_dist_trig_by_default = 1". Not entirely sure how they are changing the distance in code but there is a forum post about it here from Deka

Hey all! I seem to not be getting any missile warnings from SAM launches. I have tried with both the jammer on and off. I get an inconsistent spike indication but never a launch indication. I don't have a track of this right now but has anyone else experienced this?

According to @IronMike, ED controls the functionality that would correct a bug in the current AIM54C that is preventing the "Target Size Switch" from being functional. Currently the missile always goes active at the same time/distance from target regardless of the target size switch position. In patches prior to this one, the target size switch position would change at what distance/time the AIM54C went active on the target. Note: The AIM54A is affected properly by the target size switch. This only appears to be a problem with the AIM54C-MK60 & AIM54C-MK47

So this is something to be fixed then. It just is on ED's side and not HB's, right? Like we used to have this functionality for all of the AIM54's and now it broke for some of them. I can make a bug report in the weapons section for them to fix this.

I have also experienced this in the latest patch. Happens almost everytime where the RIO ctd's when joining the backseat

As someone who has color blindness, I would retexture some colors in cockpits to make them easier for me to read/see. This required editing of the many cockpit script files. Now I cannot do that AND be allowed to fly on MP servers. That also being said I understand how some of the files in there could have been used to 'cheat' but I seem to think, couldn't there have been another way to solve this. IE maybe grep all the files for certain strings that are associated with cheating and IC just those files as they tend not to be associated with custom cockpit textures, rather than the entire directory? This truly saddens me that this happened and was part of the alure of being able to play DCS in the first place.

Any status on when we may get the target size switch functionality fixed?