I won’t comment any more on this… @jamie and I have been asking whether there might be a way where we don’t annoy you by asking about the state of things, but still are kept more in the loop of what’s going on with fixes for our issues. Nothing else.
Not pitting anything against other people’s issues. Just couldn’t follow how - as I understood - 3D MVC fix was a priority some time ago and VC-1 got more important. But I already got now, why. This was merely an example of why I thought, some more info in whatever form might have helped avoid the confusion… Didn’t want to make a point about the two issues themselves here.
Thank you very much for that! I know, you won’t be able to go into this amount of detail for every update and step, but really appreciated this…
Just wanted to make one point: Might it be possible to avoid confusion and/or frustration on the users’ side by giving more updates on the current state of things (in whatever way…) and avoid users to ask about the current state of things over and over again and therefore annoy the devs?
Admittedly, the problem has taken longer than expected to tackle. Sometimes (as developers), you think that it’ll be a quick one, so it’s not worth documenting in too much detail. Then other stuff crops up.
I hope that the next update we deliver will be one which involves testing.
I’ve set some time for it this weekend.
Just to be clear - the Vero 4K SoC supports 3D MVC, so this point only relates to OSMC generally? This thread I assumed was always about Vero 4K MVC support specifically.
