"This mission requires activation"

I get the above error while trying to play the new Red Flag campaign with Reshade/SweetFX. Is this a bug, or is it intended for the DRM to now block shader injections?

It's like that in the Su-27 campaign too. Really sucks!

I assume it works for you without the shader injection ? I only ask because you have to enter your serial number on the 1st mission anyway.

I assume it works for you without the shader injection ? I only ask because you have to enter your serial number on the 1st mission anyway.

Yeah, the automatic authentication did its thing and the campaign works fine on its own. The error only shows up when I try to launch the campaign with reshade enabled.

Hi, when it will be solved? : (

Any news? Where is the author of this campaign and who is responsible for this? : <

I don't think it's up to the campaign author to support any mod that is out there... I would say that is up to who created reshade/sweetfx to be compliant with the mission protection system.

Obviously that could be also impossible.. but in that case, you can't blame the campaign author. You could kindly ask him if he could try to solve the issue, imho :)

but in that case, you can't blame the campaign author. You could kindly ask him if he could try to solve the issue, imho :)

Yes for sure, we can ask and ask and ask, You have right and I agree. I saw some posts about this and never saw the answer. Does not look strange?

I isnt a problem of Redshade - this is tool for all games, not only for DCS. I have other campaignes, default campaignes and no any problems like this. Its a strange perhaps DRM tool and definitely its a problem or bug in this payware campaignes.

Pity.....

IMHO is tecnically speaking a problem of sweetfx. It doesn't matter how many games it could support: it's an unofficial mod. I understand that the issue should be solved by the DRM author due to the fact that this is the only condition that trigger the bug.

But you can't blame the DRM author as he MUST solve the issue. He could, maybe, try to solve it if he think that this could lower the product capabilities. This is what I'm trying to say here.

If you talk about the author - I think he wants to have more sale, so in his interest is to solve this also I think and opinions always are good (yes, this for + and for -).

I havent any payware campaine but saw posts like this. I might have bought but Im user of SweetFX too.....

Here is te reason, not the reason is "the blame" for "the blame".

If you talk about the author - I think he wants to have more sale, so in his interest is to solve this

I agree about this.

http://forums.eagle.ru/showthread.php?t=173064

http://forums.eagle.ru/showthread.php?t=172542

The problem still persists and I'm left to wonder. It isn't an issue of incompatibility between DCS and SweetFX, it's an issue with the campaign DRM preventing the user from playing DLC campaigns while SweetFX is enabled.

All the official and third party aircraft modules (and Nevada) work perfectly so the campaign DLCs appear to use a different method of DRM. I can't say I understand much technically about how SweetFX works, but if the DRM blocks injections alltogether then SweetFX will simply never work?

I fully understand that ED will not spend time supporting specific third party mods, but enabling healthy modding in general would be beneficial for both ED and consumers. Then again, SweetFX is probably the only thing to suffer this problem so we go circles.