splash

I'd like to see a Su-25 or Su-25T with PFM.

Thanks for your offer! I'd like to play L-39 a lot.

Excellent news, thanks for the update. That will be a very nice reading for Christmas.

Same here. Yesterday I was flying over St. George and there we have an airport!

F86f, Many thanks!

Excellent job, this is what i was looking for. I tried it several times with no luck.

I'd like to see classic fighters as Su-24, MiG-23/27, MiG-25, F-4, F-16, etc.

Ok, I'll go on playing under 1.5.1.

Will I have problems with activation in 2.0? I'm only playing MiG-21 under 1.5.1.

I don't have any entry under HKEY_CURRENT_USER. Neither before this update nor now. It is currently under HKEY_LOCAL_MACHINE and working ok in 1.5.1 (I didn't try in 1.2.16 and won't try it).

Do you know if it is a good idea to install this driver in a HD 5870?

I deleted MiG-21 from 1.2.16 since the last patch and I have no intention at all to install it again. In 1.5.1 it is running ok by following the steps. I understand the need of some people to run it in 1.2.16. In my Ka-50 squadon, 1.2.16 is the standard and I have to fly with it.

I followed all steps and it is working, but the registry entry has been created in: HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS\Keys\License0 and not in HKEY_CURRENT_USER/Eagle Dynamics as stated in the changelog.

My question is if we need to deactivate (running pcnsl.exe), as in the next step we delete all windows registry entries.

Great news! Thanks for the update.

Nevada includes campaigns currently?

Many thanks ciribob, awesome job!!!

Sure! Please, find it below: and the line in clickabledata.lua is this one: elements["PTR-LPE-TMB-COMAND"] = default_2_position_tumb(_("R-863, Modulation Switch, FM/AM"), devices.R_863, device_commands.Button_1, 369)

Hi, I'm using Windows 7 Ultimate x64 version. Please, let me ask you a question, have you got Mi-8? You have an AM/FM switch to select with modulation is the R-863 radio working on. In simpleradioinit.lua that radio is always in AM mode: _data.radios[1].modulation = 0 I was looking in clickabledata.lua for the switch code and try to read the position with Witchcraft, in order to introduce in the modulation field a "0" for AM or "1" for FM, but I didn't work. Despite it is a 2-position switch is not returning 0 or 1. Maybe you can have a look. Thanks again.

Hi all, in my case I uninstalled MiG-21 from 1.2.16 (I need that version to fly official missions with other modules with my squadron) and the problem is gone. I can fly all my modules (all except for MiG-21 in 1.2.16 and all modules in 1.5.1) without receiving any Starforce error or reactivation. Before uninstalling, I was asking to activate MiG-21 whether I played MiG-21 or not. I have hundreds of entries in the MiG-21 branch in the registry but it doesn't matter by now. For me it is a solution while waiting for the ultimate solution.

Many thanks, awesome job!!!

Many thanks. Mi-8 is my favourite module and it is getting more and more interesting.

Hi, I've just tested your new version and found two very little bugs: - You cannot disable Radio FX (menu is grayed all the time). - It always displays "Plugin: Enabled" in green whether it is enabled or not (Enabling DCS-SimpleRadio / Disabling DCS-SimpleRadio messages are correct). In my first trials with Ka-50 I didn't detect any fail and it is working as expected. Great job!

It'd be a very nice addition to our arsenal, wouldn't it?

I uninstalled the module from 1.2.16 and, despite the mess I have in the registry, it is working flawlessly in 1.5.1 and it didn't request any more activation. So by the moment I have no problems to play MiG-21.