Hola
He estado trabajando con los camera volume trigger para audios, me ha pasado que ingreso a la edición del tamaño del volumen se congela y no puedo salir! simplemente tengo que apagar la ventana general de edición pues de lo contrario el programa no responde. He notado que despues de confirmar una vez y luego volver a editar, a la segunda ocación el programa se congela!
Me estoy dando cuenta que a pesar que genero audios no logro salir de la edicion de triggers y tampoco me permite salvar, asi que no puedo avanzar en mi trabajo.
Saludos
Jorge
1 Like
the same problem here, plz resolve that.
Thank you for the report. We are looking into this issue.
Hopefully we will be able to resolve it today.
I’m having a hard time reproducing this bug.
Could You explain step by step, what has to be done for the bug to show up?
It doesn’t always happen to me.
It’s irregular.
It happens to me sometimes with the camera trigger volume.
The fundamental problem is that it doesn’t let me out of the action window, I can’t choose to move to another window like materials or lights.
You can go to this address, it’s in this project that’s happening to me. You can check that in the Racing zone there are buttons to drive audios that I just can’t generate Because when I choose that button as a trigger to an audio, then I can’t get out of the stock window and I have to close without saving, so they didn’t do it.
1 Like
We have released a fix for this issue in our cloud editor.
Could you please check if it solved your issue?
If yes then we will release it in the desktop editor tomorrow.
Sorry for the inconvenience, but this bug was hard to nail down 
1 Like
Thanks @krzysztof for the follow up.
I can’t open this scene in the cloud editor because it has more objects than the editor can support, but I’ll try to generate the error in other models inside the cloud editor and let you know.
Anyway, it would be nice if we could test the improvement in the desktop editor, if it doesn’t work, we keep trying, we lose nothing!
I’ll keep you posted
Regards
We’ve released Shapespark 3.3.2 with a fix for this issue.
If for some reason this problem still persists, please let us know
1 Like
Greetings @krzysztof
Thank you for your rapid response and for repairing that bug!
I hope it will let us work and of course if I find another problem I will be informing you.
We will be in touch.