F-16C, F-14B, and F-86F module problems

[eaglecash867]

The F-16C, F-14B, and F-86F modules are no longer showing up on my 2.5.5 installation. They show up just fine on my 2.5.6 OpenBeta installation, but not on 2.5.5. They were working a few weeks ago. 2.5.5 does show them as titles I own in the module manager, and I even get a red "3" on the module manager button at the top of the screen. When I click the prompt to install them (with all 3 modules checked), I get a "Version 2.5.5.41371 is not available." message. What happened? I kept a 2.5.5 installation because of all of the issues with 2.5.6, and now I don't have access to 3 modules on that installation.

 

Here is the log file that it generated.

autoupdate_log.txt

[G.J.S]

Just a guess, but could it be that you can only have one instance of each module? If you have both OB's, then trying to activate them on both would count as two instances running concurrently, so unless you bought each module twice, you can only have it running once?

 

Again, just a guess.

[eaglecash867]

Just a guess, but could it be that you can only have one instance of each module? If you have both OB's, then trying to activate them on both would count as two instances running concurrently, so unless you bought each module twice, you can only have it running once?

 

Again, just a guess.

 

That's definitely a good guess, Gary. But, the 2.5.5 installation was the "stable" release version. Its been a normal thing for me to keep one installation of the previous version's release version when the next version of the OpenBeta comes along. It has always been a great way to avoid interruption when something gets broken in the new Beta (like 2.5.6 has been since the beginning). I just go back to playing the previous release version while I wait for the next update to the OpenBeta. I haven't had this kind of issue until just recently. I know that ED is restructuring a lot of things on their servers at this point, so hopefully its just a temporary situation.

 

Thanks for the reply.

[G.J.S]

That's definitely a good guess, Gary. But, the 2.5.5 installation was the "stable" release version. Its been a normal thing for me to keep one installation of the previous version's release version when the next version of the OpenBeta comes along. It has always been a great way to avoid interruption when something gets broken in the new Beta (like 2.5.6 has been since the beginning). I just go back to playing the previous release version while I wait for the next update to the OpenBeta. I haven't had this kind of issue until just recently. I know that ED is restructuring a lot of things on their servers at this point, so hopefully its just a temporary situation.

 

Thanks for the reply.

 

It might still count as two instances of a (singular paid) module, irrespective of if they are both OB, or 1 OB and 1 stable. :dunno:

[eaglecash867]

It might still count as two instances of a (singular paid) module, irrespective of if they are both OB, or 1 OB and 1 stable. :dunno:

 

That would be true, if it wasn't for the fact that it worked up until I jumped back into it today. Like I said, what I'm doing isn't abnormal. A lot of people here do the same thing, for the same reason. Now, new aircraft modules don't work in older modules, which I understand. That's even called out in a big, red banner on the "buy now" page. I just confirmed that ED still has the F-14B saying it requires a minimum of 2.5.4 to run, and the F-16C requires a minimum of 2.5.6. They're not considered two instances if one is Beta and one is Stable.

[G.J.S]

That would be true, if it wasn't for the fact that it worked up until I jumped back into it today. Like I said, what I'm doing isn't abnormal. A lot of people here do the same thing, for the same reason. Now, new aircraft modules don't work in older modules, which I understand. That's even called out in a big, red banner on the "buy now" page. I just confirmed that ED still has the F-14B saying it requires a minimum of 2.5.4 to run, and the F-16C requires a minimum of 2.5.6. They're not considered two instances if one is Beta and one is Stable.

 

I get that, i do bud.

What i was trying to say though, regarding the two instances, is that lets say you bought the F-16 ONCE. Now, - i don't have more than one iteration of DCS, so i cannot say for sure, - but if you are licensed for ONE F-16, can you really run it concurrently on TWO separate different instances of DCS, activated at the same time?

Again, i don't really know as i only run OB, but it may run into similar to 'copy protection' used by some other downloadable items.

Since DCS connects online to verify that you own said module, if it already has a previous activation (?) for, say OB, will it allow stable? Or vice versa?

[eaglecash867]

I get that, i do bud.

What i was trying to say though, regarding the two instances, is that lets say you bought the F-16 ONCE. Now, - i don't have more than one iteration of DCS, so i cannot say for sure, - but if you are licensed for ONE F-16, can you really run it concurrently on TWO separate different instances of DCS, activated at the same time?

Again, i don't really know as i only run OB, but it may run into similar to 'copy protection' used by some other downloadable items.

Since DCS connects online to verify that you own said module, if it already has a previous activation (?) for, say OB, will it allow stable? Or vice versa?

 

Yup. You can have it in both iterations. Just can't run them both at the same time, for obvious reasons. Like I said, it worked until recently, and even tells me I have purchased modules to install. Hopefully someone from ED will have a look at my log file and fix the problem. It seems to be looking for something on-line that it currently can't access. Any time a completely new iteration comes out for the Open Beta, I upgrade my Stable version to the last iteration I was happy with so I have a backup in case the new Beta is Tango Uniform like 2.5.6 is. Tried flying the A-10C in 2.5.6 today and it was awful with how the TGP got broken. Its not just temporarily blinded by the rocket motors on my Mavericks...it stays blinded the remainder of the mission. Its almost like a person who looked into a flash and permanently damaged their retinas.