Re: [Bf-committers] Memory Error message.

[Aaron Carlisle]

Made an PR up stream:

https://github.com/CudaWrangler/cuew/pull/2

On Sun, Oct 9, 2016 at 4:06 PM, Knapp  wrote:

> Thought I could not answer you but I did reproduce the error. It happens
> when I turn on the new subsurf.
> Full message:
> Frame:1|Time:02:08.99|Mem:0,01M,Peak:0,01M|Out of memory
>
>
> On Sun, Oct 9, 2016 at 3:15 PM, Bernardo Sulzbach <
> mafagafogiga...@gmail.com
> > wrote:
>
> > On 10/09/2016 04:35 AM, Knapp wrote:
> > > When playing with 2.78 (rendering) it keeps crashing or just giving me
> an
> > > "out of memory error". I don't think this is a bug but just to much
> > > geometry on my part. The thing is that this message does not say if it
> is
> > > GPU memory or CPU memory.
> >
> > Is the message really JUST "out of memory error"? Didn't you omit
> anything?
> >
> > --
> > Bernardo Sulzbach
> > http://www.mafagafogigante.org/
> > mafagafogiga...@mafagafogigante.org
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> >
>
>
>
> --
> Douglas E Knapp, MSAOM, LAc.
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Memory Error message.

[Knapp]

Thought I could not answer you but I did reproduce the error. It happens
when I turn on the new subsurf.
Full message:
Frame:1|Time:02:08.99|Mem:0,01M,Peak:0,01M|Out of memory


On Sun, Oct 9, 2016 at 3:15 PM, Bernardo Sulzbach  wrote:

> On 10/09/2016 04:35 AM, Knapp wrote:
> > When playing with 2.78 (rendering) it keeps crashing or just giving me an
> > "out of memory error". I don't think this is a bug but just to much
> > geometry on my part. The thing is that this message does not say if it is
> > GPU memory or CPU memory.
>
> Is the message really JUST "out of memory error"? Didn't you omit anything?
>
> --
> Bernardo Sulzbach
> http://www.mafagafogigante.org/
> mafagafogiga...@mafagafogigante.org
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
Douglas E Knapp, MSAOM, LAc.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Mac OS 10.7+ for Blender 2.8

[Mike Erwin]

Realized something today:
Increasing Blender 2.8's system requirements to Mac OS 10.9 lets us target
OpenGL 3.3 instead of 3.2! Mac OS 10.7 & 10.8 were the only reasons to stay
at 3.2. Hardware (GPU) requirements stay exactly the same.

What does 3.3 offer over 3.2? (* = exciting, fits into our plans)
* instanced arrays
* more efficient occlusion queries
* 10_10_10_2 vertex attributes (perfect for normals)
- 10_10_10_2 textures
- sampler objects

Complete list here:
https://www.opengl.org/wiki/History_of_OpenGL#OpenGL_3.3_.282010.29

The differences between 3.2 and 3.3 are not major, but setting our minimum
to 3.3 means we can guarantee these features will be there at runtime. No
need for extension checks or fallbacks.

Let's bump OpenGL to 3.3 and GLSL to #version 330.
Unless someone objects, I'll update the development docs & tasks & code to
reflect this.


Mike Erwin
musician, naturalist, pixel pusher, hacker extraordinaire

On Sat, Oct 8, 2016 at 10:34 AM, Jens Verwiebe  wrote:
>
> Just FYI: Older macs can run 10.9/10/11 too jst with the bootloader trick.
>
> It warps 64 bit efi calls to 32bit efi in for example MacPro 1.1.
>
> I have exaclty done this on an 1.1 from 2006 running Yosemite ( 10.11 )
now.
>
> A demon assures consecutive updates do not ruin the bootloader exchange.
>
> Its very easy to use, see Mac Rumors forums.
>
> Jens
>
>
> Am 08.10.2016 um 16:02 schrieb Brecht Van Lommel:
> > Ok, let's do macOS 10.9 minimum then.
> >
> > I'm about ready to commit the libraries, if anyone likes to review see
> > here. Otherwise I'll just go ahead and commit things in the next few
> > days.
> > https://developer.blender.org/D2283
> >
> > On Wed, Oct 5, 2016 at 3:27 AM, Mike Erwin 
wrote:
> >> Ok, I've had a chance to read your points and dig up the hardware
facts.
> >>
> >> I was concerned about the people that are stuck on 10.7 because their
> >> computer can't support 10.8, and didn't want us to leave them behind
> >> without a very good reason. Other people/projects/companies abandoning
it
> >> are not good reasons. But...
> >>
> >> The only Mac than could run Blender 2.8 but not OS 10.8 is the first
Mac
> >> Pro (Aug 2006 - Jan 2008), and only with an upgraded GPU. iMacs,
MacBooks
> >> Pro, everything else of that era is stuck with an old GPU and won't be
> >> supported anyway.
> >>
> >> So now we know exactly who we'll be disappointing! Mac Pro owners
(early
> >> adopter or second-hand) that don't have a newer Mac to run Blender on.
> >> Seems like a very small segment...
> >>
> >> Any newer Mac running 10.6.8 or later can upgrade to 10.9 free of
charge.
> >> Nobody is "stuck" on 10.8 by hardware. They might choose to run 10.8 or
> >> (god forbid) 10.7 but we have no obligation to support their choice.
> >>
> >> After gathering these facts I am also in favor of making Mac OS 10.9
the
> >> new minimum.
> >>
> >> Mike Erwin
> >> musician, naturalist, pixel pusher, hacker extraordinaire
> >>
> >> On Tue, Oct 4, 2016 at 5:29 PM, Martijn Berger <
martijn.ber...@gmail.com>
> >> wrote:
> >>
> >>> I think 10.6 was special in the sense that a significant number of
people
> >>> lingered on that version.
> >>> 10.9 and higher have been free upgrades and that seems to have moved a
> >>> significant number of people over.
> >>> Last time i checked our download stats 10.6 had more users then 10.7
and
> >>> 10.8 combined.
> >>>
> >>> Taking that into account I would be in favor of using 10.9 as minimal
> >>> version.
> >>>
> >>> On Tue, Oct 4, 2016 at 10:59 PM, Brecht Van Lommel <
> >>> brechtvanlom...@pandora.be> wrote:
> >>>
>  Xcode 8 is currently showing this warning. So it's not clear how long
>  Apple will even officially support building for 10.8.
> 
>  clang: warning: libstdc++ is deprecated; move to libc++ with a
minimum
>  deployment target of OS X 10.9
> 
>  Apple support for 10.9 ended last month, 10.8 a year before that, so
>  those are not even getting security updates anymore. Firefox and
>  Chrome have 10.9 as minimum requirement, and I think the same or
>  higher is required for a lot of other major software. Blender 2.8
>  would be released a year or more from now, so we would be the
>  exception in still supporting 10.7.
> 
>  The one issue I personally found with 10.7 was an SDK bug that makes
>  building Python 3.5 fail. I tried to solve it for a few hours but
>  didn't find a solution yet. It's probably not a showstopper but if we
>  decide to use 10.8 or higher I won't spend more time trying to fix
it.
> 
>  I don't know of any other serious issues, though inevitably we'd
>  encounter some in the future. Personally I wouldn't want to spend
time
>  debugging OpenGL issues on e.g. 10.7 or 10.8, but maybe you're up for
>  it :)
> 
> 
>  On Tue, Oct 4, 2016 at 2:27 PM, Mike Erwin 
>  wrote:
> > Bringing this 

[Bf-committers] Blender developers meeting, 2016-10-09

[Ton Roosendaal]

Hi everyone,

Here are the notes from today's 14 UTC meeting in irc.freenode.net 
#blendercoders.

1) Blender 2.78 release status

- Lots of small issues were reported, several severe ones that require an 
update release.

- Blender 2.78 'a' will be decided on mid this week. Sergey Sharybin and 
Bastien Montagne coordinate.

- The list of crucial fixes will be added to the release log with a readable 
text!

- Windows .msi installer: the error has been solved, the SDL library was 
updated without rebuilding binary.

- The MacOS installer error for users is still unsolved. Needs dev time 
(scripts should not write in .app)

2) Other projects and 2.8

- The viewport team did a call for help:
https://wiki.blender.org/index.php/Dev:2.8/Source/OpenGL/ImmediateModeReplacement

- Brecht van Lommel: For Blender 2.8 we decided on Mac 10.9 minimum. (Current 
is 10.12)

- Grease pencil drawing uses 100% modern OpenGL now.

- Brecht: new libs have been committed and we're ready to switch to c++11 on 
macOS in blender 2.8, 
just waiting for linux now. https://developer.blender.org/D2283

I'll be in LA for a week bizz, next meeting & minutes will be handled by Sergey!

Thanks,

-Ton-


Ton Roosendaal  -  t...@blender.org   -   www.blender.org
Chairman Blender Foundation, Director Blender Institute
Entrepotdok 57A, 1018 AD, Amsterdam, the Netherlands

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Memory Error message.

[Bernardo Sulzbach]

On 10/09/2016 04:35 AM, Knapp wrote:
> When playing with 2.78 (rendering) it keeps crashing or just giving me an
> "out of memory error". I don't think this is a bug but just to much
> geometry on my part. The thing is that this message does not say if it is
> GPU memory or CPU memory.

Is the message really JUST "out of memory error"? Didn't you omit anything?

-- 
Bernardo Sulzbach
http://www.mafagafogigante.org/
mafagafogiga...@mafagafogigante.org
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Memory Error message.

[Knapp]

When playing with 2.78 (rendering) it keeps crashing or just giving me an
"out of memory error". I don't think this is a bug but just to much
geometry on my part. The thing is that this message does not say if it is
GPU memory or CPU memory. I think it would be very useful to know which it
is talking about. I assume it is GPU but then I am a programmer. I wonder
if it would crash if I turned of GPU render? Would I maybe have a chance of
it working?  How many artist would even have a good guess?

So my idea here is to make the message more specific.


-- 
Douglas E Knapp, MSAOM, LAc.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers