Hi, I necro’d a - much - older answerhub question without thinking so I’m posting this to hopefully get a little more visibility.
There was(is?) a bug/issue with UE4.5 where adding keyboard and mouse events to graphs could cause assertion errors/crashes - this “bug” - which I necro’d - with the internal tracking numbers (UE-763 and UE-4443).
An update on the issue was never posted back there and the issue is very much alive and present in ARK’s modified 4.5.1 engine/editor. Has this issue been rectified? If so, which engine and/or could I get the commit to the fix(es) to pass them onto ARK’s Developers to get this very annoying bug crushed into oblivion?
You mentioned the ARK editor in both of your posts, which leads me to believe that was the version you were experiencing this issue in. If that’s not the case, then I’ll be glad to look into the issue for you. In the future, please specify the version of the engine that you are working in when using the UE Older Versions option, as it helps to know the exact version so that I can determine if the issue is resolved in a later version or not.
If you are still experiencing the issue in UE, feel free to provide the following information and I’ll be more than happy to take a look at it for you and see if there is a resolution, or determine if a report needs to be entered:
Could you please provide the logs from your project’s Saved->Logs folder after the crash occurs?
Could you cause the crash again and provide your Machine ID from the CR window, and ensure to hit Send on the report?
Do you have any steps we can follow to reproduce this issue in a clean project?
Also, just as a side note, we mark topics as resolved for tracking purposes only, which means you are always more than welcome to come and reopen a thread if the issue is still occurring, and we are glad to provide additional support.
Forgive me, but… how does not answering my question help?
I didn’t ask about ARK, I just said that the issue hadn’t been discovered/fixed in WC’s modified 4.5.1 engine - thus why I’m trying to get the fix for it/them. I know where the forums are, my 600+ posts on UE4’s forums are purely in ARK’s sub-forums.
I asked if a 4.5 engine bug/issue had been fixed(I’m assuming it has been by now) and if it has if I could be informed of the engine release/update containing the fix, or if I could possibly get a link to the GitHub commit that contains the changes required to fix it.
Apologies for my snarkiness but I’m tired of people just saying “go to ARK’s forums”, that’s not helpful. When trying to find solutions to the many 4.5 bugs that existed when that engine was released the amount of stonewalling is ridiculous just because the engine isn’t stock or maintained by Epic, made all the more ridiculous because this was a bug in stock UE4 which you should have known considering you posted in the bug thread I linked detailing the exact issue.
Again, my apologies but I’m just over the frustration caused by lack of communication with developers, a buggy engine and editor and generic responses of shifting the responsibility.
The crash is most definitely occurring in ARK’s 4.5.1 modified engine. I never said it wasn’t. The logs from the editor won’t help you because of this.
My question was, and I provided the internal tracking numbers that were on the afore-linked bug which is the exact same issue, if there was an update on these crashes/those tracking numbers, and as the OP on that report said the issue no longer occurs in newer versions it was fixed, intentionally or not, hence my request for further information as the person who replied with the tracking numbers said they would provide an update when/if there was one, but never responded again.
Is it not possible to find those internal reports and see if they were ever updated? If the fix was not intentional and was fixed by an unrelated update, then I can only pass on the most recent offending .cpp file from GitHub to get them to compare that with theirs to see if any noticeable changes have occurred since 4.5.1.
If however there was an intentional fix, and a commit is available, I would like to pass that on so I can get the bug fixed a lot faster than waiting on Wildcard to go asking questions or hunting through source-code themselves. Their track record is not that great in this regard, and I’ll be lucky enough just to get in contact with one of them so I’d rather have something concrete on the off-chance I can get their ear long enough to give them something.
But I would at least like an answer to if the issue was resolved intentionally with a commit or via an unrelated update and the issue just “went away”.