Whatever, really, I'm so fricking tired of this nonsense anyway.
Let's see, random user uses a computer with some unknown baseline of OS and applications. God only knows what settings, permissions, conflicting software, patch levels, or just user incompetence they bring to the table.
They post some question that some part of MakerBot software doesn't work.
Now on both sides of the argument, (A) I acknowledge that MakerBot software is generally pure crap with more bugs per line of code than anything else on the planet- BUT, there is an expectation (B) of the user to bring a functioning OS platform, drivers, and hardware to to the table as well.
This is one of those retarded things were we go through this all day thread of WAGs, reaching for anything that "could" be an answer. In the end, none of us have hands on the machine, none of us really knows what is the problem.
All we know is both A and B met in the middle to produce result C- the @#$@#$ doesn't work.
Sorry for being graphic and this is not aimed at the poster or anyone specific in this thread answering. It's just an observation of the same thing that happens EACH and EVERY release of software from MakerBot in this group. Inevitably, some poor user finds out the latest version of whatever MakerBot software is out that week simply doesn't work on thier computer. It's likely the software and since MakerBot engineers don't answer here- you aren't ever going to get the answer you are looking for. All we know for a fact is that software A does not work on computer B. Tht doesn't mean that software A won't work on all computer Bs int he world, it just means that we hanve a single example of A not working on B. It could be the fault of individual computer B but how could we know what software, what driver, what OS patch, what setting, invokes problem C?