- User Since
- Sep 19 2013, 5:56 PM (296 w, 2 d)
Apr 24 2018
Apr 23 2018
Apr 20 2018
Apr 12 2018
Oh OK then... thanks for the quick answer
In this case I'll be patient: if I have any bug report to submit for the 2.79 I will submit the report as usual just following the relative Blender menu item. While for the 2.8 I'll wait because I don't feel comfortable to post to a mailing list: I just prefer the forums, but OK: cause Blender 2.80 is just still very early I'll just wait and I'll give a try on my win7 32bit for a test drive and see how goes from time to time. Hope that once in beta or release candidate the 2.80 will support my graphic card ATI Radeon HD 5400 Series for Blender Render and Eevee real time render (as cuda already are). Hoping it will be faster than just the intel core duo 32bit.
I saw some videos about eevee on youtube so I'm looking forward for the beta... to give it a try. I 'll be patient.
Apr 11 2018
Oct 15 2014
One more thing: bigger the start frame value is, greater is the desynchronization.
Sep 23 2014
Sep 4 2014
@Jennifer Godin (jenniferblender)
Thanks a lot! Your suggestion worked like a charm and has solved my problem!
I didn't know about Ctrl+a to apply the scale. Well I didn't know that I had to apply the scale neither...
Jul 24 2014
Any news about this bug?
I tried the newest version of blender (2.71) but this bug seems still present in there as well as in the 2.69.
Mar 14 2014
Any way I usually use Blender Render not Cycles
Any way I usually use blender render not Cycles
ATI is not supported?
What a shame! I bought some months ago the ATI Gcard just for blender! ahhhhhrg!!!
As you can see everywhere, in every tab page, is visible:
Light Field Tools
Mar 5 2014
Thanks for response. I followed your suggestion and the previous problem seems to be solved... but now I'm getting a new problem never happened before. It is showed into the following image:
Thanks so much.
Hope this will be solved before the release of Blender 2.7.
Mar 3 2014
"This looks like a nasty OpenGL drawing bug…"
The last 5 seconds of the video there is a comparison between before and after settings change.
Mar 1 2014
I'm sorry I don't want to appear polemic but yep it is a bit frustrating to have 2 different places organized in a different way to report bugs and advance new feature requests. IMHO it would be better to have just one place for both things.
It will be better, when a user come here to submit a new post, to have a combobox with two items: "Bug Report" or "New feature request".
The web site will organize the rest automatically.
This is enough to optimize search queries for developers or debuggers.
Also "this" web site is "developer.blender.org"... so it means it is for developers too not for debuggers...
Feb 27 2014
I'm sorry, I had just registered to the mailing list as suggested above but I'm sorry for me it is incomprehensible to understand how the mailing list and related threads work. Is there any one that has the same problem out there?
I don't understand how developers have the time to read those thread there: for me the mailing list for new feature request works very strange and it is a lot messed up.
I continue hoping to add the "new feature request" feature to this web site as a sub section or similar.
Feb 16 2014
Oh ok. Thanks.
Hope at least it will be possible to login there with the same login data used here. It is problematic to menage more and more different accounts...
Any way thanks.
Feb 8 2014
Sorry for double post but editing the original one is not possible for me:
The following attachment is the blend file I used to simulate the bug I forgot to attach it to the original post.