Announcement

Collapse
No announcement yet.

Unreal Engine 4.15 Preview

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    The foliage in the 4.15 don't have dithered LODs in my end, and at check it in the materials don't work ?

    https://answers.unrealengine.com/que...t-working.html


    *Fixed! Note you have to set all the affected materials by the same model to dithered or won't work.
    Last edited by Hevedy; 01-30-2017, 10:56 AM.
    Hevedy - Instance Tools: https://hevedy.itch.io/hevedyinstances
    Hevedy - Image Tools: https://hevedy.itch.io/imagetools

    Comment


      How about actually fixing the context menu bug which will probably remain in the next big Windows 10 update? it will break for everyone that's for sure and Microsoft still didn't do anything about it (I tried the latest build from a few days ago, same thing). I'm sure you don't want thousands of posts about UE4 Menus broken.

      Edit: It says the last version this bug exists is in 4.14, is it fixed in 4.14.3? or should we wait for 4.15 final?
      Last edited by JacobMrox; 01-30-2017, 12:23 PM.

      Comment


        I can't deploy to GearVR as it says I need to make sure the APK is signed, even though I have copied the osig files from 4.14. Also not sure if it's normal, but the new version's folder has a UE_ prefix.

        Portfolio

        Comment


          Originally posted by Fisher007 View Post
          I can't deploy to GearVR as it says I need to make sure the APK is signed, even though I have copied the osig files from 4.14. Also not sure if it's normal, but the new version's folder has a UE_ prefix.
          You should make a bug report on AnswerHub.

          Comment


            Done that, but I have rushed a bit ahead with it. Restarting my PC then doing a full rebuild did the trick. Thanks anyway! Too bad that mobile multi-view is still not working (black on one side). I was big hopes for it.
            Portfolio

            Comment


              for anyone having issues on windows 8.1 with the install and error for kb2919355 and kb2919422
              If you see any of the following Windows Update errors when you try to install the Windows 8.1 Update or Windows RT 8.1 Update (KB 2919355), you might be able to fix the problems with these solutions. If you need more help, contact Microsoft support.

              Windows Update error
              What it means and how to fix it
              Code 0x80073712
              This error might mean that a file needed by Windows Update is damaged or missing. Here are a few steps you can try to fix the problem:

              Swipe in from the right edge of the screen, and then tap Search.
              (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
              Enter cmd in the search box, and then right-click or press and hold Command Prompt.
              Tap or click Run as administrator.
              In the Administrator: Command Prompt window, type one of the following commands depending on your version of Windows, and then press Enter. Don't include a line break as shown here.
              If you're running a 64-bit version of Windows 8.1, type:
              dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35 ~amd64~~6.3.1.14
              If you're running a 32-bit version of Windows 8.1, type:
              dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35 ~x86~~6.3.1.14
              If you're running Windows RT 8.1, type:
              dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35 ~arm~~6.3.1.14
              Type the following command, and then press Enter:
              DISM.exe /Online /Cleanup-image /Restorehealth
              Type the following command, and then press Enter:
              dism /online /cleanup-image /startcomponentcleanup
              Install the Windows 8.1 Update or Windows RT 8.1 Update.
              If you're running Windows 8.1, go to the Microsoft Download Center:

              Windows 8.1 Update (32-bit version) ... http://www.microsoft.com/en-us/downl....aspx?id=42327
              Windows 8.1 Update (64-bit version) ... http://www.microsoft.com/en-us/downl....aspx?id=42335

              If you're running Windows RT 8.1, try to install Windows RT 8.1 Update (KB 2919355) again from Windows Update.

              Note: Use the troubleshooter to resolve Windows Update errors "0x80070002" or "0x80070003". This problem occurs when some files in the Windows Update are missing, even though the update is downloaded and extracted successfully. Fore more information click the link below.

              http://support.microsoft.com/kb/910336

              i tried everything else. this actually worked.

              Comment


                Blueprint nativization is now stable - but
                https://issues.unrealengine.com/issue/UE-34557 (ServerTravel with nativization)
                is still backlogged. Does networking have such a low priority? :-(

                Comment


                  Originally posted by Gnometech View Post
                  This sounds great, but why limit it to mobile VR? PC VR could benefit from this too.

                  - Dave
                  We're working on implementing this for the PC when using the forward renderer. We had the mobile version working first, so we went ahead and pushed it out for this release.

                  Comment


                    Why is UE-41065 marked as "by design" ? If that's true, it's going to be the first time I can't upgrade to a new UE version. Breaking all emissive colors in existing projects isn't cool
                    Helium Rain, a realistic space opera

                    Comment


                      Originally posted by muchcharles View Post
                      I've heard talk that this change didn't make it into 4.15:

                      https://github.com/EpicGames/UnrealE...28c95663ebb5be

                      But it is already in 4.14. Just wanted to make sure this doesn't get lost in the cracks.
                      I believe we've finally found the root cause of the performance discrepancy and we're working on addressing it. We wont be bringing over this specific change (it was more of a stop gap while we investigated the issue), but we are working on a fix.

                      Comment


                        https://answers.unrealengine.com/que...-check-if.html

                        This is still happening in 4.15

                        I can't use ScrollBox without breaking my game's camera controls.
                        Freelancer Game Dev Generalist and Unreal Consultant | Portfolio
                        Unreal products: Dynamic Picture Frames, Neo Kinect

                        Comment


                          Originally posted by Gwenn View Post
                          Why is UE-41065 marked as "by design" ? If that's true, it's going to be the first time I can't upgrade to a new UE version. Breaking all emissive colors in existing projects isn't cool
                          Wondering this myself, seems like a pretty bizarre change to do on purpose. Or at the very least get some suggestions as to how we can get a nice glow going without just making our emissive lighting turn white/purple.

                          Comment


                            Totally agree. Why this behavior ?

                            Comment


                              For the record, the new glow behaviour isn't an issue for me because of how it works. What bugs me is having to re-tweak all glow values everywhere in the game, while other UE versions usually didn't break content.
                              Helium Rain, a realistic space opera

                              Comment


                                Originally posted by Gwenn View Post
                                Why is UE-41065 marked as "by design" ? If that's true, it's going to be the first time I can't upgrade to a new UE version. Breaking all emissive colors in existing projects isn't cool
                                Yeah, that can't just be "by design" since it breaks all current content. If it is by design, then at least every material needs a checkbox where you can check if you want this new behavior where an emissive blue is getting purple and later white, but that checkbox should be disabled by default for every material that was created before 4.15.

                                Originally posted by Gwenn View Post
                                For the record, the new glow behaviour isn't an issue for me because of how it works. What bugs me is having to re-tweak all glow values everywhere in the game, while other UE versions usually didn't break content.
                                But it is an issue because of how it works, you can no longer get the look you had before. It is impossible now to get any saturated color that's causing a lot of bloom. For that it has to be multiplied by ~20, but once you do that with any color its just something like white. So you can't have a strong glowing blue or red material now, they will no longer be blue or red.

                                So the issue is not only that you would have to redo all your materials, but also that its impossible to get the look you got before.
                                Easy to use UMG Mini Map on the UE4 Marketplace.
                                Forum thread: https://forums.unrealengine.com/show...-Plug-and-Play

                                Comment

                                Working...
                                X