Gaulish Gaming Banquet: editor

pegperegogaucho

Then you can just say "We've got an issue with the Banana door!" instead of "We've got an issue with the door at memory location 0x038F6628!" "What are you talking about? I'm running 64 bits!"

pegperegogaucho

adrientd

Lol, indeed, I think at some point naming objects will be the way to go.

adrientd

I'm about to implement marker orientations rendering, and I wonder if it worth using the second orientation (pitch), since it is always or near 0.

adrientd

I even tried on the pathfinding cinematic bloc, it doesn't seem to have any effect (maybe a flag is required first?)

pegperegogaucho

Only way to find out is to check the entire disassembly :Obelul:

pegperegogaucho

I don't think it's important, we could skip it.

adrientd

Yes that's what I will probably do, so I don't have to worry about recomputing the yaw and pitch from the gizmo matrix :Obelul:

pegperegogaucho

Oh by the way, is the beacon rotation using the gizmo intended to be kind of broken? :Pauselix:

pegperegogaucho

Also, setting the choreokey to -1 from the main window crashes the editor, can you fix that in the next commit (or just remove the selector)?

adrientd

I know that for some reason the rotation angle displayed is not exactly what is done to the beacon :Obelul:

adrientd

especially when the mouse is far away

adrientd

I don't know why it does that, could be some precision error with ImGuizmo?

adrientd

Maybe I need to update it.

pegperegogaucho

It works perfectly for the squad

adrientd

I guess that you must have got the crash quite a lot :Obelul:

pegperegogaucho

Not really, I just noticed that yesterday :)

adrientd

Oh ok, but indeed this is probably a very easy way to crash the editor if you don't know what you're doing

adrientd

since you just need to press the minus button accidently and poof it crashes

adrientd

I guess ImGuizmo doesn't like that the rotation to snap to the 8-bit precision while it is being modified 🤷‍♂️

#editor