Ivan Lyubovnikov

Here’s the link: https://www.soft8soft.com/product/verge3d-tech-support-and-consulting-plan/

Hi dibeholder,

This happens because you set the ssr resolution multiplier to 10 in the puzzle. That means that the ssr effect needs a buffer 10 times larger than the viewport size. WebGL has limits on the maximum resolution that you can use, and it simply won’t work if you exceed the limit.

That’s why it works in in the puzzle editor where you have a smaller viewport and doesn’t work in the final scene where it’s almost fullscreen. I’d recommend to set the resolution to 1 and increase it only if the quality of reflections is not satisfactory.

Holt_Interactive wrote:

I can provide a link to the published file, but I’d rather get that to you outside of forums as my client is confidential.

We provide private support only as a part of a techincal support plan or for enterprise customers. But you can try to isolate that issue in a simple test case and post it here. Most likely, it’s related to the camera limits, positions of certain objects and the puzzles that run procedural animation.

Also, the vertical and horizontal rotation limits are calculated in the world space regardless of the camera’s orientation. For example, the default values for the horizontal limits are 0° and 360° degrees which means no restrictions at all. But if you change it to something like 50° and 250°, then the camera won’t be able to move/rotate into the sector which lies outside those limits. Unless you tween the camera to such position. But then it will be snapped towards a limit after the procedural animation ends.

So, if you’ve changed the rotation limits on the camera, then that’s probably the cause of the issue.

Hi,

I noticed in the video that you started dragging over some other object. Does this still happen if you start dragging when your cursor is exactly above that Deckel object?
Also, is that object parented or does it have any constraints?

Thanks for the input! BTW, supporting metaballs is in our TODO list, so they eventually be exported as meshes and will be rendered too. For this reason it’s probably better to use Empty objects instead.

Hi Rick,

Unfortunately, that material cannot use more than 5 shape keys because it’s also used for a skinned mesh. The documentation here says about the limit of 6 shape keys, but in case of skinning or using certain nodes we can only support 5 while 6 will cause the error that you have right now.

We’ll update the documentation to make it more clear how many shape keys you can use exactly depending on a particular material/mesh setup. We’ll also think about how to increase the amount of supported shape keys, but it’s not a high priority task for us right now.

Hi,

GLiFTeK wrote:

turns out the hover over won’t work while user’s button is pressed while dragging another object.

The reason this doesn’t work is that “when hovered” considers only the first or in other words the nearest object that appears under the mouse cursor. And in your case it’s the object that is currently being dragged. That means that when you are dragging an object you are also constantly hovering above it :)

I think we can implement an option for “when hovered” to check not only for the nearest but for all objects that appear under the cursor. We’ve added this task to our TODO list.

UPDATE: we supported the Custom Distance option in the recent Verge3D 3.3.0 version.