Jump to content

Silkworm Missiles


AG-51_Razor

Recommended Posts

Is there a problem with the Silkworm missiles now? In a mission that I made quite some time ago, they worked as they should (or at least as I think they should) and now, when I start that mission, they are not in the mission at all! The really odd thing is, when I open it up in the ME, they are there.

 

 

 

So, I came upon this issue when I was trying to build a new mission this morning but could not get the missile to fire on a blue ship at all. That is when I decided to go back and look at the other mission I built. However, in the case of this new mission, the silkworm is there in the mission while running, it just won't launch.

 

 

Both missions are attached here. The first mission I mentioned is "Measured Response" and the new one is "Going Straight"

Measured Response.miz

Going Straight.miz


Edited by AG-51_Razor
spelling error corrections

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I added an A-50 to red side and the Silkworm fired in Going Straight. They can't see over the horizon without an airborn radar.

 

 

I also made my own mission with ships much closer and they were able to fire without any external support.

Awaiting: DCS F-15C

Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files

 

Link to comment
Share on other sites

I added an A-50 to red side and the Silkworm fired in Going Straight. They can't see over the horizon without an airborn radar.

 

 

I also made my own mission with ships much closer and they were able to fire without any external support.

 

Thanks Exorcet. Did you see the same thing did in the first mission, the Silkworms not showing up while the mission is running but they are there when looking at it in the ME?

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I didn't have time to look at the first mission before, I have now and the problem is the Silkworks are set to spawn at 17:50 while the mission starts at 17:30. They will spawn after 20 minutes currently.

Awaiting: DCS F-15C

Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files

 

Link to comment
Share on other sites

I didn't have time to look at the first mission before, I have now and the problem is the Silkworks are set to spawn at 17:50 while the mission starts at 17:30. They will spawn after 20 minutes currently.

 

DOH!!! :doh: Thanks Exorcet I figured it was going to be something stup.....er, simple but that is over the top. I must have changed the start time at some point. Thanks again :thumbup:

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I added an A-50 to red side and the Silkworm fired in Going Straight. They can't see over the horizon without an airborn radar.

 

 

I also made my own mission with ships much closer and they were able to fire without any external support.

So AWACS can provide targeting data for Silkworms? That never occurred to me... I was surprised by their low range, but it makes sense if their own radar can't see beyond the simulated horizon. I'll try it later, interesting.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...