Ashley, firstly. I am sorry for these long winded responses. I did not think I had to write such in-depth responses, but clearly they are needed.
What evidence have you exactly provided? I cannot seem to find anything that suggest you have provided solid evidence of what the cause is. I find it strange because you say you have not reproduced the issue, but yet know who is to "blame" (I hate to say blame, but you keep throwing that term around. Playing the blame game gets no one anywhere's fast. I could care less about blame, I just care about the issue being fixed)? How can you say what is wrong, without reproducing it and knowing exactly what needs to be done to fix it? And, if you know what the issue is, could you please enlighten us in detail? If I missed this evidence you speak of, could you please point me to where you have solid findings of what causes this issue.
I also have trouble here, because you keep saying you cannot reproduce the issue, but have shown you hit the issue yourself. I have asked numerous times for results on certain testing, but you have (mostly) ignored my every attempt to help out. You have said a 1 second delay is normal, but when I question why it is instant on W7, and gave an example of if C3 had a 1 second delay per line of code you wrote, would that not be an issue. . . you ignored that completely.
To be clear (and this is just one example, there are many), numerous times I have asked you to compare W7 to W10 to notice the difference in performance. I have not seen your results for this test. I have also asked you for more details in regards to what you have tried and found (all for the sake of determining the root cause of this bug). Each time, you have provided vague answers, or completely ignored them altogether. Only after asking a few times, did you go into a few details (but as stated previously, leaving out a lot of crucial details to make the replies meaningful to the bug report). I am not sure why I need to ask so many times the same thing for you to finally provide some details. This thread could have been 1 page long had this been handled differently.
Again, no blame game here. I am asking, or suggestion, perhaps moving forward you could try to be a bit less vague with your answers? These types of responses don't help, and delay the bug further. They also cause unnecessary clutter and the need for further clarification.
This question does not make sense, because C2 is not idling in this situation.
Perhaps idling was not the right word. When C2 is lagging, what is it doing. That is what I meant. Comparing W10 to W7, what is the difference when you debug it.
We're a small team, and we're only human. If you are refusing to co-operate and believe the things I say, I will probably prioritise my time with users who do co-operate and believe the things I say. I've made a special effort to investigate this issue ahead of the normal schedule and have spent some time detailing the evidence I've found and, with the experience of dealing with thousands of bug reports, what I believe it points to the cause being. If this counts as "complete disregard", then I am sure nothing I do will please you. I think you are just trolling me, so I will step away from this issue for the time being and return to it on our normal schedule, or if any compelling new evidence is raised and discussed in a constructive and co-operative manner.
I don't believe anyone could seriously take me as a troll with this bug. The amount of effort I have shown in trying to get this resolved, really surprises me you could even call me un-co-operative and a troll. I only want to get this issue fixed.
The fact that you are making a whole platform suffer, because you think I am trolling, is just unbelievable. Are you overlooking the numerous examples, pictures, user-accounts, and videos posted throughout this thread by numerous users?
I have shown C2 has performance issues on Windows 10. There is solid evidence and a ton of data collected on it in this thread.
I have offered up my time to you. I have offered to help on many occasions. You have ignored my every request to offer help. I have offered talking to you over a sharing session, so you can see the issue and debug it further. I have offered to send you a VM. I have offered to debug the issue if you send me the proper tools. Every. Single. Request. You have ignored. So, how exactly am I being un-co-operative and come off as trolling? I (and many others, as seen in this very thread) genuinely want this issue fixed.
To be clear. If you get any hint, of anything other than me wanting to have this bug solved. Please re-read this entire thread (I would recommend this anyways, so you can see how many questions have gone unanswered and possibly answer them, and perhaps you might see I have the most sincerest regard with this bug). My goal here, is to find and have fixed the C2 Performance issues in W10. I have no other intent, except to help the community. Many members of the C2 community are affected by this bug. Many have thanked me many times for my due diligence and suggestions to help mitigate the issue. I ask you Ashley, if you truly think I am trolling you should re-read all of these post from start to finish. You have the wrong idea, and there is a large misunderstanding. Let's get that cleared up so we can move forward and better C2 for the community. If we don't, slowly overtime you are going to see more and more of these reports by various users as more people jump to W10 and projects get larger. You are going to have frustrated users who started C2 as a beginner and their C2 lags as their projects get more advanced. People who have moved on from C2 before Windows 10, are going to come back to a nasty surprise when they try and update old projects on their new W10 machine. I'll ask again because you have not answered, is none of this a concern to you? Do you not care about C2's performance on W10 despite the amount of users who have reached out and provided valuable feedback on this issue?