AlexCaboose
-
Posts
268 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by AlexCaboose
-
-
33 minutes ago, zildac said:
Does it not work with 2.8?
Whoops, posted on the wrong mod. Meant to be the rain fix.
-
1
-
-
Will this be updated for 2.8 compatibility?
-
2
-
-
Did you remember to turn on MIDS LVT?
-
1
-
-
This mod was crashing DCS for me when slotting into a jet as of 9/29/2022.
-
I've heard it's a thing IRL, but it doesn't generally happen in DCS except at extremely light weights (like after a sortie) or on an incline. An example of areas of where it does occur is the EOR by the 03L end of Nellis (low weight), or Incirlik EOR on the 23(?) end due to the incline.
-
The DTC lets you customize however you want anyway. Why not make the default more user friendly?
-
1
-
-
1 hour ago, Deano87 said:
What @BIGNEWYis saying is that the GBU-24 is designed to be laser guided continuously from release to impact. It has a totally different seeker to earlier Paveway units. Fire the laser the whole time during the bomb fall. It is not meant to be lased in the last 10-15 seconds like the more primitive PW1-2 series weapons.
Adding on to this, the PW2 uses “bang-bang” guidance, which is basically a bunch of full deflections, which is probably why there is no DLZ. It’s inefficient and leads to a lot of overshooting on the way down. PW3 behaves more like a JDAM and should be continuously lased.
-
2
-
-
-
Yeah, I think someone goofed and this line was for the Hornet
-
What are these HOTAS improvements? Are these additional bindings or differing logic? There's no indication of what's changed in the patch notes.
-
AIM-120s should be loaded on the wingtips in the Viper. AIM-9s go inboard to reduce wing flutter and stress. You shouldn’t be flying the Viper outside of mid 400kts if you can help it to maintain best rate speed unless you are pulling for the 1C HOBS shot with the 9X. You need to fly the Viper like a Viper, not a Hornet.
-
2
-
-
1 hour ago, Silver_ said:
I totally agree but I remind you that the HAD screen shows data from the POD HTS mounted on the side of the aircraft and not from the missile's predisposition, in fact the HAD will show a range according to the type of anti-radiation missile mounted since the on-board computer knows perfectly what type of missile has been equipped and not from the preset data in other modes. What's more, when you program the missile in WPN (POS) you are programming part of the missile's behavior based on avionics and inertial positioning data and part is managed by the missile itself, in fact, according to HANDBOOK, the mode in which it is completely independent of the avionics and managed exclusively by the missile is the HAS mode (it is the most primitive/primary way of management) the POS mode, excuse me for saying so, but many parameters do not reside in the missile and are stored so that others can represent them displays such as HAD. The HAD is based exclusively on the sensors mounted on the POD HTS (AN/ASQ-213). So it doesn't make sense for the range to go narrow when changing it in POS mode.
I'm well aware of where the data for the HAD comes from. When in PB, you get a narrow cone, you do not get the ovoid. That's consistent with other simulators out there.
-
44 minutes ago, Silver_ said:
I do not care what it is called or should be called, what I know is that a configuration made in POS should not affect the HAD. They are two completely different forms of launch.
They're not though. HAD is just the display. The launch mode, as I was mentioning earlier, is still going to be a submode of POS. When you go to the WPN Video page and select PB, you are changing the mode the HARM is shooting in. HAD is just displaying that change and will give you a much more narrow launch window, because it's meant to be used against a pre-briefed target. In PB, you are giving the HARM a terminal search profile of 20nm radius if I'm not mistaken, which is huge. EOM that terminal search range is 5nm radius.
http://www.ausairpower.net/USN/HARM-Profiles-S.jpg
That picture provides a good example of the flight profiles of the HARM. EOM is the most accurate flight profile.
-
On 9/13/2022 at 12:13 PM, D4n said:
And as previously stated, it'd make sooo much more sense if "HAD" 'd be renamed to "HAM", harm attack mode. Because the actual display is actually called MFD (or MFCD)...
That wouldn’t actually make any sense at all. The mode is POS, and the submode is generally EOM. It’s called the HAD because it’s displaying the attack profile of the HARM and various targetable emitters, their general locations, the emitter status, and accuracy of the fix. You are still shooting in a POS submode, so the mode doesn’t change.
-
1
-
-
It's definitely many. ATC rework was promised years ago, and I hope it's in the works.
-
1
-
-
20 minutes ago, Droning_On said:
thanks but QNH is referancing sea level not airfield level. The ATC specificaly notes runway QFE at a Barometric Pressure level below what I can set on the F-16C Altimeter control knob?? Runway in Question was Nellis btw !!
Just seemed strange
That doesn't give you anything useful for TOLD at 1850 feet.
-
2
-
-
Most countries use QNH, not QFE. To expand on this, QFE is altitude above the field, whereas QNH is altitude above sea level below transition level (usually 18000ft). QNH should give you a better understanding of your aircraft’s performance for TOLD.
-
2
-
-
-
1 hour ago, ac5 said:
Well, thanks to your replies, but I don't get it... How do I release GBU's or CBU's in CCRP as it was usual
before last stable update 2.7.16.28157?
The last few OB updates, ED made it so that you need to release them with 5mil constraints instead of 3/9 which to my understanding is incorrect. That means you need to be very accurate with lining up the ASL to release.
-
The magnetic heading of the runway with ILS active.
-
On 12/29/2021 at 7:51 AM, BIGNEWY said:
Updated list from the team, the manual will be updated soon.
Display Name RWR DED ID Class number SAM SA-10 S-300PS SR 5N66M CS 103 1 SAM SA-10 S-300PS SR 64H6E BB 104 1 SAM SA-11 Buk SR 9S18M1 SD 107 1 SAM SA-10 S-300PS TR 30N6 10 110 1 SAM SA-11 Buk LN 9A310M1 11 115 1 SAM SA-15 Tor 9A331 15 119 1 HQ7 Self-Propelled LN 7 127 1 HQ7 Self-Propelled STR HQ 128 1 SAM SA-5 SR "Tin Shield" TS 130 1 SAM SA-6 Kub STR 1S91 6 108 2 SAM SA-8 Osa 9A33 8 117 2 SAM SA-3 S-125 TR SNR 3 123 2 SAM SA-2 TR SNR-75 Fan Song 2 126 2 SAM SA-5 TR "Square Pair" 5 129 2 SAM SA-13 Strela-10M3 9A35M3 13 118 2 SAM SR P-19 S 122 2 CP 9S80M1 Sborka DE 109 3 SAM SA-19 Tunguska 2S6 19 120 3 AAA ZSU-23-4 Shilka A 121 3 EWR 1L13 S 101 4 EWR 55G6 S 102 4 CV 1143.5 Admiral Kuznetsov SW 301 5 CV 1143.5 Admiral Kuznetsov(2017) SW 320 5 FFL 1124.4 Grisha HP 306 5 FFG 11540 Neustrashimy TP 319 5 CG 1164 Moskva T2 303 5 FF 1135M Rezky TP 309 5 FSG 1241.1MP Molniya PS 312 5 CGN 1144.2 Piotr Velikiy HN 313 5 Type 071 Amphibious Transport Dock PS 408 5 Type 052B Destroyer MR 409 5 Type 052C Destroyer HN 410 5 Type 054A Frigate MR 411 5 SAM Patriot STR AN/MPQ-53 P 202 6 SAM NASAMS SR MPQ64F1 NS 209 6 SAM Roland ADS RO 201 7 SAM Hawk SR AN/MPQ-50 HK 203 7 SAM Hawk TR AN/MPQ-46 HK 204 7 SAM Roland SR RO 205 7 SAM Hawk CWAR AN/MPQ-55 HK 206 7 Rapier FSA Blindfire Tracker RP 124 7 Rapier FSA Launcher RT 125 7 AAA Gepard A 207 8 AAA Vulcan M163 A 208 8 Ticonderoga class AE 315 10 Oliver Hazzard Perry class 49 401 10 LHA-1 Tarawa 40 407 10 DDG Arleigh Burke IIa AE 412 10 CVN-70 Carl Vinson SS 402 10 CVN-71 Theodore Roosevelt SS 403 10 CVN-72 Abraham Lincoln SS 404 10 CVN-73 George Washington SS 405 10 CVN-74 John C. Stennis SS 406 10 CVN-75 Harry S. Truman SS 413 10 @Frederf This is for the HAD. The "class" is the HAD threat table. You can see the SA-15 matches up to #1 as you mentioned.
Edit: I can't remember who made these kneeboards, but someone posted them in another thread some months ago when the HTS was released.
-
2
-
-
The full table is above, but you can always create a manual table and turn off the default tables for faster scanning.
-
On 12/11/2021 at 12:44 PM, Raskil said:
Hi,
I use VAICOM Pro in TX Link mode with SRS. I can do the short TX button press without any issue. The command gets recognized executed and Vaicom suspens again.
Addionally I want to daisy chain my own Voice Attack profile, so I can get voice commands for a few things I need in VR (mainly holding down the FCS Bit switch in the FA-18 and for setting SRS overlay modes".
So I created a second voice attack profile with commands in them and linked them in the Vaicom Voice Attack profile under "Include commands fron other profiles".
If I tap the TX button now, I can say the commands from my own profile as well. They get executed as well, but unforteuneatly, Voice Attack/Vaicom does not go back to "Listening suspended" After my own command executed.
How can I fix that?
Regards
Raskil
Did you ever get this resolved?
-
I am unable to get the TX setting to work correctly. When I long press, listening does not suspend, despite following all of the steps in the manual. The only way for me to be able to talk over SRS with this setting is to basically go through 3 button clicks before I am able to speak, and Vaicom/VA are listening constantly for any communication.
VAICOM PRO plugin for VoiceAttack
in VAICOM
Posted
Yeah, busted for me now too. Vaicom seems to be dead.