Apple Mobile not working & color issues in V4.

Thank you for the file. We reproduced the issue and now looking into.

prettypicturegirl wrote:

I really do not know how to condense the model further, tried remeshing with Quad remesher, but it does not seem to reduce the faces by much.

There’s a lot of things you can do:
1. Remove unnecesery polygons that do not form the shape of the model.

2. Bake normal maps for tyres (like it done in Scooter demo) to ruduce amount of poligons. The tyre is very simple in mesh but have a lot of details on it.

For more details look at this video and this article.

prettypicturegirl wrote:

Can you point me to a tutorial on how to do this in the most simple (!!) way?
Neither my client nor myself use Blender for actual modelling.

You can use decimate modifier for some models, for tyres better to do a retopology. There’s a lot of videos on the youtube jsut type Retopology Blender, optimize mesh. It’s a common thing in realtime graphics. Or you can use such tools like retopoflow for tyres and decimate modifiers for other meshes.

prettypicturegirl wrote:

They use SolidWorks, I use Rhinoceros.

I worked as engeneer-designer about 5 year, it was my main workflow^ Solidworks => Blender for rendering, previously I workd with 3ds max about 7 year and found blender best for optimizing mesh from engeneer CAD software.

prettypicturegirl wrote:

Hence baking and such is something I have not done before.

It’s commong thing in realtime graphics, just type baking normal map in blender.

Hi there, I find this subject interesting so I downloaded your scene and tested it out.

The app is hosted is still on 3.9.0 so moving it to 3.9.1 would be my first suggestion. If this is for a client you dont want to be using 4.x at this time…its all alpha with lots of bugs that has to be worked out….stick with 3.9.1, otherwise you are fighting things that are broke that you have no control of anyway. Just figure you should minimize your difficulties.

The rest of this assuggestions only and is meant to give you a point of view. You have obviously spent a lot of time on this project and its looks like it’s nearly complete so good job.

SolidWorks and Rhino…great packages for engineering. I am an engineer as well so greatly familiar with these. Using these packages and only rendering in Blender..ya you can do that all day and get good results. However, creating models for WebGL / V3D, these are not your best tools. It can be done but it’s like trying to unscrew a phillips head screw with a butter knife. Ya, it can be done but you usually mess up the screw head and you definitely cant torque it much. Your tools whether it’s MAYA, Max or Blender are designed to generate the geometry you need for WebGL. I might even argue that Blender is better suited than the other two. You are far better off learning blender….go through the basic online doughnut tutorials and get a good understanding of how to poly model with good topology. It will save you so many headaches in the future. As an example your poly count is 1.64 million triangles…when the scene probably could be done with under 100K triangles and would take less than a day to create from scratch. Just giving you a perspective on the cost of trying to fix a CAD model to work vs just making it new.

General experiences working with CAD files and getting them to work for game, low poly and Verge3d scenarios. The general rule…use them as a guide but don’t use them. Dont descimate them, dont do anything to them. The best approach is to create a low poly model you create and then bake the normals from the high poly CAD model to your model. You will end up with a very low poly model that can be easily modified. Yuri goes over this with the scooter tire example. There are lots of demos on how to do this on Youtube too.

Regarding your tires – Given you are controlling the camera zoom and not letting the user get close to the tires…why not just dump the tread and get the benefit of the reduced poly count. Additionally, since the two tires are the same. I would delete one completely and duplicate link it or clone it once in Verge3d. Same for the rim I would imagine. Since the camera is so far away and based on the current lighting there is no way to see the tread so why have it in the scene? My two cents.

tris vs quads – In general, you want to design/develop in quads to keep good topology so you can easily add detail/loops if needed to tweak things such as light bounces on a bevel, etc. If your geometry has triangles…you are forced to use generic tools that really only hurt your end result more than help. According to the Verge3d documentation you want to keep things in Quads but an occasional triangle will not hurt anything.

One issue I am noticing on almost all surfaces is z-fighting. The camper shell and shadow are the most obvious. Since the shadow is breaking, I would adjust the camera near and far clipping planes. There could also be geometry issues. As an example, the treads on the tire are separate objects placed over the tire geometry leaving faces under the tread. Because the two outer faces are close together you can experience z-fighting, not to mention extra poly counts that serve no purpose.

Problem with light probes – you have an error still with 0 cubes reporting but 3 planes reporting. Given the scene, I don’t see any use for reflection cubes at all…I think you could take them out

Lighting – you have a light that adds performance-related issues.
You don’t have any parts animating in the online version so there is no need for a light to produce a shadow. You are better off baking a really nice shadow onto your floor and getting a performance gain by not having the light. Unless you just want clouds to be a part of the reflection of the solar panels you might be better served with a studio lighting map than clouds…you can always add the cloud as a texture to the soloar panel.

Doing this all in Verge3d – you have done a lot of work making this configurator and I think that’s great but you are now wanting it to work on iOS/mobile. Verge3d will scale the scene by default vs being responsive making the buttons and things smaller than mobile standards for button sizes/targets. Before going much further down the road you may want to consider doing the menu in HTML/CSS rather than V3D and having proper responsive menus.

Any way…these are just suggestions… and worth two cents only.
Good luck on your work.