Sweet view texture resolution inconsistency

[Anonymous_aa64e24c61]

I’m following up on this thread: https://support.capturingreality.com/hc/en-us/community/posts/360008861832-Sweet-View-texture-resolution?input_string=Texture%20view

Experimenting with unwrap reaolution I can now show that it is indeed a bug.

All three examples are exactly the same geometry and alignment, only the unwrap is different. The model is geo-referenced to 1m per unit.

Here you can see the unwrap with 0.001 texel size, very close to the Optimal Texel Size - the 3D model is not to far off the original resolution of the images:

 

This is the unwrap with 0.01 texel size, as to be expected much less sharp but still ok:

 

Finally, the unwrap with 0.002 texel size, which was created last. It should be close to the 0.001 unwrap, but look how it looks like instead:


[Anonymous_243cb9bf6e]

Hello Gӧtz,

I tried to reproduce the problem with the similar unwrap settings but did not encounter this issue. Do you have this problem with all models? Also, can you please try to use clipping box and display only small part of the scene?

[Anonymous_aa64e24c61]

Hi Zuzana,

the clipping box does not change anything - the texture is still being loaded for all the model, as I can tell from the slow progress.

And no, it only happens occasionally, the first time when I posted the linked thread and the second time now. The fact that it happens within the same project and with identical geometry indicates to me that it is random and related to the display of the 3D view…

[Anonymous_243cb9bf6e]

It is standard behavior that RC sometimes does not display the full texture resolution. As mentioned in the linked thread, RC is trying to fit them to max one 16K texture (or 4 8K textures, 16 4K textures, etc.). Therefore, the textures in the 1st case and the 3rd case are scaled to fit the GPU. 

To better understand the situation with your 3rd model, can you please share with us your GPU specifications, especially the size of VRAM? Also, would it be possible to share with us the project file and folder with these three models and their textures so that we can test it on our side?

[Anonymous_aa64e24c61]

Hi Zuzana,

yes, I could in theory do that but the project files are about 6.4 GB and that might blow my flatrate.

Is the texture not incorporated in the project files?

[Anonymous_243cb9bf6e]

Hi Gӧtz,

yes, it is. We need only the project (project file and folder). I meant to delete all other models from the project and keep only those three models with textures to minimize the size of the project. Would it be possible to upload it for example via Google drive?

[Anonymous_aa64e24c61]

Ah ok, that’s what I did and it still has 6,4 GB.

Shall we start with the model that doesn’t work, 0.02?

As I said, the first two (0.01 and 0.001) behave exactly as expected.

I don’t use google drive and my usual service (Zeta Up) only allows for 500 MB. Don’t you have some upload space on your servers?

[Anonymous_243cb9bf6e]

Unfortunately, it is not possible to upload on our servers due to security reasons. Would it possible for you to use some other service? For example MediaFire or Mega?

And yes, if possible send us at least the 3rd model. Thanks.

[MikeS11]

Gotz did you find the issue ?

I’m having a similar issue but where the sketchfab autotexture was much much better quality @ 27% texture quality than anything I can unwrap and redo manually with multiple textures … Both at 8k textures.

Oddly I can have 85% texture quality with 80% utilization and it looks terrible next to the 1 texture file 27% quality 86% utilized sketch fab auto.

[Anonymous_aa64e24c61]

Hey Mike,

I haven’t followed up on this yet because as usual real life got in the way… 

Anyway, for me it is not too big a problem because it is merely a display issue, the texture itself is fine.