Am 03.02.2017 um 16:57 schrieb clipka:

> That's a tricky one: No matter what value we actually choose here, it
> will always be possible to write /some/ more or less pathological scene
> that triggers this type of crash.
>
> But what we certainly should do is replace the hard-coded value with a
> macro, which we can then define in the platform-specific compile-time
> config of the backend module. This way, any user running into such a
> problem at least has the opportunity to build their own modified binary.

Tried it with Beta 3... Works sometimes ;)

Example 3:
Render is 38% finished. Speicherzugriffsfehler :(

Example 5:
Render is 76% finished. Speicherzugriffsfehler :(

The other examples work fine :)

-- 
Thorsten aka ThH

Post a reply to this message