WHAT THE FUCK

File: Untitled.png (224KB, 1258x704px) Image search: [Google]

224KB, 1258x704px

to this

what the fuck is happening here?

This file is from max 2015 but still this fucking thing should be working properly in 2017

>>568218
I can't see anything wrong with this.

Maybe there's some AMD inside your computer

>>568225
RX 580
but this shit did not happen on my R7 360 in 2015 Max

>>568227
>this did not happen with my completely different GPU and software version

Dont see diffarence from da 1st pic

>>568217

Just save an obj from the old max and import it into the new max. I notice things like these when max files change.

>>568217

dude. just use fucking blender.

>>568570
It already looks like he put it in a blender

>>568218
When things like this occur the aforementioned export to obj fix tend to fix it. Other things that usually fix any mesh errors are resetting xform of the meshes and import them into a clean max file.

Errors like these are pretty rare, but common enough that they will occur to you sooner or later if you use the program on a daily basis.

>>568593
Kek. Here's a (you).
(you)'ve earned it.

>>568217
Its because its built on dx which is complete garbage

>using Max
>ever

>>568218

it's a feature

>>568648
Thanks