Project: Paper2D

[anonymous_user_21a58d97]

@;223117

I’d actually expect similar performance here no matter what kind of actor you are moving around (sprites, static meshes, etc…) and doubt it is sprite-specific; 35k actors is a lot. However, I’d be thinking more on order of a few seconds to move that many actors in editor, not something like minutes, and wouldn’t expect an ongoing FPS hit after you’ve finished moving things.

One other tool that is useful is that you can stream in levels with a transform offset (which is especially useful when procedurally generating levels from sublevel ‘tiles’ that you might load multiple copies of at different locations), but you shouldn’t be forced to use that for your use case.

Cheers,

My biggest concern right now is not dragging many actors at once. It took me about an hour to move my levels around but since it is now finished and it had to be done only once I am ok with it.

My biggest concern is fact that with no blueprints open, just editor I have 100% CPU usage. Without me moving, selecting or dragging anything with real time preview disabled. Does amount of actors on viewport has an impact on CPU usage ? I am trying to figure out if is normal behavior , a paper2d limitation or just something wrong with latest 4.8 from . I really need your expertise on . It would really help me steer in right direction. If is normal how on earth will I be able to finish my game?

Thanks in advance. I really appreciate everything that you are doing for us.