What the heck, just tested a basic add subpatch surface modifier, and the object (a simple cube) goes away…poof, vanished.
Same if I load a scene from blender 4,2 in to 4.4 with subpatch surface modifer on it, it is gone.
Should I report a bug, or is this done already, or not a bug?
version: 4.4.0 Alpha, branch: main, commit date: 2024-10-07 22:54, hash: 2e881eacd1a7, type: Release
build date: 2024-10-08, 01:17:02
platform: ‘Windows-10-10.0.19045-SP0’
Why would you not report as a bug?
Sounds like a bug.
Just checking if it´s working elsewhere, before reporting, seems a bit weird though that such simple thing wouldn´t have been seen before, just adding a subpatch modifier must be so commonly used…so.
Should go for the 4.3 release, but have so many versions of blender installed.
No offence, but trying/using beta’s that far out, and having issues, is a discussion to be held at the developers forum, not here.
But that’s my € 0.02 
I think more people would be able to check it, if notified here.
More will look at it here than in the developers forum, after verification…by all means, we can take it over to that place…in right order.
Don’t think so tbh.
These beta’s are just for the hardcore enthusiasts, I’m still running 4.2.x LTS because any new version breaks things and messes up long term projects
Quickest route for these beta’s is contacting the devs, so they can hammer out the bugs before the beta’s become a bit more ‘mainstream’. The devs converse there, they don’t really visit this site for bughunting.
I had no clue the betas was just for hardcore enthusiasts, never saw me as one, I just went for the latest release I could find you know, but …my mistake, I should have gone for blender 4.3.
Need to install that, since I have issues with the volumetrics in eevee, but that was a new change where they have destroyed the global volume scatter, so I doubt it is a bug specificly related to 4.4.
In the past two years, I have never used that modifier. I don’t even remember other artists discussing using it…
In any case, as Rob mentioned, the whole point of a beta is things may not be working right. Devs want (quality) bug reports - that’s a major goal when sharing the beta.
ETA: I’ve just been informed that you probably mean the Subdivision Surface modifier. Which does explain why I’d never seen anyone discuss a subpatch modifier in blender…
Experimental versions are not technically betas, but alphas. Term ‘beta’ is reserved for a release candidate before its official release.
@MI65 if you are downloading anything from the daily builds from https://builder.blender.org/download/daily/ you are downloading the development version that can and is unstable in certain ares depending on ongoing development. Those versions can and are used in some productions but you need to be prepared for breakages.
And I agree with @RobWu here. Any bugs you should report the proper way. People who use experimental versions are most likely aware of bugtracker and how to use it.
If you want a stable version download it from here: https://www.blender.org/download/
I relic from Lightwave, where it is called subpatch/subdivision surfaces.
and don´t tell me no one is hardly using subdivision surfaces, that would be absurd.
I know where to download a stable version, I just said that I should.*
I know they are unstable and may not work, I just wanted feedback on that version, if it´s an error on my end, or the version error.
That can be extremely hard to diagnose, especially without proper debugging. You may never know what is causing the breakage. Best solution is to properly document the crash/bug, if possible with logs and report it through the official channel. If its reported already your report will be marked as duplicate and closed and you can watch the earlier ticket for the solution / bugfix to your problem.
But I didn´t ask for what is causing the breakage as the initial analyse
, only if it is causing an issue for others with the same version, that is where to start, after that we can discuss in dev areas what it is all about.
Which means someone needs to test it, conclude, or we are just arguing in circles around where to post the right questions.
Yes. The bug triaging team. On the bugtracker. And if there are volunteers from the community - the better. But its all happening there not here.
I’m not arguing if one or the other is right or wrong, but it works that way and I don’t see any point in changing that.
that seems like a pretty old build. Does it happen in the latest one too?
I just subsurfed a cube no problem in today’s. I download the latest alpha everyday because I like to play with the new stuff but also to report bugs that slipped in. Some builds are just unusable because some simple thing crashes to desktop. Usually those are fixed pretty quickly
That´s the latest I have downloaded, I should perhaps go for the stable release instead, if I am going to have to be a little productive and not just test new stuff out.
Thanks for the feedback,
I will have to regress from awake state to something else for now though.
Cya around.
Nobody is saying you can’t test the latest & greatest alpha, but just report bugs the way they should be reported. And that’s not here.
yeah, there is no use in reporting a bug for an old alpha build if it doesn’t happen in a new one. Probably you could even find the bug as resolved in the bug tracker if you are curious. Generall I consider asking the community first about an issue to find out whether it’s a you problem or an actual bug is a good idea. If it turns out that you just needed a driver update or hit the wrong shortcut and now nothing moves it’s some time saved for the devs.
Again, I wouldn´t even go there unless someone checks it for verification before I
report it that is.
Like that.
And with that, I let this rest, and I bid you goodnight, no need to answer much more, I know where to go from here.
