xeon

yup…turning off Camera Panning will solve the problem

the issue you are going to have to over come is what the ASDW keys do natively vs what you are trying to add to their functionality. ASDW will move the camera by default.
So if these are the keys that you have to use….another solution would be needed.

If you are using a First Person Camera….the commands will work after the camera is moved.
If you are using No Controls on your Camera the command will work instantly
If you are using Orbit the ASDW keys other than camera seem to be ignored.

• This reply was modified 3 months, 1 week ago by xeon.

Can you show you puzzles that you are using?

You will find that many of your presets / settings from 4.1 will need to be updated manually in 4.2.

In you 4.1 file check your cameras clipping distances, record them. Then in. 4.2 check them and set the to what you had in. 4.1. You may have to do this for your view port cameras too.

Any chance you can share your project ?

1. Does the slider appear when you test your app?
2. Is the html slider apart of the project html or another page?
3. Are you implementing this in an ifarme and your slider is in the main page housing your iframe?
4. Where in your puzzles did you put the print console puzzle? Is it after your set variable?

Hi there,

I think lighting and of course shadows can make a break a specific projects that heavily rely on lighting. Using physical lights have a significant performance hit that many projects cant afford and in those situations, baked AO, shadows and lights are more performant but there are situations where physical lighting just has to be used and in those situations I have found that Blenders standard lighting techniques and methods work quite well….with the notable exception being shadows. If I recall the V3D asset store has a free demo called the Tea Ceremony, that might be helpful. Soft8Soft often references the Scooter demo as a preferred way of lighting that may be helpful too.

I have often thought of a tutorial on shadows but I find there is no general rule that I find common to all projects with respect to dialing in good lighting / shadows. The lighting and shadows are always based on light proximity, and other details unique to a scene.

However the basic lighting principals that you can find many tutorials on youtube for blender will work in V3D…you will just need to refine the Verge3d Settings for things like blur radius, ESM bias, Shadow Filtering, Map side, cube size, cascade size, high bit depth, soft shadows, light threshold,.etc not to mention light position and intensity. All of these things vary with the version of Blender and Version of V3D you may be using.

Blender has some plug-ins for 3 point lighting that will generate and allow you to easily modify the settings and it will output properly for V3D.

If you have a scene you are trying to replicate or an image that shows the look you are trying to achieve, share it / post it and people on here might be able to guide you to a quick solution.

Depending on which version of blender and V3D you have updated from to 4.7.1 your shapekeys targets and may need to be redefined.

I would suggest testing if that your issue.

Lights are expensive when it comes to performance. They impact redraws, triangle counts, shadow maps… and overall costly. They require lots of calculations when turned on and off. To avoid this…you may want to bake your shadows and and lights and just control lights on and off with texture changes rather than physical lights far more performant.