Hi, Good discussion. Please keep this up. Identifying issues people have or assume they would have is the best way to make progress in the group as a whole. It sounds that eliminating these issues should be fairly straight forward. Best, Philipp Am 30.10.2013 14:45, schrieb Jonne Nauha: > Yea I understood that the CPU side mem is not freed eg. the js side data > from the XHR response. Did you have GPU mem unload when xml3d mesh nodes > are removed from the DOM? You had the auto detection how many things are > still referencing to a particular asset, so when the last one is removed > it could be unloaded from GPU. > > It could also be nice if there is a API to unload assets from code, not > by finding all the nodes that use it and removing them from the DOM. The > dom nodes could be left alone but just unload the mesh under it, it > would then just not render anything until the mesh is loaded back. Does > this make any sense in the context of xml3d? > > Do you have any time estimates for custom loaders supporting async > loading? What about compressed textures? These are probably the > significant things if someone wants to try prototyping something with > xml3d + Tundra scene model. We need custom Ogre asset loaders and we > need compressed textures for efficiency on big scenes. I'll assume the > CPU side mem releasing is a non issue and fixed trivially. > > Best regards, > Jonne Nauha > Meshmoon developer at Adminotech Ltd. > www.meshmoon.com <http://www.meshmoon.com> > > > On Wed, Oct 30, 2013 at 11:35 AM, Kristian Sons <kristian.sons at dfki.de > <mailto:kristian.sons at dfki.de>> wrote: > > Am 30.10.2013 10:12, schrieb Toni Alatalo: > > Yes this referred to external loaded resources only — as that’s > what the city model blocks have, right? > > Yes. And only to the raw response data from the XHR. > > > > >Even without this we can easily load and render scenes of > large sizes. > > But only ones that fit in memory at once, no? The new city model > does not. > > > How large is your city model, anyway? > > 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 <tel:%2B49%20681%2085775-3833> > Phone: +49 681 302-3833 <tel:%2B49%20681%20302-3833> > Fax: +49 681 85775–2235 <tel:%2B49%20681%2085775%E2%80%932235> > kristian.sons at dfki.de <mailto: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 > ___________________________________________________________________________________ > > _________________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu <mailto:Fiware-miwi at lists.fi-ware.eu> > https://lists.fi-ware.eu/__listinfo/fiware-miwi > <https://lists.fi-ware.eu/listinfo/fiware-miwi> > > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.eu > https://lists.fi-ware.eu/listinfo/fiware-miwi > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern 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 Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131030/75297654/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy