Article written by Antonio Olmo Titos

MSc software engineer (University of Granada, Spain); Erasmus student (Technical University of Milan, Italy). Software developer with work experience both in Spain and in England, ranging from open source and Linux distros to Python and the web to Adobe technologies (Flex, ActionScript, AIR).

4 responses to “Bibliotecas 3D para Flash: conclusiones”

  1. Tweets that mention Bibliotecas 3D para Flash: conclusiones – No Smoke --

    [...] This post was mentioned on Twitter by Sandra León Paraíso and Alberto García, Cycle IT. Cycle IT said: Bibliotecas 3D para Flash: conclusiones: El presente artículo cierra la serie que venimos dedicando a la creació… [...]

  2. Bibliotecas 3D para Flash: Sandy 3D Engine – No Smoke

    [...] No Smoke Blog oficial de Cycle IT Saltar al contenido Acerca deContactar@cycle_it « CycleFramework ya no es dependiente de Flex Bibliotecas 3D para Flash: conclusiones » [...]

  3. “Molehill”: introduce Flash Player to your GPU! – No Smoke

    [...] 3D library that was fast adopting Molehill was Alternativa. As we mentioned on an earlier post, they developed one of the first games using an earlier version of Molehill: Max Racer Demo. Until [...]

  4. 3D in Flash: optimising performance (1)

    [...] following up from the results of our recent comparison of 3D libraries [in Spanish], we opted for Away3D [in Spanish] as our 3D engine of choice. The ideas, performance tips and [...]

Leave a Reply