Merged sprites are broken

Hello,

I would like to report that merging sprites is broken in 4.13.

That is causing me great issues since they are an absolute must for performance reasons. To simply put it, without them I cannot publish on consoles because the CPU render view family gets choked.

I desperately need them to be fixed as soon as possible so I can start working again.

https://www.dropbox.com/s/geqk9nei3rr989w/bandicam%202016-10-12%2021-39-26-034.zip?dl=0

link textThank you.

Hi ,

The issues you’ve previously reported on the Xbox forums has been logged here: Unreal Engine Issues and Bug Tracker (UE-35780)

The issue you’re showing in the video is not one that I’ve seen reported or one that I can reproduce with the test assets I have. Please include any known steps to reproduce the issue or a test asset that clearly demonstrates the issue and I can log a ticket for that as well.

Thank you!

Hello ,

I found some time and created a repo project for you.

Just split them to return to their original position,and merge them again.
https://www.dropbox.com/s/95xn9eho4mtxe3z/MergedSprites.7z?dl=0

Cheers.

Thanks for taking the time to follow up but I got a repro for this a long while back. This issue is still opened, though.

Is there a way to steer the pot a little in hope that they will fix it? As I said in my first post, without it I might not be able to publish for the consoles because of frame rate issues. It is killing performance by more than 15fps!! (not being able to merge sprites). Not to mention that this issue must have something to do with the fact that nothing renders for the XB1 regarding merged sprites.

I’ve reassigned the ticket to the rendering team to look at and determine if this is something that should be on the backlog or scheduled for a fix. It all will come down their own priorities. Keep in mind that it’s an experimental feature and is not supported for production-ready projects. It’s not uncommon for things to break or change for these types of features.

With access to Source, you are free to see what changes were done between 4.12 and 4.13 to fix this yourself or return to 4.12 for active development if you need this working. It’s best to stick with a version of the engine that is stable and develop there. Before moving to a newer release, any upgrades should be thoroughly vetted to make sure it doesn’t break the project.

You cannot do that with consoles. You need the latest SDK’s in order to publish or even test your game. It looks that Paper2d was a bad idea…

Thank you.