- User Since
- Nov 2 2016, 11:06 AM (80 w, 6 d)
Jul 24 2017
The 3D print toolbox can't make the meshes manifold and find a lot of errors, mostly due to zero area faces. It happens on e too, but e can be cleaned with limited dissolve.
the triangulation indeed produces 0 area degenerated faces, which can't be cleaned with limited dissolve.
please attach a .blend to reproduce the issue. 15 steps is way to much
Jul 21 2017
solved by latest commit :D
Jul 18 2017
can you also attach a file to reproduce the error? If it's not reproducible on other PCs, you may have installed the same update as https://developer.blender.org/T52064.
In the enterprise I work for, all windows 10 machines are unstable at least once a weak, windows 7 is nearly impossible to crash.
First of all, when you do assumptions, you should speak more gently. Nobody should do what you say or want.
Second, Blender does respect permissions, I couldn't reproduce your bug. If I try to write to a folder I'm allowed to write in, it works, whatever folder/partition it is, if I'm not allowed it won't.
So you have to better describe your problem and speak normally.
and with windows 7? Windows 10 is known for it's instability. It's only 2 years old...
At least on windows 7, the bug is not reproducible.
when I open the file, "camera" without .001 is the active one in viewport and also the scene camera. So I guess you mean local camera and not active?
Anyway, I can confirm the bug. switching between scenes restore old local camera after it was removed
Maybe a good idea, but the tracker is not for festure request.
That's indeed an old known problem. I wish it could be fixed for 2.79, but it will most certainly only be for 2.8.
The scrolled position is in fact great, it should just scroll back up when there is nothing visible.
Jul 13 2017
Jul 3 2017
thanks for the fix
Jun 28 2017
Note that 2.78c works for this card, at least on windows.
Maybe a good workaround in the meantime would be to not update the UI or once per second while dragging the scrollbar.
I can confirm that it's fast with the new depsgraph. Even with outliner opened. Scrolling with mouse well in the outliner works smoothly even. But dragging the scrollbar to go quickly to another position in the outliner will hang blender...
Indeed, what a mess, I can confirm the bug.
please attach a blend
I can confirm the bug
Jun 26 2017
any news on this one, to model correctly, a proper normal orientation is required.
thanks bliblubli, I never would have thought that a glossy shader alone could create the crash.
Yes and I have an empty file with just a camera that can't render in Corona and is 500MB big :D Pretty heavy emptiness. I was trying to find the problematic object untli I noticed even with no object it would still crash during export...
read the docs, read the text writen in the UI (it writes kernel is compiling when you render for the first time), read the answers the devs write (there is no BPT in 2,78c = it uses normal PT = it is faster. Use normal PT in 2.79 and it will be much faster. You will help make Blender better by doing your part of the job correclty!
Jun 8 2017
it only writes segmentation fault in the command line. Other lines are startup messages with found python bundled.
Jun 7 2017
the file is simple, it's a cube with one material. But it's copyrighted. That's the only problem.
I can confirm the crash on Windows 7 x64 with latest master, but please reatach the .blend with the script in text editor. And add "import bpy" at the top for other to test out without manual work.
Then report the bug to the addon author. Thanks for the report. Closing.
Jun 6 2017
I can't reproduce it with attached file, even when activating dof in camera property panel. I think you better report the bug to Nvidia.
Jun 2 2017
@Lukas Treyer (cnd) Thanks for the fix, it works. I tested on several files and the rotation was right. I don't see why it would be right on some files and wrong on other, but only time will say if it works in all cases I guess.
Jun 1 2017
Just tested with 2.78c and new addon version, still the same problem with dupliface (options used above)
@Lukas Treyer (cnd) it only happens with dupliface, using those options:
edited task name to reflect changes in behavior.
@Lukas Treyer (cnd) the missing rectangle bug is gone with latest commit, thanks.
The wrong 90° rotation is still there with duplifaces. The extra rectangles (which are not dupliface geometry nor geometry from the DXF) are also still there.
bug seem to be fixed by latest commit. Thanks.
thanks for the very fast fix
Note that the full model takes 10 minutes to import but is also empty, so it does something. Other DXFs containing 3DFaces work.
poly or bezier, I don't see why the normals shouldn't be calculated correctly?
May 30 2017
np, thanks you for the fix.
That would mean there is no way to flip faces of curves?
I can confirm the bug on 2x RX 480 with latest driver and latest buildbot
I can also confirm that the bug wasn't in 2.78c, so it's a regression. I can't change the titel so I set to high as regression have higher priority.
I also had to zoom a lot more to trigger the bug.
makehuman importer has been removed in https://git.blender.org/gitweb/gitweb.cgi/blender-addons.git/commit/e2ebaa80b48550cdbb0e47f29e39e59ab57085b1
So maybe you better report the bug to the makehuman team?
Please follow guidelines. You must attach a blend file showing the problem. The steps you describe won't work, because you have to activate dof in the N panel -> shading.
Regarding your bug in the video, it doesn't happen on RX 480, so it must be a driver bug?
@Bastien Montagne (mont29) bug is gone in latest build. Don't know what resolved it, but thanks for fixing.
May 29 2017
Those pynodes are really usefull possibility. Is it so complicated to internally use the node group (instead of the pynode) for GLSL? I mean the group exist anyway, you just have to use it for OpenGL render ?
I can understand it may sound a bit hacky, but a proper solution can still be used for 2.8.
ok, I didn't understand everything yet, but thanks for the solution with 3 nodes instead of 1.
May 12 2017
ok, I can understand. Maybe adding a warning or UI feedback about ignored elements would help users to understand what happened.
What about the patch? I think those line don't do what was intended and at least in this case, it solve the problem by incrementing 001 to 002 to 003 instead of making the name always longer with 001, 001.001, 001.001.001, 001.001.001.001, etc.
I learned as much as I could about Python as you asked and did my best.
@Lukas Treyer (cnd) thanks for the fix and sorry if you perceived it as a judgement, it was not meant so. Simple was compared to what else I import like digital terrain model that your importer handle very good. I really appreciate your work, it's really usefull.
any news on this one?
any news on this one?
May 5 2017
This is not an error?
Apr 28 2017
Mar 21 2017
Hi @Okavango (Okavango), thanks for this first release and the very detailed doc. Here is a version with all console prints commented. It is faster. Now, the redo panel prints have to be solved.
Mar 17 2017
@Okavango (Okavango) updated again and ensured that all files are overwritten, rectangle now works, sorry for the wrong report.
Regarding the redo panel, I have no Idea, sorry. The best thing would be to print nothing there to avoid slowdown. Maybe you can ask the pros on IRC ?
Can't wait for the final release :)
Mar 16 2017
Hi @Okavango (Okavango) really interesting addon collection :) Some notes after using it:
- The NP Point Distance operator prints hundreds of lines in the redo panel, making the UI very slow. All other operator print a lot of text in the redo panel, but less.
- float box works great, but float rectangle disappear after second LMB click. Hiting enter works.
For roto move and point align, some docs would be great.
Really helpfull collection, thanks for sharing.
Mar 15 2017
Feb 7 2017
I'm still investigating, but removing small parts make the bug disappear and those part alone don't trigger the problem either. So it's hard to bisect/narrow the problem. It looks like it's a combination of things plus a random component. In the meantime, we just have a script that reload the file after a crash as reloading alone is already "solving" the problem.
I will post here as soon as I managed to make it reproducible.
Feb 2 2017
Hi @Lukas Treyer (cnd) ,
Ok, sorry for this one, didn't know it's related to pyproj. I think a helpfull message in this case would be good. For people creating those files, they can find where the problem comes from, but for people becoming such files, they will just be unable to use your addon without any hint on how to solve the problem.
Could you have a look to the other dxf importer bugs please? https://developer.blender.org/T50239 , https://developer.blender.org/T49917 and particulary https://developer.blender.org/T49915 as this one gives wrong result silently, making user work on a wrong basis.
Feb 1 2017
Jan 30 2017
Investigation is advancing. Crash is due to a modifier. When I select everything and convert all to mesh, then I can work and render hours long wihtout problem. Still have to find which modifier is triggering the bug now.
Jan 27 2017
sorry for the late reply, I tried to reproduce the bug on a simple file and on complex files with subdvided cubes and white materials, all possible modifiers, tried to render up to 10 times on every change. It took lot of time, but I couldn't get it to crash twice in a row with reproducible steps. Reloading the file, redoing the steps before the crash and rerender would work although it did crash a minute before. I did all that with a fresh buildbot build and deleted folder in appdata.
Will continue to investigate.
Jan 18 2017
Jan 12 2017
After updating to latest buildbot, the file "Ohne Titel1.pdf" imports correctly, but the original file still doesn't. Sorry for the bad example, will put as incomplete until I can make a simple example.
Jan 11 2017
Jan 9 2017
Ok, I managed to get access to the computer producing the pdf files. Here is an example file:. It imports without problem in inkscape, photoshop, etc...
Dec 21 2016
tried to edit the pdf in another program, I removed enough things to make the pdf import, but it is now like rotated 180° on x axis (so it's up down)
On the left, Blender (Wrong) on the right, acrobat reader (right)
For this, I can attach a file:
@Howard Trickey (howardt). I mean the pdf intellectual property. I'm not allowed because of laws if you prefer. The pdf where made with Autocad if I'm right, but I don't have it, so I can't send a dummy file with the problem.
exact same problems are in 2.78a.
Dec 20 2016
Maybe it helps. This fileis very simple and also fail. If you scale the selected face only by 2% (Hit "S" then type "1.02"), it works:
Dec 19 2016
Operator is bpy.ops.mesh.intersect_boolean() and it also fails on 2.78a