

Ramsay
-
Posts
3744 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ramsay
-
-
Not sure. But close enough that he gets missile lock on me and fired.
Sounds like you should have reset - if you haven't detected the hostile by 15 NM you should open up some distance before trying to reacquire (it's too easy for a hostile to get under your radar)
I have radar scanning at 140 degrees should I lower it?In general, yes (the wide sweep makes the update rate slow).
Shouldn’t they show up mission map?It'll depend on the mission settings.
There's a simple practice mission here
-
I check and it just bounces back and forth between Hi and Med.
It does 1 bar at Hi, the next at medium - as the bars overlap, it covers the section of sky using both PRF modes at the expense of reduced detection probability, the Hi/Med scan order changes for the next top to bottom pass.
I'll initially use 4 or 6 bar with a 80° sweep to detect most targets, range will depend on size, aspect and altitude.
L-39ZA @ 26 NM / 17,000 ft
TU-142 @ 118 NM / 25,000 ft
Having an AWACS in the mission to populate the SA page via the data link and give BRA calls helps.
Please share a track where you can't detect targets.
Tested in DCS Open Beta 2.5.4.28090
-
In Wag's YouTube video on Datalink & SA Display, he says the number after the call sign is distance () but later on in the video he says it is fuel state (). Which is correct?
For the time stamps linked, the second number is Fuel State.
What the line reads depends if the contact is Hostile/Unknown or a Friendly sharing info via link-16.
Friendly ID ..................... E3, F15, FA18 OD086 / 12.4 ........... Callsign / fuel state i.e OD=OverlorD flt No. 086 / 12,400 lbs fuel BRA 045 / 10 ........... BRA 45°T for 10 NM BE 090 / 30 ............ with respect to BullseyE - 90°T for 30 NM (BE line is blank if no A/A BE waypoint has been set) Hostile/unknown ID, possibly blank ............... SU27, MG29, IL76, UKN, possibly blank Ground Speed / Heading ........... 602 / 142 = 602 Knots / Heading 142° (Ground Speed / Heading is usually out of date, lets you know what was happening ~20s prior) BRA 045 / 10 ..................... BRA 45°T for 10 NM BE 090 / 30 ...................... with respect to BullseyE - 90°T for 30 NM (BE line is blank if no A/A BE waypoint has been set)
-
And the inability to see the info on the bottom right? Just put it down to EA bug? Has it been reported?
It's the Warning Advisory on the LH DDI and is said to be realistic, hence why the SA should be on the MPCD and the Radar on the RH DDI.
-
What am I doing wrong, and is there a use for TMS Forward Short besides allegedly locking a maverick target after using the TGP?
Without a track, it's hard to tell.
This is my procedure (note I have custom keybinds) :
DSMS Select Mavericks Set Mavericks on RH MFCD Use UFC to set Mav Slew to 1.0 (UFC 1, then OSB8 ) Set TGP A-G on LH MFCD as SOI (coolie hat left, Delete) Boat Switch Forward to Switch IR Mode WHot [R-Ctrl+ LH Arrow] Find target using Slew controls (Arrow keys) China Hat Forward-Short to change FOV (R-Shift+Up Arrow) DMS Up/Dn to Zoom In/Out (R-Shift+POV Hat) TMS Up-Short to cycle Area/Point track (R-Ctrl+POV Hat Up) TMS Up-Long to set TGP as SPI generator (R-Ctrl+POV Hat Up) HUD Bottom LH shows TGP as SPI China Hat Forward-Long to slave all sensors to the SPI (R-Shift+Up Arrow) Maverick as SOI (coolie hat right, PgDn) TMS Up-Short to Lock on Mark Point
Tested using AGM-65D's @ 5 NM in DCS Open Beta 2.5.4.28090
-
Is this only in the beta DCS or has it gone into the release version?
Just in Open Beta - there are some bugs to fix, as well as features to add.
This interrogation method seems a bit long winded, but I suppose it's true to the real Hornet?:(There are more features to come, AFAIK there's an IFF auto-mode plus the radar tracks/bricks will inherit some HAFU symbols.
-
All good guys, thanks. What do the numbers on the SA mean once the aircraft has been identified?
At SA cursor - Mach and Altitude (FL) i.e. 0.7 | | 25 = Mach 0.7 @ 25,000 ft
Bottom RH corner of the SA page
Friendly ID ..................... E3 OD086 / 12.4 ........... Callsign / fuel state i.e OD=OverlorD flt No. 086 / 12,400 lbs fuel BRA 045 / 10 ........... BRA 45°T for 10 NM BE 090 / 30 ............ with respect to BullseyE - 90°T for 30 NM (BE line is blank if no A/A BE waypoint has been set) Hostile/unknown ID, possibly blank ............... SU27, UKN, possibly blank Ground Speed / Heading ........... 602 / 142 = 602 Knots / Heading 142° (Ground Speed / Heading is usually out of date, lets you know what was happening ~20s prior) BRA 045 / 10 ..................... BRA 45°T for 10 NM BE 090 / 30 ...................... with respect to BullseyE - 90°T for 30 NM (BE line is blank if no A/A BE waypoint has been set)
-
Do you have a track?
Here is one, the bug is a little like the SA BRA bug, if I fly 0°T everything is correctly positioned.
Normally the map turns about the aircraft, aligned with north on the compass rose on both the HSI and SA page.
Here I'm approaching Radar AA on the disused airfield near Kobuleti
If HSI MapM is set to North Up, flying 0°T everything is correctly positioned on the SA page (as compass rose and map North are aligned).
However at 90°T, AA threat rings, bulls, etc. are in the sea, as the map stays fixed and doesn't turn with the SA compass rose.
Tested DCS Open Beta 2.5.4.28090
FA-18C SA Map when HSI is using N up, 2_5_4_28090, LastMissionTrack.trk
-
B-be gentle guys :huh:Does not play well here.
Plane ends in the grass before reaching the runway, sorry.
Same, but I was able to look at Captain Orso's mission.
There is a light wind from the West (5 kts toward 67°T) and Kobuleti ATC/aircraft are using RWY 25 which does not have ILS.
Only RWY 07 has ILS and that is turned off, hence you will not detect a ILS signal.
-
I got this game to learn about modern fighter A2A combat. My first plane was the F-18 which I am still learning and I enjoy a lot. I'm thinking of the Easter sale, and I wonder if buying the F-5 and some of its campaigns would be worth it.
The main reason for getting the F-5 is for the extra content that I can buy in the form of campaigns and missions. I'm not a fighter enthusiast who feels like he needs to collect and learn a bunch of planes. One solid fighter is all I need. But maybe the F-5 could teach me useful info that I can apply to the Hornet later. I'll also admit that for someone who is completely new to DCS, it is a little hard for me to learn the Hornet because it is WIP. It would be nice to have a time tested user's guide and a plane that is not changing so much to learn with.
Although the F-5 has simpler systems, it's harder to use effectively - starting out, you'll be using AWACS/F10 to find targets.
Would this be a waste?IMHO, yes (other than learning to appreciate the Hornet's systems more).
Would the F-5 bring anything to the table that is worth mentioning in terms of learning BFM skills?Not, particularly - you can turn off the Hornets data Link, set your radar to 2 bar/80° and load up 2 sidewinders and achieve a similar spec.
Did I "miss a step" in the progression by starting with the Hornet?Yes, but not in a bad way. A T-45 trainer is equipped with Hornet systems to train navy pilots, in a sim. it's possible to train in the Hornet without cost/equipment penalty.
Should I just stick with the Hornet and wait for it to develop around me? I do enjoy a lot of things about the plane. It's just that I finished the tutorial and all the free content that it came with, and I'm not sure what to do now.It sounds like you're ready to move to the Mission Editor and create some simple training missions.
Yes I still feel like I have everything to learn.I'm not interested in an A-10 c or a helicopter. I like fighters. The user created missions tend to be advanced and complicated.
Perhaps look at the navy's CNATRA (T-45) training material and setup some simple 1v2 missions vs L-39 or similar using the ME and once confident/bored step up the difficulty/aircraft type.
Easter's coming, so I'm gonna buy something. If not a plane, then another map.Buying maps, you'll face the same issue re:content and the need to use the mission editor.
With regards to other aircraft, it'll depend if your happy to be a "jack of all trades (master of none)" or have the patience to practice/become expert in the Hornet in all it's aspects.
I switch modules for variety ("a change is as good as a rest") - but it gets harder to maintain competency the more modules you own.
-
Note: The CE2 is now available via the Steam Store.
https://store.steampowered.com/app/1024703/DCS_Christen_Eagle_II/?curator_clanid=4471395
-
Haven't been to multi seat MP yet - how does that prompt look like? Is it a window popping up right amidst the screen that I have to click away?
A request dialog 'pops up' on the LH side of the screen, near where the chat text scrolls.
-
In real life AWLS = ICLS (same equipment/microwave radar) but, as Razbam designed/implemented the Harrier's AWLS before ICLS in DCS was a thing, they made it compatible with DCS's ILS.
As the real Harrier AWLS has no way to set a ILS frequency (it uses one of the 20 ICLS channels), DCS AWLS/ILS frequencies are set via a lua file.
The DCS Harrier AWLS is a bit of a fudge but about 45% owners (small survey) want it to remain as is, which is fine - however it needs fixing so it works in Nevada, etc.
AN/TPN-30B (a portable AWLS/ICLS station with integrated TACAN)
In use (by F/A-18's)
-
A1-F18AC-NFM-000
Page VII-24-55
None of that says that MIDS won't work if a TACAN station broadcasts on one of those frequencies (if it was that easy to jam, MIDS wouldn't be very jam resistant).
Only that TACAN DME range is reduced to the rear aspect.
Flight test data at afloat stations shows that maximum tail-aspect DME ranges of approximately 22 nm at 6,000 feet and 26 nm at 15,000 feet can be expected to make DME unreliable when headed outbound in the marshal stack.At shore stations, flight tests have shown substantially better tail-aspect DME ranges (e.g. 52 nm at 15,000 feet).
DME ranges in the forward and side quadrants of the aircraft, and bearing performance in all quadrants, are not impacted. Therefore, approach performance on the affected channels is nominal.
NOTE
MIDS equipped aircraft may experience TACAN bearing and DME dropouts. MIDS equipped aircraft with a centerline tank may experience loss of DME during outbound legs from TACAN stations 1 to 29X and Y, 47X to 63X and 64Y to 92Y.
What we see in DCS is very different to TACAN LOS/signal strength issues.
-
Isn't it about time that the AWLS channels are included on the standard kneeboard airfield cards?
The AV-8B is still in early access, AWLS is ICLS anyway, so you should be using a TACAN approach if flying realistically.
There's nothing to stop Razbam adding a AWLS/ILS page to the module's own set of pages - but first, they'll want to get their AWLS/ILS channels working in Nevada*.
*note: It also doesn't make alot of sense to have AWLS at Tiblisi, Mineralnye Vody, Belsan, Sochi and Nalchik, as AWLS is designed to be used with TACAN to line up on the approach vector and none of those airfields have TACAN.
-
Now if I touch ANYTHING on CVN, like deleting its tacan transmission in advanced wp actions, it all works.
Its not the TACAN because with another mission I manually set that (same settings) and it also works. Attached both. The mission with '2' in the end works, the other one does not have datalink for me.
Mission 2 works because the Stennis TACAN 1X has not been assigned to a unit, so isn't transmitting.
Assigning it to "Unit #001", will break the F-18C data link again.
Setting the Stennis's TACAN to 74X, works fine.
Take care when assigning TACAN channels.
-
Do you mean from BE to the target?
Yes, top left is the cursor, bottom right is the target.
-
Just to be clear, the call on the upper left of the SA is from BE to TDC and the call on the last line of the lower right is from BE to ownship?
No, the lower right BE is to the target from the link-16 info i.e. your TDC cursor may be placed a little different.
ATM, there are two bulls displayed - top left for the cursor, and bottom right for target info. (only displayed when the cursor is over a target).
What is the bug on the last one?The bugged SA BRA bearing is with respect to your heading, not the cardinal direction, so
• BRA 0 / 10 = at your 12 O'clock for 10 NM i.e. straight ahead for 10 NM
• BRA 90 /10 = at your 3 O'clock for 10 NM i.e. turn 90° left and fly 10 NM
rather than
• BRA 0 / 10 = 0°T for 10 NM i.e. north for 10 NM
• BRA 90 /10 = 90°T for 10 NM i.e. east for 10 NM
as it should be.
Tested DCS Open Beta 2.5.4.28090
Note: Top right is bearing, distance and time to your selected waypoint.
-
I created a practice mission just to test out SA. Threw in an E-3 and few hostile aircraft. The AWACS didn't appear. I swapped the E-3 for the E-2D and got the same result.
Did you add EPLRS to the AWACS in "Advance (Waypoint Actions)"
If it's an airspawn you should be good, else IIRC, you'll need to turn on the D/L and IFF on the UFC.
Can you share your mission or track, so we can see what's up.
I posted a track file from a simple practice mission with a E3 and MOOSE spawned C-101, L-39 and F-5E here -
https://forums.eagle.ru/showpost.php?p=3818419&postcount=7
... you could play it and take control or rename the .trk file to .miz and put it in "Saved Games\DCS\Missions" to play/examine.
-
I have bought the SU 33 with 10 missions from a russian carrier. And now all missions are gone!?(
The Su-33 has a couple of missions in 'Missions' and 'Quickstart/Instant Action'.
So I'm guessing you are asking about the Campaign 'Sea Dragon'.
• I find 2 Su-33 Campaigns 'Heavy Sky' and 'Sea Dragon' under "Campaign>FC3"
As I own FC3, rather than the standalone Su-33, YMMV.
A copy of 'Sea Dragon' can be found in the User Files download section, if it's not included in your install for any reason.
• https://www.digitalcombatsimulator.com/en/files/3303252/
and can be installed to
• Saved Games\DCS\Missions\Campaigns\en\Sea Dragon
... or similar i.e.
• "Saved Games\DCS.openbeta\Missions\Campaigns\en\Su-33 Sea Dragon Campaign (fixed by MadDog-IC)"
User installed campaigns are found under "Campaign>My campaigns".
-
Guys, when we have SA page now, where I can find expantation of HAFU symbols? Thanks!
The HAFU icons are mirrored, the top half how you've IFF'ed the the contact, the bottom - how link 16 (E3, etc.) has IFF'ed them.
https://forums.eagle.ru/showpost.php?p=3797498&postcount=128
https://forums.eagle.ru/showpost.php?p=3812342&postcount=134
-
It's the blank line(s) for the error advisory that appears near the bottom of the LH DDI i.e. Autopilot status, inlet ice, FPAS, etc. - it's true to real life.
-
I would call 2 additional people having the same problem being able to reproduce the issue but hey thats just me I guess. well time to spend my evening rebuilding the mission from scratch again
The issue with your mission is the inclusion of 2 tankers with TACAN
• KC-135, TACAN 1Y
• KC-135MPRS, TACAN 2Y
... they stop the E3/Hornet datalink working.
Disabling both (using the late activation check box) fixed the data link.
I didn't do much investigation, but re-enabling one, but putting it on TACAN 17Y allowed TACAN azimuth and the E3-->Hornet data link to work (note - TACAN 17Y didn't give distance but I didn't check the tanker's ME settings).
-
Please include a track.
Here's one, it wasn't recorded specifically to show the bug but can be fast forwarded and you can take control as needed.
FA-18C, SA BRA bearing bug, 2_5_4_28090, LastMissionTrack.trk
Datalink SA - Number after Callsign is Distance or Fuel State?
in DCS: F/A-18C
Posted
Target Mach and Altitude is shown either side of the cursor i.e. 0.7| |25 = Mach 0.7 @ 25,000 ft