Yeah I know this method but I’d like to be able to save parameters to the Widget because the Saved folder should be ignored when you are pushing files to perforce or github
Did sth change with RT translucency? I can’t even get a simple fogplane to show in RT mode. Didn’t this work in a previous Preview version?
Also switching back to raster translucency in PPV doesn’t seem to work once you’ve toggled it to RT only once.
In Preview 7, Foliage’s brush can’t be seen, and the engine becomes very vulnerable to crash.
At the same time, it seems that every time the engine is turned on, there is always a part of the shader that needs to be recompiled and cannot be stored.
VR htc live does not work, impossible to use, will we be able to work with virtual reality in 4.22 ???
Where’s the download link for 4.22 ?
Just click on plus button and choose engine version.
Preview 7 barely usable with menus and name edit fields closing by themselves after a short timeout, new assets created disappearing when not giving a name fast enough…
I’ve had that happen when an FX (Niagara) editor is open, but only then. I think it’s an FX problem.
OMG… UE4.22 has lots of bugs…
and DEV didn´t even added Directional Gravity for Charachter BP with movement component…. requestet since 4 years ago.
hello everyone, trying to get 4.22 running. I am running things on a 2080, driver version 419.67 (03/25/2019, latest driver) when I try to launch the editor it crashes instantly saying my video drivers are out of date. Do I need an older driver version maybe? I did set the -dx12 flag on launch and my win10 is up to date aswell, (version 1809)
I also have a titanX and a second 2080 in my machine. Do I need to disable the titan maybe? 2080 is my primary gpu though so I figured that one should take priority on launch?
have a nice day everyone
@theredbearded I think other people got crashes aswel when having more than one card in the same machine, but at least those reports they were both same model, I would disable or remove the TitanX completely and try again.
Please, send the crash files by the crash report screen.
@ will try that. where can I find the crash log? looked in programfiles/4.22/engine/programs/crashreportclient but that folder is empty.
edit: unplugged 2nd 2080 and titan, still crashing with same error window. this is what shows in the log
edit2: somebody on reddit suggested to try the creator ready drivers instead of the gameready drivers, will try to install that and reporting back soon
Hello FrederickD,
I haven’t seen any other reports of that issue at the moment. Would you be able to send us a bug submission describing the issue you’re experiencing? Please use the following form: Unreal Engine Bug Submission Form
Always when a crash screen appears you can click on the send button and it will automatically send the files to Epic. The files sent by the crash report screen are located inside your project’s folder under the Saved/Crashes folder.
I installed the creators driver (419.67, 03/20/19) still getting that error unfortunately. I might just wait for the non preview release I think… [USER=“36033”] J[/USER] do you have any further ideas by chance?
edit: i thought i had it running but it turned out i forgot to use the dx12 shortcut and it’s not working using the flag. I just started through the regular launcher and forgot that part… fml guys i was so happy for a second haha
@ I don’t get that send dialogue unfortunately but I found the log file in that directory. here is the log file
someone on discord just told me there was no crash in that log and the exit was just a regular editor exit. any ideas on how to help you help me in this case? not sure how to get relevant crash info
Yeah, I can confirm that one wasn’t showing any error. Are you sure there is nothing inside your Crashes folder inside Saved folder?
there isn’t any Crashes folder there even 
people in the slackers discord told me that this was just a drivers crash and the engine can’t really do anything about it so maybe thats the reason for there not being any crash logs and therefore not being a crashes folder?
at this point I tried everything I can, re-installed my drivers, removed all gpus but one but still getting the same error. I will wait for the final 4.22 release I think since I don’t know what else to try at this point. if there is any way I can send some crash log to epic to help figure out why the driver crashes I’ll be glad to help.
@ are we still talking about the same directory? documents/unreal projects/projectname/saved/(Crashes)?
Yes. It might be indeed the drivers crashing and that would be a reason for the crash report screen not appearing. There is few suggestions thou, but follow if you are really comfortable doing this, because interruptions in the procedure might render your system unusable, so I would also suggest asking for someone with experience doing it and of course full backup on your stuff:
- check if there is any BIOS updates for your graphics card model at the vendor’s website
- check if there is any BIOS updates for your motherboard model at the vendor’s website
- power supply meets demand for the graphics cards
- let your system CPU to boot non-overclocked (stock speeds)
Proceed with extreme caution and be aware that power interruptions during the process will make your system not able to boot or in case of graphics card won’t allow it to work. Make sure you got a no-break working properly (remove the power cable to see if it holds the system under load) and also do one change at a time and test, until you get a positive result or extinguish tests.
@ thanks for the suggestions!
my CPU (threadripper 2950x) isn’t overclocked and my PSU (1000W) should be able to handle everything under load since I never had a shutdown rendering on 100% load in octane or doing any other heavy work in maya/houdini.
I updated my mainboard BIOS to the latest version before, no new updates to date (asus zenith extreme x399 with build 1701) after I built my PC because at first it didn’t even recognize my 2080s at all with 3gpus installed. I am not really too comfortable doing all that stuff though if I can break things in the process because this is my main workstation and I’m working on some projects right now so I can’t really afford anything to break right now. I’ll just wait on a more stable release since I just wanted to play around and test performance on the 2080 I don’t need 4.22 to work right now and my machine is running stable for everything else I need to work with right now. I’ll revisit 4.22 once it officially launches and if the errors persist I might go down that road. have a great day, thanks for helping me out 
edit: forgot to mention, I removed my 2nd and 3rd gpu to test with single 2080 but got the same error. so I don’t think it’s a problem with the PSU tbh