Closing, please follow the bug report guidelines: you must attach a .capx that reproduces the problem, and please include all relevant information inside the bug report itself without referring to any other threads (which usually is just confusing because the thread talks about a bunch of other unrelated stuff)
Ashley, did you read this, or did you just see no capx and closed it? The first thread had barely any information about the bug in the report...I thought I included more. I thought I was pretty clear that any capx is doing this, including the samples that come with construct. Now I have to recreate this, with the exact same information and include the sample capx, that you already have. Seems pointless.
In this case, including the first thread was very relevant. It shows what I have tried and what solutions have already been suggested. The thread was only a few post, not hundreds of pages. I explained the issue, and included the thread to show more if people were curious but it was not needed for the bug report itself, it was supplementary. Guaranteed, if I did not link to it, someone would have told me to look at that thread and try the solutions there.
So, before I go recreate this. Any comment on what exactly you want? Otherwise, I am literally recreating it exact same with the sample capx's that everyone already has.