SchumiF399

Same for me F16 throttle broken, windows sees the axis fine.

I had this happen numerous times. Mainly in air to air engagements. Here is a small tacview between myself in an F16 and an F15 (Zipper 1-1). Missile is guided to pitbull and then decides it no longer wants to track and oscillates. Tacview-20230708-101355aim120-DCS.zip.acmi

add me to the list

AMRAAM is a joke nowadays half the shots I fire ended up in the AMRAAM having an effing seizure.

OK, I managed to get a track file from my very first engagement on the GS server with a jamming F/A-18. Both AMRAAMS are what I consider high PK but they miss. The AIM 9X was shot as a last ditch effort, it came closer than the 120s. AMRAAMS are useless against jamming targets at any range! Server_1_Operation_Urban_Thunder_V7.2.9-20230119-170719.trk

AIM 120s are definitely broken against jamming targets. Small tacview attached between myself (BLOWN HEAD GASKET) and another random player (ARTAX) . First launch at 8.55 NM, mach 1.81 and missile goes stupid as do the next 2 amraams. Had to resort to Aim 9x to get the kill. ED please have a look at this. Tacview-20230109-175220-DCS.zip.acmi

Here is a tacview file of an engagement between myself and another random person on a different server(Blown Head Gasket F16[me] and a Mig-29 [Boofly]). I am extremely new to tacview so please bear with me. This guy was jamming and all three missiles go dumb. The last missile was below a mile so I didn't really expect that one to hit. Tacview-20221231-102846-DCS.zip.acmi

Very interesting, I hope someone from ED chimes in and provides some insight as to what is going on at the moment.

I see, but haven't I burned through his jammer at that point ?~ 16miles? I've noticed that when a hostile is jamming and I acquire a lock I don't get range info until I burn through it. The missiles were tracking fine at first. Is it as intended or is it borked? Thank you for your help!

Hello guys, I've been having really weird behavior with my amraams going dumb as soon as they are going to hit a target. I don't expect a 100% kill ratio every time I fire one but lately after the latest open beta mini patch I am lucky if 2 out of the 6 amraams I am carrying hit their mark. Below are 2 short videos of what keeps happening to me. The 2nd one is a tacview replay. Sorry in advance for recording on my phone. Triple monitors do not play well with recording software.

I I already have the monitors setup in Nvidia surround, under same menu there is an option for bezel correction. It only takes positive values. What I mean by my racing games is that there is individual parameters I can change within the game to achieve a negative offset.

Just installed the Asus Bezel free kit on my 32-inch displays. I got everything physically lined up to a T but the image on the side monitors is still a tad bit off. I am able to add negative bezel correction in most of my racing games. Can the same be done in DCS? A lua file perhaps? Thanks.

Ok, here is a multiplayer track file (https://drive.google.com/file/d/1XAPqSU5id5tDnBTjfwux0I_YMT5FdV-8/view?usp=sharing). I am unsure on how to shorten it. On my very first attempt at engaging a target I keep trying to lock the first target, I keep messing with radar elevation and azimuth. I end up locking the friendly. Not quite the high altitude scenario I described in my earlier post but I think I am well within range to obtain a lock. I think even the radar elevation bugged out as I had to tms right and go into TWS to get it back to normal. Anything after me crashing the jet into the mountain isn't worth seeing. (Shows how poorly I fly)

Is this really working as intended? I'm having trouble locking high altitude contacts at 20-30miles. My FCR shows a SOLID RED DL contact overlaying a smaller WHITE square. TMS up and nothing happens!

It’s definitely more playable now, this makes me happy. I don’t know what I was thinking when I said I wanted to take a break.