Hi folks,
While doing some (Python) testing at work I ran into what seems to be a
misguided setting of maximum values on scene.render.fps and
scene.render.fps_base
As we know:
frame_rate = fps/fps_base
fps is an integer,
fps_base is a float
so for instance, we get:
29.97 = 30 / 1.001
I found that
Yes it does to some extent, it's basically the same as building Blender
with the WITH_SYSTEM_AUDASPACE option enabled so far.
Cheers
On 2017-06-19 03:57, Jacob Merrill wrote:
> Does this effect the GE?
>
> (bge sound actuator etc uses audaspace)
>
> On Jun 18, 2017 11:54 AM, "Jörg Müller" wrote
Hello,
I would like to request a wiki account in order for my Addon script to be
approved. Thank you, and please let me know if there's any other
information you need to make this process more convenient for you.
Sincerely,
*Dana Cunningham*
*Plugin Developer*
Phone: +49 (0)30 555 78748
eMail:
Thank you!
*Adriano A. Oliveira*
Coordenador do Colegiado do Curso de Cinema e Audiovisual
Universidade Federal do Recôncavo da Bahia (UFRB)
Centro de Artes Humanidades e Letras (CAHL)
Matrícula: 1673892
(71) 99181-0123 [VIVO] / (71) 99146-8523 [TIM]
2017-06-20 9:31 GMT-03:00 Clément FOUCAULT :
Yes it's completely work in progress.
Final output will be unclamped and not already tonemapped.
Regards.
2017-06-19 17:57 GMT+02:00 Adriano Oliveira :
> Hi guys,
>
> First of all, congratulations to Dalai and Clémant for the outstanding
> Eevee progress so far.
>
> I just would like to know ho
