BarTzi

A/C sub menu is also partially implemented, and doesn't give accurate info (wind is one example). And speaking of the HSI, what about the HSI related HOTAS commands? The one that cycles HSI and SA is very important in my opinion.

Why do you have to increase the wind that much to get it to pitch?

Not the most efficient way, especially in combat, but just TDC depress on the DT2, and it will make it the new and only L&S

From NATOPS page I-2-13: External Transfer Caution Display. On F/A-18C/D aircraft, an EXT XFER caution display on the DDI indicates that external fuel is available and should have transferred. The caution is also displayed when external fuel is available at BINGO and FUEL LO. What's wrong in DCS: At the moment, it doesn't take the fuel quantity in the tank into account. It will immediately pop EXT XFER when you set any external tank to STOP on the EXT TANKS panel - which is the correct behaviour. However, it will also do it when the tank is completely empty - which is wrong. EXT XFER empty tank.trk

C/F means chaff flare mode, which is very vague. Since we don't have access to NTRP, it might be good to ask ED about it.

+1

It usually happens if I use the radar to lock or bug someone during the flight. It also doesn't lock, it just bugs the target, so no RWR spike.

Yes, I think it's described here: Channel Display Windows. When the corresponding radio is on, the selected channel (1-20, M or G) is displayed on the 16 segment alphanumeric display window. The diagonal display segment in the lower right quadrant of each display window illuminates whenever transmissions are received on comm 1 and comm 2, respectively. That's from NATOPS page I-2-112. (You might want to check that last sentence about the illumination during transmission with an SME, because that's also missing in DCS)

Any update on this? It makes a Hornet that is more than a mile away from you look like a massive torchlight. I would also like to add that changing the position of the light intensity knob (position lights) does almost nothing to help this.

The current version of Syria is missing two important airfields within the detailed area of the map. My guess is that the map will be refined and expanded with time (like PG), and more airports will be added.

The problem with expanding the map south is it will only give you more gameplay options if you go further down all the way to the Suez canal. This will require much more work and I'm not even sure it will pass the current DCS limitations. This map is called DCS: Syria, not DCS Israel. In an Ideal world we could have Israel in the center with all serrounding countries, which will allow us to create more idf/iaf scenarios. It's not the case. In all honesty, expending EAST is the way to go. More of the Syria / Iraq border to represent modern day ops vs ISIS.

It should be visible 10nm out according to documentation.

And that's the point.. If the pod LOS doesn't move to the offset location, what's the real purpose of offset as it is modeled in DCS at the moment? Shouldn't it be like the ATFLIR? In DCS it does everything else except moving the LOS, which seems odd.

The E seeker will be slewed to the offset (it follows the designated target while uncaged), and will try to spot the laser there. The F will be slewed to the offset and try to track a target. If it's correct, offset has no purpose. The point is to track something, while you offset the pod LOS to a different location. This whole thread is about whether or not the pod LOS should center on the offset target, like the ATFLIR: Currently, it does everything except shifting the pod LOS.

Using offset will defenitely update the designated target location (HUD). It will not lase that spot, so a laser guided bomb will most likely hit the center of the pod LOS anyways. Now that we know that the 65F will track the new offset location (this also works for the E), and that the designated target is updated on the HUD, it makes much more sense that the pod LOS should also move to the offset location. Otherwise, you will need someone else to lase for you, or you will be limited to use this with JTAC only.

I think the designated target will be updated if you use offset. It's jus the pod LOS that won't move.

That's my point. If what you are saying is pretty much using a mark point, why does offset exist in the way that it is right now? It's redundant for no reason, which might suggest the way offset was modeled is not 100% accurate.

The way to launch it is to hold pickle after the MAV is ungaced and the seeker is looking at the target. The TGP will start auto lasing and MAV LKD will momentarily appear on the HUD, as the missile leaves the rail. TTMR is still a thing even if the TGP isn't lasing.

I think he means the possibility to change the weather settings in the mission to be the same as the real location at the start of the mission

Yeah - right. I was able to take control while replying this track and hit every target I wanted.

Because the F model will try to lock every new target designated by the TGP. You don't have to undesignate anything. Also keep in mind we don't have markpoints and some hotas shortcuts that will help in this case.

I don't know, I don't really see an issue here: https://www.thedrive.com/content-b/message-editor%2F1562203225359-f-16.jpg?quality=60

In a HOTAS centric piece of softwawre, no GUI will ever be good enough in my opinion. The ultimate solution is a built in voice recognition capability, tied to a slightly improved F menu. Just like voice attack.

Thank you for including my livery pack in the base game! There's one small issue with the way they were added: not all textures are of the same livery version. This is 100% my fault for updating them regularly, which made it hard to keep up. This can be easily solved by updating to v1.31 and replacing/overwriting all of the textures, including the tail art (they were all changed in one way or another). Download links: https://www.digitalcombatsimulator.com/en/files/3308784/ https://www.digitalcombatsimulator.com/en/files/3308785/ https://www.digitalcombatsimulator.com/en/files/3308782/ https://www.digitalcombatsimulator.com/en/files/3308780/

The Turkish one being selectable for the USA is the minor glitch here :)