Nevermind! Aparently I simply missed this slider on bottom, it was indeed set to 0
False alarm, thanks for pointing it out Antonio!
Guys......Just download the latest daily build and It now work fine as soon as I opened the file and rendered it..........either you fixed it already or I am a victim of my own stupidity.....anyway keep up the phenomenal work.....really loving all the new toys
@Jason (jsboudreau) please make a new report
@Martin Ackerl (MartinAckerl) are you talking about the last file I uploaded? I’m gonna try it!
Can't reproduce on 2.80, 9541ce2c261b, blender2.8, 2019-02-21.
Try latest build.
Can reproduce on 2.80, 9541ce2c261b, blender2.8, 2019-02-21.
I think it caused by
Outliner visibility unification: Implement 3 levels of viewport visibility like in here T61788.
Please, share your .blend file to investigate problem easier otherwise it hard to know what happening.
And please add Blender Version (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen).
Alright great for 2.8 ! Keep up the good work guys.
I'm not sure exactly which option you requested to confirm but I think my values are normal.
The selected vertex display without problems on any other scene other than blank "New" ones
@Joan (jbetbe) Probably not a big help, but on my iMac Pro it works if I disconnect at least one other image texture (counting 7 textures).
- Fix triangulation issue
- shift versioning code to prevent loading problems with 2.80.45
@ALESSANDRO NASCIMENTO MILHIOLO (alessandromilhiolo) the only problem with that is, every time you download a new build you need to add the --factory-startup. By deleting the userpref.blend file all is solved. It creates a new blank one and it is done. Well, not exactly because you need to activate some of the add-ons and setup you Preferences but you only need to do it once. Since I deleted that file, I used another 5 or 6 daily builds and all run ok and create video from image sequences.
This same bug above is in the latest stable version of blender 2.79
Hi, There is still an issue with importing in .obj files that have pure black in the color channel.
Large(ish) memory commits in some instances can quickly overwrite all remaining disk space
I'm asking that physics simulation and scene respect the frame rate beyond the the draw rate for viewport rendering.
Now it works like a charm.
Sorry, I wasted your time. I did not find a good explanation for all cloth parameters and they are little bit different from 2.79.
I think little diagnostic or error message if self-collision distance is bigger than minimum mesh cell would be helpful to avoid some simulation errors.
Looks like only self-collision distance can prevent from self-penetration: not too big to keep simulation successful and not too small to prevent self- penetration. Is there another way to prevent self-penetration?
Hi Sebastian! Thanks for the reply!
@Brecht Van Lommel (brecht) pardon me if I say something stupid, but... as far as I understand, this shadow issue happens when a face projects its shadow to one of its adjacent face. So isn't there a way to prevent faces to cast shadows on their adjacent faces? Dismiss them from the shadow say, when smooth shading is on?
Thank you for clarifications.
Thank you for the update Sina.
Ah, I see. That's unfortunate... but thanks so much for letting me know about that... I discovered a workaround that gives me the best of both worlds. :-) Switch back to the Blender default config, activate your settings from that menu, then save a custom preset. If you need to make any changes (such as turning on extra shading options in the pie menu), switch back to the Blender default config, change the settings, then save a new (or overwrite) a custom preset. Works perfectly... thanks so much William!!!! This really made my day. :-)
These only appear when using the built-in keymap. If you use custom keys we cannot display this. You can reset to the built-in keymap to see it again.
@Sebastian Parborg (zeddb) Blender 2.79b worked after copying the dll file into the blender.exe location but it is little slower than it used to be in the past. However, the latest experimental build of 2.80 beta is still not working. I want to show you an screenshot below about what happens when I open blender 2.80 beta: