I don't think anyone is trying to troll you, to be honest. They are just giving their take on things... and as a public forum, that is their right.
All that said...
By "before release", it was the in the final stretches. Everything more or less checked out - but performance in SS was just not close to where it needed to be. Again, PW is doing the development, 505 is the publisher (updating the stores, etc) - so wires crossed would be my best guess. I wasn't physically standing in the room or on the call/etc, so I have no idea directly. I'll flag the Amazon thing to them, best I can do.
As for "quick" fix - it is as Proto was saying, I would assume. I say assume because I am not a coder, don't code any of it, and likely would have no idea what things meant if I were told. Pragmatically speaking (as I understand it), optimizing/performance is the most squirrely beast in this area - again because it is not tied to a "specific error". Rather it is a function of things not being efficient enough... or some process conflicting with another for resources, etc. As such, it requires a ton of experimentation.... larger rewrites.... back and forth to see if X change yields Y improvements (or makes things worse/the same). Perhaps PW thought they had a better line on places to look/work that would bear fruit than they did? Again, I am not sitting there directly - all I can go on are the builds we get to see. Prelaunch was just not even close. 1.3.1 was leaps better, but still not there. I haven't had another build since.
It does ultimately tie back to Switch being a relatively underpowered piece of hardware (parallel example, watching my kids SS vs Ender Dragon put Powerpoint to shame) - but regardless, it needs to get done, and I am confident it will get there (based on the progress thus far). I wish I could give you more direct technical details, but again, not a coder... and it isn't even coded under our roof as a team. Nor do we directly manage any parts of it - more just in an advisory role.
That said - to reiterate - SS is top-of-pile for us in regards to Switch development... and PW/505 know this.
All that said...
So when you guys got your hands on it obviously was before release. I still don't understand. How was it assumed it would be a quick fix if it was so bad?
By "before release", it was the in the final stretches. Everything more or less checked out - but performance in SS was just not close to where it needed to be. Again, PW is doing the development, 505 is the publisher (updating the stores, etc) - so wires crossed would be my best guess. I wasn't physically standing in the room or on the call/etc, so I have no idea directly. I'll flag the Amazon thing to them, best I can do.
As for "quick" fix - it is as Proto was saying, I would assume. I say assume because I am not a coder, don't code any of it, and likely would have no idea what things meant if I were told. Pragmatically speaking (as I understand it), optimizing/performance is the most squirrely beast in this area - again because it is not tied to a "specific error". Rather it is a function of things not being efficient enough... or some process conflicting with another for resources, etc. As such, it requires a ton of experimentation.... larger rewrites.... back and forth to see if X change yields Y improvements (or makes things worse/the same). Perhaps PW thought they had a better line on places to look/work that would bear fruit than they did? Again, I am not sitting there directly - all I can go on are the builds we get to see. Prelaunch was just not even close. 1.3.1 was leaps better, but still not there. I haven't had another build since.
It does ultimately tie back to Switch being a relatively underpowered piece of hardware (parallel example, watching my kids SS vs Ender Dragon put Powerpoint to shame) - but regardless, it needs to get done, and I am confident it will get there (based on the progress thus far). I wish I could give you more direct technical details, but again, not a coder... and it isn't even coded under our roof as a team. Nor do we directly manage any parts of it - more just in an advisory role.
That said - to reiterate - SS is top-of-pile for us in regards to Switch development... and PW/505 know this.