DCS 1.2.7 Open Beta - Preliminary Changelog

[fjacobsen]

Hmmm...

 

Since the annoucement of the preliminary changelog for 1.2.7 BETA 36 pages of posts has been made before someone questioned how this would work out.

When I asked too about it I got an answer that made me look a bit stupid, cause it seemingly was very clear how this would work out.

But not until I asked about how this would work did anyone start to ask into it.

 

So honestly it seems that I´m not the only one missing the nature of this update.

No problem for me though - I guess I will try it, but maybe it should have been expelained more clearly from th outset.

 

Fjacobsen

[Nate--IRL--]

Open Beta for 1.2.7 was only announced a few hours ago - it wasn't in the initial announcement :)

 

Nate

[HiJack]

I'm sorry but I don't understand this last change to go for a beta of 1.2.7? Exactly why do we have the auto updater? Isn't that to be used for small fixes after release? And isn’t there a perfectly good way to force the updater to run the previous version for those that can't stand the bugs in the new version? Not complaining but a bit puzzled ;)

[Nate--IRL--]

In order to participate in the Open Beta you must use the Open Beta Updater/installer, it will NOT touch your current 1.2.6 install. This is deliberate. The Open Beta is for Testing Purposes for those that are inclined to help.

 

Nate

[fjacobsen]

Maybe an autoupdater with a "Beta" checkbox.

 

Checking this means that also beta updates are installed, wheras unchecked only the lat official update will be installed.

 

That way users can dertermine whether they want to run betas (at their own risc) or not.

 

Fjacobsen

[HiJack]

In order to participate in the Open Beta you must use the Open Beta Updater/installer, it will NOT touch your current 1.2.6 install. This is deliberate. The Open Beta is for Testing Purposes for those that are inclined to help.

 

Nate

OK so this will then be a full new install and not an "update" that takes all current settings in to account? So when the release come and uses the current settings we will have new problems anyway? Or can we make a new DCS folder in saved games by copying our settings first? Like "Saved Games\DCStest\" ?

[cichlidfan]

Maybe an autoupdater with a "Beta" checkbox.

 

Checking this means that also beta updates are installed, wheras unchecked only the lat official update will be installed.

 

That way users can dertermine whether they want to run betas (at their own risc) or not.

 

Fjacobsen

 

How about if they have a download link that you go to if you want the beta? No new autoupdater code required.

[Nate--IRL--]

OK so this will then be a full new install and not an "update" that takes all current settings in to account? So when the release come and uses the current settings we will have new problems anyway? Or can we make a new DCS folder in saved games by copying our settings first? Like "Saved Games\DCStest\" ?

 

Might be better that you start with a new "Clean" config, from a testing perpective. But you can copy settings from 1.2.6.

 

Nate

[Nate--IRL--]

Maybe an autoupdater with a "Beta" checkbox.

 

Checking this means that also beta updates are installed, wheras unchecked only the lat official update will be installed.

 

That way users can dertermine whether they want to run betas (at their own risc) or not.

 

Fjacobsen

 

Does steam use the auto updater? I forget. Might be why it is done the way it is done.

 

Nate

[danilop]

...This is an optional beta' date=' and if you do not wish to take part, you certainly do not have to ...[/quote']

 

Fair enough. Waiting for 1.2.7 final then.

[cichlidfan]

I am all for this. The possibility for more exhaustive testing before release should make for a much better release.

[Mustang]

I am all for this. The possibility for more exhaustive testing before release should make for a much better release.

 

Agreed, and to truly replicate any MP crashes we need the high player count, going open beta can only help :)

[NRG-Vampire]

 

Adjusted valid stores for F-15E:

Added AGM-65G – Station 2 & 18.

Added AGM-65G – Station 2 & 18.

GBU-31(V)3/B – Stations 2, 7, 9, 10, 11, 13, 18 only.

GBU-31(V)1/B - Stations 2, 7, 9, 10, 11, 13, 18 only.

MK-84 - Stations 2, 7, 9, 10, 11, 13, 18 only.

GBU-10 - Stations 2, 7, 9, 10, 11, 13, 18 only.

GBU-27 - Stations 2, 7, 9, 10, 11, 13, 18 only.

Removed AIM-120 from stations 7, 9, 11, 13 (can only be carried on MELs where CFTs are removed).

Removed AIM-7 from stations 7, 9, 11, 13 (can only be carried on MELs where CFTs are removed).

 

i dont understand the removed sparrow and amraam changes :dunno:

those are real/valid loadout for the mudhen

http://www.f-15e.info/joomla/en/weapons/weapons-stores/121-ejector-launcher

 

Edited December 15, 2013 by NRG-Vampire

[HiJack]

Might be better that you start with a new "Clean" config, from a testing perpective. But you can copy settings from 1.2.6.

 

Nate

OK, made space and done backups so I'm ready for a new version on the SSD :)

[SyntaxError]

Am I understanding the Open Beta story correctly in that you have to download a completely separate installer from DCS.com? Is there no way to have it done through the updater or a v1.2.7.exe patch installer so you don't have to download the 6GB+ and install the full game again?

[Flagrum]

When ECM now becomes a viable tactic against SAM with 1.2.7 and since we will be able to equip the ALQ-184 and the ALQ-131 - what are the differences between both pods? Or rather, what different capabilities could we expect in-game?

[hypersonik]

i dont understand the removed sparrow and amraam changes :dunno:

those are real/valid loadout for the mudhen

 

^

this

[Lt.Seahawk]

Am I understanding the Open Beta story correctly in that you have to download a completely separate installer from DCS.com? Is there no way to have it done through the updater or a v1.2.7.exe patch installer so you don't have to download the 6GB+ and install the full game again?

 

 

If thats the fact, most of the people will possibly wait until it can be updated with the auto updater, since not everyone has a 100mbit+ Internet connection.

 

(To be honest, a open beta only makes sense when everybody can be part of it, so I hope, as you do probably, that there will be a chance to update it "ingame".)

[ФрогФут]

When ECM now becomes a viable tactic against SAM with 1.2.7 and since we will be able to equip the ALQ-184 and the ALQ-131 - what are the differences between both pods? Or rather, what different capabilities could we expect in-game?

ALQ-184 is 100 kg lighter and has less drag.

[Flagrum]

ALQ-184 is 100 kg lighter and has less drag.

Thanks. That already is quite nice.

 

I just also found this where some of the differences of the real thing(s) are discussed: http://www.f-16.net/forum/viewtopic.php?p=157668

 

Leaves the question if differences in their effectiveness against threads are modelled in DCS (I doubt it but I am totally okay with that ... at this point in time :o).

[Rotorhead]

This change to open beta actually makes great sense to me. Actually, all previous DCS versions were betas IMO - at least judging by the number of bugs and WIP features contained in each of them. Honestly, I was always clicking the update button with uneasy feeling "what will it break this time".

 

And the worst part, you couldn't opt-out of the beta in any way, except not updating from the previous version - which in turn meant you're stuck with that version bugs, which were fixed in the newer one.

 

This way, ED will have greater chance of ironing-out the bugs in the "real" beta, and then releasing more stable and bug-free versions. Something we all wanted all the time I think.

 

And what's the best news, you can try out all the new features in the beta version (which may also mean more frequent releases), but still have the possibility to come back to stable, hopefully bug-free version at any time shall something go wrong. So hopefully, no more "today's update made my DCSW unplayable" type of rants.

 

Having both versions installed at the same time is great IMO, but I agree there should be Steam-like updater which allow you to change your stable version to beta and vice-versa if you prefer it that way.

[Haukka81]

i dont understand the removed sparrow and amraam changes :dunno:

those are real/valid loadout for the mudhen

http://www.f-15e.info/joomla/en/weapons/weapons-stores/121-ejector-launcher

 

 

 

+100

 

For this.

 

Why they remove those? , they are used RL in those stations.

[Azrayen]

Am I understanding the Open Beta story correctly in that you have to download a completely separate installer from DCS.com? Is there no way to have it done through the updater or a v1.2.7.exe patch installer so you don't have to download the 6GB+ and install the full game again?

 

Hi,

 

What you ask is technically doable (in general, I'm not involved in DCS dev or testing) but involves a significant risk: if you've messed with your 1.2.6 files, you may encounter bugs that are not "part of" 1.2.7, and declare bugs that devs won't be able to reproduce, understand, and fix.

In addition, developers should invest time to create the necessary functionality (which also should be tested to ensure that it does not have bugs ...), thus "wasting" time.

 

Yes, the open-bêta as built by ED induces the need to do a full download "again". If you're not willing to do this (due to personal Internet line low speed, for example), then you have to remember there is no obligation to participate to the open-bêta stage.

Eventually, the 1.2.7 (finale) will be available through the usual "auto-updater" channel.

 

Cheers,

Az'

[ENO]

Not sure I understand the issue.

 

1) Install 1.2.7 understanding that it's separate and an option to install. Like 1.1.1.1 versus 1.2.X

2) Don't install 1.2.7 and wait for the rest of us to help sort out the problems.

 

Separate.

 

Means.

 

Separate.

 

Why, what where when how and who?

 

Separate, folks. Good grief- capture it.

 

Climb on or don't- but for the love of whoever you believe in if you don't jump on then don't you DARE complain about what doesn't get fixed.

[HiJack]

No I’m sorry, I just don’t see the gain in having a separate install of DCS World but I will participate. Does this “beta” 1.2.7 mean that the normal “testers” have found weaknesses in the 1.2.7 build? Or can’t provoke the network bugs? Or is the build of 1.2.7 not working in an update at all? If it doesn’t work at all ED should go for a new build and let the “testers” test using the normal auto updater. I see massive problems for ED support on this decision, support tickets on two different versions? So first question on any reported bug would be “what version are you running of DCS World?”. And I guess the next question would be “what module version do you have?”. No I’m sorry folks I think this will be a nightmare for ED support and for the BUG reporting forums.