- User Since
- Jul 12 2012, 1:55 AM (266 w, 4 d)
Jul 3 2017
when did i posted the error? when 2.78c was released. to say it is invalid.. is invalid. i dont know what have changed in that case in 2.79 ... by the way where is the download for 2.79? its not my job to test your software problems in every test build. i have to do other jobs. i want to make you aware of the problem,which is reproduceable nothing less or more. your job is too fix it. i ask myself why i spend money every month to help this development?. this thread is closed now from my standpoint.
hmm. i dont know which version you have but to mark it as invalid. instead of downloading the free houdini apprentice version and test it? sorry. was the last time that i tried to help. its reproduceable. guerillia renderer is no valid highend production enviroment!! my opinion! the problem is reproduceable in nuke and houdini. and fusion thanks for not willing to check it. thats all what i get from this. Goodbye. You lost a blender defender and my help.
Jun 19 2017
I tested the export in Linux with 3.19 Kernel wich is recommented by the OS developer. Also tested with Kernel 4.0 and 4.4. The result is the same. I am working on 4.4.79 in general cause of hardware requirements.
So i tested alot at the weekend and i found out that the problem only occur with high amounts of polygones.
Jun 18 2017
Apr 16 2017
Ok accepted. At which rate is dwaa and dwab compressing? I asked because if you maybe scaleup the pass from 2k to 4k it would be nice when the compression rate is not above 50. Thats why i asked about a manual slider for compression. I guess if it would compress at 45 as default. all should be fine. Thanks for reactivating the issue and yeah happy easter.
Hi, yes thats true, but, you dont brought it to the end. You implemented 50% of the DWAA and DWAB support. I can't see any Compression Rate Tab or Setting, but that is really crucial. At which Rate is your DWAA or DWAB compressing? Propper Values are between 20 and 500. A DWAA Layer is used as Compositing Layer with a Production Ready Compressing between 30 and 50. A final composed Layer will be saved with DWAB at 150.
Hmm, Not nice to hear.. I think you dont get it.. ITs not a missing feature or a nice to have, its essential. The entire DWAA and DWAB Support is useless... because with the actuall methode you compressing all Renderlayers.. like ZDeph and other Aux channels. By doing that you entirely kill the Renderlayer...Its worthless to use it. I wrote it here because you need to Fix this ASAP, otherwise no serious Artist should or will use it. ..
Feb 10 2017
First of all very nice with Blender 2 78b it works nice. But is it possible to store point color dats on those curves? I think thats not possible but is it possible to import alembic files of point clouds with stored color data what alembic is exporting in houdini. Its stored but blender dosent import it..
Sep 25 2016
Ps When you play the animation foward step by step you see the lagging of the curves.
Feb 29 2016
i cannot believe it.... For what an vdb cache when translation between packages is not possible that i cannot believe this.. i hope that was planned as a substep for a planned import functionality, if not it would be insane. Sorry to say...
May 29 2014
Sorry for the off topic. But i have to say something. Sorry for my words, but in my point of view blender will not make the breakthrough to the industry with the tools itself inside blender. it can only conquer the markets with cycles. The Key is to be faster and with more quality then other render tools. That is for alot of guys i know for myself the only reason to make the change to blender. And so in my point of view it will be not good to drop the performance of some of the tools. Because a true artist dont need a new special button for creating a very good new simulation in physics and so on. Every Studio is working with different tools to get the best out of every software. Blenders Cycles Engine is the fastest VFX Renderengine i know for years. in my entire life, and i do it now for more than 17 years. I know exactly from what iam talking about. The key is speed and Quality inside Cycles. That is the most important point for alot of guys to make the switch...
thanks the Testbuild Two is acceptable.. Nice work !!! my test scene only took 2 sec more.. that is ok..;)
May 27 2014
thanks i will do;)
thanks for the fast reply. and your work. you done a amazing job with cycles. But i have to say i will not switch to version 2.71 till this is fixed. Because when i use it, its like i wasted my money with having a new card and lost a lot of speed in calcualtion.
my kernel_sm_50.cubin is from Thursday, 20. March 2014, 12:30:25 filesize: 1.186 kb .... its alot faster...
Thanks i read all the posts and so on. And have to say i dont understand why the Cuda Builds of all version after 2.70a are so slow.? I got a Geforce 750 Ti OC my Test Shot needed with my old version only 1 min and 41 sec... even the latest build it took more than 2 minutes..? what happend? the speed improvment of my 750 in comparission to my old 550Ti drop nearly by one third that is nothing good. if this will not fixed i will use two different versions one for GPU and one for Smoke renderings. is it not possible to update the old faster cuda 5.0 kernel?
Hi, is it possible to DOwnload the latest version? somewhere else?