Skip to main content
Updated broken link
Source Link
atil
  • 26
  • 4

Disabling "multithreaded rendering" from Player Settings > Other settings might work (As these guys have pointed out)

My own experience was some postprocess effect was horribly conflicting with the hardware I was developing on (though mine was PC). I found out the culprit by deactivating everything (gameobjects and components) in the scene one by one. (I had noted down other people's solutions herehere)

Hope this helps.

Disabling "multithreaded rendering" from Player Settings > Other settings might work (As these guys have pointed out)

My own experience was some postprocess effect was horribly conflicting with the hardware I was developing on (though mine was PC). I found out the culprit by deactivating everything (gameobjects and components) in the scene one by one. (I had noted down other people's solutions here)

Hope this helps.

Disabling "multithreaded rendering" from Player Settings > Other settings might work (As these guys have pointed out)

My own experience was some postprocess effect was horribly conflicting with the hardware I was developing on (though mine was PC). I found out the culprit by deactivating everything (gameobjects and components) in the scene one by one. (I had noted down other people's solutions here)

Hope this helps.

Source Link
atil
  • 26
  • 4

Disabling "multithreaded rendering" from Player Settings > Other settings might work (As these guys have pointed out)

My own experience was some postprocess effect was horribly conflicting with the hardware I was developing on (though mine was PC). I found out the culprit by deactivating everything (gameobjects and components) in the scene one by one. (I had noted down other people's solutions here)

Hope this helps.