I want the money back

I have to say that, even in a flight simulator, I never, never, never rotate with full aft stick :music_whistling:

Well, my bad, indeed the FBW doesn't follow stick input.

So the problem was Starforce activation ? There was a warning banner on the forum yesterday...

Wait until 130-150kts to set T/O trim (<--any aft stick sets it).

Seems like the trim is meant for AB takeoffs, as well.

Edit: By the way...I haven't flown the latest 2.0...Is that the problem here? I probably should've read the thread! :p

Wait until 130-150kts to set T/O trim (<--any aft stick sets it).

 

Seems like the trim is meant for AB takeoffs, as well.

 

Edit: By the way...I haven't flown the latest 2.0...Is that the problem here? I probably should've read the thread! :p

StarForce being itself has screwed up the latest patch for 2.0.

StarForce being itself has screwed up the latest patch for 2.0.

Lol wow...Thanks for the info.

Hi guys, I'm just as sad about the problem as you guys are, unfortunately many have found it's out of our control right now so waiting on ED for a fix.

 

The instant the patch came out, tested to see if the patched version was working okay and found the exact same scenario seen here. Full throttle, got not afterburner, at a certain airspeed the FBW commands a full up elevon response.

 

I'm also having issues with pretty much any other EFM based module it seems. I went so far as to do a full clean re-install of alpha last night and still coming back after work today the same issue occurs but does not happen in the development build, which points to other suggestions that the DRM protection is the root cause but I can't say for sure.

 

It almost looks like memory address pointers to functions and/or data got all corrupted and screwy so it's getting odd responses and different behavior for each module.

 

Apologies this is happening guys but hopefully they find a fix soon!

One of the LNS devs actually tested with an unprotected version of the game and found out it was not subject to the issues you're describing.

So yeah, almost certainly the fault of the copy protection.

Apologies this is happening guys but hopefully they find a fix soon!

Thanks for the update, we're hoping alongside you!

--gos

Можете забанить! Уже было! правда теперь я ни кого не оскорбил, и все на вашей совести))) Разбам является сторонним разработчиком? ВЫ несёте ответственность за то что пускаете в обнову???

Вас крайне неприятно читать, уважаемый. Истерика вперемешку с дешевыми понтами никакого результата кроме заслуженного бана вам не даст.

Apologies this is happening guys but hopefully they find a fix soon!

We'll wait as long as will be needed :)

Thanks for a great module and I wish the Typhoon would be made by your team :)

After latest patch ( 2.0.5 update 2 ) the problems still remain :(

I'm having the same issue although it only happens in 2.0 and not 1.5 glad it seems to be an issue being looked into and not something wrong with my hardware...

Ya even after the 3/17/17 update the issue still persists which is a huge bummer...

Folks, it is something that we cannot control since the problem is inside DCS. Like you we have to wait for the fix to arrive.

Ya it's just a bummer is all not trying to make you guys at RAZBAM feel bad. I just think the Nevada terrain is sooo beautiful haha oh well back to the Caucasus

*or downgrade to 2.0.4

*or downgrade to 2.0.4

I don't think that is possible anymore as I heard the files have been removed from their server.

I don't think that is possible anymore as I heard the files have been removed from their server.

That seems to be hit or miss. Some people have done it successfully even after others posted logs indicating that the files were not available. It is worth a try.

That seems to be hit or miss. Some people have done it successfully even after others posted logs indicating that the files were not available. It is worth a try.

Oh! Ok I didn't know that! Thanks. :)

Oh! Ok I didn't know that! Thanks. :)

Based on a post that Skates made, just a minute ago, many of the people experiencing problems were doing it incorrectly. So definitely give it a try.

Because you are running the DCS_Updater from within a Release or Open Beta Branch (Hence the INFO: 1.5.6.xxxx Version Number on Line 5 of the Log).

There is no 2.0.x.xxxx Versions on the Release or Open Beta Branches, which is why it says version unavailable.

 

If you want to revert an Open Alpha Install, Run the Updater from the Open Alpha Bin Folder.

well. just bought the M2KC and tested for very first time on the 2.0 ... god... after 2 hours trying to takeoff with the plane crazy i was thinking that it was me that i cant handle such a plane o.O

I have found a work around that works for me guys... I reverted my installation of DCS World 2 to version 2.0.5.1648 using the Updater's command line entries... this fixed the issue with the F-5 freezing and the Mirage 2000 departing controlled flight while retaining the ability to use to the Viggen and play the new F-5 ACM campaign! Hopefully this works for others!