DCS Update Patch Notes Discussion Thread

VEAO Hawk update? :)

VEAO Hawk update? :)

F14.....:music_whistling:

Given the time passed since the last beta patch release, I feel they should have released the open beta branch today and that 3rd party would have waited for the next open beta upgrade window.

 

Certainly better than no updates for yet another week.

 

Hint: Maybe they can still do this on Friday and the late 3rd party can still work till Wednesday?

Exactly my thoughts when i readed the message

If it's a very popular module like the F-14 I can see it causing a lot of heartburn to those wanting to fly online with others in the new branch. Also some of the maps becoming unplayable because the module is no longer compatible.

If it's a very popular module like the F-14 I can see it causing a lot of heartburn to those wanting to fly online with others in the new branch. Also some of the maps becoming unplayable because the module is no longer compatible.

Could be, but they'd still have the option of playing on stable branch servers.

Could be, but they'd still have the option of playing on stable branch servers.

let's be real

do they?

All the good multiplayer servers are on beta, pretty much anyone interested in DCS is on OB...

...this said, I don't think it's the F-14, because HB has a track record of jumping on issues earlier than ED can, but I hope whoever it is comes out with a "sorry" at least, after we get the patch.

:chair::chair: I don't have next week!

:D

...this said, I don't think it's the F-14, because HB has a track record of jumping on issues earlier than ED can, but I hope whoever it is comes out with a "sorry" at least, after we get the patch.

I wasn't speculating on which module it is, it's not really important, 'could be' was aimed at people complaining about not being able to fly their module as a reason behind ED's decision to postpone the update again.

The point I was aiming at is that it wouldn't be the first time that some module is out of sync with the latest beta (IIRC, cockpit lighting issues?), so I'd prefer they release the update sooner rather than later and the last 3rd party can sync on whenever they're ready.

That way, most of the users win and ED can begin getting more error feedback on the new VR optimizations.

I also think they should release the patch on Friday with or without the 3rd party, this way they can take their time and write their code. Holding everything up for a 3rd party is well.....

I wasn't speculating on which module it is, it's not really important, 'could be' was aimed at people complaining about not being able to fly their module as a reason behind ED's decision to postpone the update again.

 

The point I was aiming at is that it wouldn't be the first time that some module is out of sync with the latest beta (IIRC, cockpit lighting issues?), so I'd prefer they release the update sooner rather than later and the last 3rd party can sync on whenever they're ready.

 

That way, most of the users win and ED can begin getting more error feedback on the new VR optimizations.

cockpit lighting =/= unable to use a module, though. That doesn't happen often.

DCS Update Patch Notes Discussion Thread

To release 2.5.5 today would mean their module would not function within DCS World. We very much hope to see this resolved next week

thanks for the update.

a difficult decision to be sure, but it’s the right call given the situation

I don't bother much with the usual updates, but 2.5.5 is the VR improvement patch and we have been waiting for this forever!

I don't bother much with the usual updates, but 2.5.5 is the VR improvement patch and we have been waiting for this forever!

It's just 6 days away now !!!!!! :thumbup:

People who are asking for release it tomorrow, maybe would cry if they do it, because they think it's another module that needs update, but maybe it's their favorite module ... :lol:

I don't bother much with the usual updates, but 2.5.5 is the VR improvement patch and we have been waiting for this forever!

So another few days shouldn’t be a big deal. Potentially breaking someone’s favourite aircraft really wouldn’t be cool.

I’m with ED for holding off until they’re happy with the test results.

Which is the purpose of the stable branch then ? The update could have been released yesterday without that third party module, and include it the next week update.

This happened in the past and we choose if run the stable or the beta branch. Probably the delay isn't only due a third party and ED need to fix some things too.

+1. Having two versions installed is becoming useless.

They want to release the A8 next week, too. It's only sensible to postpone the patch to next week, instead of Friday.

I don't bother much with the usual updates, but 2.5.5 is the VR improvement patch and we have been waiting for this forever!

...agree and feel the same...have mentioned it but was called "obsessed" etc by some "pleasant" chaps around here !

Which is the purpose of the stable branch then ? The update could have been released yesterday without that third party module, and include it the next week update.

That is what the stable is for. Release the beta update at the scheduled time and anyone not finished with their project must wait! Ppl affected by the missing unit should reside to stable.

Lets also have alpha than !

Could be, but they'd still have the option of playing on stable branch servers.

This is very true. For some reason I keep ignoring the fact we have 2 versions out there. Each with it's own purpose. With times like these, unless I am missing something, is good for this particular purpose. Test for the unknown with knowing there are some things still in WIP. If the OB was to come incomplete I could accept the disabled module. Another week wont bother me either. I have a working F-18 that I am still enjoying! :)

And what of the user whose only module is that 3rd party a/c and has only the HD space to hold a single copy of DCS?

There is a huge amount of online the community that uses exclusively the Beta; are they supposed to re-edit all their missions to remove the affected aircraft? How are they supposed to know which one it is? How many hours would it take?

And what of the user whose only module is that 3rd party a/c and has only the HD space to hold a single copy of DCS?

 

There is a huge amount of online the community that uses exclusively the Beta; are they supposed to re-edit all their missions to remove the affected aircraft? How are they supposed to know which one it is? How many hours would it take?

Well, where's the problem exactly? It's called Open Beta for a reason, they don't have to update if the mentioned limitations of the latest Open Beta update would influence the missions they're running.

There's still a choice to be had here and nobody loses anything, let's not create a problem where there's none present.

So they don't deserve a VR FPS boost then? Or a slew of other due fixes?

The point is moot. ED is not releasing the patch until the 3rd Party has completed their works to enable integration of their module.

Nobody 'deserves' anything in a Beta.

It's for the Developers 'Beta' Tests.

The Devs should do what they want. Period.

Sent from my Moto Z Play using Tapatalk