Redglyph

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)

In mission 3? The option exists, at some point you are normally told "New radio item available (F10) Inform when you are ready to move on after tanking". Tanking is not mandatory - I would never have passed this point otherwise :D

Thanks! You must be right about Nellis, well spotted! Just looking at the coordinates confirms it, those are from the original file and its comments, and I haven't checked all of them. I'll simply make an update of the kneeboard I suppose. Having Tonopah Test Range on RSBN 27 is really bugging me sometimes, because TTR and GRL should be the two most frequently used stations for a MiG (historically at least), yet the user has to click many, many times to switch from one to the other :/ Perhaps when I figure out how to simply pre-configure this knob in missions it will be less stressing for my mouse ;) But I was tempted to simply swap it with another, less frequently used station, or sort them all out from North to South. Wouldn't be nice to change everything, though, and since this was also in the original settings it's probably best to keep it. Another solution would be a mouse-friendly knob. Hmm. Anyway, sorry for my ramblings :D

In case it helps with the coordinates, here's a link to what I had for the MiG-21 :) https://www.digitalcombatsimulator.com/en/files/2333411/ https://forums.eagle.ru/showthread.php?p=3023098

bump

I saw they warned about other issues too. You have the option to revert to version 2.0.5.1648, read this post to see how: https://forums.eagle.ru/showthread.php?t=114030 (look for "Updating or Reverting DCS World to the latest build of a Specific Version")

When all MiG-21s are downed by enemies and nothing is left to repair, they'll have to notice :D

Ah well, they'll surely see it at some point :)

Just one or two tiny changes I'd make in the training 03 on navigation. When setting the time to destination, it's worth mentioning that the pilot must click twice on PREP to get the correct waypoint there, otherwise it doesn't work and the extra brackets don't appear on the HUD. It's not obvious to detect why. :) It's probably best to tell that the RD isn't implemented yet, after all the training is for "beginners " who are probably not aware of the missing features. ;)

I couldn't find any reliable pattern about it :/ You'd probably best increase the severity, this one is honestly more than minor, and seeing I have a few bugs reported back in early November with minor priority that haven't even been looked at, this one could remain for quite a while... ;)

Nice to hear :) That'd be nice, in the road map there is a "F-5E Air Combat Maneuvering Campaign" which seems to be the F-5 counterpart of Sabre's A-10C training campaign.

You must be onto something. :) From what I see, for example the first training missions of the F-5E and the M-2000C have the same settings, tooltips are not enforced. My general settings allow me to see tooltips and I have the "Use these settings in all missions" checked. If I run the F-5E training, I can't see tooltips, and if I run the M-2000C training I can. Now if I load the F-5E training mission in the Mission Editor and save it, later I can see the tooltips when I run it from the same training menu, so some settings must be changed. When I compare the "options" file, in the .miz newly saved mission and the original, this particular line changes (along with others): ["tips"] = false, becomes ["tips"] = true, in the options["difficulty"] part. So apparently the saved options are not entirely correct, and they don't correspond to what is shown in the Mission Editor either.

I confirm the bug in DCS 1.5.6.1938.247. I first though that pressing the test button, but this isn't a work-around. It seems to shut it off, but the volume knob simply doesn't do anything.