- User Since
- Mar 20 2019, 3:58 PM (17 w, 3 d)
Thu, Jul 4
using factory defaults .. default blender keymap ..
Wed, Jul 3
Tue, Jul 2
Yes, I'm having AMD driver 19.6.2 (Stable) .. and blender-2.80-648e8a1f1d4a-win64
Ok thanks. Here is the file now
Did I prepare the minimal file wrong? Just confirm, this for me. Here is what I did it... selected the planes in my original, copy and paste in new blend file and save. If I open this minimal file now... by going into render preview mode, and after applying the fix, I can see all 4 images properly. Do I need to provide you image files seperately?
Sun, Jun 30
Here is a minimal file, I tested it in yesterday's build as well "blender-2.80-648e8a1f1d4a-win64".
Fri, Jun 28
I'm using Eevee. In cycles, there is no issues.
May 9 2019
two alternative methods that came to my mind regarding this are:
Why not just use 'Straight' instead of 'Standard' since.. a straight conversion is being done. Using the word 'Standard' is not right in my opinion, as people may or may not know .. what is the standard way to do it, or may have been following a different 'standard' in other related softwares like Maya, Zbrush, etc.
Apr 29 2019
Apr 28 2019
I'm hiding the objects from render, not their use in particles system.
- not the eye icon (which is for hiding in viewport) .. nor the collection level icon..
- I mean this one (marked as 2) .. the camera icon.. on object level
Apr 16 2019
@Sebastian Parborg (zeddb) : Ok thanks about the part. But it is 'very' annoying to me to have to use alt+a, instead of just clicking empty space.
Apr 15 2019
In other software as well as the intuitive feeling is this, that clicking in empty space should unselect everything. Blender does it for faces/etc selected in modelling viewport (edit mode), for example.
Apr 13 2019
Apr 10 2019
yes, I have checked on my side. That workaround is working in 009dbc2bc9fb . Thanks for pointing out.
Just so it is helpful to track the cause, I'm reposting the version details I posted in the other thread (T63468).
Not Working for me in the build 009dbc2bc9fb (dowloaded today: 10 April), d2d84132ddf9 (April 7) and 700346d377dd (Downloaded April 2).
Mar 21 2019
Than any ETA on this? Because there are other bugs that were fixed after 4th March and might hinder my workflow. Plus, I would be missing out on new features added since then.
I did not understand that very well sebastian (I'm not specifically asking you to explain though). Just suggest to me as to what I should do as end user.
I'm pretty sure that I have clean drivers(though I can check very deeply as well), as I had to do a clean back up few months ago, as some bug on AMD side was causing a annoying error (Basically AMD control panel was showing that updates were available, when you were already on latest drivers). I know how troublesome GPU drivers can get sometimes (thus I'm on a stable version, while a optional version is available).
@matc (matc) : I will download the 2.79 and test the same scene in it, and post the numbers shortly, to help out. Btw, although I'm unaware of the techinical details, but I kept a rough eye on my task manager, and the peak was hit for few seconds inbetween and towards the end as well. This is not a big deal now (for me), since my render times have increased significantly (ever since I unticked the second GPU listing mainly). But just letting you know, in order to help with future optimizations.
Mar 20 2019
It seems you are right on that issue mostly, I just did a test render and checked performance in Task Manager and GPU Tweak 2, and this attached screenshot (Image1) shows the results. But then, I rendered the same scene with CPU option unticked in the user preferences, and the checked both Task Manager and GPU Tweak 2.