Cindigo 1.1.13 Beta
- PureSpider
- Posts: 1459
- Joined: Tue Apr 08, 2008 9:37 am
- Location: Karlsruhe, BW, Germany
- Contact:
cindigo 1.1.14 coming tomorrow. sry to say that mac version will be there a few days earlier. pc version sunday. whats coming:
* reworked export routine. in extremen cases up to 10x faster export(even more if you heavily use instances. xml generation that is, mesh export is as fast as ever)
* a few little bugfixes
* improved instance handling (MUCH faster, better). believe me, its superior
what started as a little optimization for being able to export the lucys became major refactoring and optimizing
* reworked export routine. in extremen cases up to 10x faster export(even more if you heavily use instances. xml generation that is, mesh export is as fast as ever)
* a few little bugfixes
* improved instance handling (MUCH faster, better). believe me, its superior
what started as a little optimization for being able to export the lucys became major refactoring and optimizing
-
- Posts: 51
- Joined: Thu Jul 03, 2008 10:46 pm
- Location: Berlin, Germany
- Contact:
- PureSpider
- Posts: 1459
- Joined: Tue Apr 08, 2008 9:37 am
- Location: Karlsruhe, BW, Germany
- Contact:
- pixie
- Posts: 2332
- Joined: Sat Dec 29, 2007 4:54 am
- Location: Away from paradise
- 3D Software: Cinema 4D
- Contact:
In Amiga you have a Use state and a save state, in use state the changes aren't saved and that means that when computer reboots you do not have to worry with what you had messed around since it would have no effect in the next time you boot, if you felt comfortable enough you would then save. Although I am talking on an OS the metaphor could easily apply here, there was even a time where it actually took place in cindigo, when animation system was first introduced, if you typed scene, and on the next typed scene again it wouldn't overwrite and as such it would compile right away.
My suggestion would be creating a dumb project drawer that would be erased each time and a scene created without user worrying where it was saved, and once the user find himself comfortable enough he could then save. So instead of just two states he would then be presented with three:
View | Save | Cancel
My suggestion would be creating a dumb project drawer that would be erased each time and a scene created without user worrying where it was saved, and once the user find himself comfortable enough he could then save. So instead of just two states he would then be presented with three:
View | Save | Cancel
@pixie:
im not sure if i get what you mean :S
heres a little console output of a scene with more than 60k instances. have a look at the export time of the meshe and the total export time
and thats on a mac mini!
i cant compare it to previous versions(because of the crippled console output), but when the next version is released, you can try yourself. its A LOT faster.
edit.: this is a worst case-scenario for the old export. it would probably take a minute or even longer.
edit2: ignore the typos
im not sure if i get what you mean :S
heres a little console output of a scene with more than 60k instances. have a look at the export time of the meshe and the total export time
and thats on a mac mini!
i cant compare it to previous versions(because of the crippled console output), but when the next version is released, you can try yourself. its A LOT faster.
edit.: this is a worst case-scenario for the old export. it would probably take a minute or even longer.
edit2: ignore the typos
Who is online
Users browsing this forum: No registered users and 42 guests