Announcement

Collapse
No announcement yet.

4.20 crashing days after release

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

  • replied
    Originally posted by BFuller View Post
    Tell me about it! I get to a certain point using the Udemy course one minute it works fine the next off it goes! The thing that gets me upset is that it has been going on since I think version 4.17 right up to version 4.21.1. It's still happening! So hopefully the next update will FINALLY resolve the crashing issue along with a updated VS 2019 that's out in the coming months! Right about now though I'm not holding much hope for it to be resolved by then! As of a few minutes ago it opens the editor but then it just closes or shuts down. It's a good engine that helps understanding how to use C++/Blueoprints to bring up a workable demo, however if and when it keeps on crashing it's simply not worth the effort to try and get something stable to show! Oh well it looks like I'll be twiddling my thumbs again until the NEXT update comes along!
    UE4.21.1 will probably still receive hotfixes before UE4.22. , so I would just recommend for production purposes to use the latest stable release, so now it would be UE4.20.3. So far, the only not recommended release would be UE 4.19.x, but all others are OK to start a project. Trying to create something on the latest active release can always come to point of having severe issues that can put your project on a hold status.

    Leave a comment:


  • replied
    Tell me about it! I get to a certain point using the Udemy course one minute it works fine the next off it goes! The thing that gets me upset is that it has been going on since I think version 4.17 right up to version 4.21.1. It's still happening! So hopefully the next update will FINALLY resolve the crashing issue along with a updated VS 2019 that's out in the coming months! Right about now though I'm not holding much hope for it to be resolved by then! As of a few minutes ago it opens the editor but then it just closes or shuts down. It's a good engine that helps understanding how to use C++/Blueoprints to bring up a workable demo, however if and when it keeps on crashing it's simply not worth the effort to try and get something stable to show! Oh well it looks like I'll be twiddling my thumbs again until the NEXT update comes along!

    Leave a comment:


  • replied
    When I had a machine with integrated gpu, a lifetime ago, I would just disable it on Windows device manager

    Leave a comment:


  • replied
    That's not an issue with UE4, by default if you have a computer with both the integrated Intel GPU and a separate Nvidia or AMD gpu then it will try to automatically choose which GPU to use so that it can use the low-power Intel GPU for low-power situations. However, I've found that Windows does not do a good job of managing that and it's better to just set it to use the Nvidia/AMD gpu for everything.

    Leave a comment:


  • replied
    I found that if you have a laptop and it is running on Intel, for some reason (UE4 and Intel paired up to better "utilize" the Intel core) it will decided to utilize the Intel's CPU instead of your graphics card. Switch your preferred settings for your laptop's graphics card to high performance on Battery and Plugged in. I've had it working like this for a long time, and haven't experienced the crash ever again, however I have to keep my laptop plugged in. If the laptop isn't plugged in, regardless of any settings I've messed with, it won't utilize the high performance graphics card and trying to do anything that would normally be a simple thing GPU wise will kill your Intel CPU and crash the engine.

    TLDR: Set your Graphics settings to High Performance on Plugged In/ Charger and always keep it plugged in when working with the Engine.


    Hope this helps you guys the same way it helped me.
    Last edited by MaraAnkiri; 01-16-2019, 07:11 PM.

    Leave a comment:


  • replied
    losses is also experiencing crashes covered by https://issues.unrealengine.com/issue/UE-51650

    Leave a comment:


  • replied
    losses This is something odd. I have been doing a project from scratch, adding folders, creating materials and material functions and nothing happened as described above. I have also switched later to the new Material Layer system and was even hoping to have some crash, but all is doing fine till now and see that I have totally converted the material setup created to the new layering system, with no crash (using 4.20.2).

    Are those insta-crash jumping out of the crash-dump screen? Are you able to at least send the crash-dump?

    Leave a comment:


  • replied
    Some 30 minutes to create a new folder, import an FBX and get the mesh into my Scene.
    You basically have to save all after doing anything to get in before a crash.

    Leave a comment:


  • replied
    Back to crashing 4-5 times until I can do something as simple as creating a new folder.

    Simply cannot work like this, at this point I need to decide if I continue with the engine or move to Unity.

    Leave a comment:


  • replied
    With update to 4.20.2 I can no longer open a new project, nor open a project made with the 4.20
    When I open the editor, it comes to 72% closes and does not give me the crash report, just a windows screen that says it is sending a report to microsoft!
    I use a MSI GT75VR 7RE Titan PC with a GTX 1070

    Leave a comment:


  • replied
    MSI GS65, constant crashing in the editor. Simpy loading a mesh or trying to edit a material.

    Unreal Engine is useless to me atm...

    Edit: Did a couple of things, so far so good.

    Verified 4.20.2
    Also went into Nvidia settings and changed the Preferred GPU setting from "Auto" to "High Performance Nvidia Processor"
    Last edited by losses; 08-25-2018, 04:15 AM.

    Leave a comment:


  • replied
    I've tried everything but throwing the kitchen sink at it and it still freezes (as of update 4.20.2) I've checked all the drivers (NVIDIA, Intel, Windows operating system) and they are ALL up to date. However no matter what I try and do, it works well for one second, then literally unusable the next. I'm unable to change the setting in Intel because there's not a option to link it to the Unreal Engine Editor. I've linked the NVIDIA graphics card to the Unreal Editor and it still freezes and crashes! It's becoming exhausting to even want to install the update, because at the back of my mind I'm thinking "Is this one going to WORK?" Something needs to be done, because it was working FINE up until version 4.17, then it went downhill and fast!

    Leave a comment:


  • replied
    I’ve never had as many crashes in any other version than 4.20. Just today alone, I’ve had at least 8 crashes just at random. Usually straight after I hit compile on a blueprint and before clicking save. I’ve lost and had to redo so much work today.

    Leave a comment:


  • replied
    Same crashes its a pain in the *** when im trying to build a game and i cant stream because of the crashing always going on
    Attached Files

    Leave a comment:


  • replied
    I was having this problem as well, but seemed to have solved it in a really weird way. The laptop, that I use for 95% of my work, has a 540m and an Intel 3000HD. I have a shortcut to the editor and instead of launching it with the 540m, I launch it with the integrated card. UE will still make it force the 540m(confirmed within the logs and Nvidia GPU Activity), but it seems to alleviate my problems. In the logs, it will show that the Intel card is only DX10, so I presume that it's forcing the Nvidia card because it has DX11.

    I had been getting BSODs with the watchdog error just trying to open the project browser. I was also getting random crashes with the material editor. Haven't had one since I started booting UE with the integrated card.

    Again, this is a really strange workaround and I can't exactly explain why it works, but it works and it's definitely using the 540m...

    Leave a comment:

Working...
X