(Note: The picture below is not really helpful)
This is the command I'm using, summon minecraft:falling_block ~ ~ ~ {NoGravity:1} (I'm using a repeating command block set to always active and unconditional)
When using this command, the block barely gets shown, it might flicker a little, but the majority of time it doesn't show at all. Here is a link to a project that uses these commands ---> https://www.planetminecraft.com/project/fnaf-security-breach-rtx-showcase-trailer/. If you test this in any 1.16 version compared to the current 1.17 version, you will see a big difference. Hopefully this post helps you and others as well.
Attachments
Comments 2
I can confirm this. In earlier versions, if you spawn a falling block with Time:0
every tick, it would appear as a single falling block which you were able to move by spawning it at different positions. Now, due to the flicker, this is no longer the case.
One solution could be to set Time
to -1
:
/summon minecraft:falling_block ~ ~ ~ {NoGravity:1,Time:-1}
This however will not look as smooth as it did in 1.16 and below and seemingly two falling blocks are sometimes present at the same time when moving the block (Like the flicker with Time set to 0, just offset by 1 tick and harder to notice)
You need to specify the
Time
NBT data in the command: