Rongor

Since the terrain will likely be included anyway because of the extension of Afghanistan covered by a rectangular map module, will we see places of importance just behind or even a bit further the border? For example: - Termez, Uzbekistan, literally at the border, has an airfield, could be an important base for the DCS C-130J. - Abbottabad, Pakistan, could be the location of an intense counterinsurgency operation, commencing from Bagram and Jalalabad, Afghanistan. - Peshawar, Pakistan, east end of the famous Khyber pass coming from Afghanistan Of course there are so many more possibilities (Kashmir, a tiny bit of China just behind the Afghan Wakhan mountains to include a Chinese airstrip, a connection to the Persian Gulf map, cities of Islamabad and Dushanbe...) but I understand that there has to be some limit (well I pretend to understand, in fact I am unable to) Thanks for considering

Access from the Indian Ocean supported by air2air-refueling would mean so much more possibilities. The Baluchistan region between south Afghanistan and the Ocean wouldn't even require any detailed scenery, terrain only would be just fine. Please don't miss this chance to include the opportunity for long range naval air ops.

I get what you guys are saying. Still I can't mark your comments as solution until its confirmed that the manual needs updating then

Here I close in to a group of red Il-76, commencing at 40 NM distance, down to 1 NM and below. At no point does the L+S interrogation nor the auto interrogation I switched to later manage to IFF any of these contacts. I guess the reason might be that it doesn't IFF to hostile and only clue it will give is that its not friendly... I end up directly behind my L+S tracked Il-76 and while the IFF is still asleep, the NCTR also doesn't ever ID this aircraft in front of me. of course there is proof: no_IFF-no_NCTR.trk

The manual claims I need to press cage/uncage, yet this toggles the Sparrow's loft mode on and off and doesn't affect STT. Only way to enter STT is SCS right. Yet I do have to move the TDC on the desired contact, so the whole process of designating a primary target beforehand seems a bit irrelevant when I can't conveniently put this into STT. I'd also be interested to know how to drop STT quickly as the nws/undesignate doesn't appear to reliably do this.

Just RTBed with a single engine. After shutting down for repair, the ground crew refuses to accept the task because I should shut down my engines. Both are shut down, power levers are both to off. Still ground crew claims I have to shut down before they repair.... The mission has run for about 55 minutes. I guess you don't want the trackfile (53 MB) then?

Units can't pass underneath this bridge in Beirut and instead get stuck.

In the recent days I noticed several occasions in which the CMWS detected missile launches, which then turned out to be from SA-15. Only the RLWR didn't detect the SA-15 at all before. So no "SA-15 searching", "SA-15 tracking", "SA-15, launch" alerts, only "Missile". I am currently regularly playing on the Rotorheads server for helo gameplay. There is usually high numbers of all kind of SAM systems littered across the map there, so you get in contact with these quickly. It could of course be a problem with the SA-15 instead, launching on targets without any prior radar use. I am not sure Tor systems have a manual launch and guidance mode though and in all these occasions did the Tor launch from 4+ NM away. Other Apache players on the server noticed it too. Today I had it happen right after starting up and taking off, so we can now enjoy a rather short track to review. After around 5 minutes of cold start, you will see me rolling out of a hangar at Beirut, do a running takeoff out of this motion, then do a right turn. The missile alert happens in that right turn. Turning my head to my 5 oclock, you can see the missile coming from the far mountains in the east. After that one is defeated by terrain masking, another one gets launched. Only then the RLWR did notice there is SA-15 activity. I hope this one can be cleared up. RLWR_SA-15.trk

Doesn't affect AI or George as well. In fact it would surprise me to see the FCR being affected. Would mark a new era of realistic line of sight in DCS.

Bound my turret controls to a gamepad. Works well. Only when switching into isometric view, the mouse is taking over. I can't find a way to prevent this. Any ideas/experience?

did report this 9 months ago...

I guess nobody is performing this test or already deaf?

This issue seem to have been cured after patching to 2.9.1.48335 yesterday. Will get back to you in case it comes up again.

We can bind controls to crank left and right engines, yet there is now way to flip the switch back to center. This would come in very handy, since the full start procedure requires to crank without engine start in at least 2 situations of the checklist.

This was made in daylight sitting at Nellis. Why is this so bad to see?

I am reliably crashing to desktop whenever I startup my Hornet on my favorite MP server. By testing I could narrow down that this is triggered by some avionics being powered (generators coming online when engine start). With normal startup procedure the game will crash when the first engine (L or R, both same symptoms) has spooled up. If I switch off the generators before, engines can maintain idle RPM and react to throttle inputs normally. The moment I switch on the generator of the running engine, CTD... Happens also when not starting engines at all and connecting to ground power. After all 4 external power switches are flipped on and MPDs are switched on, crash to desktop. Fellow players experience this as well. latest openBeta and running MT... attached tracks/logs: 1. both engines start with generators off, then generators on SYRIA_TPE_v1_RUN1-20231112-114419.trk dcs.log-20231112-104825.zip 2. right engine start with generators on SYRIA_TPE_v1_RUN1-20231112-113904.trk dcs.log-20231112-104204.zip 3. no engine start, external power SYRIA_TPE_v1_RUN1-20231112-113240.trk dcs.log-20231112-103525.zip dcs.log-20231112-104825.zip dcs.log-20231112-104204.zip dcs.log-20231112-103525.zip SYRIA_TPE_v1_RUN1-20231112-114419.trk SYRIA_TPE_v1_RUN1-20231112-113904.trk SYRIA_TPE_v1_RUN1-20231112-113240.trk

I can't hear anyone and I don't think its a viable solution to ask dozens of my fellow players to reenter all their frequencies. Especially since they claim they hear me.

So far I didn't hear anybody on VOIP. This feature just doesn't work.

answer to 3rd: UFC/DED List>DLNK>page2 The info on the right end of the DED claims #1 is our own STN. No idea what the T in the * means.

Still not fixed in 2.9

If you're out of range, it naturally won't give you anything

Which TACAN mode did you use?

I noticed this myself very recently. I find it hard, often impossible, to trim the aircraft for level flight with the trim hat on the stick. The tiniest actuation seems to have a way too powerful impact. Using a Thrustmaster A-10/F-16 stick for it, I wouldn't know how to adjust senistivity as the trim hat is a set of buttons not axis.

I am doing it exactly as told in the tutorial training mission, yet in 5 of 6 cases, the propeller will only do some unmotivated turns and then stop again. Is there a reliable undocumented procedure you guys can tell me?