Ive tested the 4.14.3 in 5 configurations all with 16 and 32 GB ram SSD’s i5 - i7’s upto the 6950x(Very High End) and NVidia Titan Gtx 6Gb and Titan X 12gb, windows 8.1 and 10, all using visual studio 2015. And You Guessed it, Crash, Crash , And More Crashes. Just opening up a stupid vehicle’s skeletal mesh and changing its material maybe after the second change. Crash. Simple Task Which even a crappy Laptop should be able to do. Became impossible. What gives???
Really whats wrong with 4.14.3. These crashes are retarted. 4.13 worked excellent. It’s like new features which seem very useful but what’s the sense when the engine is now useless/Unusable.
Im not here to rant about a F’d up update. Actually I do think the engine ROCK’s,At least 4.13. I would really just like to know if this issue will ever be resolved, or has it been fixed in 4.15 or should I just stick to 4.13 and kiss new feature good bye. or what. Because it seem’s like this is a dead thread. And some gave up.
BTW: I apologize if I offend it’s not my intension in anyway, it’s just frustrating.
At this time, there are no further planned hotfixes for 4.14. If you’re experiencing crashes with that version, I’d recommend two things:
Update to 4.15 to see if the crashes are resolved
Post a Bug Report for each individual crash, and we can investigate and provide you with a link to the ticket if one exists. If you are using a source build of the engine, you can grab the fix commits and merge those into your current engine version if you don’t want to update.
In the future, please post all crashes in the Bug Reports section, and include the following information so that we can investigate:
The logs from your project’s Saved->Logs folder after the crash occurs.
The callstack from the crash, as well as your Machine ID from the crash reporter window
A set of steps we can use to reproduce the issue in a clean project.
I Thank you for your reply. So then 4.14.3 is a dead stick for me, as for logs mine are the same excact logs that have been posted, and as you can see in various system environments. But oh well I hear you thanks anyway, you to have a great day.
As stated, if you are experiencing crashes, please feel free to post a new thread for each individual crash in the Bug Reports section and we can investigate and see if we can find a solution.
Yes Sean, I hear you. You need post and Crash logs for each issue, & that’s what everyone has been doing and you know what They all post the same Crash logs, I have the same ones they posted, the only thing that changes is the drive letter, That’s all. Anyway look I just wanted to update you a few things, you can erase this if you like, but I think you should know, if you don’t already.
Specs -
i7 Extreme
16GB Ram (UEdoesnt even use more than 8gb)
SSD drivers 1- for the OS & 1- SSD dedicated to the engine only)
Video Cards i tried so far :
GTX 550 TI
GTX 760
GTX 780
Tittan 6GB & 12GB
Visual Studios 2015
OS / Windows 8.1 - And the ■■■■■■ Win 10 - (Both Clean Installs)
UE 4.15 didn’t change anything im still getting the same issues as 4.14. Especially opening a skeletal mesh asset. It freezes then crashes. My team and I don’t the time to post the same crap posted many time’s by many user’s. But really this is becoming ridiculous.
Random assets like a vehicle for example, when you open it’s skel mesh Crash
using the -opengl4 switch allows you to which sucks BTW but only a workaround
when vehicle and I mean a custom vehicle so much as touches another vehicle it flips around as if it were smacked silly ( Not Good At All) and trust me when it comes to vehicles I know a lot (The guys at RockStar can tell you)
Converting a UE4.14 project to 4.15 till now if it has a Uwheeled componentvehicle it wont convert project, (6 hrs later we had to just manually copy paste it over because it couldn’t find the Uwheeled component parent for what we had)
Like I said this is just food for thought, nothing personal but aggravating.
What once worked great now doesn’t at all.
But I wont take any more of your time. So I Thank you for yours
Oh and By the Way (The Issue Is Not RESOLVED at ALL) May you and your team Have a Wonderful day