Back to the Shapespark home page

Lag while moving camera in Full Screen Mode


I have recently made my first project with Shapespark, and I found out that the camera movements is smooth and lag free when I play it on my mobile. However, when I play it on my PC on full screen, the camera movements are very much laggy and feels like it’s lower than 10 FPS. When I play it in minimized mode then the transition of camera movements feels ok.

Can anyone tell me how can I solve this issue and get a smooth and lag free camera movements in Full Screen mode on my laptop.

My scene is uploaded on :

We are aware of one similar case where FPS on desktop Chrome is slow when in a full screen mode. So far we haven’t been able to pinpoint the cause of this lag. Do you have Firefox browser on your laptop and could you test if Firefox works well?

OMG ! It works super smooth on Internet Explorer and Firefox. Haven’t tried it on Safari yet. Can you please fix up this ASAP, as Chrome is currently the No.1 Browser used worldwide and it can help a lot of ShapeSpark users…

To clarify, this is specific to some certain hardware configuration or drivers (we are not sure yet), normally Chrome works without such performance issues.

I see. However, this issue is same on my client’s PC, my alternate PC, and my friend’s PC as well. I have been testing this issue with all types of PCs but it seems it’s the same performance everywhere.

If you see it on all computers it must be some other issue. Could you upload a version of this scene without a video texture and see if it also has such problem? You can make a copy of the scene folder in Documents\Shapespark\ folder, not to remove the video from the original scene. As this is a rather small scene, perhaps a video codec or video resolution is causing troubles on Chrome. Shapespark is using video textures as uploaded in the editor, without any format transformation or resolution reduction, so a high resolution texture could cause performance issues.

Yes, I did feel that the performance improved when I removed the video texture. However, it wasn’t a perfect experience and there was still a visible lag which compromised user experience.

I had few doubts in my mind

  1. Can using too many lights in a small scene affect performance ?
  2. Can using too many textures on materials affect performance ?
  3. Can using too many light probes affect performance ?
  4. Can using too many reflective materials like glass or metal surfaces affect performance?
  5. Can using a large file size of HDRI image as Sky affect performance?
  6. Can the number of triangles in the scene affect performance?
  7. Can using High res Light map affect performance as compared to low res Light map?

I have seen many scenes made using shapespark and have observed that many users don’t use full capabilities of the software in terms of material finishing and light baking. Is this something I should consider when I make my scene to give best performance and user experience to my clients ?

One surprising thing is that all of these performance issue only arises as I enter full screen. The experience is lag free when I view it on an embedded popup. So, I think there is something wrong only with the full screen mode and not with everything in shapespark.

To clarify by ‘full screen’ do you mean after pressing the f button, so the only thing on the screen is the scene, or when a browser occupies full screen, but still has address bar visible?

As for your performance related questions. Only the number of lights and size of the sky texture does not have any impact on runtime performance. This is because lights are baked, and are nor processed at runtime, and the sky texture is automatically scaled down, so no matter how large the input texture is, the output will have the same resolution.
Textures, light probes, reflective materials, geometry size and lightmap size all have some impact on how much work GPU has to perform. For smaller scenes this impact is negligible, because the GPU is still able to render 60 frames per second even if you add more textures, increase the lightmap resolution, or add a couple of additional objects.

Games usually have a lot of budget to dedicate to optimizations to ensure smooth performance on all devices. Archviz projects have much smaller budgets and much shorter time frame. Most Shapespark customers can’t afford to spend a month optimizing a scene and finding rendering bottlenecks on different devices. It could be more reasonable to follow a couple of rules of thumbs:

  • Try to use not more than 2 lightmaps
  • Try to keep the geometry size in 2-4 millions range. Often a scene will have a couple of very detailed objects, and replacing them will decrease the size significantly, without much work.
  • Usually, reducing the number of textures is not needed. Looking and Shapespark scenes, it looks like it is much easier to include complex geometries in a model than to include enough texture for them to become a performance bottleneck.
  • Use at most one light probe per room. If you have rooms without any interesting reflective materials, or rooms that are not important from presentation perspective (like storage), don’t include light probes there.

Look at other Shapespark scenes posted on this forum to see how large scenes are reasonable. Most scenes are apartments or houses. There are many office spaces, but they require more optimization work. Large projects, such as often target only desktop devices and could require a lot of additional work to run on mobile.

1 Like


Thanks for writing in brief. I am clear on what the best practices are when making a scene now. By full screen, I mean when I press “F” key. The overall movement lag comes in when I enter F key mode. After optimization, I was able to reduce the lag somewhat, but still it’s not perfect and smooth like it is for other browsers like Firefox and Internet Explorer.

One more questions: is it constant lag with unusably low frame rate, or is it an occasional freeze and jump that happens every couple of seconds?

Yes, it’s a freeze and jump type of effect. It doesn’t lag continuously.

I have decreased movement speed and the effect has visibly reduced.

1 Like