Any news 2.5 final release date?

[animaal]

I uninstalled 1.5 today; the only version I need is 2.5. I find the performance generally good in 2.5, although my laptop and playing style might not be the same as everybody else's.

 

I'm delighted to have just one install to worry about, as opposed to the three I had a month or so ago.

 

The issues that affect me most are the unresolved issues in DLC campaigns - e.g. some missions that can't start, or others where the new Caucuses map obscures landing areas or other objects of interest. But I know these are things to be fixed in the campaigns, not in DCS itself.

 

All in all, I'm far happier being able to fly the 2.5 Open Beta than being still in 1.5 and being told that 2.5 is "coming soon".

[Jacks]

I feel you're pain, but to be fair to ED and personally speaking I haven't seen many of the issues you mention. I fly in VR and have now managed to get my setting so it flies smoothly (most of the time) and looks quite stunning.

 

I am very pleased with how things are progressing and the fun I get out of this sim far outweighs its frustrations, for me at least.

 

Keep the faith! :thumbup:

 

I wish I could achieve a smooth VR experience ......

Edited March 4, 2018 by Jacks

[dedde01]

Guys, you have to see the glass half full!!

There is someone near the ED's office who is becoming rich by selling coffee cups to the devs!

[NineLine]

The statement here still holds true:

 

https://forums.eagle.ru/showpost.php?p=3399945&postcount=130

 

DCS World 2.5 Update

Since last week’s newsletter, the team continues to address items discovered during the Open Beta test period. Items such as fog discoloration, night lighting, multiplayer performance, load times, and others are all being addressed for the release version. It is very important that any changes made for the DCS World 2.5 release version maintain or improve game performance of the 2.5 Open Beta.

 

Open Beta is a release of DCS that is not ready for full release. The goal is to have it put out against many different users using many different configurations. If you are not happy with 2.5 you can still use the release version and either wait for a patch or wait for the release version of 2.5. Open Beta software is not for everyone.

[martinistripes]

This seems rediculous to me... "Release 2.5 now!" "OMG how can you release a BETA with bugs?!"

 

This^

 

Nobody is forced to download an OB. Take it with the bugs or wait. That's all.

[BlacleyCole]

As a programmer I understand thinking you have tried everything only to release it with different hardware configuration and users that want to break it on purpose and those that break it from lack of knowledge.

 

I’m been pleased not every programming team would be able to release on a weekly schedule.

[Ratcatcher]

As a programmer I understand thinking you have tried everything only to release it with different hardware configuration and users that want to break it on purpose and those that break it from lack of knowledge.

 

I’m been pleased not every programming team would be able to release on a weekly schedule.

 

Oh I get it, its our fault...nice. :doh:

[feefifofum]

His point is - it is literally impossible to test every single thing on your own or within a small group of official testers. Every user does things a little differently, often using the program in ways you never considered.

 

This is where an open beta comes into play - are there bugs the team is aware of at release? Most likely, this is why the product is labelled as a beta. But it's at a point where the team need to see results from a wider user base in order to proceed in the most efficient way possible.

 

Participate or don't, it's up to you. Lament that the beta has lasted longer than originally projected, if it makes you feel better, but it's very likely the same people that lament the delays would be the ones standing outside the office with torches and pitchforks if a "release" version contained issues such as memory leaks and invisible objects.

 

Rest assured the team is working hard to bring 2.5 to a full release status. If you can't wait for the shiny new map, hop on the beta bus. Many of us are flying and enjoying it within the constraints of the current issues, including my group who have run 3+ hour ops weekly with elaborate scripting in the new Caucasus map with no issues once the invisible objects were identified and replaced.

[Ratcatcher]

Sorry, that may have been his point but saying "users that want to break it on purpose and those that break it from lack of knowledge." does not come across in his text.

 

Clearly you both come from the programming side of things and not public relations...

[imacken]

I feel you're pain, but to be fair to ED and personally speaking I haven't seen many of the issues you mention. I fly in VR and have now managed to get my setting so it flies smoothly (most of the time) and looks quite stunning.

It's not about how smoothly it runs, or how good it looks. There are major issues to be addressed and clearly ED are working on them. Otherwise, we would have had a release version by now. However, you can see by the number of posts and identified issues, that it is far from ready for release atm.

Happy that everything is all OK for you though!

[Ratcatcher]

@imacken.

I don't doubt there are some major (and minor) issues that need addressing. My post was merely pointing out that, like in most things in life, there are two sides to every story.

 

Some posts prior to mine were practically calling for a lynch mob due to the release of 2.5 in its current state. I was just giving my personal opinion that my experience has been pretty good.

 

Yeah I know, lucky me!

[NineLine]

All you need to know is that 2.5 is in Open Beta, ED releases to open beta to get the largest sampling among different configurations before release. Its not ready for release and has not been released fully. If you dont like helping test software, its best to avoid Open Beta releases.

[Tread_Head57]

Clearly you both come from the programming side of things and not public relations...

 

 

:megalol:

Edited March 5, 2018 by Tread_Head57

[BlacleyCole]

I wasn’t saying you were one of the users trying to break it but there are users out that try everything to see what works right and what doesn’t it part of their using it they’re not the ones that just fly by the numbers and such. I had a guy helping me who I gave each released to him and told Jim to try each and every option and document wether it worked as expected or went haywire. It was the only way to release it to my users.

[Johnny_Rico]

As a programmer I understand thinking you have tried everything only to release it with different hardware configuration and users that want to break it on purpose and those that break it from lack of knowledge.

 

I’m been pleased not every programming team would be able to release on a weekly schedule.

 

 

How can I break something on purpose or from lack of knowledge?

Kinda confused by that line ?

Edited March 6, 2018 by Johnny_Rico

[Fri13]

How can I break something on purpose or from lack of knowledge?

Kinda confused by that line ?

 

Breaking something on purpose, is different from breaking something by mistake or accidentally. "on purpose" means that you know that you are doing something that will break it and you want to do so. That is difference like breaking a law on purpose (like speeding to hospital while someone is dying at your backseat, so you know you are doing wrong but you are trying to save someone's life) or by accidentally.

 

From "lack of knowledge" it is like a child that doesn't have a knowledge that hot oven burns hand, so when a child tries to open the oven knowing they shouldn't touch it, doesn't just know why and gets burned, it is lack of knowledge.

 

In testing you try to on purpose to break things. like you are creating a mission with 1500 units firing same time. Or fill all kind logic loops that you know should cause trouble.

Or you don't know what you are doing and you just "mash the code" with some random things hoping something good and you just happen to break things. And such can be not valid testing as normal person might not never do such things as it is not expected.

[Haukka81]

It was mentioned in the patch notes about the problems

 

https://forums.eagle.ru/showthread.php?t=200724

 

and Wags the producer also made a statement about the delay

 

 

 

plus us as moderators have been trying to pass on info, not sure what else we could have done to communicate it more.

 

anyway, hope we wont have long to wait now.

 

 

 

The 2.5.0 "Release" version will launch a week or two later, depending on how the Open Beta release goes. = https://www.digitalcombatsimulator.com/en/newsletters/newsletter26012018-2b897d3a693546bc47e17459ce0b316c.html?bx_sender_conversion_id=16352

 

Least that was empty promise.

 

Or least dcs week or two is long ;)

 

 

 

 

Sent from my iPhone using Tapatalk

[philstyle]

Least that was empty promise.

Or least dcs week or two is long ;)

 

 

 

"depending on how the Open Beta release goes"

 

 

OK, I'm a critic of the wait too, but your quote doesn't do what you seem to think it does.

[Reflected]

I don't understand the complaints. We got 2.5 beta and it's awesome. Better than 2.2 or 1.5. Does it have bugs? Sure, but now that so many people are testing they can get more feedback and progress faster. How can anyone possibly expect them to promise when all the bugs would be fixed? Or just enough to call it "2.5 release"? How could anyone know? It's a journey of continuous improvement anyway, so it doesn't really matter if it's called beta, or release.

 

So my advice is to download the beta, and enjoy it. There is a lot to enjoy. If you don't want to, then wait for the release version and remind yourself that it was your choice to wait. Let me tell you that the release version will have bugs too, but ED will work just as hard to squash them as in the beta version.

[Donut]

I am thinking that the 2.5 Open Beta release was rushed and released only to satisfy the "promise" of being delivered by the end of January. Everything in DCS has been delayed and 2.5 is apparently no exception. We should all be acclimated to this by now but it is getting a bit tiresome, discouraging, and frustrating. Let us hope that this is not a preview of what the Hornet release will be like; however, DCS is unfortunately developing a history of delays and a long list of unreleased features, maps, and aircraft from both ED and third-party developers.

[PeaceSells]

Sorry, but the cockpit buttons lights problem is there since 2.2. The memory leak should have been the first thing fixed... it breaks multiplayer for many of us, myself included.

 

While "don't install betas if you can't stand bugs" is true, it really doesn't justify some stuff...

 

You just can't say we can't stand bugs. We wouldn' be playing DCS release version if we couldn't stand bugs.

[Esac_mirmidon]

Try something else. The World is wider than flight simulators only.

[PeaceSells]

Try something else. The World is wider than flight simulators only.

 

Great advice, I would hire you as public relations!!

[Esac_mirmidon]

If any activity is a source of tiresome, frustration and discouraging, just stop, take a deep breathe and do something else.

 

If some cant enjoy the journey better not start walking.

[Donut]

If any activity is a source of tiresome, frustration and discouraging, just stop, take a deep breathe and do something else.

 

If some cant enjoy the journey better not start walking.

 

Good advice and that is exactly what I have done. I have not touched DCS since December as I have been waiting for the 2.5 release version as well as the Hornet and Tomcat. However, I don't think ED would be very supportive of this advice as it creates an unsustainable business model. We have a small, unique community and ED cannot afford for people to leave or take breaks. They need continued and growing support.