https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3ADingTo%2FGSoC_2016%2FWeekly_Reports%2FWeek11 2026-09-04T00:37:16Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:DingTo/GSoC_2016/Weekly_Reports/Week11&diff=152095&oldid=prev 2018-06-28T21:20:56Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 21:20時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:DingTo/GSoC_2016/Weekly_Reports/Week11&diff=152094&oldid=prev 2016-08-05T18:08:57Z

<p></p> <p><b>新規ページ</b></p><div>= Week 11 =<br /> <br /> == What I did this week ==<br /> <br /> ==== Half Float Support ====<br /> I did some work on half float support.<br /> <br /> * Added support for CUDA half. I still have one error there, which I need to solve, but hopefully can do that soon. Otherwise I ask for help, probably I am just missing something. <br /> * Started to work on support for converting half ImBuf buffers (e.g. Smoke) to half format, to further save memory.<br /> <br /> I will commit these things on Monday latest (not at my Desktop this weekend), need to iron out some todos still as well and de-duplicate code.<br /> <br /> ==== Statistics ====<br /> Brecht showed me some nice Renderman statistics last week, which is a XML / HTML file, that gets saved to disk after each render. Instead of adding more info to the Blender UI, I started to look into this kind of logging output. Benefits:<br /> * No further clutter inside of Blenders UI (and it's still not decided where to put such infos anyway), nor is the info hidden inside a terminal, so it's better for the user.<br /> * Cycles would save out a log file next to the render output (one for each rendered frame), like render_statistics_001.html.<br /> * The file would contain statistics about the render such as:<br /> ** Render Time / Duration, Start-/End time.<br /> ** Detailed memory statistics<br /> ** Visually nice elements such as pie charts, showing how much memory was used for each category (BVH, Textures, Attributes...)<br /> <br /> That is also very useful for renderfarms and headless servers, and can be implemented quicker than into the Blender UI. Note: That thing is meant as additional information, not as a real time logging instrument. For error messages or live info, the terminal is still the way to go. This is meant more as a summary for people to check after a successful render.<br /> <br /> == Next week ==<br /> * Commit my code for half to my branch and hopefully merge it to master after code review.<br /> * Implement the html summary logging as explained above.<br /> <br /> == Questions ==<br /> * Where to save the logging data on runtime? We can of course pipe all the VLOG info to some temp struct / buffer, and use that to fill the html then, but there might be a more simple / elegant solution.</div>

wiki>DingTo