-
Posts
3180 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Tholozor
-
Probably related to the ARI bug?
-
TOO1 and TOO2 are individual to each weapon station (i.e. TOO1 on STA2 is different from TOO1 on STA8). This permits you to have up to 8 total individual TOO targets across all 4 stations, as the Hornet's maximum JDAM load is 8 total (2 for each station if loaded on BRU-55). Stepping to another station will invoke that station's last selected TOO mission. As an example, let's say you have 4 JDAMs loaded on BRU-55 racks on Stations 3 and 7, and you have 4 targets you want to engage. You might designate them like this: - TOO1 on Station 7 on target 1 - TOO2 on Station 7 on target 2 - TOO1 on Station 3 on target 3 - TOO2 on Station 3 on target 4 Or you could do it like this: - TOO1 on Station 3 on target 1 - TOO1 on Station 7 on target 2 - TOO2 on Station 3 on target 3 - TOO2 on Station 7 on target 4 Since the system doesn't "assign" TOO missions to individual weapons mounted on the rack, you would have to manually switch between TOO1 and TOO2 for each station between drops, otherwise *both* weapons on the rack would release on the same TOO mission. Personally, I prefer to use the second method of assigning targets between TOO1 and TOO2 on each station, as the active station will automatically step to the next one when a weapon is released. This way I can release all the weapons on their TOO1 missions first, then switch them to TOO2 as it steps back through the release order.
-
You can select the FMU-140 on the CBU-99 version of the Rockeye.
-
Turn down the gain, set the MPCD to night mode and adjust the contrast.
-
Seeing aircraft on the SA page only if TACAN is on
Tholozor replied to gunterlund's topic in Bugs and Problems
Did you also turn on Link16 from the second DL menu on the UFC? -
Seeing aircraft on the SA page only if TACAN is on
Tholozor replied to gunterlund's topic in Bugs and Problems
This version of the Hornet has TACAN and Link16 embedded in the same MIDS terminal, as opposed to older models that had a separate AN/ARN-118 TACAN module. -
Correct, but since Bob is "in control" he takes care of any turn coordination or thrust lever adjustments to keep the helicopter stable.
-
If you're not providing any more lateral input to the stick, Bob will interpret that as "don't turn." Think of it like dual-linked controls in the real helicopter where they move together. You're "guiding" Bob as to what you want him to do by moving the stick and thrust lever.
-
What do you mean by "it won't let me"? What weapon are you using? Do you have a track we can look at?
-
Apache AH-64D Flight Model and further Development Status in 2024?
Tholozor replied to Terrifier's topic in DCS: AH-64D
The tail rotor/crabbing is already a known WIP issue: -
Already reported:
-
The Weapon Insertion Panel uses alpha-numeric codes to tell the SMS what weapon is loaded with what fuze configuration. The code for the nose well is different if the weapon is equipped with a DSU-33 or not.
-
The M240H, which is the specific version equipped on this CH-47, does not include a guard on the barrel.
-
Any skins out there with 00- or 01- tail numbers?
Tholozor replied to Vampyr's topic in DCS: F-16C Viper
The good chunk of Block 50 F-16s in U.S. service were built in the early 90s. There were only a small handful of 00- and 01- serials that were built for U.S. service (about 4~5 for 2000 and about 10 for 2001). Compared to this, the amount of U.S. Block 50s built in the fiscal year for 1991 attribute to about a little over 90 airframes. That's not to say that the 00- and 01- serials are "invalid" (especially considering the original default livery for the DCS F-16 was serial 01-7052). It's just that the 91- serials for U.S. Block 50s are much more common. -
Any skins out there with 00- or 01- tail numbers?
Tholozor replied to Vampyr's topic in DCS: F-16C Viper
You would probably have to either find a custom livery that already changes the fiscal year of the serial number or make your own; that part of the decal isn't dynamic. -
Is the pod still in standby mode (STBY)? Top-left OSB to change the pod's mode (STBY, A-A, A-G).
-
@darkman222
-
just lil parking thing dont know if its really a bug
Tholozor replied to Pingodingo's topic in Bugs and Problems
If you're referring to 'YF1497,' that's the MGRS grid. -
Probably this mod:
-
CHECK TRIM will appear if the stabilator trim is not set correctly for takeoff, not sure why it's still present while airborne. BALT on the advisory line (ADV) just provides a constant reminder to the pilot that barometric altitude hold is engaged.
-
The E and F model Mavericks that the Navy uses have the heavier ~300kg warhead, which are only authorized for use on LAU-117 single rail launchers.
-
You can change the pilot's helmet in the advanced options for that aircraft in the 'Additional Properties' tab in the editor (the tab only becomes available if the aircraft is a Client or Player slot). You can select JHMCS, NVGs, or 'Not installed' (which will just be a normal HGU visor). The ground crew menu also allows you to select JHMCS and NVGs, but there's no option to remove either at the moment. Whichever option is actually equipped will override the 509 argument.
- 1 reply
-
- 1
-
-
There was no big announcement, it just kind of happened.
-
Known issue:
-
Lightning II pod laser ranging and markpoint/SPI accuracy
Tholozor replied to Yeti42's topic in DCS: F/A-18C
Markpoints have a bug currently where the elevation is saved incorrectly: