You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sorry to bother,but I have a question about 3dtiles vector data(*.vctr),I found the float32 precision is not enouth by using the following test data.
the right rendering effects is a smooth arc line,in fact the cesium rendering effects is not like that.
In addition I found the zigZag precision is not enough too。Is there any suggestions?
Best regards.
John.
var tuBuffer = [1.7888602042793667,
1.7888602218491425,
1.7888602394189008,
1.7888602569886767,
1.7888602745584525,
1.7888602921282108,
1.7888603096979867,
1.7888603272677623,
1.7888603448375382,
1.7888603624072965,
1.7888603799770724];
Hi @zero406-CC - part of the problem is that the legacy vctr format only stores uint16 quantized values. A new vector format (CC #25) will likely offer at least float32 precision. In the meantime you can try makes your tile sizes smaller.
I'm sorry to bother,but I have a question about 3dtiles vector data(*.vctr),I found the float32 precision is not enouth by using the following test data.
the right rendering effects is a smooth arc line,in fact the cesium rendering effects is not like that.
In addition I found the zigZag precision is not enough too。Is there any suggestions?
Best regards.
John.
var tuBuffer = [1.7888602042793667,
1.7888602218491425,
1.7888602394189008,
1.7888602569886767,
1.7888602745584525,
1.7888602921282108,
1.7888603096979867,
1.7888603272677623,
1.7888603448375382,
1.7888603624072965,
1.7888603799770724];
0.44911862847305678,
0.44911858692608042,
0.44911854537910401,
0.44911850383212581,
0.4491184622851494,
0.44911842073817126,
0.44911837919119485,
0.44911833764421838,
0.4491182960972403,
0.44911825455026388];
2008.03930909731,
2007.9940567584999,
2007.96180013509,
2007.9424727723599,
2007.93603485229,
2007.94247311154,
2007.9618008141499,
2007.99405777883,
2008.03931046102,
2008.09765208978];
The text was updated successfully, but these errors were encountered: