Saving PCG World At Runtime - Beginners Guide To Unreal Engine 5 | Saragan

Поделиться
HTML-код
  • Опубликовано: 1 янв 2025

Комментарии • 8

  • @dominicharvey7306
    @dominicharvey7306 Месяц назад +1

    Looks like the issue is still present in 5.5, so many thanks for this!

    • @saragandev
      @saragandev  Месяц назад

      @@dominicharvey7306 you are welcome, I hadn't had time to try it in 5.5 so glad this is still relavent

  • @Borszczuk
    @Borszczuk 4 месяца назад +1

    You should mention exact version of UE you are using because if you say the "easy way to do it is broken" then I would rather like to know if I am affected or not. Can you please at least add that to the description

    • @saragandev
      @saragandev  4 месяца назад +1

      Apologies, I will do, I am not sure exactly which versions it has started, all versions up to now that I am aware of but you are right, I will add it to the description for reference :)

  • @dominicharvey7306
    @dominicharvey7306 14 дней назад +1

    Hi, the solution is working well. However, in my case I noted that my collision preset are lost. Are you experiencing the same?

    • @saragandev
      @saragandev  14 дней назад

      Not that I noticed but I haven't looked too much in too much detail, when you save and load, maybe save the collision profile and set it on the instance on load, I think for me the instance loader I had was auto set to a specific collision, not tried different ones so I could see how that might be an issue

  • @jxzzz8447
    @jxzzz8447 3 месяца назад

    Hi,Do I need to use multithreading if I have a large amount of tree(like Minecraft)?

    • @saragandev
      @saragandev  3 месяца назад +1

      HI @jxzzz8447 I have not needed to touch anything specific with multithreading, PCG is instanced meshes and is mostly processed on the GPU, Unreal does support multithreading obviously and by default and there are dedicated threads for audio/render/stats but nearly all of the rest are done in the game thread, i believe rendering is one or 2 frames behind the main thread. In all honesty I have not noticed any performance issues when rendering a lot of trees and or foliage. I would look more to world partitioning and nanite, this will lower quality and even hide trees far away that are not required to be rendered which will drastically increase performance. As for saving, not really had any issues saving a lot of transforms, i think the serializer is quite quick