

BarTzi
Members-
Posts
967 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by BarTzi
-
I stand corrected.
-
It's not a method of calculating impact points, as Tholozor stated above. You asked what letter appears, and there is none. It's not used.
-
None, it's not a case.
-
The Viper doesn't have PB either.
-
Since this function does not exist, you can't bind anything to do it. You can achieve the same result if you bind the correct push buttons that do it when the HSI \ SA is displayed. You can set the HSI to go over the sequence automatically as you reach the waypoints, if that helps.
-
Mind if I join in and say the same bug applies for squelch?
-
Since day one
-
Why were there NO HiViz liveries for the NAVY created
BarTzi replied to CanopyJettison's topic in Wish List
Saving space\ time \ money. -
Hi guys, As you noticed, my previous work is now a part of DCS. The standard liveries can be seen in DCS if you place an Israeli Viper in the mission editor. Thanks for your support and your kind words I spent hundreds of hours making the decals right, and I'm glad to see the liveries used by so many people. In case you wish to still use the 60th anniversary version or barak 2020 one without having duplications / conflicts - i've made a separate pack which contains only those versions, and uses the textures already included within DCS (to save space). Enjoy: https://www.digitalcombatsimulator.com/en/files/3313552/
-
Checking NATOPS is indeed the right way. However, when reading about the displays it's important to note our hornet has the AMPCD, and as a result we should refer to the sections that detail the brightness control for the AMPCD only. Therefore, check 2.13.4.6.1 -2.13.4.6.5 instead. 2.13.4.6.1 Off/Brightness Control. This rotary switch is located in the upper center of the AMPCD and is used to turn the AMPCD off (OFF position selected) or to select the brightness level. The brightness control is enabled only when a mono raster display from the DMS is displayed; otherwise the brightness control is disabled. If the brightness control is actuated while disabled, an AUTO legend appears at 200% size to the left of the display center and is removed 5 seconds after the switch is released. If the brightness control is operating, a variable number from 0 to 9 appears at 200% size to the right of the AUTO legend to indicate the current intensity setting and is removed 5 seconds after the switch is released. 2.13.4.6.2 Night/Day Brightness Selector. This rocker switch is located in the upper left corner of the AMPCD and is used to select the lower brightness control (night) range and disable automatic contrast control (NITE position selected) or to select the higher brightness control (day) range (DAY position selected). When NITE is selected, the display is NVG compatible and contrast may be manually adjusted with the contrast control. When DAY is selected, automatic brightness control is disabled and display brightness may be manually adjusted with the brightness control. However, if a color display (digital map) is selected, the automatic brightness control circuits are automatically engaged. 2.13.4.6.3 Symbology Control. This rocker switch is located in the upper right corner of the AMPCD. Momentary actuations of the upper half of the switch incrementally narrows the symbology, making it sharper and dimmer. Momentary actuations of the lower half incrementally widens the symbology, making it brighter and less sharp. If the switch is held in either position, the symbology is continuously adjusted to the upper or lower limits. 2.13.4.6.4 Gain Control. This rocker switch is located in the lower left corner of the AMPCD. Momentary actuations of the upper half of the switch incrementally increases background video brightness. Momentary actuations of the lower half incrementally decreases video brightness. If the switch is held in either position, the gain is continuously adjusted to the upper or lower limits. 2.13.4.6.5 Contrast Control. This rocker switch is located in the lower right corner of the AMPCD. Momentary actuations of the upper half of the switch incrementally increase the contrast of the display. Momentary actuations of the lower half incrementally decrease the contrast of the display. If the switch is held in either position, the contrast is continuously adjusted to the upper or lower limits. When the contrast control is operated, a variable number from 0 to 9 appears at 200% size to the right of the display center to indicate the current contrast setting. Five seconds after the switch is released, this number is removed.
-
I don't think so. The bomb hits every time. Which one were you using?
-
Man is the only one that works 100%. Loft requires additional symbology. It might work in DCS without it at the moment, but I would not count on it. Dropping it 'in range'/ 'in zone' shouldn't change the final result, which is a hit on target. The difference is how the bomb hits the target. Drop it 'in zone' if you wish to setup terminal parameters.
-
You should report this as a bug :)
-
First of all, let's have all of the low vis liveries :) Some iconic squadrons are strangely missing, like VFA-25.
-
Read the posts from KlarS again. It was very well explained.
-
Yeah, it's confusing. Especially when the deployed baskets make you forget you have to call ready pre-contact :P If you try and tank like that your probe will go through the basket.
-
[NO BUG]GBU-31(V)1 and GBU-31(V)3 should no longer be available.
BarTzi replied to BarTzi's topic in Bugs and Problems
You are correct. Nearly all bombs have arguments that control the type of texture and type of fuze. That's how we got a screenshot of a grey gbu-54 when it was added for the a-10. The coating is already in the game, and this thread was opened mainly because: 1. If you don't plan on enabling the coating for those bombs now - adding the bombs (v2, v4) does nothing more than confuse people. 2. If you do add the coating now - add it to all of the bombs, and find a way to make the bomb list less cluttered. We only have the textures, and the bomb itself is not selectable. Also, when you add the different type of fuzes to that list it gets a bit... too much to handle at its current implementation. -
reported earlier HMD target designation shifts - Slant range related
BarTzi replied to GVakarian32's topic in Bugs and Problems
+1. Also - try to designate a target using the air to ground radar, and then switch sensor priority to the hmd. It will shift the target position by more than a few miles. -
[NO BUG]GBU-31(V)1 and GBU-31(V)3 should no longer be available.
BarTzi replied to BarTzi's topic in Bugs and Problems
I respectfully disagree. The plane is in early access still. RAZBAM just removed the X2 gbu-16 (on one pylon) options from their harrier, which will have an impact on every mission that used that loadout. The loadout shouldn't be unrealistic just because of previous missions. I'd like to also mention that I'm only bringing this up because the (v)1 and (v)2 are the same bomb, and (v)3 and (v)4 are the same bomb. It's just confusing. Also, keep in mind we should be getting more options for the fuzes (the ones that are on the JDAM right now are not very common nowadays), which will create even more subversions of the bombs, and more clutter if it's not cleared. -
It's one box. I just picked the worst frame possible. It's taken from the Jolly rogers cruise video: As for ATFLIR and mark points, are you referring to the small triangle looking icons with numbers next to them? If so, those can't be mark points since you can add more than 9. Those could be target points, which is another thing.
-
The first one shows a radar contact afaik.
-
Edit: should be in the bugs forum. My bad. When the selected air to air weapon cannot be used (usually it's when you set the master arm to safe), the name of the weapon is crossed out on the HUD. It should also be the same for the JHMCS. hmd weapon status.trk