I bought an asset from the market place, and added it to a new blank project. I open the blank project with the new content, find the Map in the content and then begin loading the map.
UE4 just gives me a beachball and becomes not-responding in Activity Monitor with 300%-400% cpu load. I wait, and wait, and then I realized it’s just taking an incredibly long time to load - even taking 5 minutes to move from 84% to 85% in loading the map. After waiting for long enough (I’d say close to 30 minutes), the map loads.
Every time I build lightning on the map - after the editor is going through the light build process - it “completes”, but then it gets to Encoding Textures - which just beachballs at 50% (encoding light maps). Trying the same tactic of wait and hope it hasn’t crashed - I wait for around 15 minutes at which point it finally stops beach balling and finishes.
This same asset, ran on the same computer in Windows 8.1 (bootcamp) runs fine - loads within a minute, lighting gets built with no hiccup in reasonable time.
- What’s my best course of action here? Maybe there’s an obvious way to fix this problem?
- How can I have a good workflow for building/deploying to iOS if I can’t run the editor well on OS X and don’t have another machine to set my Mac up as a remote build system?
My machine specs:
2.3ghz quad i7
512gb solid state
Windows 8.1 (bootcamp)
Asset in question:
Top-down city, loading the Showcase map.