Bunny Clark
-
Posts
1632 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Bunny Clark
-
-
On 1/6/2023 at 7:13 PM, Sedlo said:
It’s fictional?
A what if, if it were.
Oh I totally get that, I just wanted a more detailed backstory for the situation is all. What can I say, I'm a foreign policy nerd.
QuoteThere are Tomcats because there are no Super Hornets.
That totally makes sense!
QuoteThere are Sparrows in the first mission because… well, because.
Don’t worry, AIM-120 appears very shortly.Ah, I just need to play more missions then. I should get on that!
-
On 1/6/2023 at 5:20 PM, BuzzU said:
Bunny.........No answer to my question? I figured you'd know for sure.
I'm actually not sure. I've heard that the LITENING can't survive carrier operations, though that claim registers a bit high on my BS meter as I don't imagine it's much more fragile than ATFLIR. I've heard that the centerline mounting position the USMC uses for LITENING causes problems with carrier operations, as the pod picks up grease and oil splatter from cat shots. I've also heard that LITENING theoretically works just fine off the boat, the Navy just never saw the use in testing it to certify it for carrier ops since they already bought ATFLIR and certification costs time and money.
I don't have enough information to know which of the above explanations is most true.
-
Just starting out this campaign, looks promising!
I'm a bit confused about the backstory and setting though. There's an insurgency in the UAE? Iran has something to do with it? And if it's 2013 why are there USN Tomcats and why do I only have Sparrows?
-
They're not functional for anything in SP really. In MP they can be used to control SRS channels, but I don't think any AI assets in DCS can communicate using MIDS Voice yet.
-
On 1/4/2023 at 6:36 PM, DukeAngus said:
i use the TGP on the bottom mfd display the Advanced Multipurpose Color Display (AMPCD), i find it gives me a picture that i can easily use.
Technically, that's unrealistic. The AMPCD isn't wired into the aircraft video system, so it should not be able to display the FLIR page, nor Maverick video. ED said they were going to correct this years ago and haven't yet, so that capability may disappear on you some day, or maybe not, who knows?
-
Yup, the Hog and the Hornet work quite differently. I actually prefer the Hornet, to be honest, the Hog will let you have weapons and sensors pointed in all different directions with a target point in another totally different location and you need to hit buttons to bring it all back together. Not so with the Hornet. It's what's called a "single line of sight" aircraft - all sensors should always be pointing to the same place all the time, and that place should always be the target. There are a few exceptions to this, and some people try to drive at those exceptions to make it work more like a Hog - don't do it, embrace the Hornet workflow.
The fundamental concept of target workflow in the Hornet is that you have one Designated Target location, you can think of this like SPI, it's a similar idea. One sensor is always the Priority sensor providing Target Designation location, this is a bit like SOI in the Hog, but the difference is that the Priority sensor (identified by a diamond in the corner of the MFD) will by default be providing the Target Designation. There's generally no "Make SPI" command. If you're slewing around the FLIR pod in a ground stabilized mode, you are moving the Target location.
There's no indication in the HUD/HMD for where the FLIR pod is pointing because there doesn't really need to be. Nearly all of the time, the FLIR is pointing at the Target, and there is a Target indication in the HUD/HMD.
If you want to start looking for a target around a waypoint, select that waypoint on the HSI or SA page, and hit the Waypoint Designate (WPDSG) button. This will immediately designate the waypoint location as your Target and slew all weapons and sensors to it. The A/G radar will point to it, the FLIR will point to it, you'll have a target diamond, range, and a steering cue in your HUD and HMD, uncaged Mavericks will slew to it, and JDAMs in TOO will have the target point uploaded to them. If you want to look around the area with the FLIR make the FLIR page Priority, select Scene mode with SCS, and start slewing around. As you do, all other sensors and weapons will follow the FLIR pod. When the FLIR is pointing at your target, turn in and engage. No need to hit any additional buttons, where you're pointing is your target. If you want to return to the waypoint, move to a different waypoint, or markpoint: select it on the SA or HSI page and designate it again.
To designate a target with the HUD or HMD the process is very similar. Set the HUD to Priority with SCS Up, point the dot in the center of the reticle at the target, and depress the TDC Designate button. No need to differentiate between the HUD and HMD, the Hornet is smart enough to figure it out on its own - if you're looking at the HUD it'll use the HUD, if you look away from the HUD it'll use the HMD. Once designated you can keep slewing it around from the HUD/HMD, or make the FLIR priority and take over marking the Target location from there.
The Hog is a bit of a ponderous aircraft. The Hornet is a strike fighter, it's designed to quickly acquire one target, attack that target as rapidly as possible, and GTFO.
-
5
-
-
There's usually not even a reason to open the FPAS page unless you want to know your ideal altitude and speed. The HSI will show you your estimated fuel remaining on arrival of any selected waypoint or TACAN station. If you just want to know your fuel state when you arrive at the next waypoint, a quick glance at the HSI will tell you, no maths needed.
-
1
-
-
Have you installed any mods?
-
The Weapon Select Switch is a HOTAS switch, it's a side-mounted thumb switch on the stick. It's not clickable anywhere in the cockpit, you'll need to bind it to buttons on your controllers. It works best as a 4-way or 5-way hat switch, that's what it is on the real Hornet. The real-life binds are:
Forward = Select Sparrow,
Right = Select AMRAAM,
Depress = Select Sidewinder,
Aft = Select Guns.
-
Whiskey11's solution above is an excellent option, and probably the easiest and least time consuming way to do this. You can do it with JDAMs too if you have an accurate enough target point, though I don't think we have the official implementation of loft deliveries yet in the Viper, which will really help making longer range lofting attacks with JDAMs. This method can be less effective (i.e. deadly) if there are more low-altitude air defenses along the run-in approach path. If there is fighter cover, it can be very effective as the fighters may not detect you inbound, and then hopefully by the time they know you're there you've dropped and are on your way out at high speed.
Another completely unrealistic option is to dance around the edge of the SA-10 WEZ, goading it into shooting low pK missiles at you, defeating them by turning cold, and repeating that until all the launchers are out of missiles. Then fly in above the SA-15 WEZ and drop JDAMs or CBU-105s with impunity. This is great if there's a bunch of low altitude air defenses, but won't work as well if there are additional long range SAM sites around, or if the enemy has fighter cover.
-
2
-
-
15 hours ago, CBStu said:
In general would doing a re-arm to the ATFLIR mess up a mission that had the Litening originally?
Generally, no, there's no way that could cause a problem. If the mission had LITENING loaded on the canter pylon and you swap it to ATFLIR at the expense of an AMRAAM, that could cause an issue with the mission where the designer anticipated you having an additional missile available to you. Unlikely that success or failure in the mission would hang on one AMRAAM, but it may make things more challenging than the designer intended.
-
On 11/27/2022 at 9:40 AM, jonsky7 said:
You can switch it to night mode, top right knob, will get rid of ghosting and has little effect on display brightness.
Night mode does not get rid of the ghosting, it just makes the ghosted image dimmer and green.
-
On 11/13/2022 at 10:28 AM, konstpan said:
I'm so embarrased! Indeed there is an axis bound, and this is what caused the problem I reported.
No worries, we see this a lot with the Hornet because of how it's elevation axis works.
-
On 11/15/2022 at 10:34 AM, Brun said:
Requiring the user to compromise the directness of their control setup (very detrimental for AAR for example) for the sake of AP is not a solution. Ironically, this is a bigger problem with higher-end hardware than more mainstream sticks.
I'm running a Virpil WarBRD base with 0 deadzone and have no problems at all with BALT or any other autopilot modes.
It takes a fair bit of stick deflection to force BALT to disengage, and when it happens there's a master caution.
-
1
-
-
Do you mean setting up a campaign as a mission creator? Or flying a campaign as a pilot?
-
16 hours ago, Dragon1-1 said:
Technically, I suppose you could mount a LANTIRN system, complete with the navpod, to our F-16, and it would probably work.
I'm pretty sure the TFR on the NavPod would work, but for FLIR projection to work the HUD has to be capable of displaying raster images. That's not something all HUDs are built to do, and I'm not sure the HUD on the Block 50 is physically capable of it.
-
On the EHSI both the HDG and CRS knobs can be depressed. As stated above, depressing the CRS knob is how you adjust the brightness of the EHSI. I don't think depressing the HDG knob does anything. But you can click and depress it in the cockpit too.
@jaylw314 EHSI Mode is changed with the "M" button that is located between the CRS and HDG knobs, centered below the EHSI display.
-
3
-
-
9 hours ago, 104th_Crunch said:
I will assume that there will be no upcoming functionality with the ICP controls, but you know what they say about assuming?
Was just curious.
The Block 40/42 aircraft have a different HUD but share the same ICP. I don't think the HUD on the Block 50 supports FLIR image projection, leaving the FLIR controls on the ICP with no function on the real aircraft.
-
1
-
-
On 11/2/2022 at 3:44 AM, Ephedrin said:
what data do AMRAAM and Sparrow need to be loaded into? The Amraam is guided via datalink and the sparrow is a semi active radar homing missile that doesn‘t get or require any data at all. The connection between aircraft and Aim120 happens when you bump the weapon select switch up doesn‘t it?
For AMRAAM: Initial target data is sent to the missile in case the datalink fails or the track is dumped immediately after launch. The datalink itself also needs to be initialized so the missile knows what datalink signal to be looking for. If the target is close enough for the missile to go active off the rails, the initial target data that is uploaded is what it will use to begin its search and target acquisition, so it doesn't need to wait for a datalink signal before maneuvering for intercept.
For Sparrow: the missile is "tuned" to the launching aircraft. Each aircraft's illumination signal is encoded, and then the missile tuned to that signal, so that the missile can tell its target apart from the targets being illuminated by other aircraft for other Sparrows.
-
4
-
2
-
-
23 hours ago, AE0MT said:
This is a fantastic campaign, and I am working my way though it. Since it requires Supercarrier, any chance it can be modified to enable ACLS on the missions? Thanks!
Yup, I need to come back and add that to the relevant missions. Planning on doing that as I make sure that 2.8 didn't muck up any weather settings.
Someday I hope to come back and record real human voiceovers for at least some of the dialogue. Someday ...
-
1
-
1
-
-
A good quick reference is the HSI or SA Page. The target point reference should be directly abeam of the ownship aircraft symbol. If it starts to drift down: increase bank. If it starts to drift up, decrease bank.
-
2
-
-
On 11/4/2022 at 2:01 AM, Tholozor said:
If you're running HSI/SA or FLIR on the left DDI, you'll have to select AZ/EL manually from the TAC menu.
Technically, the menu is also a page that cannot accept Priority. So, if you want to jump from a page that can accept Priority to AZ/EL on the Left DDI in A/A, or the Radar page on the Right DDI, a slight shortcut is to hit the Menu button on that DDI and then SCS towards it.
Probably doesn't save any time if you're mousing, but with physical MFDs or a touchscreen it can be a bit faster.
-
11 minutes ago, 16th Widowmakr said:
Can you tell me where I can find or make a KU panel that has a widow for the KU text to show through? Thank you
Like the one bottom center in my profile? You can just download my profile from here and use it.
-
Awesome!
Yes, the DCS default monitor configs live in the DCS install directory, while user created configs are supposed to live in Saved Games.
Exporting RWR to a fourth display
in DCS: F/A-18C
Posted
If you're already accustomed to editing .lua files, this is pretty straightforward.
You'll want to edit two files first:
\Mods\aircraft\FA-18C\Cockpit\Scripts\IFEI\indicator\IFEI_init.lua
and
\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\indicator\RWR_ALR67_init.lua
In each file, add the following lines:
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("VIEWPORT NAME")Replace "VIEWPORT NAME" with whatever you want to call that viewport.
Keep in mind every DCS update will revert these changes, so make a backup or use a mod manager.
Next, go to your monitor config file and add new viewport definitions with the names you just used for the two init files.