lennycutler Posted April 4, 2018 Share Posted April 4, 2018 (edited) After installing the current release version today, i was asked upon startup of DCS Ver. 2.5 for my Serial Numbers for the DCS SU-27 and SU-33. I skipped past these screens and all seemed normal. I checked my Module Manager and found entries specifically for the DCS SU-27 and one for DCS SU-33....when I only really own Flaiming Cliffs. I tried this a few times with the same starting message that I needed to enter serial numbers...and the system said I could have authorization for 2 days etc. I got rid of this annoyance by simply deleting the entries for the DCS SU-27 and the DCS SU-33 from the module manager screen. I then tested the system with missions for both planes and as I suspected no problems were encountered. This did not happen in the 2.5 Beta. I hope ED ensures that those of us who own flaming cliffs do not have to be bothered with this issue in the future. Edited April 4, 2018 by lennycutler Velocity MicroI7-4790 Windows 7 Home Premium 16Gigs RAM EVGA NVIDIA GTX 1070 500GB SSD TM Hotas Warthog Link to comment Share on other sites More sharing options...
ED Team c0ff Posted April 4, 2018 ED Team Share Posted April 4, 2018 You somehow had those planes installed as separate modules. That's why. Dmitry S. Baikov @ Eagle Dynamics LockOn FC2 Soundtrack Remastered out NOW everywhere - https://band.link/LockOnFC2. Link to comment Share on other sites More sharing options...
lennycutler Posted April 4, 2018 Author Share Posted April 4, 2018 Yes, somehow they were in the old Mods folder. Velocity MicroI7-4790 Windows 7 Home Premium 16Gigs RAM EVGA NVIDIA GTX 1070 500GB SSD TM Hotas Warthog Link to comment Share on other sites More sharing options...
Recommended Posts