| Age | Commit message (Collapse) | Author |
|---|
|
|
|
CMake: `WITH_CYCLES_DEVICE_OPTIX` did not respect `WITH_CYCLES_CUDA_BINARIES` causing the optix kernel to be always build at build time.
Code: `device_optix.cpp` did not count on the optix kernel not existing in the default location.
For this to work, one should have before starting blender
1) working nvcc environment
2) Optix SDK installed and the OPTIX_ROOT_DIR environment variable pointing to it which is not set by default
Differential Revision: https://developer.blender.org/D7400
Reviewed By: Brecht
|
|
Some Wintab drivers report a zero length queue, this causes an unplanned never ending loop.
Differential Revision: https://developer.blender.org/D7392
Reviewed by: Ray Molenkamp
|
|
Currently in fractal_noise functions, each subsequent octave doubles the
frequency and reduces the amplitude by half. This patch introduces Roughness
input to Noise and Wave nodes. This multiplier determines how quickly the
amplitudes of the subsequent octaves decrease.
Value of 0.5 will be the default, generating identical noise we had before.
Values above 0.5 will increase influence of each octave resulting in more
"rough" noise, most interesting pattern changes happen there. Values below
0.5 will result in more "smooth" noise.
Differential Revision: https://developer.blender.org/D7065
|
|
|
|
|
|
|
|
|
|
Fixed an issue that was likely introduced in a past cleanup.
|
|
|
|
|
|
time-steps
Problem was mentioned in T74062.
|
|
Together with Windows Ink support, this should fully resolve T70765.
Differential Revision: https://developer.blender.org/D6675
|
|
Rather than using the last state of the tablet, we now query the history of
pointer events so strokes can follow the pen even if Blender does not handle
events at the same rate.
Differential Revision: https://developer.blender.org/D6675
|
|
Ref D6675
|
|
Ref D6675
|
|
It's not used by Blender anymore and it's unreliable since this state really
only makes sense associated with events in a particular order.
Ref D6675
|
|
No functional changes yet, this is work towards making CPU and GPU results
match more closely.
|
|
Issue was that the noise simulation was trying to bake with a minimized domain size (adaptive domain initializes domain with size (1,1,1)). Similarly to the base resolution bake, there should be no noise baking happening at those domain sizes - a domain at this size is considered empty.
|
|
Fix for new assertion statements that were introduced in bfdc42d9906a.
|
|
|
|
This reverts commit 82a8da0ec38a70efde4a91957824c67d0e60b8ad. It was completely
wrong. Fixes T75388.
|
|
Make sure that noise uses the unaltered velocity grid. This is particularly important once external velocities get added to the velocity grid.
|
|
For a real-world distortion the payload is quite uniformly
distributed across scanlines. Surely, in the corners more
iterations of minimizer is needed, but that happens in threads
without scheduling overhead.
|
|
Need to communicate available number of threads to the camera
intrinsics implementation, otherwise default value of 1 is used.
Must have been single-threaded for a very long time.
|
|
This refactor cleans up code for the Manta file IO. It also improves the cache 'Replay' option.
|
|
Refactored the caching system so that return values are no longer ignored. The aim of this refactor was to make the caching more robust.
|
|
|
|
|
|
|
|
|
|
Caused by 34465a7fb091.
|
|
|
|
All DirectX management happens on Ghost level now, higher level code can
just assume everything is OpenGL (except of the upside-down drawing that
still needs to be done for DirectX). This is similar to how the
metal-layer is hidden outside of Ghost.
The Ghost-XR graphics binding for DirectX is responsible for managing
the DirectX compatibility now.
|
|
Thanks to Sergey and Ray for the help identifying the problem.
|
|
|
|
I rather avoid types like
`std::vector<std::unique_ptr<GHOST_XrSwapchain>>`, which is easy to do
in this case.
|
|
This patch adds an AVX implementation of Perlin noise in Cycles.
An avxi type was also added as a utility based on the respective
type in Intel Embree.
Only 3D and 4D noise were implemented, there is no benefit for
utilizing AVX in 1D and 2D noise. The SSE trilinear interpolation
function was used in the AVX implementation because there is no
benefit from using AVX in interpolating the last three dimensions.
Differential Revision: https://developer.blender.org/D6680
|
|
I think destructing the XrSession would destruct this anyway, but rather
have this done explicitly, consistently and in a controlled manner.
|
|
Improved loading times for mesh files by reading bigger chunks of data from the disk at once.
|
|
Improved loading times for particles files by reading bigger chunks of data from the disk at once.
|
|
Removing the GHOST_kKeyUnknown check from processKeyEvent() produces
epeated unknown key events whenever a modifier key is held down, due
to the way ghost uses GHOST_kKeyUnknown as a filter value for modifier
key events.
Differential Revision: https://developer.blender.org/D7257
|
|
Differential Revision: https://developer.blender.org/D7253
|
|
|
|
Currently results in unstable particle behavior and incorrect meshing.
|
|
It appears this slipped through the code review
Reviewed By: sebbas
Differential Revision: https://developer.blender.org/D6760
|
|
Reviewed by: brecht pmoursnv
Differential Revision: https://developer.blender.org/D7136
|
|
This works similarly to the CYCLES_OPENCL_TEST
environment variable to allow testing on unsupported
hardware.
Note: like the OPENCL test override, this is
for *testing* only and bug reports on unsupported
hardware will *not* be accepted at this point in
time.
|
|
Events for keys specific to certain keyboard layouts unknown to Blender
were ignored. Now pass them along as unknown key events for which we
can still handle text input, like we already do for Linux and macOS.
Differential Revision: https://developer.blender.org/D7229
|
|
engines
Random Walk subsurface scattering did look different with OptiX because transmittance is
calculated based on the hit distance, but the OptiX implementation of `scene_intersect_local`
would return the distance in world space, while the Cycles BVH version returns it in object
space. This fixes the problem by simply skipping the object->world transforms in all the
places using the result of `scene_intersect_local` with OptiX.
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D7232
|
