-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor crashes if component variables are edited #53
Comments
It doesn't crash for me doing that, you'll have to provide some sort of crash report. Also though if spamming editing that particular variable is the only cause it wouldn't be in the plugin regardless. |
This is strange. I tried to replicate it again and it threw a different error than it did yesterday (yesterday it was something related to reading null pointer in primitives code, now it's this). Appears to be an Unreal Editor bug of some kind, sigh, this silly engine never seems to just want to work without issues. It just bothers me a bit that it started occurring after I installed the VR expansion plugin, and might sometimes occur on first attempt to edit the variable (and thus crash the editor and nuke all of my progress). It usually occurs after hitting "play" and stopping the game at least once.
EDIT if you'd like to check out the exact project where the issue occurs, it's live in this open source repository: https://github.com/Meow/AsymmetricVR |
Are you sure you aren't running out of memory? |
Yes. It barely uses 2-2.5GB of RAM at the time of the crash (and total system memory usage is less than 25%). VRAM usage also sits under 25% utilization. |
Talking about disk memory, but dunno, I don't know anyone else with this issue and its not plugin related. |
I have 350GB free SSD space and only 1 partition. |
I've been getting this specifically when a GrippableSphere is the root node of a Blueprint Actor, I have an attached Niagara component, and I connect "On System Finished (Niagara)" event to "Destroy Actor" targeting self. With that event in the graph connected to Destroy Actor, I can't change any dropdown variables on the GrippableSphere without crashing. |
That is for sure entirely not plugin related, when the properties in editor are modified the way the engine works is that it reconstructs ALL of the components of an actor so that the preview shows it fresh (very expensive and weird but it does ensure that everything is correct). Its likely causing your particle effects to die trying to kill the temp actor the editor displays. |
That was what I thought as well, but when I recreated the exact same setup on a normal SphereCollision, everything worked as normal. It was only on GrippableSphere that it crashed. It's not a horribly work-stopping bug, though (at least for me) because I can just disconnect the nodes if I want to change anything, and reconnect them after. |
The exact same log / crash message? Because I doubt that, the one there is regarding page file allocation and there isn't a single custom thing in the grippable sphere that would interact with that. |
You're right, they are different. I've been getting that same access violation error at random times the time across the last 3 Unreal projects I've worked on and assumed when I shouldn't have. That one's probably an editor bug. My GrippableSphere-specific crash code is an assertion error:
|
The editor crashes with this plugin installed in Unreal Engine 5.4.3. Steps to reproduce:
Unsure if that's an Unreal Engine problem, or the plugin problem. Would appreciate any help regardless.
The text was updated successfully, but these errors were encountered: