Hi , is there any info on why that issue was marked “Won’t Fix”? It still exists in 4.25 and the 4.26 previews - any custom latent action taking FLatentActionInfo as the first parameter will be called infinitely.
Hi , is there any info on why that issue was marked “Won’t Fix”? It still exists in 4.25 and the 4.26 previews - any custom latent action taking FLatentActionInfo as the first parameter will be called infinitely.