| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
zoom
Yes, again.
There's some t within which reset is not allowed. This is so no reset happens
too often for performance issues. If camera changes too often, some reset could
be missed because of this timeout.
For now tag engine for update, which will update viewport from blender side.
Proper solution could be to detect such a changes from blender side and tag
cycles for refresh instead of trying to detect changes form cycles, but that's
for later.
|
|
|
|
values were breaking the bounding box computation, now they should have no influence.
|
|
* Compile fix when building without OSL.
|
|
|
|
properly,
causing memory to increase continuously during animation render.
|
|
importance sampleing.
|
|
binary,
and vice versa.
|
|
sync with intended zoom
Didn't initially notice one possibility when GPU render would fail here,
|
|
switched,
pointed out by Chad Fraleigh.
|
|
|
|
intended zoom
Made sure no pause_cond.wait() happens at the same time as session as resetting.
|
|
there seems to be some sort of compiler bug in CUDA toolkit 4.2, uninlining a
few functions seems to avoid it.
|
|
types don't get messed up either. (Relating previous fire fixes)
|
|
|
|
names, there were too many and mixed in with the classes namespace.
|
|
from Viktoria S. (viktorias)
|
|
|
|
|
|
instead it had value 10000.
|
|
a mesh. (OBJ export no longer needs, so save some CPU cycles and skip tessellation)
|
|
Conflicts resolved:
release/datafiles/startup.blend
release/scripts/startup/bl_ui/properties_render.py
source/blender/SConscript
source/blender/blenloader/intern/readfile.c
|
|
|
|
|
|
* Enable Lamp MIS again, it works on a GTX 570 (which is sm_20) with latest SVN. Tested by vitos1k in IRC:.
Feedback from GTX 580 users would be appreciated on this.
|
|
Reported by "aquo" on IRC.
|
|
|
|
|
|
|
|
Stupid oversight, don't use floats for indices.
|
|
Before 1 was no damping, which is inconsistent with the rest of the
simulation.
|
|
film panel.
|
|
which makes it impossible to toggle from fullscreen to windowed mode
when startup.blend is saved in fullscreen mode.
Reshuffled checks a bit, which is actually makes sense, will investigate
which change caused regression since 2.65a tomorrow.
|
|
|
|
|
|
Issue was caused by rare cases when camera move happens just after
last sample was finished, this would lead to missing delay reset
because render cycle will go to pause_cond.wait(). No reset will
happen at this point because of some kind of optimization which
checks whether camera is tagged for update and wouldn't do reset
in this case.
Talked to Brecht and seems this optimization is not actually needed
and removing it will solve issue with frozen preview.
|
|
render thread,
and rename ToggleRender to set_resolution to follow RNA conventions.
|
|
after
recent fix.
|
|
Issue was caused by couple of circumstances:
- Normal Map node requires tesselated faces to compute tangent space
- All temporary meshes needed for Cycles export were adding to G.main
- Undo pushes would temporary set meshes tessfaces to NULL
- Moving node will cause undo push and tree re-evaluate fr preview
All this leads to threading conflict between preview render and undo
system.
Solved it in way that all temporary meshes are adding to that exact
Main which was passed to Cycles via BlendData. This required couple
of mechanic changes like adding extra parameter to *_add() functions
and adding some *_ex() functions to make it possible RNA adds objects
to Main passed to new() RNA function.
This was tricky to pass Main to RNA function and IMO that's not so
nice to pass main to function, so ended up with such decision:
- Object.to_mesh() will add temp mesh to G.main
- Added Main.meshes.new_from_object() which does the same as to_mesh,
but adds temporary mesh to specified Main.
So now all temporary meshes needed for preview render would be added
to preview_main which does not conflict with undo pushes.
Viewport render shall not be an issue because object sync happens from
main thread in this case.
It could be some issues with final render, but that's not so much
likely to happen, so shall be fine.
Thanks to Brecht for review!
|
|
* Some more variable cleanup for old texture output.
|
|
'NoneType' object has no attribute 'texture_mapping'
* Issue was caused by a remaining part from the "OUTPUT_TEXTURE" node UI code, from the original Cycles branch.
|
|
|
|
without SSE3 support, due to 80 bit precision float register being used for one
bounding box but not the one next to it.
|
|
|
|
* Fix for r53689, there are two noise types, signed and unsigned.
Caused Musgrave Texture to render differently compared to SVM backend.
|
|
update to the ubuntu workaround from Shinsuke Irie.
|
|
|
|
|
