﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	phab_field
2618	Run AI logic in a separate thread	Josef Kufner		"Funny thing happened. AI tried to build Civic Center on top of little hill, but there is no way uphill. A few workers got stuck under the clif and game dropped to slideshow with 100% CPU usage.
Problem is, that stupid behavior like this, can make game completely unplayable. AI planning should be performed in its own thread with no option to destroy responsiveness of user interface. I don't mind if AI is burning one of my CPUs, but I really don't like to watch unresponsive slideshow.
AI bugs causing this problems should be fixed, but first, AI invocation should be moved away from rendering and user interface.
I see in top, that there are multiple threads and only one of them is working very hard. So in case that AI is already separated from UI, there is probably bug in communication between these two."	enhancement	new	Should Have	Backlog	Core engine				
