2021-10-05 at 9:14 am #458402021-10-05 at 9:14 am #45841
The newly introduced ambient occlusion technique now works on Intel 600-series chipsets, as we implemented a work around the driver bug. Thanks for reporting this!
We fixed the following issue specific to 3ds Max (and possibly Maya): HDR maps were forced to convert to low-dynamic-range PNG format on some Win 10 systems, which resulted in broken lighting. Although the reasons for such behavior remain unclear, we were able to implement a workaround by explicitly specifying the MIME type for such files in the Python exporter. Thank you for the report and assistance in nailing this bug!
We removed the console warning that looked something like 404 Failed to load detect-gpu.umd.js.map. This issue was reported through the Enterprise support channel.
We fixed the bug with incorrectly working intensity of Area lights when using units other than meters (in 3ds Max).
Finally, we fixed various deficiencies related to compatibility with Blender 3.0 Alpha which is currently in active development.
By default, the coordinates provided to the set/get object transform puzzles are set relative to the object’s parent (aka parent space). Now these puzzles obtained the option to work in world space.
The get body param and apply body param physics puzzles obtained a new drop-down option to affect rotation.
Finally, the visibility breakpoints feature, released a few days ago, now works not only for mesh objects but also for cameras. For example, you can swap the cameras (e.g. to increase/decrease FOV) when the scene is viewed in landscape or portrait mode.
2021-10-05 at 9:15 am #458422021-10-05 at 5:34 pm #45879psykokwakParticipant
- This reply was modified 1 week, 6 days ago by Yuri Kovelenov.
Thanks for that update.
I note that I still have the warning
DevTools failed to load source map: Could not load content for https://www.mywebsite/detect-gpu.umd.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
- You must be logged in to reply to this topic.