Jump to content

IMPORTANT MiG-21bis StarForce PATCH - MARCH 2017


Dolphin887
 Share

Recommended Posts

Dear all,

 

Most of you know we have issues with the StarForce protection for the MiG-21Bis module.

The primary complaint was that the protection was not flexible enough for the users' hardware and/or software changes.

 

We took this very seriously, and dedicated our time to work on the fix along with the people on the StarForce team.

 

Our Starforce patch will be distributed along Eagle Dynamics next DCS World openBeta patch, which should be released by the end of this week.

 

This is a major patching event for all of us, and it will require your cooperation for a proper and successful execution. In short, in order to save one activation for MiG-21Bis, you will have to deactivate the module BEFORE the DCS 1.5.6 patch is downloaded to your PC. We advise you to do this in next 24 hours.

 

We have created a guide with detailed instructions that will help you prepare for the incoming patch: please find the attached two identical documents written in English and Russian languages.

 

Please feel free to distribute them among your friends that are using the MiG-21Bis module.

 

Note that if you are using DCS World 2.0.5 openAlpha, you do not have to do this at this time. However, when Eagle Dynamics decide to distribute the patch for DCS World 2.0.5 openAlpha, we will distribute the same StarForce patch; thus a simmilar procedure will be required if you do not use any other version.

 

If you patch 1.5.6 openBeta first after doing the procedure, it is not required again for 2.0.5 openAlpha update.

 

If there is a 2.0.5 openAlpha update and you update that first ((doing the procedure) before updating 1.5.6 openBeta), then you do not have to do it for 1.5.6 openBeta.

 

The same as in 1.5.6 stable release. We will do our best to keep you informed in time.

 

We sincerely appologize for this inconvinience. Our ultimate goal is your satisfaction: there are things we have to do to get there, and there are some thing we have to do together.

 

We will provide help along the way and we hope this transition will be sucessful. We also hope you will like the fixes we prepared in the next patch.

 

If you need any help please write us at support@leatherneck-sim.com.

 

Your dedicated developers,

LNS

Important MiG-21 StarForce patch MARCH 2017 EN.pdf

Important MiG-21 StarForce patch MARCH 2017 RU.pdf


Edited by -Rudel-
  • Like 2

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • Replies 291
  • Created
  • Last Reply

Top Posters In This Topic

Thanks Dolphin! This is only a suggestion, but why not just refill all of the activations for your customers who have supported this product?

 

We did that - we added 2 activations for every key. Its mentioned in the documents.

 

However, the remaining number of activations might not show correctly until the patch "sticks" to StarForce server.


Edited by Dolphin887
typo

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Thanks for the heads up about this and the detailed instructions to deal with it. Product is now deactivated.

Justificus

 

System Specs:

i7 4970K @ 4.8, GTX 1080 SC, 32GB G.Skill DDR 2133,Thermaltake Level 10 Full Tower Case, Noctua NH-D15 6 Cooler, Win 10 Pro, Warthog, CH Pro Pedals, CH Throttle Quadrant, Oculus, 1 32" & 2 19" Monitors

 

 

 

Modules Owned: A-10C I+II, Ka-50, FC3, F-86, Mig-15, Mig21, UH-1H, Mi-8, CA, P-51D, BF-109K-4, FW-190 D-9, Hawk, NTTR, M-2000C, SA342, F-5E, Spit Mk. IX, AJS-37, Normandy, WWII A.P., AV-8B, F/A-18C, L-39, Persian Gulf, Mig-19P, I-16, Super Carrier, F-16, Channel, Syria

Link to comment
Share on other sites

Thank you Dolphin.

 

Thanks for taking care of the Fishbed community so kindly and thanks for the impressive fixed bug list you have recently posted in the bugtraker.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Link to comment
Share on other sites

First: Thanks for your work on solving this issue. :thumbup:

 

I have two questions :

 

1. Do you refill deactivations as well?

I had my activations refilled back when there were problems with 2.0, but when I checked my deactivations, I had only three left.

 

2. How do you handle the difference between activation types used in 1.5 and 2.0?

Last time the difference meant that every time you switched between 1.5 and 2.0, StarForce required a new activation.

Will this be a problem again?

System specs:

 

Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440)

Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use

 

Link to comment
Share on other sites

We did that - we added 2 activations for every key. Its mentioned in the documents.

 

However, the remaining number of activations might not show correctly until the patch "sticks" to StarForce server.

 

Cool! 2 is better than none for sure. Just to clarify - I own two keys, will both keys get 2 activations added even though I only intend to reactivate one?

Link to comment
Share on other sites

No.

 

Only a Fishbed lover.

 

PD: The info is in the PDF XDDD.

 

"Troubleshooting

If you patched MiG-21bis refuses to activate for any reason, to avoid further complications please

exit the DCS and perform deletion of registry entries for “Leatherneck Simulations” (explained on

page 8 ).

Note that we provided 2 additional activations per each key.

If you need any further help, please contact us at support@leatherneck-sim.com"

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Link to comment
Share on other sites

No.

 

Only a Fishbed lover.

 

PD: The info is in the PDF XDDD.

 

"Troubleshooting

If you patched MiG-21bis refuses to activate for any reason, to avoid further complications please

exit the DCS and perform deletion of registry entries for “Leatherneck Simulations” (explained on

page 8 ).

Note that we provided 2 additional activations per each key.

If you need any further help, please contact us at support@leatherneck-sim.com"

 

Yes I read the part about the 2 activations in the pdf if you posted this info for me, however my original post asked if ALL activations could be refilled because for me 2 does not equal the 7 I would like to get back on one of my keys.

Link to comment
Share on other sites

What i understand:

 

If you have two keys, lets say one with 4 activations left and the other with 6 activations left, after the update you are going to have the first key with 6 and the second key with 8.

 

Thats my guess.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Link to comment
Share on other sites

1. Do you refill deactivations as well?

I had my activations refilled back when there were problems with 2.0, but when I checked my deactivations, I had only three left.

 

2. How do you handle the difference between activation types used in 1.5 and 2.0?

Last time the difference meant that every time you switched between 1.5 and 2.0, StarForce required a new activation.

Will this be a problem again?

 

 

1. We will check this at StarForce server.

 

2. I admit that's the worst case scenario for us. The only thing I can advise at the moment is simply not to use (try to activate/deactivate) MiG-21bis in unpatched DCS 2.0.5. You can still use all other aircraft. We will talk with TFC/ED management if it is possible to release MiG-21bis patch for 2.0.5.

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

We advise you to do this in next 24 hours.

 

Maybe you don't have a choice, but that is pretty short notice! A lot of people are going to miss it.

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Link to comment
Share on other sites

Starforce is the DRM being used. All Mig-21 users are Starforce users.

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Link to comment
Share on other sites

1. We will check this at StarForce server.

 

2. I admit that's the worst case scenario for us. The only thing I can advise at the moment is simply not to use (try to activate/deactivate) MiG-21bis in unpatched DCS 2.0.5. You can still use all other aircraft. We will talk with TFC/ED management if it is possible to release MiG-21bis patch for 2.0.5.

Thanks for your swift reply Dolphin.

I really hope you manage to knock down the issue this time.

:thumbup:

System specs:

 

Gigabyte Aorus Master, i7 9700K@std, GTX 1080TI OC, 32 GB 3000 MHz RAM, NVMe M.2 SSD, Oculus Quest VR (2x1600x1440)

Warthog HOTAS w/150mm extension, Slaw pedals, Gametrix Jetseat, TrackIR for monitor use

 

Link to comment
Share on other sites

This patch is intended for openBeta. When ED releases the update for the stable version, follow the same procedure in the PDF

http://www.leatherneck-sim.com/

https://www.facebook.com/leatherneck.simulations/

 

i9 7980XE, 128GB Ram, SLI GTX Titan Xp, Win10 Pro, SSD, 2 x 256GB SSD, 4 x 512GB SSD RAID 0

i7 4960X, 64GB Ram, GTX Titan, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller

i7 2600K, 16GB Ram, GTX 580, Win10 Pro, 240GB SSD, 3 x 4TB HDD

Pentium 4, 2GB Ram, GeForce 6800 Ultra, WinXp Pro, 3 x 500GB HDD

Link to comment
Share on other sites

PLEASE let ED starforce guys know to open up VirtualMachine restrictions on paid maps, this is a HUGE deal - most multiplayer hosting companys run VM's, your counting them completely out! https://forums.eagle.ru/showthread.php?t=183227 - this matters for all starforce maps (I own 2 copys of the map and I cant use it atm because of this) - I dont know where to else to put this message, the starforce guys need to know

Developer of DDCS MP Engine, dynamicdcs.com

https://forums.eagle.ru/showthread.php?t=208608

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...