[Soc-2017-dev] Weekly Report #07 - Sculpting Brush

[Tom M]

Raja I think you should start sending in daily reports.  I've been
checking in with you regularly on irc, and you made no mention of
having difficulties with BLI_array.

If you don't mention your issues in a timely manner then you don't get
the help you need and you end you end up wasting your time.


On 7/14/17, Raja Kedia <rajakedia2222 at gmail.com> wrote:
> Hello Developers,
>
>
> *What I done this week:*
>
> First of all as per my target, I started with dynamic array implementation
> in my brush. LetterRip and mont29 suggested to check BLI_array.c and use
> BLI_array function to increase array size dynamically and according to use.
> Still, there was some minor implementation problem as it was not working as
> expected rather there were few crashes. I changed my focus to dyntopo mode
> implementation before dynamic array as after dynamic array implementation,
> if there would be any problem in dyntopo then it would be difficult to
> remove.
>
>
> Now in dyntopo correction, the problem I was facing was related to
> continuous vertex index changing due to multithreading. While, storing
> index, I tried to limit threading and also imitate cache->first_time to
> create something like second_time in cache for calculation. The advantage
> of using second_time could be that it can calculate central vertex as a
> whole and it might not be affected by multithreading. But still no
> achievement was there. It was working same as before. I was thinking of
> stopping multithtreading for time being and I asked mont29 and LetterRip in
> irc and they hinted me to make brush work without interrupting
> multithreading as it won’t be a great idea. I tried BLI_mutex and related
> function (inspired from layer brush) but still there was nothing much that
> I gained.
>
>
> Finally, LetterRip hinted me to checked what is the coordinate status while
> using brush. I checked and since grab brush uses original coordinate, we
> thought of using coordinate as index. I tried studying more about bm_log
> functions and it was a bit helpful. Finally I was able to develop topograb
> brush which is working in dyntopo without crashes( still there is some
> error related to mirroring in dyntopo but it can be solved easily now).
>
>
>
> *What I will do next week:*
>
> This week, I might be able to complete topograb brush and it can possibly
> be tested by artist. Most of the things and code development has already
> been done and there are still a few error to fix. Next, it should be fully
> functional while using dyntopo mode without any crashes. I will be trying
> to deliver this brush by next week.
>
> Thank you.
>