- User Since
- Nov 2 2016, 11:06 AM (29 w, 4 d)
Fri, May 12
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?
Fri, May 5
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
Dec 13 2016
Nov 2 2016
This bugs reappeared in latest VS2015 builds.