ugh

not enough information dude
is it a path, a group or a compound path?
any pathfinder flags?
size?
give us a anchor point view via cmd-Y at least

File: Screen Shot 2017-04-04 at 10.50.23 a.m..png (437KB, 2866x1592px) Image search: [Google]

437KB, 2866x1592px

>>304028
Its a path,
unsure what a patch finder flag is? iv recently moved from windows and did not have this issue with the same files befoe.
its 14 x 15 inches

That is one seriously fucked up path; the lines of the flower are crossing themselves. This results in an faux compound path, which is not a good thing.

Select it, run Divide, then Combine back together.

File: Screen Shot 2017-04-04 at 11.58.05 a.m..png (205KB, 1156x1008px) Image search: [Google]

205KB, 1156x1008px

>>304037
i see, so thats whats causing it?
i have it on this cloud aswell but no paths seem to be crossing

File: Screen Shot 2017-04-04 at 11.58.28 a.m..png (569KB, 2880x1538px) Image search: [Google]

569KB, 2880x1538px

>>304041

>>304041

On the cloud, it looks like a problem with either the graphics driver (which could be OSX or AI) having a problem resolving the transparency. Make sure you've got the latest proper driver, and AI is the current version.

Without the file, I'm sort of just shooting in the dark here.

>>304041
definitely looks like a GPU issue
Either restart your computer or try working non-retina

>>304042

Ok, seeing the vectors helps. You can also try this.

You're masking out the EEEE shapes. Instead of masking it, try converting the EEEE shapes to complete paths, using the pathfinder tool to literally cut off the tops. Then delete all the newly unnecessary parts.

Then at least the transparently isn't trying to resolve cloud-over-EEEE.

>>304044
>>304043
>>304045
thanks for the help guys its definitely a problem with GPU preview, when I turn on pixel preview the problem goes away,
its a brand new macbook pro :/

>>304046
Adobe is always behind with updates. Whenever a new OSX version is released or new hardware gets launched, Adobe's newest tools never work 100%. The Photoshop CC hotfix for Mavericks was a fucking joke

>>304050
Mavericks was a fucking joke.

>>304052
snow leopard 4 lyfe nigga

>>304050
>Whenever a new OSX version is released or new hardware gets launched, Adobe's newest tools never work 100%

And who's fault is that? (hint: not Adobe)

>>304054
to be fair though, Adobe has historically been given HW/OS access early but i don't know what the situation is today
plus developer previews and gold masters are a thing now so you'd think Adobe et al would be prepared.

>>304055

True, they get early access. But sometimes OSX doesn't even work right with itself. Mavericks was utter crap in the GPU department when Apple released it.

https://discussions.apple.com/thread/5493333?tstart=0

>>304056
>Mavericks was utter crap in the GPU department when Apple released it.
updating to mavericks caused irrepairable damage to my machine