St3v3f

I am very happy to hear that. A stable version of this mission is a dream come true :) How about you put in a CAS mission or two. Like, you get a tasking with coordinates to a friendly convoy. Once you reach it's position it starts moving and will give you targets as JTAC, like roadblocks or a group of enemy tanks approaching it. Somewhat like a small version of Gudauta Rush. By the way, I have been running the 1.1.2.1 version for over 6 hours two days ago. Everything was working well until I was kicked out (my own fault though). So it seems to me that the mission is working without further issues on 1.2.1

Should have been the real target then...

Are you sure you took out the convoy and not just a random patrol? Patrols are usually 3 vehicles, convoys that belong to a tasking about 6 vehicles long. Both travel on the same roads sometimes. Love this mission too and host it quite often these days (with a few adjustments :)). Unfortunately, sooner or later the mission logic seems to die. It's gotten better after i disabled the slmod commands for requesting taskings and a sitrep, but it's still not entirely okay

Same issue here, but aside from that, it seems to work well :thumbup:

Setting the affinity for a process is not about forcing it to use multiple cores in the first place. It's about limiting it to certain ones. Why he tries to have the game run on certain cores only, I don't know. There are some possible reasons for that. Maybe he wants to have the game run exclusively on some cores and everything else on the others. Older Quadcores like the Q6600 were also more like two Dualcores rather than a real Quad. Cores 1 + 2 and 3 + 4 each share a cache that the other pair doesn't have access to. So running a two thread process on cores 1 and 2 would be faster than cores 2 and 3

I tried it with the program Forcecore, but it didn't work either. Seems like DCS overrides these settings...

Can you do that in Multiplayer for other pilots too?

Oh, totally forgot about the second part of your question ;) The MPS-410 pods are loaded onto your outermost stations. They are ECM pods, like the ALQ-131 on the A-10. If you load up the MPS-410s and press E, you will see a green light on your right side in the pit start to blink and become steady after a couple of seconds. That indicates that the pods are active and once the light is steady, they are at full power. Essentially, they try to protect you from radar SAMs. There is something similar for IR SAMs built in (no pods needed). Press LShift + E and a light on the left front of your plane will indicate it's active.

These diamonds are not "designated for you". These are radar emitters like radar guided SAM units or search and EW radars. If you equip an ELINT pod on the center station of your SU-25T and activate it (I), it will pick up those emissions and display them on your HUD as diamonds with a designation of the target type. That way, you can lock them up and fire anti-radiation missiles at these targets. This mission type is called SEAD :) All other types of targets will not show up in your hud (IR SAMs, Tanks, buildings, etc.)

Your engines have to be completely shut down on the Su-25T for repair / rearm / refuel Press rShift + End and wait until the RPM needles are down to zero. That can take quite some time. Once that happened and assuming the airfield is under your coalition's control, it should work

The behavior discussed is new, it came with 1.2.1 or one of the autoupdates Falcon explained everything. If there is no search radar, the launcher will first acquire the target via an optical targeting system (hence no warning prior to launch). Once that happens, the missile is launched and guided via the launchers own radar (which means it will show up on the RWR during this period)

I've had those since 1.2.1, even before installing TARS for World

Yeah and Falcon explained why

Thanks for clarifying that :)

A fix that requires a fix that requires a fix is not a good fix, that's the point. In my opinion, you learn to live with those little issues. Having each of them replaced with another one on a daily basis is no good either. So I would rather have release cycles of one or two weeks with good fixes than what it was like the last days (for me at least)

Yeah I guess they wouldn't be as dead accurate without the radar as they are in the game, would they?

Ah well then, I guess life got a lot harder ;)

Great, at least now I know why the SA-11 kept shooting in Hardcore Terrorists even though the search radar was killed... However, I don't think the current status is realistic either. It just launches the missile without appearing on the RWR before. That also means that the Su-25's ARMs are useless. Shouldn't it be tracking and locking the target before firing?

I'm starting to hate the autoupdater... First with 1.2.1 I've had problems with the mousepointer. When moving the mouse, the game would show the standard Windows cursor for fractions of a second, when holding still it was as usual. No biggie Then I autoupdated yesterday. The cursor was fine now when moving, but everytime I switched from a different view (F10 map, external view etc.) back to the cockpit, the cursor disappeared until I moved it over a switch or something that would make the cursor change. On the bright side however, the server's mission wouldn't override my snapview settings anymore (yay!!), which was annoying me in DCSW from day 1. And with today's autoupdate, that is already gone again... :chair: BTW, the (new) cursor issue is still there of course

It's working fine now with 1.2.1

It's working fine now with 1.2.1

Mission 4 of the Deployment campaign for the Ka-50 is broken. If I try to start it via the campaign menu, I can click "next" but nothing happens. If I try to open the mission file via the mission menu or in the mission editor, the game becomes hung up on the loading screen Running DCSW 1.2.0

I have recently bought the Black Shark and found flying with the return-to-center trim mode (having to return the stick to the center position before making new control inputs) better. It's working fine in singleplayer, but when I join a multiplayer game I have the other mode. I couldn't find anything about this issue, anyone else had that?

I installed that and the game crashed when the first JTAC I contacted was just about to give the remarks. Could be a coincidence though Update: Had some JTAC contacts today and they worked fine. But response time is very long now

Had that issue when I carried over my control settings from DCS A10. I could assign a key to the reload window but it would not work. Defining them from scratch helped