I just installed max 2017 and it's acting like autistic piece of shitit randomly goes from this
to thiswhat the fuck is happening here?This file is from max 2015 but still this fucking thing should be working properly in 2017
>>568218I can't see anything wrong with this.
Maybe there's some AMD inside your computer
>>568225RX 580but 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
>>568217Just save an obj from the old max and import it into the new max. I notice things like these when max files change.
>>568217dude. just use fucking blender.
>>568570It already looks like he put it in a blender
>>568218When 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.
>>568593Kek. Here's a (you).(you)'ve earned it.
>>568217Its because its built on dx which is complete garbage
>>568218it's a feature