Dear Toni, I'm a bit surprised from your conclusion from the indeed good discussion from Monday. > 1. Ability to free memory: currently xml3d.js never frees memory This is wrong. We only talked about external loaded resources being cached for possible reuse. This is NOT related to any other memory managment in xml3d.js. The caching strategy for the raw data can be improved and I filed an issue for that: https://github.com/xml3d/xml3d.js/issues/25 Even without this we can easily load and render scenes of large sizes. > 2. Ability to load data in the background (parse meshes in worker): > currently xml3d.js loading can be synchronous only Doing this is in the responsibility of the mesh format handler plug-in and is possible today (though not tested). However, we want to provide a better integration with the resource management. https://github.com/xml3d/xml3d.js/issues/24 > (already known: 3. Support for gpu-supported texture compression > (speeds up the loading to mem too)) https://github.com/xml3d/xml3d.js/issues/23 Kristian -- _______________________________________________________________________________ Kristian Sons Deutsches Forschungszentrum für Künstliche Intelligenz GmbH, DFKI Agenten und Simulierte Realität Campus, Geb. D 3 2, Raum 0.77 66123 Saarbrücken, Germany Phone: +49 681 85775-3833 Phone: +49 681 302-3833 Fax: +49 681 85775–2235 kristian.sons at dfki.de http://www.xml3d.org Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 _______________________________________________________________________________
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy