liu.yan Posted August 25, 2017 Share Posted August 25, 2017 Along with the growth of our project, more and more enormous objects are generated in the context, therefore, there will be an obvious screen-pause the first time we invoked method "getIntersection" of a huge object. This pause only occurs at the first time we invoke that method, hence we speculate that there might be cache mechanism at the first time invoking that method, if so, can we finish that kind of caching ahead of calling "getIntersection"? but, again, that's just a speculation. After all, all we need is the solution or suggestion to solve this screen-pause problem while invoking "getIntersection" of a huge object at the first time. Looking forward to your replying. Link to comment
silent Posted August 25, 2017 Share Posted August 25, 2017 Hi Yan, You can do this intersection tests during startup in custom "warmp-up" procedure (during the loading time) and then just use all the methods you need. We are doing similar thing in Superposition (during the loading time we preapring all the objects, "warming-up" shaders and so on). That will be fastest solution to implement I think. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
liu.yan Posted August 25, 2017 Author Share Posted August 25, 2017 another question is when is that custom "warming-up" procedure suppose to happen, in other words, where should we add our methods in code, Link to comment
Recommended Posts