Shadow_1stVFW

Looking for if the landing area lights could turn on based off say an aircraft within the ICLS service volume and Time = after sunset In the event of a radio failure due to damage or using a script with built in ATC, this would be very useful at night.

I don't believe there is any RCS values at all. I think its a simple flag for what can be engaged and what can't. One of the chinese ships tracks bombs. (Which I'm not looking forward too, come on now) It can't be down to the weapon itself (I hope) because if a walleye is untackable and a JSOW is I have some issues with that. My main gripe so far is JSOW is classified as a missile where the walleye is not.

It makes perfect sense when you consider DCS sees it as a missile. Therefore the TOR can see it. That's my rub, it sees that rocket and can track and shoot it but not the GBU-31? And fine, if it's going to see missiles and not bombs, because DCS, can we at least be consistent with what a "bomb" is? Like why is the Walleye a bomb and not the JSOW? The JSOW and JDAM work almost the exact same, but the JSOW is a missile? I can understand the RCS of weapons being hard to make, sure. But let's be consistent in the meantime.

Is there a plan to visit the radar cross section of weapons in DCS? Currently its pretty clear by my testing point defense surface to air systems detect incoming missiles and not bombs. This produces an issue when bombs such as the Walleye, GBU 31, GBU 38 and others, which should produce very sizable radar cross sections are not detected. But munitions designed to to reduce radar cross sections such as the JSOW are detected. And since I'm on the topic, why is the walleye a bomb and the JSOW a missile? Both are guided, unpowered (flight) munitions. The walleye is even designated an AGM. Seems logically inconsistent. I'd even be happy if the JSOWs moved to the bomb category for the same reason Walleyes are, whatever that reason is. Sent from my SM-G960U using Tapatalk

Is there a plan to visit the radar cross section of weapons in DCS? Currently its pretty clear by my testing point defense surface to air systems detect incoming missiles and not bombs. This produces an issue when bombs such as the Walleye, GBU 31, GBU 38 and others, which should produce very sizable radar cross sections are not detected. But munitions designed to to reduce radar cross sections such as the JSOW are detected. And since I'm on the topic, why is the walleye a bomb and the JSOW a missile? Both are guided, unpowered (flight) munitions. The walleye is even designated an AGM. Seems logically inconsistent. I'd even be happy if the JSOWs moved to the bomb category for the same reason Walleyes are, whatever that reason is. Sent from my SM-G960U using Tapatalk

There is a UFC button in either the JDAM display or the mission page with a UFC option for HT. Height of function cam be set there. I had success with everything 1200 and below 1500 just seemed too high. And for something armored. You'll want to drop that lower to decrease the area and concentrate the damage Sent from my SM-G960U using Tapatalk

This and the APU Sent from my SM-G960U using Tapatalk

Try double tapping the nws button. Sent from my SM-G960U using Tapatalk

The landing area lights should trigger on automatically. For example when the deck crew run out of the way because they know a jet is coming, the lights could come on. Or with the ball overlay. When using something like the airboss script, running through case III comms twice just for lighting is a pain. Sent from my SM-G960U using Tapatalk

Me and a friend of mine are having an issue where the script is not saving units when running on our computer, but it runs just fine on our server for our wing. Do you have any idea about why that would be?

You're hitting SSS depress and creating an INS target point and your displays are changing for that. Sent from my SM-G960U using Tapatalk

I posted this on discord and didn't want it to get buried, so I'll do it here. I'm sure there are people with knowledge of the system, but I feel like there should be a way to A) change the coordinate system entry on the scratchpad from DDMMSS, I know UTM is coming, but there should be something. and B) the CAS page should be able to populate the lat, long and elevation from T0. I could be wrong, it's a gut feeling.