Part of the Neomark Graphic on my Primal Rage is starting to separate from the regular cover stock. It's not huge, but there is the beginning of some separation. It's like a fine crack that isn't, if that makes sense.
 
At this point, it's not a performance issue, but it's not giving me warm and fuzzes. I quickly showed it to my proshop guy, and he said he'd be willing to send in a picture, but he didn't think they'd replace it at this point.
 
Anyone else experiencing this kind of issue??

My Venom shock is doing the same thing. They better replace it since I only bought it in june

My Primal Rage is less than a year old also, and it doesn't have a whole lot of games on it. I keep it in my ball locker at my primary bowling center, so heat/cold and other potentially bad environmentals shouldn't be coming into play.
 
On the Motiv website, they say the Neomark graphic is the coverstock. If that's so, how can there possibly be separation?? It's clearly separating at the boundary between the graphic and the regular cover.
   
Let me know how you're proceeding on yours. I'll be an unhappy camper if Motiv declines to take care of it, even as minor as it is right now.

J_Mac I think pretty well got it.



Looking at the patent application (US Patent Numbers 8,221,252 and 8,480,503.), the graphic is basically just a plug shaped like the logo. They mounted it to the core, then poured the ball around it.

I had an early SX-1 crack starting at the logo.  It was supposedly an early problem that was solved and the ball was replaced by my drillers distributor.   

Pics or I don't believe it! JK I just really wanna see!

Pics of my Venom Shock logo separation.

That is bizarre.

Quote from: milorafferty on September 08, 2014, 09:37:03 AM

Pics of my Venom Shock logo separation.

Yours looks to be a little worse than mine, but it's the same kind of separation. My fear is that my Primal will soon look like yours, and then morph into something even worse. 

That is how mine started and wound up cracking all the way around the ball.  Evidently it's still an issue with what I see posted here.