#BRICKSMITH MAC CODE#
Realistically we can only say BrickSmith is incompatible with Big Sur until new code is written.
#BRICKSMITH MAC PATCH#
If anyone could write a patch that mods zooming, I can try it (I have 3 different OSes in my office) and see if we're in business, but it's not a trivial change. Allen had to put BrickSmith down but I haven't had time to pick it up.
#BRICKSMITH MAC MAC#
I.don't know how exactly to do this - my day job is in 3-d graphics but not Mac UI tinkering, and as may be obvious by my posting here once every year, the comment "we don't have active mac developers" is probably right.
The fix for this is the same as the fix that would have allowed for native Catalina compilation:rewrite Bricksmith's view system to somehow cope with "zoomed" layers. If we set it to be big enough to look good at high res, a large model ends up being an 8k x 8k FBO, which is bad.Īs of Catalina, we were in a situation where a developer had to get an old SDK to compile against to _trick_ OS X into thinking that BrickSmith was an old app despite being compiled on a new OS, to get access to that backward compatibility pass. We embrace "render to the surface" then as you zoom in, the view just gets pixelated and blocky as the VRAM surface is _stretched_. But it's also _not_ how BrickSmith works, and breaks the view system. This is actually, architecturally, the right way to do things in that it lets 3-d accelerated code render directly to a VRAM surface that the compositor can then work with. This in turn means the 3-d code renders to the underlying pixels in "UI space" - when you zoom in, we just draw the model bigger (using 3-d transforms).Īpple has been deprecating this way of working in favor of having all 3-d UI views render to their own dedicated layers. I can at least tell y'all what has gone wrong with Big Sur Andy's comments are correct that BrickSmith is unusable on Big Sur, and there isn't a good work-around.īasically: BrickSmith is built around the idea that the 3-d view doesn't have its own layer in Apple's UI compositing system. (, 13:30)Andy Zmolek Wrote: Made the mistake of upgrading not expecting that nothing that rendered in 3D would work anymore. Until I get feedback from Beta 3, I'll leave Beta 2 up (which was built with last year's Xcode). However, the officiall version of LDView (4.3) was built long enough ago, that if that's what doesn't work, it doesn't surprise me at all. I can't think of anything off-hand that would cause LDView not to work in Big Sur. Even if they aren't really bricked, they are at the very least non-functional for days or weeks.) (Given that Big Sur seems to have bricked a bunch of MacBook Pros, I am not being paranoid.
If not, then it's not going to be fixed until I can trust Big Sur not to hose my system.
I just released a new Beta of LDView built with the latest Xcode, and hopefully that will work in Big Sur. The earliest version that can be supported by any app built with the latest Xcode is 10.9 Mavericks. In addition, they constantly force developers to stop supporting old versions of macOS. I don't have Big Sur, and I won't have it for at least another two months, since frankly, I have learned not to trust Apple's major OS updates any further than I can throw their UFO headquarters building. Extremely frustrating, because Apple constantly breaks backwards compatibility on things, both publicly (when they do things like remove support for 32-bit apps) and secretly (when old programs just stop working). Awesome, because it's (IMO) relatively easy to develop for.
#BRICKSMITH MAC SOFTWARE#
As a software developer, macOS is both awesome and also extremely infuriating. It's that we don't have any, active developers for MacOS programs. (, 23:47)Orion Pobursky Wrote: MacOS is fine.
0 kommentar(er)
