Pretty obscure and edge-case, but it likely helped someone. There are a myriad of material setups, so this fix is only going to apply to that material you show. A title update would be cool, specifying what material this is targeted at. For example, picture a video titled "Fix Character Movement Studder Issue", but the fix is changing one node in a blueprint from a marketplace character controller plugin named "Character Controller X". You'd want to title the video "Fix Character Movement Studder Issue in Character Controller X", or "Character Controller X Studder Fix". Solid documentation and logical data reference/naming in game (and any) development is an important skill, so not trying to be mean or naggy, but rather giving positive critiques. This video just popped up on my feed, I peeked out of curiosity, only to learn I'll probably never need to refer back to it. The title had me fooled that it might be handy to save for future reference. Also, this can fall apart quickly. A more generic fix would be... executing a material library rebuild command. Toggling a random boolean will do it, though this also might not always work as there are a myriad of settings related to material recompilation that breaks the fix. All the being said, keep up the great work. The community can always use new heads willing to share their knowledge and showcase their cool stuff!
@RoughEdgeLtd15 күн бұрын
Thank you for the encouraging words! It was never my intention to trick or clickbait you, I have tested this on 4 other materials so it does "work" but it does only act as a bandage before it breaks again... There are many ways to go about this, including the steps you mentioned, but this seemed like the most straightforward "fix" as well as it gave me an opportunity to shamelessly plug our master material 😅 Nanite is pretty unstable but effective when it comes to selling visual quality so I don't believe there's a real permanent fix to this issue without modifying the source code of Unreal Engine.
@thesciencedudes76545 ай бұрын
Thank you. Very informative.
@mohammadrahnavard37092 ай бұрын
Tnx bro! I had this problem a week ago, finally i disabled nanite, should try it on the project with nanite! I hope it works
@austinnthurber26192 ай бұрын
You're a saint
@lenxie45012 ай бұрын
packaged game work?
@RoughEdgeLtd2 ай бұрын
Only in versions 5.4 and above.
@yosaphatmade31973 ай бұрын
Thanks for sharing, I have this problem a few days ago. I fixed it with turning off nanite and turning it on again but after sometimes, after I save the project, the problem will occur again. So is your method will cleary fix the problem and the issue will not happen again?
@RoughEdgeLtd3 ай бұрын
Hello, Yes, from experience it has been a permanent fix as long as I do not add a new material or exchange textures in an existing material instance. Once I've painted and sculpted the environment and do not plan on adding more materials, I refresh the instance and leave it at that. It's best to enable and adjust Nanite at the very end of your workflow.
@ZEW57543 ай бұрын
doesnt work
@RoughEdgeLtd3 ай бұрын
Hello, In that case, make sure your texture samples use the "wrapped" method, refreshing the material instance will work regardless, it's a matter of user error so chances are you missed or skipped a step. You can also try enabling the "Nanite Skirt" option, set it to 0.05 and rebuild. You could also make sure that your height map textures are all connect and there are no errors present in your master material.