OTOY Forums

Adding a glossy material in 23.10 closes Blender.

This also happens when adding a spot light and enabling nodes for that spot light. (would be a good place for the volumetric spotlight)
But the post was mostly for the glossy material bug.

Same for me. I came to report the glossy issue too and found out there is more bugs, so thank you. Hopefully a fix soon.

We have updated the 23.10 and 24.0 client links to fix the glossy crash. Please re-download and install again. Thanks!

Why will not you increase a version number?
Honestly stability issue like this wastes of my time.

roentgen wrote:Why will not you increase a version number?
Honestly stability issue like this wastes of my time.

Not sure I get what's the issue you are talking about. You can consider this an hot fix. All you need to do is to download the current installer again and re-install it. Why would you need a different version?

linograndiotoy wrote:

roentgen wrote:Why will not you increase a version number?
Honestly stability issue like this wastes of my time.

Not sure I get what's the issue you are talking about. You can consider this an hot fix. All you need to do is to download the current installer again and re-install it. Why would you need a different version?

I would say sorry for advance if you are not a developer.

Why would I need a different version(number)? I have never considered that but, you know, I use the version number to;

1. help to identify an issue as an issue that people talk about here if there are some similar issues.
2. report to developers. I think it's better that information to produce the issue.
3. notice that the new release's came up in the download page or headline.

To developers:
When you have a hot fix, will you consider to put the build number down the release?
I missed a hot fix you said while I checked the download page every day. This is my fault.
But just I would love to know you have a hot fix WITHOUT REMEMBER THE DATETIME OF DOWNLOADED. Usually I can do this by checking short digits, the version/build number.

Please, consider increasing version or giving a build number clearly, please.

Please, consider increasing version or giving a build number clearly, please.

We normally always do it.
This one has been a very special case, since the crash was identified basically the same day we released the "bugged" version.

Unfortunately I don't agree that immediately.
A past release, 23.1 or around, we met to confuse at the same kind of situation.

viewtopic.php?f=114&t=77082

That time I wrote "23.1" on a report but there was newer "23.1" than "23.1" I have.
I did re-download and re-install as you said, however the issue still reproduced. I confused that the fix was incomplete or it wasn't same issue or re-installing was failed.
There was nothing that's sure thing for me. No way to make sure whether re-install's done or even a download link was correct.

If you give it a version, build or patch number, you could identify the issue, I could notice the fix and make sure that re-install was succeeded.