Redglyph

Well, that's the 23rd page of this thread ;)

1) Using the new beta You should be able to deactivate it from the 2.0 or the release, since it's still the old version. If you do that, and then activate from the beta, you won't be able to fly the MiG in the 2.0 nor in the release anymore, until they're patched too (pretty soon from what they said). It's probably the easiest in your case. If that doesn't work, it's not very hard to delete those keys in the registry, then activate from the beta. 2) Not using the new beta You also have the option of reverting the beta to the penultimate version, fly the MiG in both beta and alpha until the alpha patch comes out. Or simply leave it as it is now, and ignore the beta until all versions are patched (don't forget to deactivate before updating though!). If you don't want to see the activate pop-up, in either version, disable the MiG from the module manager, it won't be uninstalled so you don't lose anything.

That's good news, thanks! Is there a way to see how many deactivations / activations are still available, without going through the process? And what are the rules now? I'm wondering if I can switch between the beta and the alpha, but since I ran out of deactivations I'm being cautious. (I suppose that hasn't changed, and it's "-1 deactivation per deactivation" no matter what, "no change per activation" when a deactivation has been done before, "-1 activation per activation" otherwise, for ex. if the registry entry has been deleted, or a new installation on a new computer?)

Apparently the number of deactivations is limited too, so DO NOT SWITCH between versions, because even if your number of activations is preserved, you'll quickly run out of deactivations. That's weird.

Ah well, I'll just edit the date then. Thanks!

I don't know who you contacted back then, but things have changed since Leatherneck / Magnitude and Heatblur have reorganized. Have you tried to contact the support of Leatherneck directly (see first post)? They're very responsive and helpful. In any case, as said before, you have to choose between the latest beta and the other branches for the MiG. Just deactivate it in the other branches until they are updated with the new licencing scheme. That way, you won't be bothered with the activation pop-up every time (but you won't be able to fly the MiG). Or, if you look back some pages, several people explained how to go back and forth between beta and the other branches. Not ideal right now, but for the best if that means no more problems in the future.

OK, thanks, better safe than sorry :)

Is that your key number? You should probably edit this image.

A glider? :smilewink:

Was it fixed finally? It seems I just had this problem again, or I did something wrong with the INS.

You can activate either in the latest beta (1.5.6 update 1), or in the other release/alpha branches, but not all the branches at the same time. There is only one MiG-21 key set on your computer, but 1.5.6 is now using a new version of the DRM. And... I was late ;)

A little Cessna to get back home from the airfield base would be great :D

I still don't understand why ED didn't warn people in the newsletter and/or the update thread :rolleyes: If you have a 2.0.5, you should still be able to deactivate from there, which the Mods\aircraft\MIG-21bis\bin\pcnsl.exe from the 2.0.5 installation. Otherwise, check the pdf document in the first post of this thread, it gives a procedure to remove the keys directly from the registry. Lastly, you can opt to revert to an older 1.5, check how here.

The keys are unique for all versions, so when you update (either yesterday's 1.5.6.3690 - update 1, or the future 2.0.5), and run the new version, you'll be asked to activate your product with the new licencing scheme, and from that point on it will only be valid for any "future" version based on this Starforce patch. So if you run an "older" version, it won't work anymore. Let's say you update to 1.5.6.3690, activate from there: if you want to get back to 2.0.5.3521, you have to - run pcnsl.exe from the active 1.5.6 module, - deactivate - run 2.0.5 And if you want to run 1.5.6.3690 again, you have to do it all over again with the active 2.0.5's pcnsl.exe, and so on. So it's possible to switch back and forth, it's just a bit awkward. It's probably best to choose 1) whether you really want to update to 1.5.6.3690, and if so, 2) in which version you want to fly the MiG. Finally, if I'm not wrong, if you activate it for 1.5.6 update 1 and run 2.0.5, you'll be asked to activate it. Just don't and click EXIT to run 2.0.5 without the MiG. For some reason I had the licence box opening twice, and had to click on EXIT twice before 2.0.5 was launched, so I guess this issue may happen.

Actually, it doesn't seem possible to deactivate the new version from 2.0.5 anymore, so no switching. Or perhaps by messing with the registry. EDIT: nevermind, the new pcnsl.exe has to be used to deactivate the new version, and the old to deactivate the old, it's different, makes sense.

Works for me too in 1.5.6 update 1, that's great! :)

Good to know, thanks. But does it mean that, if someone has done the procedure to run 1.5.6 update 1, it has to be done again to switch back to 2.0.5, or in fact every time the user switches between 1.5.6 update 1 and 2.0.5?

Apparently works for 1.5.6 update 1 (1.5.6.3690.269). Sadly I don't think ED will ever take this fix, so we'll have to go on patching the A-10C after each update.

Hum, this would have been a relevant info in today's changelog thread, too bad ED didn't mention that.

"Maximum unstick ground speed 360 km/h", from the DCS manual (pg. 32). The procedure is as follows, according to a manual for exported versions of the MiG-21bis: - speed 150-200 km/h: pull stick 3/4 back, until the nosewheel begins to lift off - speed 250-270 km/h: nosewheel lift-off, maintain 11-13° AoA - speed 340-360 km/h: take-off (*) The speeds depend on the load, obviously, and IAS. (*) memorize the attitude, the view of the horizon and the distance to the ground just before the wing wheels unstick, because you want to have the exact same view when you land :) Yes... it's frustrating to see Magnitude 3 LLC has fixed so many bugs and today's update still doesn't include these fixes (and since the performance issue introduced recently is still there in 2.0.5, it's probably safer to wait a little more...).

Updated to v4.

Great, thanks! :) This should definitely be stickied!

That doesn't seem to work, or perhaps it's restricted to a few modules. I tried with the M-2000C and the Mig-21bis, and it does add info to the mission file, but unfortunately nothing to set up the avionics or other cockpit settings. It would be great to have such a feature instead of setting them by script, the default configuration rarely fits the requirements, that's why I usually prefer cold starts ;)

01200.529 INFO EDCORE: # -------------- 20170318-060459 -------------- 01200.530 INFO EDCORE: C:\Eagle Dynamics\DCS World OpenBeta\bin\Transport.dll 01200.530 INFO EDCORE: # C0000005 ACCESS_VIOLATION at E54EBE93 00:00000000 01201.787 INFO EDCORE: Minidump created. That looks like a known issue with DCS, check this out. You could open a thread in those subforums, the additional info could help them solve the issue. Make sure to give enough details on your system and DCS configuration (see Bignewy's questions).

Don't fret, it seems things are moving since this weekend's annoucement. :) As a matter of fact, see the bug tracker: https://leatherneck-sim.mantishub.io/view.php?id=591 (and some other duplicates)