Urho3D editor crashes on component creation

when i create staticmodel, editor closes. why?

Can I assume that you downloaded the latest sourcecode from https://github.com/urho3d/Urho3D ?
And you are using Linux?

I have the same issue - there is a bug in the latest version of the editor.
If you download the older Urho3D 1.7 sourcecode from https://urho3d.github.io/ you will find that copy of the editor will work - and you can copy that working binary into your more recent source folder with no problems.

yes, im using latest version from github.
no, i use windows

thanks, editor urho3d 1.7 does works!

Out of curiosity, has anyone figured out what the issue with the editor is? Maybe we can get a pull request together to fix it.

From where I stand (Linux), this issue appears to be something to do with selecting objects in the scene - at least that is part of the issue - application crashes silently when attempting to select any scene object. No error is logged. I have not attempted to reproduce the issue under gdb so I currently have no firm details on exactly what exception is being triggered or where. Note that I can create scene objects, but I can’t select them for manipulation purposes.
Now I hear there is a similar issue in the Windows build! I was not expecting to hear that

See https://github.com/urho3d/Urho3D/issues/2384. Retested using Fedora 30 with GCC 9.0.1 and the Editor didn’t crash on me.

I have upgraded AS in the “upgrade-angelscript” dev branch which contains some upstream bug fixes. I would appreciate feedback if it resolves the issue here.

I will look into it tomorrow, I’m fried for today, the teaching course is much more challenging than expected - hopeful for an instant fix, but happy to be part of the solution.

One of the CI (Clang STATIC) build test failed due to segfault when test running the Editor, which is great because now I may have a deterministic way to reproduce the issue just by using CI instead of launching my MacOS VM.

I am observing a weird behavior from AS in the Editor that I cannot yet explain. Somehow it only happens for me when I build using the latest Clang version that Fedora 30 provides. It also means I have a way to reproduce the “issue” locally now. What I am not sure at this moment is whether it is the same issue at all because what I have now with Clang is the same with CI, segfault on starting up.

EDIT: Unfortunately it is different issue.

I am able to reproduce the segfault after a component (e.g. Light component) is selected in the Editor locally using my Ubuntu VM yesterday night. Hopefully it would make finding the root cause easier using this Linux VM later when I got time. Should all the attempts fail then I would probably consider to push Lezak’s workaround into the branch.

p.s. The Editor scripts are very ugly as the result of all these years of individual patching

Ugly code == Bugfixed code. Be proud of all those hairs and warts, because each one of them was hard-earned.

@cadaver often mentioned how the editor that comes with the engine is mainly a neat AngelScript demo. Maybe this is a nice opportunity to consider forking the *** editor that was written in the meantime?
It should be quite compatible… with the C# bits surgically removed.

I have committed a change in the Editor script to ensure the intended method binding for the StringHash::operator ==() is being called.

Oh, and there’s also Atomic Editor of course.