Funny enough, i have some outstanding x86 issues on it, haven't gotten around to resolve those. will take a stab at that tomorrow.
As much as I'd like to simplify things, it seems too early with that percentage.
Pushing my luck here, last time i asked @Ton Roosendaal (ton) , the x86 users were around 15% , too early to drop x86 support as well?
Ok, seems this patch will happen along with an upgrade to VS 2017 then. I'm all for only supporting a single VS version at a time to keep thing simple
Wed, Nov 22
2013 worked for us,
2015 had occasional weird codegen issue in cycles, i just don't trust it, so we stuck with 2013.
2017 seems allright, but cuda support kept holding us back, I made D2913 to sidestep that issue and clear the way for an official compiler bump. There's some other minor issues like our boost version is too old to officially support 2017, but it seems happy (even though it's outputting a ton of warnings about this)
Why are we still supporting VS 2013?
llvm5 is also a no-go for 2013.
Yeah 2013 is officially a nogo, but with the osl 1.9rc1 adding back in support for oiio 1.7, i guess we could do oiio 1.7.17, until we drop 2013 support?
Updated with msvc2015 support for OIIO (2013 i still need to look at further) OSL/CLANG are still to be done.
Mon, Nov 20
same as Roel "rendered tiles on GPU are completely black. No artifacts." (entire render is black)
radeon pro 580
if I go into the denoiser settings and turn off direct diffuse the denoised tiles aren't black
Thu, Nov 16
Wed, Nov 15
Tue, Nov 14
- I got release/x64/msvc2015 to link, but any osl render crashed instantly
From OSL 1.9.1:
I started this a few days ago,I have a bunch of patches ready for compiling on windows. Couple of things to note though:
Mon, Nov 13
Yes, I disabled Automatically hide and show the menu bar and the problem is gone. Usually I hide everything and use fullscreen in every app for more useful space.
Sun, Nov 12
I don't have this problem with my Intel Iris card, but also have not upgraded to 10.13 yet, it's likely something broke there.
On 11 - 8 and 11 - 12 build on 27" Mac, and works fine here.
Sat, Nov 11
It is on the latest MacBook Pro.
Intel Iris, I would guess that it's the integrated GPU on mac. So drivers should be up to date with latest macOS.
Oct 24 2017
Thanks @Arto Kitula (akitula). Just tried your build and sadly the glitch remains.
Oct 23 2017
It's a Mac OS X bug, it also happens with other apps.
MacBook Air 11"
Mac OS X 10.12.6
I'll do a build for you.
I just tried this build from builder.blender.org. Not sure if this is the one I need to try: blender-2.79.0-git20171022.57a0cb797d6-x86_64
Oct 22 2017
@Dalai Felinto (dfelinto) would want to try out, but I gave my GTX to my son for gaming purposes and don't have the setup anymore.
@Stephen Hamacek (hammers) Could you try this? If you need build, just ping me and I'll do build to try out (if buildbots aren't working)
Couldn't reproduce. Could you give more specs of your system?
Oct 21 2017
Oct 16 2017
Oct 10 2017
@Arto Kitula (akitula) will let you handle this one then.
Oct 6 2017
It would have been nice to solve this, but for the next release we will require macOS 10.9 minimum. Apple themselves stopped supporting macOS 10.7 3 years ago.
Oct 1 2017
2x smaller compared to what?
You misunderstood me. The render result is 2x smaller at 1:1 zoom. It has nothing to do with metadata.
Sep 29 2017
Sep 28 2017
Thank you @Brecht Van Lommel (brecht) !
Thanks, I've updated the documentation now, we'll do some further improvements in D2861.
Sep 27 2017
I guess specifically what's missing is that Blender does not support reading and using certain image metadata (like DPI for jpeg).
Sep 26 2017
In the past I had a GTX660 pc card (unflashed) alongside the Radeon original mac card. Now running a (non official) mac flashed Titan with Radeon card.