-
Posts
4501 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Harker
-
This is correct behavior. VS is a legacy mode that's incompatible with MSI, so it's not available via the pushbutton rotation.
-
Yes!
-
BRU-55 with 2x AGM-154A ignores TOO2 coordinates
Harker replied to vilson.farias's topic in Bugs and Problems
Yes, all steps look correct. As long as you remember to select TOO1 for each station, launch from each station, then change each station to TOO2, and launch, you should be able to hit all eight targets. (Correct on the QTY use as well: QTY will just allow you to drop from multiple stations, the weapons will still go to their respective targets.) -
BRU-55 with 2x AGM-154A ignores TOO2 coordinates
Harker replied to vilson.farias's topic in Bugs and Problems
Sounds like correct behavior. TOO1 and TOO2 (as well as PP1-6) refer to the station, not to the individual munitions on that station. The JSOWs will go "wherever the station says they should", at the time of launching. Also, TOO1/2 and PP1-6 are station specific and are not shared between stations (using QTY or otherwise). For example, if you select to TOO1 on STA2, and fire the first JSOW, then you must manually switch to TOO2, if you want to use the TOO2 coordinates for the second JSOW on STA2. -
Since a hostile firing at you will (should) inevitably start maneuvering, staying in INTL will ensure the best of both worlds. When you're engaging a target, you should try to get a high update rate on them, by narrowing down the azimuth, or using TWS, which will do it for you (I use TWS 40/4 or 20/6). That way, even if you only pick up the HPRF returns, they'll still provide fast updates, and when/if HPRF starts losing out to MPRF, you'll immediately pick the latter up, without having to fiddle with the radar. Or use STT, which will automatically use the correct PRF for the present situation, regardless of your previous setting. (In DCS, STT uses HPRF for all hot targets, and MPRF for all cold targets. It should use MPRF as much as it can though, for increased resistance to notching, only resorting to HPRF if necessary, i.e. STT on a hot target at long range - reported internally).
-
The default starting point of the system is INTL. Most times, you want to switch to MPRF, so that comes after. It's less common to be in HPRF only, and then switch to MPRF.
-
investigating AIM-7 Sparrow will not guide after FLOOD manualy initiated
Harker replied to GumidekCZ's topic in Bugs and Problems
As per official docs, FLOOD can indeed be manually selected with a Sparrow in flight, and the use case in this scenario is to salvage the shot, if the radar is having trouble maintaining STT. So, if this is is not possible in DCS right now, it's indeed a bug. -
The bricks are still there, but may be hard to see over the terrain video. The terrain showing in GMT and SEA without INTL being selected, is a reported bug that only occurs in MT.
-
DCS: F/A-18C Screenshots and Videos (NO DISCUSSION)
Harker replied to Vitormouraa's topic in DCS: F/A-18C
-
not a bug Message "shoot" still not appearing and A-A radar often loosing lock
Harker replied to ac5's topic in Bugs and Problems
You need the steering dot to be inside the ASE circle, and be within max range, in order to receive a SHOOT message. In your screenshot, the dot is to the right of the circle and you are outside of max range. -
ED didn't do anything, these are unofficial mods, and it's up to the people who made them to ensure that they keep working between updates.
-
You can switch to TWS, same as before, by using OSB 4. You don't need to press the DDI button either, you can switch by hovering over the radar mode (RWS) with the TDC. It'll expand the list, and you can select TWS from there.
-
acknowledged Aircraft markings after latest uppdate.
Harker replied to Jsood's topic in Bugs and Problems
Is this a vanilla or a custom livery? If it's a custom one, the structure of the description.lua file changed. You can find the new format by looking into any of the liveries included with the base game, in CoreMods. -
Hi, to my knowledge, nothing related to this mod has changed in the last update. Tested and it still works OK for me, without any changes. I suggest re-applying the mod step by step, and if you'd be so kind to post if it worked.
-
I'm sorry, I don't use export and I don't have experience with it. Is this problem isolated to this mod, or is it present without it as well?
-
correct as is TWS designates a contact no matter what
Harker replied to Razor18's topic in Bugs and Problems
You can narrow the scan or select a specific azimuth value from the pop-up list/OSB if you want, but unless you do, TWS should always choose the widest azimuth setting available. If pilot adjusts the azimuth -> TWS keeps that azimuth, as you cycle through 2B, 4B and 6B (if it can, based on the number of bars - azimuth limitations). If pilot does not adjust the azimuth -> TWS will choose the widest azimuth available, as you cycle through 2B, 4B and 6B. Again, not available in DCS for now. -
Yeah, I can't watch the track now, but the behavior in the video is definitely a bug. Good catch with this occurring if you're not in A/G.
-
Still separate.
-
correct as is TWS designates a contact no matter what
Harker replied to Razor18's topic in Bugs and Problems
That's a separate thing entirely, but the way it's always worked in DCS is that the radar works with overwrites, as in, any change (except acquisition modes) will overwrite the settings, requiring you to set them again. Or you can de-select and re-select your weapon, which will load its own settings. I don't have specific info on whether or not RWS should resume its old settings, once exiting TWS. What I do know is that TWS should always choose its max available azimuth for the current elevation bar setting, unless a specific azimuth option has been explicitly selected by the pilot. We don't have that in DCS, for now. -
acknowledged Aircraft markings after latest uppdate.
Harker replied to Jsood's topic in Bugs and Problems
The structure of the description.lua changed with the last patch. You can find the new structure in the livery folders in CoreMods or by generating a new lua file with the Model viewer. -
This was wrong in the past and corrected now. CCIP should not be available with a ground designation, it should always revert to AUTO. The program will still say CCIP, because that is the program's selected mode, regardless of designation.
-
correct as is TWS designates a contact no matter what
Harker replied to Razor18's topic in Bugs and Problems
Yes. You should maintain a high search volume until you are ready to target anyway, so you can sanitize the airspace in front of you. So, RWS until you're at the 45-50 NM point. You then switch to TWS for targeting and high update rates. -
correct as is TWS designates a contact no matter what
Harker replied to Razor18's topic in Bugs and Problems
It was actually introduced that way initially in DCS, then broke some time ago, now it's fixed :). -
correct as is TWS designates a contact no matter what
Harker replied to Razor18's topic in Bugs and Problems
The behavior is correct as is, TWS will always have an L&S, as long as there is at least one available trackfile. At least based on public info. If you enter TWS without an L&S, it'll automatically make Rank 1 the L&S. If you press RSET (which is supposed to just reset targeting) in TWS, it'll return the L&S to the Rank 1 trackfile.