Will there be a 1.1.2 ?

[NateDaBeast]

1 minute ago, Claw said:

 

This hits the nail on the head pretty squarely. VPP assumes a lot of things, such as 1g. That fact results in things like landers that like to slide uphill on the Mun. PhysX has some intentional limitations. And Unity makes a lot of assumptions as well (that match up with changes to PhysX).

One thing right off the bat is that the new Unity/PhysX wheel system is actually a step in in terms of individual behavior. The problem is that it assumes a lot of things and isn't particularly flexible "on the fly." VPP adds a lot of functionality, but is also predicated on "make car X, tune car X, live with car X for ever." KSP isn't built that way, so it's rather difficult to get an "across the board" balance, because of how everything interacts.

Add to that the other issues that have been discovered within Unity, and it becomes a complex web to untangle and work around. 

 

We've been aggressively attacking memory leaks and working to speed up code everywhere. Unfortunately, we have zero control over how mod makers build their code. So bear in mind that add-ons are also capable of leaking and creating garbage as well.

Yea I know that tends to happen with other mods, but it's even when you run vanilla when its ridiculous for the memory usage.

[moogoob]

All the problems I've had  (constant CTD) from 1.1/1.1.1/1.1.2 turned out to be from mods. Now running nothing but Mechjeb and KSP's been as sturdy as a rock.

[NateDaBeast]

2 minutes ago, moogoob said:

All the problems I've had  (constant CTD) from 1.1/1.1.1/1.1.2 turned out to be from mods. Now running nothing but Mechjeb and KSP's been as sturdy as a rock.

Not getting crashes anymore but still freezing up sometimes as of 1.1.1 

I will be testing 1.1.2 in a bit.

[Claw]

On 4/29/2016 at 5:50 PM, Alshain said:

According to one of the Squad employees, bug reports on the forums pretty much get ignored.

That's not entirely accurate, or perhaps it's a miscommunication.

During the pre-release, bug reports on the forum were expressly discouraged. It was simply too much to keep up with bug reports on the forum and in the tracker. However, day to day, but reports in the support forum do get looked at, though not always commented on. In 1.0.5, we pulled in a lot of reports off the forums. But since the forum isn't really well suited for documenting, tracking, prioritizing bugs, and managing bugs, the usage of such isn't particularly obvious.

Bugs in the tracker aren't exactly ignored either. If we are working on a bug, the report will often get copied into another section of the bug tracker which corresponds to the current state of the development pipe. So if we're working in QA, the bug report gets copied to QA...etc.

[Alshain]

22 hours ago, Claw said:

That's not entirely accurate, or perhaps it's a miscommunication.

During the pre-release, bug reports on the forum were expressly discouraged. It was simply too much to keep up with bug reports on the forum and in the tracker. However, day to day, but reports in the support forum do get looked at, though not always commented on. In 1.0.5, we pulled in a lot of reports off the forums. But since the forum isn't really well suited for documenting, tracking, prioritizing bugs, and managing bugs, the usage of such isn't particularly obvious.

Bugs in the tracker aren't exactly ignored either. If we are working on a bug, the report will often get copied into another section of the bug tracker which corresponds to the current state of the development pipe. So if we're working in QA, the bug report gets copied to QA...etc.

Ok, well I don't want to name and shame, but one employee said bug reports in the support forum were nothing but an annoyance, and yes I paraphrased that earlier, maybe a little inaccurately.

Edited May 1, 2016 by Alshain