- User Since
- Sep 11 2009, 11:13 PM (514 w, 2 d)
Tue, Jul 16
Sun, Jul 7
Thu, Jul 4
Sat, Jun 29
Jun 7 2019
Jun 1 2019
May 26 2019
May 18 2019
May 16 2019
May 12 2019
May 10 2019
May 9 2019
May 2 2019
Apr 29 2019
Apr 27 2019
Apr 19 2019
AMD does not really support thoses GPU anymore so it is unlikely to see driver update for these.
@Clément Foucault (fclem) I know, I know, sadly, how is the story ..
this generation of videocards now work very well especially on windows, why deprecate them after solving most of the known problems?
Apr 15 2019
Mar 29 2019
good to see that this problem has been noticed and confirmed ...
now, let's make blender a monster in performance ...
Mar 26 2019
the same thing happens for other addons with the last build ..
I downloaded the latest build blender-2.80-adfdae3fc2f4-win64
the bug has remained unchanged , at this point, I think it was only fixed for the non-workaround gpus
Mar 24 2019
hei Clem, as usual I did the usual "progress" test on the "mr_elephant" scene and I'm just impressed, on my old radeon hd 7600
now in particular working in Solid mode and in Lockdev mode is practically the same in terms of lightness, congratulations!
Mar 22 2019
@Clément Foucault (fclem) no more bugs , this problem was solved long ago on my gpu Radeon HD 7600m (the legacy drivers)
Mar 21 2019
location: <unknown location>:-1
in my case I just need to press Clipping region ...
but I think it's due to the fact that my gpu is part of the workarounds-gpu's
Mar 20 2019
Mar 19 2019
here is the blend file
@Brecht Van Lommel (brecht)
the blender file is the wanderer from the blender eevee samples, but it doesn't matter, it happens with all the files, only in the models with heavy geometry it is easy to notice ...
haven't you seen the video I've attached ??
Mar 16 2019
Mar 14 2019
@Paul Kotelevets (1D_Inc) I was curious about mechanical blender and I went to try it, I also found the post on blendernation that then links this proposal ...
I read on the site of mechanical blender who chose to create a self build because it was not implemented in blender ...
here obviously my curiosity emerges, why hasn't this patch set been implemented?
I looked around the tool, and it doesn't seem to work badly ...
too bad that has been proposed since the end of 2015
Mar 13 2019
In the cad applications, this operation is a standalone tool and often has the name "move" and is separated from the simple functions of grabbing to move objects ..
Mar 9 2019
Mar 7 2019
man, you finally understood where my gaps are.
Mar 6 2019
@Brecht Van Lommel (brecht)
I apologize, I thought they were related and that they could be good insights from a user perspective that could also be useful via development to do "the possibility of excluding individual objects or individual functions not strictly necessary" from the rendering.
Guys, I apologize if I call your attention to this link, but I believe that are making important things known about the use of memory with the instances of collections in blender 2.80 compared to blender 2.79 ...
I'm not sure if this is the right place to be brought to the attention, but I think it's very important.
select the blender folder, shift+ rigtclick mouse --> menu open cmd/powershell
OK I downloaded the latest build
heavy crash here :)
try if you get crash even by starting blender with this:
Mar 4 2019
I commited 798d2cadc307 which might be related to the perf improvement you got but i'm not certain.
I also noticed something that is making me really very very happy ...
that once the "vbo" has recalculated ... the gui starts to become light and responsive ...
(I always speak in heavy scenes with eevee activated)
the opposite is that "this buffer on the gui" is downloaded and recalculated every time I set a new color or parameter in general ...
it is a pity that do so ...
but surely it is much better than before ..
and with some polish work ... you could get great results here.
the shaders now take a bit more to take shape the first time I set the scene in EEVEE mode, and even to load they put a pinch more ... I always talk about those heavy scenes ...
@Germano Cavalcante (mano-wii) Nice Strike man!
it seems something similar to what happens with my old gpu Amd Radeon HD ...
I did some investigations, which may be useful in this case too ...
Mar 3 2019
windows 10 here.
on my old Radeon HD 7600 it works well.
From Adaptive to Alpablend in clip mode and also in hashted mode
just an opinion of an nostalgic man.
I miss the compactness of the old panels very much,
Probably they were not perfect, they could be improved,
but all this waste of space in the new panels, I can not make it fit for good.
and I found out that multicolor in edit mode (by selecting all objects) is not working ... and that's probably what does not make blender crash in wireframe in edit mode ... because I just get out of edit mode blender crash
@Germano Cavalcante (mano-wii)
I have done other digging work:
on all heavy scenes like mr_elephant, wasp_bot, wanderer, all crashing scenes, if I select all objects and enter edit mode, there is no way to crash blender, switching from wireframe mode to solid mode ...
also with the attempt to fix ae977d13f8e9 the situation has remained unchanged, blender continues to crash with the wireframe mode ...
it seems that the more you have wireframes in the buffer, the more chance you have of a crash
@Germano Cavalcante (mano-wii)
nope, keep crashing, nothing has changed
Mar 2 2019
@Germano Cavalcante (mano-wii) I just tested the last build blender-2.80- 490a385c8124 -win64
Mar 1 2019
please, duplicate and also istantiate
Feb 28 2019
I have tested the same files with the internal gpu intel HD 4000
I can confirm that by starting blender with the same files, I do not have any crashes ... so I suspect there is some mess with the usual buggy amd Radeon HD Drivers for the pre-gcn obsolete gpu
@Clément Foucault (fclem) @Germano Cavalcante (mano-wii)
Feb 20 2019
Feb 18 2019
I do not know the situation on Mac OS,
but on linux and windows you have to address blender on the "discrete" second gpu, otherwise blender uses the first internal gpu ...
so I guess it's the same for Mac OS for the egpu ...
somehow you have to start blender with the RX580 ...
I assume therefore that not only can you not use cycles openCL , but you're not using the entire RX580 with blender, even with eevee
just my opinion of two cents ....
Feb 14 2019
It's good to check if Blender is pointing to the right GPU when it opens. (just check the system-info.txt)
Good to see that AMD is starting to work safely.
The GPUs that will give headaches are the Intel's ones with those fickle crashes.
hei @Germano Cavalcante (mano-wii) yesterday I spent many hours coloring this scene of a certain complexity for fun, and blender as well as being very fluid and fast in setting the parameters of shading is never crashed ..
I think this has solved a lot of trouble on this kind of gpu's, I'm right that this progress depends on this patch or I'm wrong?
Feb 5 2019
Feb 3 2019
Feb 1 2019
if someone understands what happens with the damned shader backend compiler ... here the sources ...
good and bad news...
Jan 22 2019
Please let me know if I could help in any way.