LY suddenly crashes 100% all the time when opening Canvas UI Editor (In any project)

What is your GPU????

Nvidia GTX 680

I don't quite understand though why any GPU would make LY crash when open the UI Editor.

Also why just since today. You really think GPU could trigger this? Can you elaborate on that?

(I actually could switch Graphics cards. I put in the Nvidia two or three days ago to see if there is a performance difference - because of these motion stutterings -and CUDA support. The other one is an ATI. I could switch back to the ATI, it's much newer and has way better specs. I would lose CUDA support though. )

Have you tried updating your drivers? I'm just trying to help you. I'm not exactly sure if this can help but I just glanced at the stack trace and someone can correct me if I'm wrong but it looks like it's coming from the renderer so I was thinking maybe it's a driver issue.

Thanks for that. Unfortunately, these are the latest drivers. I updated everything when I installed LY a couple of days ago. So I don't think this is in play here.

Deleting the BinTemp folder and going through a larger required rebuild afterwards also didn't help. Just finished that right now. I think I need to wait.

Otherwise uninstall/reinstall again. But that would be 5th or 6th time. I think I'd rather wait until the next version is released if that's my only option. But I will try switching GPUs tomorrow, who knows, maybe your instinct is correct.

You know what, I think I do this right now, why not...

No. ATI Card = same thing. But at least I tried.

FYI: I went through the whole Tools Menu. All other Editors work. (open without freezing/crashing) The Canvas UI Editor is the only exception.

I am out of ideas now. I'll wait until hopefully someone with more insight can tell me more.

Just a hail mary but another thing you might try is opening the canvas UI without having a level open in the main editor. I've found that sometimes the particle editor will mess up if I have a level open in the main editor. Worth a shot.

Might also try deleting what's in the Cache folder and doing a redo for asset generation with the asset processor.

[quote="wcb, post:7, topic:9835"] Just a hail mary but another thing you might try is opening the canvas UI without having a level open in the main editor. I’ve found that sometimes the particle editor will mess up if I have a level open in the main editor. Worth a shot. [/quote]

Did that already. :slight_smile:

Might also try deleting what’s in the Cache folder and doing a redo for asset generation with the asset processor.

Alright, will try that too.

I had this issue before, and a fresh full rebuild fixed the issue for me. It must have forgotten something in the build the first time around for me. maybe the same problem for you? not sure though.

[quote="wcb, post:7, topic:9835"] Might also try deleting what’s in the Cache folder and doing a redo for asset generation with the asset processor. [/quote] No. Didn't work...

[quote="WashedUpStudios, post:9, topic:9835, full:true"] I had this issue before, and a fresh full rebuild fixed the issue for me. It must have forgotten something in the build the first time around for me. maybe the same problem for you? not sure though. [/quote]

Thanks for the info. I really hoped I didn't have to reinstall again. Did that already 3 or 4 times... That's all in all ~20 hours uninstall/reinstall already in 8 days or so... . :face_with_head_bandage:

What I really don't get is that it just stopped working today... Nothing changed since yesterday. The last couple of days were fine, I used the UI Editor without any problems.

Well, I know you've been messing with reducing the size of your executable. It may be the case that you disabled like, LyShine Samples gem or something and it may be trying to load them and crashing it.

You can't disable LyShine. I've looked into that right in the beginning as stated in the original post:

[quote="Lytz1, post:1, topic:9835"] Because LYShine can’t be disabled/re-enabled as a GEM I don’t know how to approach this. [/quote]

It is required 100%.

Also if you would disable a GEM it wouldn't be available in the editor in the first place, no? :slight_smile:

Yeah. I think it's beacuse LyShine actually requires some components in the LyShine Samples gem for some reason.

If that's really the case the "Samples" should also be marked as "required" and forced to stay selected if otherwise the whole friggin' engine falls apart... 😂

@REDACTEDUSER

tagging this so someone on the team sees it. This is actually really important because I've also experienced this. LyShine samples should be marked as required or all required components moved to LyShine gem.

Hey @REDACTEDUSER

Thanks for letting me know, I'll ping someone from the LyShine team about this.

Cheers!

Tom

@REDACTEDUSER

Created an issue for this LY-123012. After investigating, I don't believe there is a dependency from LyShine to LyShineExamples. Here's the relevant section from LyShine's gem.json file:

"Dependencies": [
{ "Uuid": "ff06785f7145416b9d46fde39098cb0c", "VersionConstraints": [ "~>0.1" ], "_comment": "LmbrCentral" },
{ "Uuid": "5a149b6b3c964064bd4970f0e92f72e2", "VersionConstraints": [ "~>0.1" ], "_comment": "Texture Atlas" }
]

And here's a search by UUID of all of the gems that do rely on LyShineExamples:

rg -F c7935ecf5e8047fe8ca947b34b11cadb --iglob *.json AutomatedTesting\gems.json StarterGame\gems.json SamplesProject\gems.json ProjectTemplates\AtomTemplate${ProjectName}\gems.json ProjectTemplates\DefaultTemplate${ProjectName}\gems.json LargeWorldsTest\gems.json Gems\GameStateSamples\gem.json Helios\gems.json

I tried it out and disabled the LyShineExamples gem, and was able to launch the UiFeatures level as well as the UI Canvas Editor without any issues.

When referring to "launching" the UiFeatures level with LyShineExamples disabled - none of the canvases within the level actually load (since the canvases live in LyShineExamples). But the level itself is able to open, close, and enter/exit game mode without any crashes.

OK. I know that this person @REDACTEDUSER

So based on that I presumed Lyshine requires something in the lyshine samples gem regardless of what that JSON says.

This is true. Also:

[quote="WashedUpStudios, post:9, topic:9835, full:true"] I had this issue before, and a fresh full rebuild fixed the issue for me. It must have forgotten something in the build the first time around for me. maybe the same problem for you? not sure though. [/quote]

So I am not sure if this really can be eliminated 100% as the problem.

@REDACTEDUSER Which version are you using? Maybe something silently changed in 1.27? I uploaded the error.dmp etc, maybe someone already looked at it? IDK.

Then again it seems that sometimes LY behaves quite randomly on different systems. I don't know. But anyway, reinstall helped here.

Whoa. Same thing again right now. Just like that.
I think it might be true that the shine examples might not have anything to do with it. I didn't touch any gems the last couple of days.

The only thing I did is I switched projects to a different one (where a rebuild was required, so I didn't want to do that because -> time... time... time...) and then back. And then UI broke again.

I am switching to a new system in a couple of days, then I need to reinstall anyway. So no big deal. But man, someone really should take a look at this...

(BTW: In this project I use the render to texture gem, rendering something from the UI onto geometry in the 3d world. Render to texture is tagged as "experimental", so maybe that has something to do with it? Not sure if anyone else who had that problem can remember if they might have used the render target feature as well...)

I use render to texture with no issue, when you rebuilt your other project did you just do game and engine or all? Because with just game and engine it should not break like that, all will transfer game to game with what you rebuilt that I can see.

No no, I always build game & engine -p.

Was just a guess. But unfortunately it seems no one can do more right now than guessing... Until someone takes a look at the error dump. :slight_smile:

Like I said, I think there is some random shenanigans going on from time to time.

We'll see how everything goes when I have the new system running. The actual one behaves a bit wonky in general with several applications.