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

[Raja Kedia]

Hello,

Sorry for such a late reply. But really I had not got much time in last two
days.

First of all about the bugs that Letterrip has pointed out previously, I
have explained the cause for most of the bugs in a report that I have sent
in topograb thread in other mail. I have explained possible and probable
cause for the bugs and most of them were due to lack of dynamic array only
and can be solved easily once I implement dynamic array.

Regarding Dynamic array, I tried it but I guess the problem might be
related to wrong pointers declaration as Sergey mentioned. I will see that
once again. Actually I left it out then for a while because I thought that
once topograb for normal array is done, It would be better to go with
dynamic array after that. It is because if we find any error in topograb
before dynamic array implementation, we won't have to worry about dynamic
array pointers and it would be little handy to solve bugs. But if you
suggest, I will make dynamic array implementation before proceeding to
other things. :)

====Others====
Also, I recently seen a message in irc, that someone was having problem
while running my branch in ubuntu. I was unable to reply at that time due
to some reasons and lost the conversation later on. I think, the problem is
that warning which once LetterRip told me about. He didn't gave me much
details hence I was not able to go through it. Since, I am a window
developer and in my system all code that I write works flawlessly, I am
unaware of complile time error in other operating system. So, I suggest if
anyone build my branch, Please do inform me about the warning or errors. I
could make necessary changes.

=============

Few more things to add,

=>  I was not able to work for a day in last week due to my college project
completion. I have told LetterRip about it but I thought it would be better
to share with all.
=>  Since my college was reopening, I was not able to working last two days
due to registration and other college related time taking processes and
formalities. Now that I have done with all these processes, I will again
start with the dyntopo error correction from where I have left it out.
=> Also, My time of working might change a bit(LetterRip knows better).
Currently, I am also unaware of the timing as i might need one or two days
to adjust with time while handling both GSoC and college but still I will
be devoting most of the time to GSoC. I will soon update about my work
time.

What will be my target before GSoC 2nd phase evaluation:
 => A functional Topograb brush. ( I will try to make it error free as far
as possible and after that artists can give there better opinion). Actually
implementation of this tool took me longer than expectation but still I
tried my best.

Regards,
Raja Kedia.

On Sun, Jul 16, 2017 at 6:49 PM, Tom M <letterrip at gmail.com> wrote:

> Raja,
>
> also if you have to (or did) take a day off, please mention it in your
> report.  Then it is clearer how much time was spent on your project.
>
> On 7/16/17, Tom M <letterrip at gmail.com> wrote:
> > 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.
> >>
> >
> _______________________________________________
> Soc-2017-dev mailing list
> Soc-2017-dev at blender.org
> https://lists.blender.org/mailman/listinfo/soc-2017-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/soc-2017-dev/attachments/20170718/ebb0999a/attachment.htm