STATEMENT ON RELEASE

[upupandaway]

After reading the post, I caught myself reading way too much into it... ;)

[Raven68]

After reading the post, I caught myself reading way too much into it... ;)

 

I may have also. I'm sure there will be someone to come along later to pimp slap me. :)

[upupandaway]

Hehe, who are you calling a pimp? ;)

Edited July 4, 2014 by upupandaway

[Irregular programming]

It means we're branching off development and making sure the aircraft runs properly on 1.3.0.

Not sure how you managed to read that much into such a simple, short, post.

 

I just want you to know that I have extensive knowledge about several different kinds of software, and can beta test 1.3.0 for you to make sure that you find all the bugs. :thumbup:

[uboats]

if i remembered correctly mig21 release was based on 1.2.8

will this target be changed to 1.3.0？

 

* if 1.3.0 edge is not done or rdy， is it possible for ed to start migration of modules？ i hope the answer is NO

Edited July 4, 2014 by uboats

[NineLine]

Almost sounds like this was an ED call after all. Which pretty much says the "delay" is out of LS control. If I am wrong please accept my apologies. I said it before Cobra, in spite of the ongoing delays I really admire your courage addressing the community. :thumbup:

 

This is not the case.

[Raven68]

I may have also. I'm sure there will be someone to come along later to pimp slap me. :)

 

This is not the case.

 

[26-J39]

The pimp slap is exactly what it's gonna be like when the 1.3.0 storm hits! :megalol:

[Irregular programming]

if i remembered correctly mig21 release was based on 1.2.8

will this target be changed to 1.3.0？

 

* if 1.3.0 edge is not done or rdy， is it possible for ed to start migration of modules？ i hope the answer is NO

 

The module isn't based on any version of DCS world, it just have to work in EDGE as that is how DCS is gonna go forward.

[cichlidfan]

The module isn't based on any version of DCS world, it just have to work in EDGE as that is how DCS is gonna go forward.

 

I wonder if they have tested all of the existing aircraft and other models in EDGE yet.

[NineLine]

I wonder if they have tested all of the existing aircraft and other models in EDGE yet.

 

It has little to do with EDGE, 1.3.0 is the current test bed that they have to qualify their module for, just happens to be the same version as EDGE, this isnt to say that once they get it working in 1.3.0 it couldnt be released in 1.2.8 for example.

[cichlidfan]

It has little to do with EDGE, 1.3.0 is the current test bed that they have to qualify their module for, just happens to be the same version as EDGE, this isnt to say that once they get it working in 1.3.0 it couldnt be released in 1.2.8 for example.

 

I take that to mean the 1.2.8 testing is done and no longer relevant.

[NineLine]

I take that to mean the 1.2.8 testing is done and no longer relevant.

 

I never said that, I dont know if there is plans to release anymore patches for 1.2.8, not for me to say.

[Jeesus]

It has little to do with EDGE, 1.3.0 is the current test bed that they have to qualify their module for, just happens to be the same version as EDGE, this isnt to say that once they get it working in 1.3.0 it couldnt be released in 1.2.8 for example.

 

:huh:

 

What you say is true , but I think it is not going to happen, why on earth they would hold it back from release to an existing build if they don't want to release it together with with the new version, sounds illogical IMHO. To me that means MIG-21BIS comes together with 1.3.0 version. And I am happy about it :D

[cichlidfan]

I never said that, I dont know if there is plans to release anymore patches for 1.2.8, not for me to say.

 

I was referring to the testing of the Mig with 1.2.8 being irrelevant.

[uboats]

The module isn't based on any version of DCS world, it just have to work in EDGE as that is how DCS is gonna go forward.

I cannt completely agree. if the infrastructure of dcs has been changed, module could be modified accordingly. so it's dcs version related

 

moreover, you didnt quite catch what i said. maybe you didn't know the prev mig21 release target LN posted months ago. you can go back and take a look. and if the edge's not well integrated into dcs (dcs alpha or even internal beta stage), i dont think they should start to test the migration of modules.

Edited July 4, 2014 by uboats

[NineLine]

I was referring to the testing of the Mig with 1.2.8 being irrelevant.

 

More than likely... I am sure LN are working in 1.3.0, but I dont know how the 3rd Party stuff works to be honest. But that would be my guess. SO yes, 1.2.8 would be irrelevant, but I am not sure that means the MiG has to wait for 1.3.0... but this is all new ground, so my chitter chat is all assumptions.

[Serp Supreme]

So what sort of stuff is required to integrate into 1.3.0? And how much work do these things take?

[NineLine]

So what sort of stuff is required to integrate into 1.3.0? And how much work do these things take?

 

No clue really, but I imagine that everything has to work correctly to ED standards... or something along those lines... I am sure most of that is covered by a NDA.

[Cobra847]

To clarify:

 

1) Core engine architecture changes obviously sometimes mean that things need to change in the aircrafts' implementation.

Depending on what these changes are, this can either be time consuming or not.

 

2) We don't know on which version we will ship yet.

We're branching off development and actively working with 1.3.0 -- but that probably does not mean a release on 1.2.8 (or a subpatch thereof) is impossible.

 

3) Generally the work that has (had) to be done has been rather minimal. :)

 

So, in essence, don't read too much into the meta around my post; we've simply been "porting" the aircraft into the next build of DCS.

No more, no less, nothing special. :)

Edited July 4, 2014 by Cobra847

[uboats]

To clarify:

 

1) Core engine architecture changes obviously sometimes mean that things need to change in the aircrafts' implementation.

Depending on what these changes are, this can either be time consuming or not.

 

2) We don't know on which version we will ship yet.

We're branching off development and actively working with 1.3.0 -- but that probably does not mean a release on 1.2.8 (or a subpatch thereof) is impossible.

 

3) Generally the work that has (had) to be done has been rather minimal. :)

thanks for more info

wait for the video today

[Serp Supreme]

To clarify:

 

1) Core engine architecture changes obviously sometimes mean that things need to change in the aircrafts' implementation.

Depending on what these changes are, this can either be time consuming or not.

 

2) We don't know on which version we will ship yet.

We're branching off development and actively working with 1.3.0 -- but that probably does not mean a release on 1.2.8 (or a subpatch thereof) is impossible.

 

3) Generally the work that has (had) to be done has been rather minimal. :)

Wow, that was fast. Well many thanks for the information. And I'm sure you know, it would be totes coolio for a release on 1.2.8 ;) but I don't want to become THAT guy, so I'll just end my post here hehe :D

[Raven68]

To clarify:

 

1) Core engine architecture changes obviously sometimes mean that things need to change in the aircrafts' implementation.

Depending on what these changes are, this can either be time consuming or not.

 

2) We don't know on which version we will ship yet.

We're branching off development and actively working with 1.3.0 -- but that probably does not mean a release on 1.2.8 (or a subpatch thereof) is impossible.

 

3) Generally the work that has (had) to be done has been rather minimal. :)

 

This right here could stand in for a nice weekly update. ;) Thanks Cobra!

[rajdary]

And besides, I understand that a lot of the hype around here, can be annoying to the devs and others, but whats the alternative to hype? It would be no interest at all.

 

Interest and hype are what sell games. If people werent thrilled or excited about it, no one would buy it, and it would be a failure. I believe the Mig-21 is the most hyped aircraft as of right now. The forums for the other aircraft seem dead compared to whats happening here.

 

Id say that the MIG21 is a mixture of various feelings : Hype(those who want it, like me), frustration and eagerness (those who backed), etc....

 

For hype only, without any other feelings mixed, i would say the HAWK module is at least level to the MIG21 (if not more, in my particular case). :smartass:

Edited July 4, 2014 by rajdary

[Rabbit_]

To clarify:

 

1) Core engine architecture changes obviously sometimes mean that things need to change in the aircrafts' implementation.

Depending on what these changes are, this can either be time consuming or not.

 

2) We don't know on which version we will ship yet.

We're branching off development and actively working with 1.3.0 -- but that probably does not mean a release on 1.2.8 (or a subpatch thereof) is impossible.

 

3) Generally the work that has (had) to be done has been rather minimal. :)

 

So, in essence, don't read too much into the meta around my post; we've simply been "porting" the aircraft into the next build of DCS.

No more, no less, nothing special. :)

 

I'm a little confused on point 2. Isn't everything going to 1.3.0? I thought the 1.3.0 version will just overwrite 1.2.8 version and so we can forget about implementing Mig into 1.2.8. And if You are developing this module towards the version 1.3.0, the version 1.2.8 will be no more, by the time the Mig will be released. :smartass: I just don't know, why asking about having this working in 1.2.8.

I know it sounds confusing as well, but here is the summary:

Will 1.2.8 and 1.3.0 versions separate things or not? :)

Thank You. If it's already mentioned somewhere on the forum, sorry for that.