No, that is not a 'simple solution'.
You have no idea what StarForce is or how software development works.
Starforce is not "their" activation system to fix, nor to adapt, nor to modify.
StarForce is a continuously updated third party DRM tool from a Russian developer that checks multiple times after a program is started if a piece of software is validly licensed. The exact way they do this is not public, but we do know that they not only assign a specific computer ID based on BIOS information and registry keys, but also check the module DLL's while the program is running.
Some info from when VEAO's Starforce was on the fritz:
Its essentially starforce thinking that we're trying to hack the aircraft dll's because of the constant communication between the ASM and EFM interface.
Why aren't other modules affected by this communication?
You can't simply flick a switch and it works.
The coders have to try things to see what happens, which they have been doing. The discussion is about what they've been trying with a solid direction going forward.
No point wasting weeks on something that won't work.
Yes it is unique.
There are two ways for the ASM and EFM to communicate; use default data the sim gives us or calculate accurate data like true air speed etc.
We calculate all EFM to ASM functions dynamically and don't use default sim data.
This gives a more accurate data exchange therefore a more accurate flight model.
But doing that has obviously caused SF to have a hissy fit, nothing we could have predicted.
Why it affects some and not others we don't know.
That's why we asked for your feedback on systems and software.
Both main programmers are here in the UK for the show hence the discussion.
The starforce implementation and constant the fact that the modules are never finished updating, is the reason why pretty much EVERY developer, not just LN, has trouble with the system.
1) Okay, so why does DCS still use Starforce?
Try to find a pirated version of DCS. Not succesful? Yeah, that's because it doesn't exist. It's not perfect, but no piracy is a strong incentive for a company to proceed with finicky software. To overcome a lot of the issues, ED has taken over as much registration and activition tasks from the end consumer as possible with the Module Manager and profile key binds, but again: it still isn't perfect.
2) Why doesn't LN change it's implementation of Starforce?
They have chosen a certain implementation because it worked during testing. After completion, it's damned hard to change something that hard coded without breaking something else or the working of the entire module for everyone. So what they did is changed some tweakable aspects of the DRM, and ease the pain of as many customers as possible.
3) Why is LN the only one with this issue?
They're not, it's a DCS-wide issue with all devs (inlcuding ED) suffering. There is just no way to actively test all BIOS systems, settings and options for all PC's ever made. Even settings within Windows themselves have led to Starforce problems for the end users (and the reason why some people need to format their HDD after buying their first modules, it's just a very aggressive DRM)
And by the way, I've seen that you not only started this thread, but have been whining and failing for a good year already. Perhaps it is time to take responsibility for yourself, e-mail Dackard to ask for a new key or just continue life since with all this laziness and bullsht on your end you don't do yourself nor anyone else any favors.
@Ice: Problem: My key acts funny. Solution: 60 seconds and you get a new key within 48 hours, no questions asked.
Again, what do YOU suggest? WHAT do they have to do?
Don't you think that if it was solvable, they wouldn't have done it already? Wouldn't that just save a godamount of time and stress for them? If your key fails multiple times in a row, you need to sent an e-mail for a new key and with 24-48 hours you receive your new key.