Redglyph

I should probably report that in the UH-1H bug forums instead :) About the campaign, lot of fun so far :thumbup:

Mission 1: I'm just mentioning this bit I've just seen and could confuse people. If you happen to change UHF, you're told to tune back to 262 MHz, but I think it should be 260 MHz, and not at 262 MHz or it keeps giving this message every few seconds. Similar issue with the search mission where you have to tune to 47 MHz FM. It keeps displaying the reminder even though it's correctly set. It seems to be customary with new campaigns ;) By the way, does anyone else had this problem on the Huey when you use the cargo view (LALT + SHIFT + Q by default) and try to get back to the normal view, it's completely off and apparently not possible to get back to the pilot's position? Is there any trick to get around this?

Perhaps you missed the two long threads of support and the unprecedented availability from their part, or the fact they cannot control all external constraints like the protection mechanism provider or ED's delivery system. To me, that looked very professional, the only glitch was not asking ED to mention this in the first update but considering the circumstances it does not shock me. They solved an old problem with a very simple method, and still get criticized for that, I'm amazed. Especially when it comes with complex products that require reading hundreds of pages of manual, this in comparison is quite basic. I don't understand why we had to do this, I suppose it's a limitation of the StarForce system or poor support from their part, I don't want to speculate. Those protections are always the matter of choosing a lesser evil. Thankfully they're not using something bad as Denuvo, that would be the day I uninstall the product.

To add to what razo+r already said, make sure to check the other April thread, the first post contains all the doc you need (check case 4 in the pdf). You only need to do this once, for either 1.5.6 or 2.0.5.

Yeah, this January bug is annoying ;) You can simply edit the mission in the Mission Editor, and change the date to early February for all the missions that are concerned. Since this campaign is not protected, you can save the edited missions (the modified files will be replaced on each update).

@ED: is that a known issue?

Have you actually read part 4?

From the message it looks like attempting to deactivate from a new version, he'll have to use step 4 and remove the registry key. (https://forums.eagle.ru/showpost.php?p=3103176&postcount=30 and replies, for ex) Oh, or were there key "exchanges" that led to their being blacklisted? o.O

It's one of the described cases in the pdf (and many, many posts in this thread cover this specific problem). Look for part 4 in the document and you should be good to go.

Perhaps they gave the choice of the cockpit then, that would make it easier. :)

No, it's indicated in km/h and meters (flight manual, pg 131 and 133). Or was it different before?

For sure. While I'm used to the standard metric system, and so km/h in cars, I learned to fly (in sims) with knots. Switching back to Russian aircraft that have km/h or in WWII UK aircraft that have mph is sometimes disturbing. But in a similar way to languages, I found that switching between them without trying to do a conversion but just keeping consistent, separate systems - "thinking" in other units if you like, helped. It would be a problem for the same aircraft, but not if they're quite different in mass, thrust and so on. Perhaps it's less of a problem for people who are new to this, still, I agree with you that anyone likes to compare to a familiar reference. Speaking of which, a Russian cockpit won't help either ;) Or the other way round of course, an English cockpit for someone speaking Russian.

The L-39 is a nice aircraft, but don't forget the training lessons are a little less user-friendly for an English-speaking cadet, and the taxiing is ... something else entirely, at first ;) In any case, not big issues, really. Not sure about the gauges... there doesn't seem to be a US metric cockpit yet, that may come one day. Anyway, each plane has its own key speed parameters (rotate at take-off, approach, touchdown, stall, ...), so if that's in knots or in km/h, you still have to memorize them, same for pressures. I don't think the units should be any problem.

If she focuses only on the flight part first, the A-10C isn't complicated. When it doesn't need to be set-up for combat missions, then a lot of functionalities can be ignored. At the very beginning, the auto-start can be used, but the start-up checklist isn't overwhelming. It is very easy to fly, take off and land, much more easy than most other aircraft (landing an F-5 or an Albatros requires more precision for instance). It has an easy-to-set autopilot that allows the pilot to take the time to inspect the cockpit or a manual without having to pause. The TAD can also be a great help when one is not familiar with the surroundings, or with navigation. And it has redundant instruments for navigation, control and performance. Other than that, I'd say the P-51D (or even the free TF-51D) is the easiest prop, though taking off and landing requires a little more practice than the A-10C, and you have to watch the engine. Finally, the F-86 is pretty forgiving and simple (and fun!). So if I had to learn it all again, I'd start by any of those three modules. Learning is also made easier with existing missions and campaigns, for that the A-10C has a huge choice, and the F-86 a great, progressive campaign.

All cases are covered in the documents in the first post, did they try to follow those instructions?

What a great encounter that must have been! Very interesting info, thanks for sharing! :)

Exactly! We won't be intimidated by a bit of stuttering! Back on topic too, I don't think there's a ticket for this bug yet, which is usually the best place to report them (after a preliminary search). Perhaps I'll write one later if that's necessary but I don't think they had much time to look at all the posts with the amount of work they had recently. Let's be patient.

It's covered in this thread, first post, check the pdf. In summary, you apply the .reg file (double-click it), it will remove your current key. Then when you start DCS you'll be asked for the key to activate the new version.

In the pdf, it's the case 4, pg. 6, since you couldn't deactivate before updating. It's "normal" that you get those error messages from the licence pop-up window, since it can only be deactivated from there before the update (I suppose it's a limitation due to how StarForce works). So you have to do the registry part ... unless you have a 2.0.5 which is not updated yet to 2.0.5.3889; if that's the case you can do the deactivation from there too, then reactivate from the 1.5.6. When you double-clicked on the *.reg file and confirmed, did it say the changes were applied successfully to the registry? You can also do the procedure manually, it's explained in the pdf of the other thread, page 8. The next step would then be to activate from 1.5.6.3930. If you get an error message, report it here with more information than just "it gives me the error", because that does not tell much - could be the version, could be you are out of activations, could be something else.

Well, that's good news, have fun! :)

Same here, the difference between 2.0.5.1648 and 2.0.5.3889 is very noticeable. Just slowly turning the head from left to right shows how much jerky this is in comparison, no matter where, on the ground, in the air, near another aircraft or not. What is weird is the framerate doesn't seem too bad, it's in the range 50 to 60 when sitting still on the runway threshold at TTR with VSYNC on and looking ahead, for example. With VSYNC off, I can look to the desert on my left and get more than 80, but the movements are still awefully jerky. I've tried a few other modules (TF-51D, M-2000C, F-86) and they seemed to show the same level of rendering performance as before, it's smooth, so this issue seems very specific to the Fishbed in my case too. I've also tried without TrackIR, with the mouse or the keyboard, but that's inconclusive since it moves faster. I'd say it's exactly the same. If there are interesting data I can provide, let me know.

The procedure for those who updated first, as well as all the other cases, are explained quite clearly in the first post (pdf files). Please give more details, the version you are using, what you mean by "doesn't work" (message), otherwise it's hard to help. EDIT, oops, missed Sporg's reply that was already there :)

Quelle version utilises-tu ? La stable / release, beta ou alpha ? Vérifie que le numéro de version est bien le dernier, pour la stable ou beta ça devrait être 1.5.6.3930.271, et pour l'alpha 2.0.5.3889.199 (tu peux voir le numéro de version en bas à droite du menu principal de DCS. Quel message d'erreur as-tu quand tu essaies d'activer le module ? Sinon, j'ai vu que la procédure habituelle dans ce genre de cas est de tenter une réparation, et essayer à nouveau d'activer le module.

I didn't get any reply either (checked my spam box too), that didn't bother me, seeing this thread I understood there would be new deactivations granted and that seemed more efficient than processing everyone's case. But I'm still out of deactivation apparently. I suppose I'll delete my registry keys again and lose one activation instead, but I wish I had my original token count back at some point, this limitation wasn't really clear from the start.

That's great news! Thanks for the explanation, Dolphin887, can't be clearer than that :) I'm pretty sure it was irony from 2IAE-CrashBG's part, or perhaps even sarcasm ;)