1.3.0 is comming or....?

[outlawal2]

I just had a mess in my pants.

 

Over what? The same news that has been stated at least 30 times previously? None of which gives a time frame?

 

???

[Buzzles]

Confused...

 

So 1.3.0 is next, great, but when?

 

Anytime between now and May 2015.

 

Reason for that timescale? Wags has put a rough estimate on the new Normandy map for DCS:WWII to be May 2015.

 

As ED have previously stated the ability to use multiple maps is an EDGE-related feature, it'll mean EDGE will probably be out by then :)

[Darkwolf]

Great, we will have Normandy for December 2015

[NRG-Vampire]

last week Sobek wrote that we will be surprised, however overleaping the 1.2.9 is not a surprise but i hope(d) we will get an update before 1.3.0/edge

 

new su-27 and focke skins at least, new moskva cruiser and su-24m 3d models (maybe with the new mig-29 model as well) :D

 

You'll be surprised, i promise.

Edited June 20, 2014 by NRG-Vampire

[Witchking]

I just can't finally wait to try EDGE. Hoping for a good performance boost. :p

[cichlidfan]

I've done a little bit of multi-thread (multi-core) programming. I've learned that it can be quite tricky to do right from a performance point of view. It can actually make things run a lot worse if not done carefully.

 

True I am sure, but since we have no reason to believe that EDGE will be, or make DCS into, a multi-threaded application...

[cichlidfan]

As ED have previously stated the ability to use multiple maps is an EDGE-related feature, it'll mean EDGE will probably be out by then :)

 

It made no sense when he said it. I have had OLD beta Nevada and the current map installed and working in DCS World.

[joey45]

Why skip. Have 1.2.9 as an intermitent update/beta for 1.3.0.

 

EDIT: or have 1.2.9 EDGE without Nevada and 1.3.0. with.....

Edited June 20, 2014 by joey45
see edit.

[NRG-Vampire]

I just can't finally wait to try EDGE. Hoping for a good performance boost. :p

 

unfortunately they converted the old f-16.cmd model (with 3700 tris) upto 11800 tris in 1.2.8 (i just realizeid it in 1.2.8.) while the edm model itself completely the same as the cmd model, nothing new or detailed parts, only performace lost...you can check in the modelviewer, and image that with all the old models which are used in the sim :( (all the conversion went wrong by ed) if i convert the cmd model then my converted f-16.edm will be 3800 tris only

so if they redo all the conversion then it's sure we will get a performance kickup

 

edited: i just checked the old f-16.edm model in all version since edm format came out (warthog beta): all wrong, and got 12000 tris approx. while my latest edm conversion brought the original 3700 tris which is same as if you open the f-16.cmd :doh: so maybe these awfully converted models cause the huge fps/performance dive

Edited June 20, 2014 by NRG-Vampire

[Demongornot]

Why skip. Have 1.2.9 as an intermitent update/beta for 1.3.0.

 

EDIT: or have 1.2.9 EDGE without Nevada and 1.3.0. with.....

 

 

I think it is cause it was probably initially expected to release something like F-15C with AFM for 1.2.8 and probably some new stuff for 1.2.9 just before Edge, like the SU-27 with AFM, or any third party aircraft such as F86 Sabre/Mig21 or their own FW190, but they have maybe reconsider it and think about release a lot of things at once, not really good idea for them cause rather than slowly fix bug during a period of two updates, they will have a bench to fix at once, but from customer point of view it can be a good new and it can be a huge auto marketing attractive solution.

 

But Edge its up to a new version, so they can't call it 1.2.9 for a lot of reason, Look at X Rebirth (ok this game is a shame) for they new (big thing) they have call it 2.0, and a lot of others game do the same.

The EDGE technology can be released without Nevada cause Georgia apparently will benefit from it, but i'm sure that the Georgia terrain support will come after or only partially at first.

And the terrain itself is done since maybe a while now, importing the terrain itself is not a big deal, but importing new terrain rendering (graphic ?) engine is quite a huge thing to do.

 

So their is no real reason to release EDGE without Nevada, mainly cause Nevada terrain will really use the EDGE engine the way it have to work unless Georgia who will only take some part of the engine.

 

This is only a theory i can be wrong but i'm sure its something close to this.

 

I'm sure they want the release of EDGE to be great, and they will probably bombing us with features/aircraft/3D models and maybe lot of new/newletters for future project around EDGE, including third party and DCS F/A-18C !

So they will probably want to skip 1.2.9 also for this reason, give us a huge surprise with a lot of content that i can't even imagine, maybe a new FC aircraft or anything else like a huge list of new AI units for example.

 

And also i think it can be a good new that 1.2.9 is skip, not cause we will have EDGE sooner, but cause if they skip an update, it mean that they don't need much more time for working on EDGE, which mean that it will probably be less buggy than what we can expect from a new technology like this at this first release !

 

Also i don't think they will release a Beta variant, who will seriously wait until the final release before testing EDGE, and maybe the new updater have something to do with this and will permit to install the new 1.3.0 while keeping our 1.2.8 if for any reason we can't use the 1.3.0

 

But again it was only my theory...

 

But if they find the need to release a new patch before, or if they ran into issue that make them need more time to work on 1.3.0, then maybe 1.2.9 will be release, and they maybe already plan it as a safety patch.

[SkateZilla]

Anytime between now and May 2015.

 

Reason for that timescale? Wags has put a rough estimate on the new Normandy map for DCS:WWII to be May 2015.

 

As ED have previously stated the ability to use multiple maps is an EDGE-related feature, it'll mean EDGE will probably be out by then :)

 

I have more than one map without edge.

 

The issue is file structure....

 

The NTTR map is essentially done. We are now waiting for EDGE to be incorporated into DCS and set up the a new file structure that will be required to support multiple maps.

[*Rage*]

... When it's ready.

 

 

Seriously, you walked into this one. :P

 

Poor wording on my part. Ive been around long enough to realise thats its done when its done:) I meant whats the big deal what the update is called? It makes no difference if its 1.2.9 or 3 or 4.....only the content.

[cichlidfan]

I meant whats the big deal what the update is called? It makes no difference if its 1.2.9 or 3 or 4.....only the content.

 

:thumbup:

[NineLine]

Poor wording on my part. Ive been around long enough to realise thats its done when its done:) I meant whats the big deal what the update is called? It makes no difference if its 1.2.9 or 3 or 4.....only the content.

 

Apparently its important internally for ED, so no it doesnt really matter to us, but I am sure there is a reason for it internally. Perhaps it was 1.3.0 in case EDGE ran into major issues (because its a more involved update) they could release a 1.2.9 in the interem to address other issues... dunno

[Paganus]

In any sort of code conversion or merge you reach a tipping point where supporting the legacy while implementing the new becomes more work than just pushing forward with the converted.

 

I guess they reached that point. Expect the road to be a bit bumpy at first.

[GGTharos]

You're right. This is more about answering SD's question and explaining the reasons behind skipping the next 1.2.x iteration.

 

The reason for the version change itself is just software versioning convention.

 

Poor wording on my part. Ive been around long enough to realise thats its done when its done:) I meant whats the big deal what the update is called? It makes no difference if its 1.2.9 or 3 or 4.....only the content.

[cichlidfan]

Expect the road to be a bit bumpy at first.

 

Which is why I am looking forward to the patch that follows.

[NineLine]

Expect the road to be a bit bumpy at first.

 

Yup, I am sure it will, new IG, and now consider all the different combinations of systems and such out there... I am sure it will be a little bumpy. I hope they do an extensive open beta as well. But we will see how they handle it all.

[SkateZilla]

Oh... I Plan to put it through it's Paces...

1 GPU, 2 GPUs, 3 GPUS, 1 Screen, 3 Screens, 4 Screens, 5 Screens Mixed Eyefinity, 6 Screens....

 

... You wont see me for a week...

[Witchking]

unfortunately they converted the old f-16.cmd model (with 3700 tris) upto 11800 tris in 1.2.8 (i just realizeid it in 1.2.8.) while the edm model itself completely the same as the cmd model, nothing new or detailed parts, only performace lost...you can check in the modelviewer, and image that with all the old models which are used in the sim :( (all the conversion went wrong by ed) if i convert the cmd model then my converted f-16.edm will be 3800 tris only

so if they redo all the conversion then it's sure we will get a performance kickup

 

edited: i just checked the old f-16.edm model in all version since edm format came out (warthog beta): all wrong, and got 12000 tris approx. while my latest edm conversion brought the original 3700 tris which is same as if you open the f-16.cmd :doh: so maybe these awfully converted models cause the huge fps/performance dive

 

IIRC...I remember this back in the day when people noticed little ships in the harbours caused a performance loss due to inefficient conversion.. I don't know if they ever fixed it...but in that case...yes. Although...hopefully if edge can make proper use of gpu, I think triangle count shouldn't be a problem with most gpu nowadays.

[FSKRipper]

Sounds fantastic, I hope the 1.3 release will also adress the open beta bugs of the current version (logbook, scripting, Performance........) :music_whistling:

[*Rage*]

Oh... I Plan to put it through it's Paces...

1 GPU, 2 GPUs, 3 GPUS, 1 Screen, 3 Screens, 4 Screens, 5 Screens Mixed Eyefinity, 6 Screens....

 

... You wont see me for a week...

 

Look forward to your results! Particularly multi gpu scaling and vram usage.

[Witchking]

Remember folks... Since GG mentioned there is still work left to do, it might be a bit before we see release.

 

Although I agree that now is the best time to release it as beta to get a large test group so that they can begin fixing stuff. Expect a bunch of special fx missing and other stuff missing.

[GGTharos]

This is exactly why now is not the time :)

 

We'll catch most of the obvious stuff internally. The OB is for testing stability, mp and stuff that falls through the cracks or that we didn't run into.

 

Although I agree that now is the best time to release it as beta to get a large test group so that they can begin fixing stuff. Expect a bunch of special fx missing and other stuff missing.

[uboats]

So there would be a long time between 1.2.8 and 1.3.0 that many to-be-released modules can be tuned and polished based on 1.2.8 and no need to worry about the influence from update of 1.2.9