SirBunker

Edit: Removed.

At least after the first mission. There was no debriefing so I assumed things went wrong and restarted the campaign a couple of times, same result. Doesn't happen with the other DCE campaigns but could still be something on my end.

Yes, I'm familiar with the method since Mbot's original MiG-21 campaign.

I get this error if I finish a mission. No txt debriefing is displayed either.

Nice, I've been waiting for someone to convert DCE for Viggen. I'll give it a try tonight.

Hi, I hope someone could nudge me in the right direction. I'm experimenting with creating a control reference for the AJS37. I've started with this as a base for understanding how things work. DCS-BIOS can successfully read the state of those four switches, but sending commands back (i.e. manipulating the switches through DCS-BIOS) doesn't work. I collected the values from clickabledata.lua, are the 300x values actually the wrong ones? I also took a look at the other modules in DCS-BIOS and noticed that some simple 2-position switches have a higher (or way higher) maximum value than 1. I assumed that on/off switches would simply have values of 0 or 1 but apparently that's not the case?

Mig-21bis did not serve in Vietnam, I don't see LNS having a particular reason to create a Vietnam map considering their announced projects either. They do have two released planes for a what-if cold war scenario on the Baltic Sea though.

No, I "learned" cold start in two minutes. That is, I learned to press a sequence of buttons and switches. I played through all the tutorials last night in one sitting. We'll see about competence after people have spent several dozens of hours in real combat scenarios.

Just gonna call bullshit that anyone is competent in ANYTHING after the module's been out for less than a day.

Graphics are relatively easy to make compared to coding the aircraft systems/avionics, which to my knowledge are completely different between the AJ and JA 37.

I suggest you check the mod packages again to see what files are there. Afaik a regular cockpit mod should do nothing else but input its dds files and description.lua to \DCS World\Mods\aircraft\[module name]\Liveries\[module/cockpit name]\[cockpit mod name]\ For example, I've seen some questionably made cockpit mods uploaded to DCS user files that try to replace the default cockpit textures, I wouldn't be surprised if that triggers the integrity check to fail. Personally I use Ricardo/Devrim cockpit mods on several aircraft and they've worked flawless so far.

This sounds fishy, I use custom cockpits on several aircraft and none of the mods have trouble with the integrity check.

1.2.16 is still available on Steam in the game's beta tab. Can't say anything about module activations though.

The way I've understood it is that the DCS SDK is required to create guided weapons, and that's only available to the licensed 3rd party devs.

Razbam are working on the Harrier. Tornado rumors have been around but no solid info. An A-4E is being made as a community mod:

That's Christmas Eve in Russia, so I'd say it's even less likely to be a DCS patch day than December 25th. :smilewink:

I disagree with your disagreement.

The F-15C also sports a flight control system with an "on-rails" feel to it.

A Baltic Sea map featuring strategic islands like Gotland and Åland would also be nice.

They said last year (or something) that there'd be a relatively short pre-release PR cycle. Even if Viggen gets released on November 28th, they still have several weeks to release proper trailers, do interviews, previews etc. The fact that LNS released a teaser now would indicate a release before Christmas, though maybe we'll have to wait two more weeks™.

80s style more like it, "bröllopsfilm" means wedding film so the joke is that someone accidentally recorded "something" over the old tape.

Exactly the sort of take on pre-release trailers I was looking for. Is the music an original piece or licensed? I want it to play nonstop :)

Sorry for going radio silent, I haven't had the time to work on these again until now. Hopefully I'll finish them next week, the tail still has some errors and the nose is just god awful. I also have no clue about US livery markings so they might not make any sense. Meanwhile has anyone noticed a texture bug with the ZA? If I zoom out, the textures partly display the Russian livery, as if there was some sort of issue with LOD levels.

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.

In other words, the texture template for C also works in ZA. You'll only be missing templates for the underbelly gunpod, fuel tanks etc which are in seperate files.