well, i know the api. unfortunately this all just reads maps from disk again. daz uploads them to ogl and don't keep them in ram. i have asked for a signal during loading, but even if there will be ever a new sdk and more surprising with such a signal, it would be tricky, since it is not possible to create the octane materials at this point, and pre-caching all maps in ram would be no good idea also. moreover, when storing octane data from its own xml format, octane loads the maps again from disk whenever a node is created from the xml export string (which would need even more complicated stuff to avoid).asennov wrote:dzApp->getImageMgr()->getImage("T:/mytextures/tex.jpg")->getImageData(targetQImage);
or some of findImage methods of DzImageMgr?
and as i said: i work with non-thread-safe apis, and obviously most thing i do need to access either one or the other. my most intensive task in the ui thread is mesh building (world coords translation, triangulation, uv-checking, etc.) which needs around 100ms per 1mil. polys on a typical quad-core. and it needs to be in the ui thread as otherwise either octane or studio will crash, or the geometry data is going to be messed up. i have tested that all, more than once, and i use threads where it is possible and at least a little useful.
and now i'd say enough of that; hope you got some picture of what happens and what not and why.
ps: when something feels fishy, in particular in such cases a video would help to judge if i need to look for a possible problem; and in that case to open an internal event monitor by pressing ctrl+alt+shift+m before doing one.
). I've just rendered that shot with low spp for speed and interactive updates turned on and there are 2 frames of 180 with this problem.
