- User Since
- Apr 13 2010, 12:29 AM (371 w, 5 d)
Fri, May 26
Fri, May 19
Wed, May 17
Seems like this bug has resurfaced, tested on rB2836003f6b
Mon, May 15
Seems like its fixed on 77a90f7666b
Sun, May 14
If you simplify the scene, does it still contain the same render issues? such as removing the sky... the distance grass... the piers... image textures etc.etc.etc. Is it possible to simplify it down to remove off the paid assets and make it decent to upload here?
Tue, May 9
Patch created at D2661
Mon, May 8
The way it is worded is that it is currently pathtracing the current tile... as in the 1st or 2nd... not 1/4 completed.
Fri, May 5
Thu, May 4
Yes I understand, but it just is not artist friendly. Especially when all web use aswell is using a # at the start of the code.
Wed, May 3
Mon, May 1
It has been over a month. Can someone confirm this bug?
Fri, Apr 28
Might be a plug in issue... there are two double faces as per this simplified file that crash it out?
Apr 28 2017
Dont worry about the plugin, here is an example blend file (generated from the plugin)
Apr 27 2017
Apr 18 2017
Been over two weeks. Anyone able to confirm it?
Still occuring on buildbot 47e0d2b235
Apr 8 2017
Can someone confirm this bug?
Apr 4 2017
Hey its been 5 days, can anyone confirm this bug.
Apr 3 2017
Mar 31 2017
Mar 17 2017
I agree icons should use the same alignment, but right now the padding on them is too little on the left hand side
Mar 15 2017
Mar 13 2017
We have figured out how we are creating these meshes (combination of remove doubles -> limited dissolve with autosmooth shade enabled, our usual process for cleaning up high poly objects which don't need to have that much complexity to them)
Mar 11 2017
Thanks for the fix :)
Mar 10 2017
The previous way it was handled in blender was just to unset the shrinkwrap targets before the conversion. As shrink wraps do not work with curves & nurbs surfaces, I would assume that it would be better just to unset pre conversion.
Pretty sure it is gimbal lock, Try changing the rotational axis to YZX or YXZ
Mar 9 2017
Mar 7 2017
Potentially could be caused by rB36c4fc1
Mar 6 2017
Feb 11 2017
I just tried it on one of our server machines running the stock windows 7 (no upgrades, nothing else installed apart from blender / drivers / windows 7 (no sp1)), crash on that aswell.
Could be because of this commit? b047d79 -- https://lists.blender.org/pipermail/bf-blender-cvs/2016-November/091529.html, fits into the right timeline.
system info txt file here --
If i delete one file out of that folder it doesnt crash
ill download a screen recorder.....
yeh i just downloaded it manually and watched.
Managed to replicate under windows. Has to do with image sequences larger then 63 images long
Feb 10 2017
This behaviour is not consistent with the rest of blender though. Have a look at modelling, if you want to tweak a vertex you right click drag if you want to quickly grab and drag a point, and the left click confirm. left click is consistent with setting the 2d cursor.
I have tried to replicate on linux and unable.. will try windows tomorrow.
The images are not the problem but more how they are loaded up.
Feb 9 2017
Ok so deleting those two materials out of the scene does fix the material list crashing.
Second crash was also from an animated texture. This one was relatively referenced instead of absolutely. Not sure if that makes a difference
This is one of the crashes. Managed to simplify it down to one material. But I cant seem to replicate it totally, as when the link is totally broken it doesnt crash.
Feb 8 2017
Deleting the next shader in the blend file (not by name) via python ( bpy.data.materials.user_clear() ) fixed the crash... However, importing the offending shader into a new blend file seemed not crash that blender out. The offending material was only two nodes, a diffuse shader and a output node.
Feb 7 2017
We currently use a python script to write certain information into the 'Note' text box at the start of each frame during rendering. This box gets passed through into the metadata. We pass through the computer name, samples, layers enabled, GPU/CPU etc.etc.etc.
Dec 7 2016
Has anyone been able to verify this bug? it has bene over a week.
Dec 2 2016
--enable-new-depsgraph seems to be the issue for me, but not with size
Nov 30 2016
Just wanting to poke this archived issue, to flag for the upcoming blender 2.8 particle rewrite that is potentially happening. It would be extremely useful to be able to manipulate particle systems via python
Nov 29 2016
Nov 24 2016
Usually once every 3-5 thousand frames.
Nov 23 2016
Nov 14 2016
Nov 12 2016
Just wondering if there is anything else needed from myself to get this into the master branch?
Nov 10 2016
Nov 8 2016
Styling Notes, let me know if there's anything else I can do!
Nov 6 2016
Right now I have left it as two separate controls, as I feel like this would allow the artists / TDs to decide which to use and when... I can remove this if needed but in my opinion it would be more ideal to have this control.
- Addressed Lukas note - When distance_cull_margin == 0 it disables distance culling
- Addressed Brechts notes - bounding box points are now transformed correctly, styling changes as well
- Brought back code which was removed initially ( camera_cull_margin was not being fetched from the scene)
KSPBlender is not a inbuilt addon nor part of blender itself. You are best to report it to the addon creator rather than here
Nov 5 2016
Thanks for the review Brecht,
Oct 23 2016
I saw the meeting notes today and noticed that this fix was not part of the revisions for 2.78a
Oct 20 2016
Will this bug be fixed for 2.78a?
Oct 17 2016
Oct 7 2016
Sep 14 2016
Sep 10 2016
Pretty sure it has something to do with this patch (or the denoising) -- used this build https://developer.blender.org/rBd7f405b726d9f7e4d315453aacb7f1dc83bfecfa on the build bot
Sep 7 2016
could it be a duplicate of -- https://developer.blender.org/T49215
Aug 27 2016
For UV sphere I would suggest equirectangular mapping
Aug 20 2016
Aug 8 2016
Just tested this on the latest buildbot (a0c1876) and its fine.
Hash is 566dd4e8a5091ba07c95ad49e891a0b4a3ee8ce2 Sorry for the confusion!
Aug 5 2016
Ok i think i have a bit more info (this was done on 99b1c10 buildbot)
Aug 4 2016
Can confirm it has been fixed!
Aug 3 2016
Aug 2 2016
Jul 28 2016
Seems like this bug is still active... Please find a different example