Announcement

Collapse
No announcement yet.

Unreal Engine 4.21 Released!

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    I got this upgrading a shootergame derived project:

    Code:
    LogTexture: Display: Building textures: HUDAssets02 (AutoDXT, 512X512) LogTexture: Warning: GetMipData failed for /Game/UI/HUD/HUDAssets02.HUDAssets02 (DXT5) LogTexture: Display: Building textures: HUDAssets02 (AutoDXT, 512X512) LogTexture: Error: Failed to build texture /Game/UI/HUD/HUDAssets02.HUDAssets02. LogTexture: Display: Building textures: LowHealthOverlay (AutoDXT, 1024X1024) LogTexture: Warning: GetMipData failed for /Game/UI/HUD/LowHealthOverlay.LowHealthOverlay (DXT5) LogTexture: Display: Building textures: LowHealthOverlay (AutoDXT, 1024X1024) LogTexture: Error: Failed to build texture /Game/UI/HUD/LowHealthOverlay.LowHealthOverlay.
    Deleting my ./Saved folder fixed it.. Just throwing that out there because Google found very little on the Failed to build texture error.

    Comment


      #32
      does support only hp and samsung wmr?

      Comment


        #33
        Where can I find more info on the Niagara Skeletal Mesh Data Interface? Especially SkeletalMeshSurfaceLocation sounds like something I might need, but there is no info on it anywhere

        Comment


          #34
          very very boring update
          please release rtx support version
          please add new and modern baking system over the old lightmass

          Comment


            #35
            You should probably write it in the changelog if you add new SceneTextureIds.
            It broke a lot of post process materials in my project. You added Shading Model ID before the CustomStencil.
            First of all, its not nice to break enum order, its even worse if you don't even mention it.

            We need to go through every post process material which uses depth stencil, and replace this line
            Code:
            SceneTextureLookup(uv, 24, false)
            to this
            Code:
            SceneTextureLookup(uv, 25, false)

            Comment


              #36
              Guys, please, UE-65983 is still present in UE4.21 release!
              'Cannot Reproduce' is not a correct status for this issue, it is very reproducable!

              https://issues.unrealengine.com/issue/UE-65983

              Comment


                #37
                How many people have Google Daydream/Cardboard VR projects here?
                Do you have issues with 4.20 and/or 4.21?

                Comment


                  #38
                  Originally posted by Farshid View Post
                  very very boring update
                  please release rtx support version
                  please add new and modern baking system over the old lightmass
                  we dont need rtx thats useless, we need better programming and documentation, especially C++ compile speedups maybe implement a cache system for UE4 build system its very slow, we also need a plugin for VS other than VAssist thats developed by Epic and that can properly search and find what you need for autocomplete + documentation intellisense
                  we also need full support for glTF 2.0 including animation and import option menu, currently only supports mesh import no animation, fbx is cancer itself

                  we also need a new roadmap update, it hasnt received one since last year
                  virtual texturing, polygon modelling, in-engine animations tools, full vulkan support, python scripting, new unreal audio still experimental etc we have yet to hear more about these, they are probably being worked on but an update would be nice

                  oh yeah and more bugfixing!!! so many bugs left unfixed since forever

                  Comment


                    #39
                    Originally posted by M3NTH0S View Post
                    oh yeah and more bugfixing!!! so many bugs left unfixed since forever
                    Stop bug-adding would work for me, though. It is silly that developers have to brace themselves each new release.

                    Comment


                      #40
                      Originally posted by diamond3 View Post

                      Stop bug-adding would work for me, though. It is silly that developers have to brace themselves each new release.
                      If you want new features, there will be new bugs, its how software works, at least until AI automated testing/fixing wil become real, if its just humans we are going to have bugs.
                      Although im not very fond of Epic's development pace and strategy, why dont they have an LTS version? they have a very cheap version abandoning strategy, for instance 4.19.2 is that version the last why? is it bugfree ? ofc not, so new bugfixes should be upstreamed into an LTS version, and release an LTS version each 3-4 regular versions or once a year. That way when you start real development and lock into a specific version you can rest assured those pesky annoying bug fixes will get streamed back into your LTS for at least 2 years. Otherwise you will either have to fix the bugs yourself or move to new version in the mid of the development or after game is released? hahaha not going to happen, it never works.

                      Comment


                        #41
                        Another bug with Daydream: Daydream VR controller no longer moves in 4.21.
                        https://answers.unrealengine.com/que...-tracking.html

                        Comment


                          #42
                          Heads up houdini folks,

                          Alembic Animation still freeze hangup 4.21.

                          4.19, works fine.


                          Anyone having success importing alembic Animation into 4.21?

                          Can you list what software you're using/export settings?


                          I just don't know what to do as our pipeline is working fine with 4.19.

                          4.20/21 don't import alembic.

                          Comment


                            #43
                            TV OS ( + iOS C++ Projects)

                            Was able to package on 4.20.3 (via remote, althought it couldnt be uploaded to itunesconnect due to the asset bug. that is fixed for 4.21)

                            On 4.21.0 am not able to package the exact same project. Here's the output from failed packaging. Thank you

                            EDIT : rsync error , was noted as Fixed on 4.21 previews but it still occurs.

                            "Fixed! UE-65075 Binary iOS/TVOS remote build fails with rsync errors"

                            New EDIT : it occurs to iOS+TVOS Builds using C++ with remote mac, blank projects ( blueprint only projects that dont require remote,build ok)
                            Attached Files
                            Last edited by GRADgr; 11-11-2018, 01:42 PM.

                            Comment


                              #44
                              Landscape tessellation bug:

                              Editor crashes instantly when enabling tessellation in a material that is already applied to a landscape. It does not crash when you enable tessellation first and then apply it to the landscape.
                              ArtStation

                              Comment


                                #45
                                Wow, the QA is pretty much non existent according to this Thread.

                                Comment

                                Working...
                                X