Jump to content

[NOT A BUG] SLAM - can't get rid of the X


Recommended Posts

Posted

Just trying the SLAM for the first time today. Whenever I select SLAM on stores page, there is a large X through the box which I just can't work out how to get rid of.

I'm sure it is really obvious, but if anyone could put me out of my misery, i would appreciate it!

 

sl.jpg

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted (edited)

The big X just shows that your weapon isn't configured and in the correct parameters for launch. 

 

I don't remember the exact details but configure the weapon correctly as shown in YouTube tutorials (putting in the correct coordinates and linking the missile to your data link pod), and then get your plane in the launch zone as shown on your hsi. 

Then the X will dissappear and you'll be able to launch the weapon.

It is the exact same logic as other smart weapons such as the jdams/jsows

Edited by notproplayer3

Full fidelity su27/mig29 ?

Posted

Thanks, but it's not working for me.

I'm happy configuring the weapon as per JDAMS etc., and I can fire it and hit the target OK, but, there is always the X through the box at all times.

This is unlike the JDAMS/JSOWS which lose the X as soon as they have timed down to 7:30.

Also, in Wags' and the Reapers' videos, there is no X when they select A-G and SLAM. For me, the X comes on immediately the SLAM is selected and never goes away!

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

I think I'll post this in the Bugs section with a track. I can't see what I'm doing wrong.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

I posted here SLAM has X through box when selected? - DCS: F/A-18C Hornet - ED Forums (eagle.ru) on this, but I think it is more appropriate here.

Just trying the SLAM for the first time today. Whenever I select SLAM on stores page, there is a large X through the box which I just can't work out how to get rid of.

I'm happy configuring the weapon as per JDAMS etc., and I can fire it and hit the target OK, but, there is always the X through the box at all times.

This is unlike the JDAMS/JSOWS which lose the X as soon as they have timed down to 7:30.

Also, in Wags' and the Reapers' videos, there is no X when they select A-G and SLAM. For me, the X comes on immediately the SLAM is selected and never goes away!

Track attached. I know I didn't hit the target - I wasn't paying attention at the end! - but you can see my point.

I may be doing something wrong, but I can't see what.

sl.jpg

Hor SLAM cross.trk

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted (edited)
2 hours ago, imacken said:

I think I'll post this in the Bugs section with a track. I can't see what I'm doing wrong.

Sorry if I didn't get back to you sooner but you are absolutely right, just tested the weapon and indeed there is a big X on the weapon even when everything is configured correctly (I think).

Though the X and the missing "in range" cue seem to be the only bugged things because I could still launch my weapon and it would hit the target just fine (even if I didn't get the data link pod working). Here's a track by the way.

fa18agm84e.trk

Edited by notproplayer3

Full fidelity su27/mig29 ?

Posted

Thanks. Yes, I posted in Bugs here with a track. 

 

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

What is happening here? I posted a bug, and that thread has been merged here! If there was any merging going on, then surely this should have been moved to the bugs section. 

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

  • Wags changed the title to [NOT A BUG] SLAM - can't get rid of the X
Posted

I also ran a test and I couldn't get rid of the X either.
Valid PP data, EFUZ set, all other parameters set, well within range, AG mode, Master Arm On. The X remained, yet the weapon could be released normally and it correctly guided to the target. 

 

The X should be removed when successful weapon release becomes possible.

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

Posted

Right, so what is happening here. Firstly the thread was moved from the bugs section, and now Wags has marked it as ‘NO BUG’!

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

Looking into this a bit more.

 

Stable version - clicking on either the SLAM or JDAM in the stores page does not produce an X through their respective boxes.  Never appears AFAICS.

 

Open Beta - clicking on either in stores page shows an X in the box.  For the JDAM, the X disappears when it has counted down to 7:30, which seems like correct behaviour. The SLAM never loses the X, which does not seem correct.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

  • ED Team
Posted

The only bug here that I can see is when it is x'd out in the DDI it is not x'd out in the HUD. 

Otherwise everything looks normal to me.

 

notproplayer3 track shows a good launch without the x'd out ddi 

 

I will report the HUD issue

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

Thanks BN.

In notproplayer3's track, I see the same thing as in my track, i.e. the SLAM X does not disappear after the countdown to 7:30 and the RDY sign comes on.  With JDAM it does. Are you not seeing that like the others here?  That is strange.

Did you see my post above yours on the difference between stable and OB?

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

Sorry to go on, but here are shots that might show it better. Both are just after the 7:30 countdown to ready. JDAM shows X has switched off and RDY shows both under the box and on the payload.  SLAM still shows the X, doesn't show RDY under the box (obviously) but does show it on the payload.

s.jpg

JD.jpg

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

You're right, there is something strange going on, as I see the same situation in your track, i.e. the X doesn't go away. See attached.  However, I can see from your screenshot that it does for you.

 

s2.jpg

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

No mods, vanilla install. Did a repair and the same result.  The thing is, it's not just me, 2 others here including Harker are seeing the same thing.

This isn't the first time that we've seen this, i.e. different people seeing different things in the same track.  The last one was the Walleye before it got fixed, I seem to recall. Weird.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

Hi guys, I have the same problem as imacken. (since many weeks).

I have "SLAM" box crossed always, also when time is lower than 7:30. 

than, in HUD i see IN RNG, I can fire it, but always crossed

 

Emibat

[sIGPIC][/sIGPIC]

Posted (edited)

Same here. The osb label stays crossed out but the weapon appears to operate correctly. Plain-jane install. Open beta without any mods...

Edited by chaos

"It's not the years, honey. It's the mileage..."

Posted
4 hours ago, imacken said:

Thanks BN.

In notproplayer3's track, I see the same thing as in my track, i.e. the SLAM X does not disappear after the countdown to 7:30 and the RDY sign comes on.  With JDAM it does. Are you not seeing that like the others here?  That is strange.

Did you see my post above yours on the difference between stable and OB?

Yes, I can confirm, there was indeed is an X

Open beta with no mods.

Full fidelity su27/mig29 ?

Posted

Very pleased to say that the issue has been fixed in today's incredible update!

  • Like 3

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

  • Recently Browsing   0 members

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