All Activity

I think I need to know the current frame of an animated model in order to get root motion working for animated objects. Is this something that can be added easily enough?

Join us on Discord every Saturday at 10 AM PST for a live chat to review the week's progress and talk about upcoming features. https://discord.com/invite/qTVR55BgGt

I think combo box for component field should not be changed by mouse scroll until i open it. I'm changing a values all time by accident when i scroll entity proprieties widget.

Fixed!

That's the correct behavior. The properties show you the rotation of all entities. If their rotation x, y, or z value is different then the field will be blank, indicating there is not one single value for all selected objects. If you change a rotation value in the properties, that change is applied to all selected objects.

Before modifying the sRGB / linear equations I think we should try storing cubemaps in linear color space. I was already planning this, but wanted to talk about it this weekend with you guys and explain the reasons for it, before making any further changes. Let's see what the result of that is after we try it, as it may eliminate this problem.

Working for me now

Okay, I think the main problem is permanently fixed. There is still a rare situation that could trigger this response but I have only seen it happen once in the entire time this system has been running.

Description: When dragging an instanced mesh from the assets into the Ultra Engine editor, it is expected that a collision collider can be added directly in the environment by selecting the mesh in the assets. However, the collider, although visible in debug mode, does not have physical properties and does not react to collisions. On the other hand, if the collider is added to the mesh before dragging it into the environment, it is visible in debug mode and functions correctly with collision physics. Steps to Reproduce: Open Ultra Engine. Drag an instanced mesh from the assets into the editor environment. Add a collision collider to the mesh by selecting it in the assets. Observe that the collider is visible in debug mode but does not have physical properties and does not react to collisions. Remove the instanced mesh from the environment. Add a collision collider to the mesh while it is still in the assets. Drag the mesh with the collider already attached into the editor environment. Observe that the collider is visible in debug mode and reacts correctly to collisions. Expected Behavior: The collision collider should have physical properties and react to collisions when added to an instanced mesh after it is dragged into the editor environment. Actual Behavior: The collider is visible in debug mode but does not have physical properties and does not react to collisions when added to an instanced mesh after it is dragged into the editor environment. Additional Information: Version of Ultra Engine: [Please specify the version you are using] Operating System: [Please specify your operating system] Any other relevant details: [Please add any other details that might help] Thank you for your attention to this matter. Chat GPT

With the gizmo it rotates perfectly when I have several selected With the gizmo it rotates perfectly when I have several selected. They rotate in relation to a center axis, when I pass values directly in the editor window the rotation is done locally on each element.

In prefabricated products, it is already working properly. But in grouping of several brushes the beam does not coll

It already works for prefabs, however if I group several brushes under a parent brush, it does not work

There appears to be some small error with very low values near zero in the linear to srgb conversion...

There is something strange happening. It doesn't even have to be transparent. It has something to do with the diffuse PBR reflection and the metal/roughness map I think...

Confirmed, I am investigating...

According to the discord talk here the bug report. If you take the model i sended you last time and drag it into the scene you can see some "circle" appearing within the windos. It also happens in the scene editor. Within the model viewer everything works fine.

Still not working the client simply states that the license is not active...

I blocked the account that is causing the problem...hold on...

I've given it a while and the problem is still there...

Will do...

Give it a few minutes maybe....

Hmm. still not working though...

No worries I think that sort of thing might become more and more common - at least its secure! :-)

Sorry. I fixed it. Our website is currently under a sort of attack. There is no danger of any security being breached, but it is triggering some automated security responses.