Rongor

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?

I summarized this issue 7 weeks ago, together with other stuff here

Hasn't been fixed with today's DCS Open Beta 2.8.7.42583. So still no way to communicate for A/G coordination which on most MP servers is on VHF FM... Pretty disappointing.

Am I really the only one with a sticky emergency wing sweep handle? Do all of you never pull it back into oversweep after landing? Again, its not me failing to wait for the auth light.

Has been like this since the F1 went early access. I'm also wondering when this will be fixed. Has been a while now and carried over into the F1EE

roger, copied the question into the M2K section. Thanks anyway!

My cartridges are still in \Saved Games\DCS.openbeta\Datacartridges yet when I open the DTC receptacle they don't show up in the cockpit anymore so I can't select one to insert. Any ideas what could suddenly be wrong?

what might be wrong if after opening the cartridge receptacle, no cartridges appear anymore to select one for insert?

Had exactly this a few days ago on a MP server. Also as a variant, I lost the cursor on the HAD while it being SOI, it was just gone. I could get the cursor back with DMD Down end then ended up with not being able to designate anything else just as you describe

I can follow what you have in mind. Yet why do these contacts then reappear after a few seconds. Because their now closer distance increased radar returns again beyond the detectable threshold? In the first occasion I lose contact at 24 NM (145.8k feet) distance while being around 6k feet above, equals around 2.4° Reacquired at 19 NM (115k feet) distance while 8k above him, means 4° In the second occasion I lose him at 17 NM distance (103k feet), while being roughly 7k feet above, this equals around 3.8°. Reacquired at 13.5 NM distance (82k feet) while 5k feet above him, equals 3.5° Both examples don't offer any consistency. First example has the target reappear at even bigger downward angle and second example isn't that much difference in both angles. While in the first occasion, I admittedly also have the nose up, target shows at the F20 mark down in the HUD, yet in the 2nd occasion, we basically have level LOS, seeing the designation box in front of us in the HUD. Especially in this 2nd case, how could the radar possibly have problems to receive the returns? Even when aircraft is nose up and the antenna is looking "down" compared to the aircraft datum, why would the antenna care? It's not like the radio waves bend towards Earth's center of gravity. I am totally confused what to make out of all this. I am only in the beginning stages of learning how to A/A combat and one of the first things I learned was that being at higher altitude will provide decent advantage regarding missile range. When a radar can't detect stuff 4 ° below the aircraft datum, this kind of defeats the whole idea of going in high at BVR.

I created a test scenario and you can watch here how it played out: (fast forward to 0:40, when the head-on MiG appears in my RWS 40 range) - 0:43 I bug the the contact, he is at 16k in 34 NM, antenna scans between floor and 35k - 0:53 antenna jumping sets in, while my TDC is close to the bugged contact, the second antenna elevation band seems to cover floor up to his altitude, 16 k. He is climbing, range 30 NM - 0:57 I move the TDC a bit, antenna jumping continues, alternating between floor to 18 and 05 to 35. - 1:05 there is a second target appearing briefly behind him, yet I set up the mission with only one enemy, so I ignore it - 1:08 I put the bug into STT, to get rid of the antenna jumping, he is at 16k, 25 NM - 1:12 the whole track just vanishes. TDC shows vertical scan range between floor and 24, so he should 100% be in. - 1:22 after 10 long seconds of zero contact, he appears again, at 17k, while TDC shows antenna elevation between 25k and 02k. Bugging causes the TDC switch to antenna elevation 36k and 14k. So I bug him again at 19 NM, while my antenna has its top elevation at 24 - 1:27 different to what I am usually doing I put him into STT again. - 1:32 at 17 NM range, whole track vanishes again, last altitude was 18k, TDC antenna elevation shows 25k to 02k - 1:35 he launches at me, while I don't have him on screen. My radar is blind, his obviously isn't. - 1:39 after being blind for 7 seconds he appears again at 21k, my TDC shows a 23-06 antenna elevation band for his location - 1:41 I have him bugged again at 13.4 NM Radar could now keep him tracked. Mission ended with me being splashed yet my focus was on demonstrating the radar work, not on winning the engagement

When those AI Fulcrums come on the server I frequently visit, I often meet them for a head on encounter. While closing in I run full AB, gaining speed and altitude advantage, to hopefully launch my Fox3 earlier. While being inbound to the enemy there are always several stages of losing radar contact. It's kind of unavoidable. I just have no idea why this is the case. I'm running CRM-RWS in a 60° arc, carefully keeoing my antenna elevation matching his altitude. He is dead center, sometimes I even STT him although hit necessary. While we both fly straight, at some point my radar just drops the contact for no apparent reason. It can then take several seconds to make the target appear back again on screen, although my antenna is still covering his 3D position all the time. Sometimes this is accompanied by antenna elevation jumping between two bands (see other reports on this). This may also trigger loss of contact yet it happens even when its not jumping or when both bands include the 3d location of the MiG. So bottom line, it's a mystery. I get the target, I bug it into SAM. Several NM closer, contact just vanishes. Following the estimated trajectory with my TDC doesn't help anything. Long moments later the target appears back on screen. Sometimes you can bug it again, sometimes the bugging will just fail, while the target still remains visible and is closing in on you. It's driving me crazy. This repeats several times in a row, until you are finally in engagement range and happen to relock again in time to Fox3 him or he remains just gone from the screen although the radar antenna is exactly where he is in azimuth an elevation, yet of course he can track you and does launch. What can we do to fix this?