Hi,
On Wiki Delay refers only to extra time penalty of some LSL functions
"... to appear immediately" yeah.. miracles...
http request must be async, or the entire script engine with just
stall awaiting for it...
This http request will be far from fast, depending on network
conditions and image size. Also having several to same endpoint, they
will be serielized ( ie only one after the other ) by the low level or
even the endpoint service. Google machines are not there to be flooded
by just you..
Processing uses a lot of CPU. The image must be converted from
original formal (like jpg) to JPEG2000 (using CPU only) and viewer
texture asset format.
When all that is done, viewers need to be told and then get the
texture.. add several more ms if not seconds..
Far Far from "... to appear immediately" in fact you may just
freeze the entire region with a few requests...
Ubit.
On 28-Apr-21 15:56, Dr Ramesh Ramloll wrote:
Hello,
The wiki says,
We are updating one of our applications that use StreetView images from
Google Maps and we use this function to display the images.
Ideally, we want the 360 surround views from Google to appear immediately
... so we used this function,
osSetDynamicTextureURLBlendFace()
which is supposed to have 0 seconds delay.
Not only does it not have 0 second delay as the opensim wiki says, but it
is also an asynchronous function, i.e. if you are loading n images ... it
will take n x delay for 1 load. We can makes things work after ploughing
through this friction ... but
Is this expected behavior?
Regards
Ramesh
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
