Aufpassen

Salute, clear skies for ever. My sincere condolences and wishing friends and family strength in what must be very difficult times.

Yes, please, end it already. The percentages didn't change for months.

Stick: Microsoft Sidewinder 2 Throttle: Saitek X52 Pro Pedals: CH Pro Pedals

My concolences to his family, friends and colleaques for their loss. S!

Hi there, since the latest update I have something strange going on with the SU-33 module. I own Flaming Cliffs, installed and functioning. Every time I start the software it asks me for a serial for the SU-33 module. Either I don't enter anythhing (the module is disabled) or I enter the key for Flaming Cliffs and the SU-33 works. But the next time I start the game it asks again for a serial. So, the question is, what is going on? And how to stop this from happening? Best regards, Aufpassen!

Image should show the problem. Nothing really serious, but I don't know how to fix this. Repair and cleanup didn't do it and reinstall of the module either. Any suggestions? Best regards, A.

Thanks guys, I also had no issues: a no sweat upgrade all in all!

Do I need to deactivate my modules before the creators update? Anybody in the know? Best, Alfie

BIOS update went smooth, no activations were lost in the process. Thanks everybody for help and advice.

Thank you for your reply. I found you can deactivate the campaigns. The exe. Under the DRM button lets you deactivate them. One more question: Is there a way of deactivating all modules at once?

Do I need to (must I) deactivate my module keys before a PC-BIOS update? And do I (can I) deactivate my campaign keys? In the module manager there is no deactivate tick box in the campaign listing. Does anybody have any idea? Best regards, Auf

BS-feature: Block Tacview alltogether (don't trust anybody on the server) or allow it (you're among friends), that is all that is needed. This is overengineered for a game.

I thought I'd solve it this way too but I can't get rid of the module update Blackshark 1 to 2 in the module manager. Anyway to do this?

Got IT!

I found that everytime the system switches from dedicated graphics card to onboard graphics you loose an activation. This can happen when windows updates but it also can happen when you change settings in the BIOS, meaning it happens even when you never opened/rewired anything inside your PC. Interesting piece of information...

Hi there Racoon, what you need is an impartial Jury of top skinners. Why not ask a few of the best skinners for other Sims, perhaps IL2 or ROF, and ask them to judge? Skinners like VPMedia for example? There are quite a few around you could ask. Also a nice way to bring the community together :)

FYI, this happened quite a few times to me (yes, I know, not very bright): I started the beta just wanting to fly, oh wait an update, press OK. Updated, but then the games says activation needed. Oh sh*t, started NOT in Administrator mode. Wanting to stop the proces I press "cancel". Unfortunately that doesn't work: as soon as the program starts you can't stop the activation proces. The activation proggie goes on the internet anyway, activates, but it can't write to the registry. Another activation gone :(

I see. So at the moment we can use either the 1.5.3 Stable or the 2.0.1 Alpha. Because of the constant stream of updates on the 1.5.3 beta version (and the much slower stream of updates on the stable branch) I uninstalled the stable version from my SSD already quite a while ago to save space. The only reason to install the stable version again would to be able to fly the mig 21 over the Kaukasus map. Everything else works flawlessly on the 1.5.3 beta version and can be combined with the 2.0.1 alpha version, meaning I can fly all other modules on both maps. There may be feature parity between 1.5.3 at the moment but experience tells me this does not last long. So here's my question: when will the beta version of the mig21 support both maps? Best regards, Aufpassen!

Hmm... I updated, I cleaned the registry with the reg-file, started the beta, activated and all is fine so far. Then I fired up the alpha version. Huh??? Now I can't get into the cockpit of the Mig21. Did a repair and still no go. Before I bork another activation, any suggestions?

Same thing here. I have two licenses, one for my desktop and one for a notebook (I like to play around with tracks while travelling). Both are down to 3 activations now, mostly because I didn't know about this alpha/beta sh*t. It is getting annoyiing.

Hmm, can I do that without losing activations?

So I have 2 PCs with almost all modules activated (exception: I don't have two keys for the new mirage, at the moment I have just one). They are activated and bound to me as a user. Flying myself on one PC and having a friend fly with me on the other one, will we be able to log in with the same user name twice?

Ah hell, deactivated all on the working machine and then reactivated all on both much machines. Just lost a whole bunch of activations for nothing. Thanks much

In Post 1 it says I can also deactivate throught the personal licensing section. I can't find that option. Where do I find it?

Hi there, I have 2 PCs with all modules (well, almost all) on both machines. Now, 1 PC threw a fit (hard disk went tits up), and I couldn't deactivate the modules. The question: How do I find out which serials are activated on the machine that is working? (Don't want to deactivate those obviously) The hardware codes that I find at the licensing page don't really tell me anything. There is more then just one hardware code for a PC. The goal is to only deactivate serialz from the machine that is broken. How do I do that? Thanks in advance!