Jump to content

The m2000 development priority given to v2.0 is disappointing


Recommended Posts

Posted

I bought the m2000c module for use with the current version of DCS, namely v1.5.2 and I find really disappointing choice to distribute priority patches on the alpha version 2.0 that requires purchase of an additional map :(

Posted

This has been discussed elsewhere. There is no priority on either version of DCS World, the update for 1.5.2 is just not out yet.

 

I can understand your frustration, I'd not like it at all either, but I'm sure you won't be waiting a lot longer now.

Posted

There is no such development priority. The reason it was updated for 2.0 was that ED released a new DLC Campaign for Nevada. We should be really happy that they bundled the M2000 updates in there despite not even mentioning them in the changelog. It is highly likely that the M2000 will get the same (or newer) update in 1.5 next time that is patched, but it's ED that release patches, not Razbam.

Posted

Updates for 1.5 and 2.0 are never released at the same time. This time 2.0 came 1st, next time may be the other way around. It's up to ED anyway.

Posted

First of all you have to understand that 1.5.2 is the current Final release and 2.0 the Alpha/Beta release. And everybody knows that Alpha/Beta versions get patched first because of removing Bugs etc. and then the Patch comes to the Stable release. And ED does that since the early OpenBeta releases. In my opinion it's pointless to be disappointed about the Patch-Release order...

 

Cheers

Modules: Well... all of 'em

 

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Motherboard: ASUS Maximus VIII Hero | CPU: i7-6700K @ 4.6GHz | RAM: 32GB Corsair Vengance LPX DDR4 | GPU: GTX TITAN X (Maxwell) | SSD1: 256GB NVMe SSD System | SSD2: 250GB Games | HDD 4TB WD Red

Posted
First of all you have to understand that 1.5.2 is the current Final release and 2.0 the Alpha/Beta release. And everybody knows that Alpha/Beta versions get patched first because of removing Bugs etc. and then the Patch comes to the Stable release. And ED does that since the early OpenBeta releases. In my opinion it's pointless to be disappointed about the Patch-Release order...

 

Cheers

 

Fact!

Intel 8700k @5ghz, 32gb ram, 1080ti, Rift S

Posted
First of all you have to understand that 1.5.2 is the current Final release and 2.0 the Alpha/Beta release. And everybody knows that Alpha/Beta versions get patched first because of removing Bugs etc. and then the Patch comes to the Stable release. And ED does that since the early OpenBeta releases. In my opinion it's pointless to be disappointed about the Patch-Release order...

 

Cheers

 

Exactly, 2.0 is testing stuff

Calm down fellas!

Posted
First of all you have to understand that 1.5.2 is the current Final release and 2.0 the Alpha/Beta release. And everybody knows that Alpha/Beta versions get patched first because of removing Bugs etc. and then the Patch comes to the Stable release. And ED does that since the early OpenBeta releases. In my opinion it's pointless to be disappointed about the Patch-Release order...

 

Cheers

 

Somehow I don't think the M-2000C was added first to 2.0 for that reason. It is however a WIP, and they have to do one update at a time. No conspiracy, no favoritism, no cause for alarm, but nevertheless, frustrating.

 

At least we have the satisfaction of knowing that the current situation where NTTR excludes a number of people is only due to the need to integrate the Caucasus into 2.0, and that won't be the case once 2.0 is complete.

 

I am sure that ED don't like the situation any more than the guys waiting for 1.5.2 to catch up.

Posted
Somehow I don't think the M-2000C was added first to 2.0 for that reason. It is however a WIP, and they have to do one update at a time. No conspiracy, no favoritism, no cause for alarm, but nevertheless, frustrating.

 

At least we have the satisfaction of knowing that the current situation where NTTR excludes a number of people is only due to the need to integrate the Caucasus into 2.0, and that won't be the case once 2.0 is complete.

 

I am sure that ED don't like the situation any more than the guys waiting for 1.5.2 to catch up.

 

I don't see how 2.0 excludes people, it's peoples choice to not buy the Nevada map. Having both 1.5 and 2.0 is not the ideal situation but I'm very thankful we have the ability to fly and enjoy Nevada.

The way I look at it Nevada train and learn the airframe then go 1.5 for the combat works well until final release

Intel 8700k @5ghz, 32gb ram, 1080ti, Rift S

Posted

It excludes people that don't have NTTR. It is a module that has to be purchased, and if you haven't purchased it, you're currently excluded from 2.0.

 

Yes, you could purchase it, but there are a number of reasons people haven't, and that isn't the solution to the problem.

Posted

Like I said its the people's decision, it's a transitional time and I applaud ED for making 2.0 available as is. The mirage update will come for 1.5 and to be honest it's not much your missing allot of work to do but it's a great bird and will be amazing when feature complete.

Intel 8700k @5ghz, 32gb ram, 1080ti, Rift S

Posted

Allow me to explain something: We submit updates fairly regularly to ED. Most of those updates go to ED's internal beta testers. The 1.5.2 and 2.0.0 are released to the public when ED has a new patch to release.

 

It just happened that they had a patch ready for 2.0 so they updated 2.0 first. The 1.5.2 will come out as soon as ED has a patch/update ready.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...