michael campbell 3di
  • Joined on 2019-01-13
michael campbell opened issue blender/blender#113038 2023-09-29 00:32:50 +02:00
shader editor's image texture node is aligning image to the wrong coordinates when box projection is used.
michael campbell opened issue blender/blender#112984 2023-09-28 00:14:15 +02:00
crash every few mins with new geo nodes tool system
michael campbell commented on issue blender/blender#112826 2023-09-25 20:29:58 +02:00
shift g layer and group options no longer work after introduction of bone collections.

Hi, the file was created in 4.0 build (one shown above). Must have already been fixed then, I'll try today's build 👍

michael campbell opened issue blender/blender#112826 2023-09-25 02:04:42 +02:00
shift g layer and group options no longer work after introduction of bone collections.
michael campbell commented on issue blender/blender#112526 2023-09-19 11:40:56 +02:00
compositor performance issue when larger empty area surrounding the image

oh, and a recursion happens if relying on

if not bpy.app.is_job_running('RENDER'):

It doesn't seem to prevent the frame change handler being entered for some reason. That's why I…

michael campbell commented on issue blender/blender#112526 2023-09-19 11:37:41 +02:00
compositor performance issue when larger empty area surrounding the image

Hi @mano-wii . I've created a simple file to replicate the issue more easily. Please note, render.render is only used to force the timeline to wait until the compositor finished execution. This…

michael campbell commented on issue blender/blender#112555 2023-09-19 10:14:14 +02:00
changing to wireframe immediate crash. Seems related to autosave

By the way, it's the first time it's happened for me, and it was directly after opening a second 3d viewport, with one solid mode and the new one in cycles mode.

michael campbell commented on issue blender/blender#112555 2023-09-19 10:11:20 +02:00
changing to wireframe immediate crash. Seems related to autosave

Just checked that other bug report you referenced, and yes, I think it's the same thing. Unusual for a bug of that nature to not be marked as high priority, especially with it happening so often…

michael campbell commented on issue blender/blender#112555 2023-09-19 10:08:56 +02:00
changing to wireframe immediate crash. Seems related to autosave

OK, I'll turn that off then and let you know if it happens again.

michael campbell commented on pull request blender/blender#108314 2023-09-19 09:00:13 +02:00
Cycles: Add Intel GPU support for OpenImageDenoise

Is it OK if I make a suggestion as a user?

To keep it as simple as possible, In the preferences have checkboxes for:

  • denoising devices (same as cycles render devices). Allow user to…
michael campbell opened issue blender/blender#112555 2023-09-19 08:15:42 +02:00
changing to wireframe immediate crash. Seems related to autosave
michael campbell opened issue blender/blender#112526 2023-09-18 15:20:18 +02:00
compositor performance issue when larger empty area surrounding the image
michael campbell commented on issue blender/blender#112146 2023-09-16 22:24:20 +02:00
Access violation in vk_icdNegotiateLoaderICDInterfaceVersion when putting computer to sleep.

I've just found something that might be related. If it doesn't crash when coming out of sleep mode, the wires in node editors dissapear. After closing Blender to try and get the wires back,…

michael campbell commented on issue blender/blender#112309 2023-09-13 03:00:58 +02:00
python - max property precision is showing unused digits.

On a side note. I notice when no precision is set, the number of decimal places shown behaves differently if you enter 0.0000001 than if you enter 0.1234567

entering: ![image](/attachments/c2d…

michael campbell opened issue blender/blender#112309 2023-09-13 02:29:28 +02:00
python - max property precision is showing unused digits.
michael campbell commented on issue blender/blender#112062 2023-09-10 02:29:57 +02:00
World aov output nodes dont work unless background node's colour is >= 0.0001

Thanks for your help. I guess build_date is the only safe option then. Do you know why the about blender date and bpy.app.build_date differ?

![image](/attachments/65ebd7cf-24c1-4604-b470-f0554…

michael campbell commented on issue blender/blender#112062 2023-09-10 02:20:59 +02:00
World aov output nodes dont work unless background node's colour is >= 0.0001

I guess version file is the one to always use then? Although you say that isn't incremented each build?

image

michael campbell commented on issue blender/blender#112062 2023-09-10 02:17:53 +02:00
World aov output nodes dont work unless background node's colour is >= 0.0001

so bpy.app.version should be incrememnted? The reason I ask is because Lukas said to use bpy.app.version(4,0.20) when checking for the new node group input creation method, but all versions show…