1.5.2 Stable Branch discussion

Gliptal · December 29, 2015

Maybe it's just me. ED just pushed 1.5.2 to the stable branch, meaning 1.2.16 isn't a thing anymore (unless you purposedly not update). Now, I would really like to update but the way ED is handling this whole open Alpha and open Beta situation is quite disappointing.

Currently, in 1.5.2, we have:

- A broken TGP simulation casued by the new terrain textures. Funnily enough, this was flagged as a "wishlist item" and not as a "bug" by ED, even though on 1.2.16 it's just fine.

- Flood lights are still broken on 1.5.2, but fixed on 2.0. I find this appalling, why is such a blatant bug fixed on a 50€ paywall version (that I have purchased) and not on the main branch is beyond me.

- A number of bugs seem to be still present, some of which pretty important (e.g. illumination flares not working, NMSP lights missing). Whether they have been squished or not can't be known unless I test it personally, because the bugs portion of the forums lacks any feedback from ED whatsoever. If I test it personally though, I loose the possibility of going back.

Now I don't expect a 100% bug free experience, but if a decision to jump to stable branch is made the obvious, blatant bugs should not be there. This is a real shame, since The Enemy Within campaign is for example only available on 1.5.2, and performance is much better as well.

I hope I'm wrong and these aren't issues anymore, and I'm just out of the loop for some reason. ED have always looked like a great developer up until now, but with this piece of news I'm really not looking forward to fly the A-10C in 1.5.

CHSubZero · December 29, 2015

I think they done it so that they don't have to maintain 3 different branches and can focus on 2 branches instead... I expect 1 or 2 minor patches to 1.5.2 or even a 1.5.3 patch in the first weeks after the russian christmas (approx middle to end of january)

Mowgli · December 29, 2015

Currently I have 1.5.2 open beta installed with all my modules - is there a way to patch it or convert it to the new stable branch or do I have to install it all again?

mig29movt · December 29, 2015

If the stable version detects your modules installed in the 1.5.2 beta, they will be just copied and not downloaded

c0ff · December 29, 2015

Currently I have 1.5.2 open beta installed with all my modules - is there a way to patch it or convert it to the new stable branch or do I have to install it all again?

To convert your OpenBeta to release, do

bin\DCS_updater.exe update @release

The menu entries will still say OpenBeta though.

So take this as a warning that you may end up with a version which says OpenBeta

in the folder name and the menu shortcuts, while being, in fact, on the 'release' channel of the updater.

Actually, better NOT do this.

A MUCH better solution:

Just install the release, it will pick up the files from the openbeta, and delete openbeta after that.

Edited December 29, 2015 by c0ff

Nac33 · December 29, 2015

after 1.2 is updated to stable 1.5 release, can we then get rid of open beta 1.5? or should we hang on to it a while longer?

Edited December 29, 2015 by Nac33

dburne · December 30, 2015

after 1.2 is updated to stable 1.5 release, can we then get rid of open beta 1.5? or should we hang on to it a while longer?

If you want to continue to participate in further Open Beta builds, hang on to it. If you rather wait for a release update, then I would think you could safely uninstall it.

Yurgon · December 30, 2015

- Flood lights are still broken on 1.5.2, but fixed on 2.0.

Do you mean the green floodlight that can be activated by the Emergency Floodlight Switch on the Electrical Panel and the Flood Light Dial on the Lighting Control Panel?

AFAIK, this was fixed in an earlier version of 1.5 and it is also fixed in the new 1.5.2 Public Release.

Hint: Don't forget to close the canopy... :smartass:

Gliptal · December 30, 2015

Do you mean the green floodlight that can be activated by the Emergency Floodlight Switch on the Electrical Panel and the Flood Light Dial on the Lighting Control Panel?

AFAIK, this was fixed in an earlier version of 1.5 and it is also fixed in the new 1.5.2 Public Release.

Hint: Don't forget to close the canopy... :smartass:

Nice. I looked at the changelogs and it isn't mentioned anywhere, apart from 2.0.

Flagrum · December 30, 2015

- A broken TGP simulation casued by the new terrain textures. Funnily enough, this was flagged as a "wishlist item" and not as a "bug" by ED, even though on 1.2.16 it's just fine.

FLIR issues are being investigated for the older map, thats all I can say right now, and honestly dont remember if I already stated that, but there it is again if I did

.

Beagle One · December 30, 2015

The Mirage 2000C shows up as a Su-27 runnign on one engine with assimetric load of french missiles under the wings if you don't own the module.

This should not happen in a stable release aimed for introducing the Mirage.

Flagrum · December 30, 2015

The Mirage 2000C shows up as a Su-27 runnign on one engine with assimetric load of french missiles under the wings if you don't own the module.

This should not happen in a stable release aimed for introducing the Mirage.

Well, DCS 1.5 is not aimed to just introduce the M2KC .....

Gliptal · December 30, 2015

.

Thanks.

lucky-hendrix · December 30, 2015

Launching the updater doesn't update my 1.2.6 to 1.5.2, it just launches DCS 1.2.6. How can i fix this ?

JANGO70 · December 30, 2015

Launching the updater doesn't update my 1.2.6 to 1.5.2, it just launches DCS 1.2.6. How can i fix this ?

Me too

I7 3770k, 8GB RAM 1866, GTX 770 OC 2GB,

NineLine · December 30, 2015

Maybe it's just me. ED just pushed 1.5.2 to the stable branch, meaning 1.2.16 isn't a thing anymore (unless you purposedly not update). Now, I would really like to update but the way ED is handling this whole open Alpha and open Beta situation is quite disappointing.

Currently, in 1.5.2, we have:

- A broken TGP simulation casued by the new terrain textures. Funnily enough, this was flagged as a "wishlist item" and not as a "bug" by ED, even though on 1.2.16 it's just fine.

They are trying to keep the map viable even though newer maps are coming, they are still tuning and tweaking the textures, its on going, but not really something that has to hold up moving 1.5 to release, the goal is getting 2.0 to release, the old map is just that, old.

- Flood lights are still broken on 1.5.2, but fixed on 2.0. I find this appalling, why is such a blatant bug fixed on a 50€ paywall version (that I have purchased) and not on the main branch is beyond me.

Well the point is to get to 2.0, a number of things might be fixed in 2.0, its a newer version in some cases fixes are in it that might not be able to be put in older versions, its just the crossroads we are at.

- A number of bugs seem to be still present, some of which pretty important (e.g. illumination flares not working, NMSP lights missing). Whether they have been squished or not can't be known unless I test it personally, because the bugs portion of the forums lacks any feedback from ED whatsoever. If I test it personally though, I loose the possibility of going back.

Now I don't expect a 100% bug free experience, but if a decision to jump to stable branch is made the obvious, blatant bugs should not be there. This is a real shame, since The Enemy Within campaign is for example only available on 1.5.2, and performance is much better as well.

I hope I'm wrong and these aren't issues anymore, and I'm just out of the loop for some reason. ED have always looked like a great developer up until now, but with this piece of news I'm really not looking forward to fly the A-10C in 1.5.

Bug fixes are always on going, you have to weigh their importance and whether they can be fixed in the current version, and if not, if its not better to push forward to get to a version they can or are fixed in. As I said, this is a crossroads for ED, a major one... but there are going to be a few speed bumps along the way.

nervousenergy · December 30, 2015

I didn't think the Mirage 2K was even available in 1.5... I've updated my beta 1.5 (witch was updated from release 1.2 when the 1.5 beta started) to release 1.52, but have no interest in actually launching it. Screaming down the strip in the Mirage is just too much fun.

Any news on progress with the unified 2.0?

Gliptal · December 30, 2015

They are trying to keep the map viable even though newer maps are coming, they are still tuning and tweaking the textures, its on going, but not really something that has to hold up moving 1.5 to release, the goal is getting 2.0 to release, the old map is just that, old.

I understand it's the "old" map, but it's still the only map not behind a paywall, and the one where most of the content is. NTTR is awesome and has enormous potential (I bought it myself), but my feeling is that pushing a stable branch in this state is not that great of a move.

Well the point is to get to 2.0, a number of things might be fixed in 2.0, its a newer version in some cases fixes are in it that might not be able to be put in older versions, its just the crossroads we are at.

This makes sense if these fixes are about new feautures in 2.0, but things that are working fine in 1.2.16 and stopped working in 1.5 should be fixed in 1.5. I don't see how we are expected to wait for everything to be ported in 2.0, a process that is probably going to take at least another couple of months (wild guess).

Bug fixes are always on going, you have to weigh their importance and whether they can be fixed in the current version, and if not, if its not better to push forward to get to a version they can or are fixed in. As I said, this is a crossroads for ED, a major one... but there are going to be a few speed bumps along the way.

Sure, and that's why Betas and Alphas exist. My personal opinion is that 1.5 should have been kept as Beta, to leave a solid working basis in 1.2.16. As it is now, if I were to update (and I don't think I will) I'd end up in a release that has more problems than the previous. Better performance, more feautures, but more problems still.

Don't get me wrong, I fully understand your point of view, I just find the situation we are forced in now is objectively worse than what we had a week ago. We're going from stable, mostly bug-free 1.2.16, a few "minor" bugs in 1.5.2, and NTTR in 2.0. Now we only have those few "minor" bugs in 1.5.2, and NTTR in 2.0. Less choice is never a good thing IMHO.

Edited December 30, 2015 by Gliptal

NineLine · December 30, 2015

We need to get to 2.0 and push on from there, things might break, its a huge change, so we are going to have to just tough it out, ED is doing their best to make things seemless, but its tough when they are supporting so many versions, honestly it would be best to just push to 2.0 and let ED focus on that version, keeping 1.2.16 and 1.5.2 and then trying to move forward with 2.0 is probably a lot of headaches, not to mention 3rd parties and ED themselves wanting to release new content...

It just calls for patience... the benefits out weight the problems, might not seem like it now, but it really is the case.

tintifaxl · December 30, 2015

To convert your OpenBeta to release, do
bin\DCS_updater.exe update @release
The menu entries will still say OpenBeta though.
So take this as a warning that you may end up with a version which says OpenBeta
in the folder name and the menu shortcuts, while being, in fact, on the 'release' channel of the updater.

Actually, better NOT do this.

A MUCH better solution:
Just install the release, it will pick up the files from the openbeta, and delete openbeta after that.

I tried this and it doesn't work. It says the installed version is the latest and doesn't switch the branch to release.

--- Log file: C:\Users\CHRIST~1\AppData\Local\Temp\DCS.openbeta\autoupdate_templog.txt
=== Log opened UTC 2015-12-30 18:41:46
INFO : DCS_Updater/2.6.12.52 (Windows NT 6.2.9200; Win64; de-AT)
INFO : cmdline: DCS_updater.exe  update @release
STATUS: Initializing...
INFO : basedir: C:\Games\DCS World\
INFO : dcs_variant.txt: openbeta
INFO : DCS/1.5.2.48726.137 (x86_64; EN;  WORLD,A-10C,F-86F,FC3,MIG-21BIS,SU27-ULTIMATE_campaign,UH-1H,UH-1H_video_EN,BALTICDRAGON_A10C-ENEMY_WITHIN_campaign)
INFO : branch: openbeta
STATUS: Checking for updates...
INFO : Got reply from www.digitalcombatsimulator.com
INFO : Got reply from srv5.update.digitalcombatsimulator.com
STATUS: The installed version 1.5.2.48726.137 is up to date.
=== Log closed.

=== Log opened UTC 2015-12-30 18:42:14
INFO : DCS_Updater/2.6.12.52 (Windows NT 6.2.9200; Win64; de-AT)
INFO : cmdline: DCS_updater.exe  update @release
STATUS: Initializing...
INFO : basedir: C:\Games\DCS World\
INFO : dcs_variant.txt: openbeta
INFO : DCS/1.5.2.48726.137 (x86_64; EN;  WORLD,A-10C,F-86F,FC3,MIG-21BIS,SU27-ULTIMATE_campaign,UH-1H,UH-1H_video_EN,BALTICDRAGON_A10C-ENEMY_WITHIN_campaign)
INFO : branch: openbeta
STATUS: Checking for updates...
INFO : Got reply from www.digitalcombatsimulator.com
INFO : Got reply from srv5.update.digitalcombatsimulator.com
STATUS: The installed version 1.5.2.48726.137 is up to date.
=== Log closed.

JANGO70 · December 30, 2015

Launching the updater doesn't update my 1.2.6 to 1.5.2, it just launches DCS 1.2.6. How can i fix this ?

Solved for me...just clean all files on you dir: C:\users\yourname\appdata\local\temp

It works fine for me

I7 3770k, 8GB RAM 1866, GTX 770 OC 2GB,

NineLine · December 30, 2015

Solved for me...just clean all files on you dir: C:\users\yourname\appdata\local\temp
It works fine for me

I7 3770k, 8GB RAM 1866, GTX 770 OC 2GB,

Launching the update shortcut would do this as well. The updater only checks once every 24 hours, so you would need to 'force' it in this case.

JANGO70 · December 30, 2015

Launching the update shortcut would do this as well. The updater only checks once every 24 hours, so you would need to 'force' it in this case.

Not for my, i tried several times, restarting the computer and all times it only launch the game, doesnt update until clean those files

I7 3770k, 8GB RAM 1866, GTX 770 OC 2GB,

NineLine · December 30, 2015

Not for my, i tried several times, restarting the computer and all times it only launch the game, doesnt update until clean those files

I7 3770k, 8GB RAM 1866, GTX 770 OC 2GB,

Strange, I can force an updated by changing my shortcut target to this:

"C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe" update

That works as well, just need to remember to remove the 'update' at the end when you want to run the sim.

Sign In

1.5.2 Stable Branch discussion

Recommended Posts

Gliptal

CHSubZero

Mowgli

mig29movt

c0ff

Nac33

dburne

Yurgon

Gliptal

Flagrum

Beagle One

Flagrum

Gliptal

lucky-hendrix

JANGO70

NineLine

nervousenergy

Gliptal

NineLine

tintifaxl

JANGO70

NineLine

JANGO70

NineLine

Recently Browsing 0 members