Comments on: Update: new 0.4.0 binaries for Windows https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/ Wed, 13 Apr 2016 15:09:25 +0000 hourly 1 https://wordpress.org/?v=474 By: Jose Conseco https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1709 Mon, 08 Oct 2012 14:14:33 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1709 I just wanted to let you know, that I updated Blender exporter to new version.
http://bartoszstyperek.wordpress.com/2012/10/07/mitsuba-exporter-1-0/
When sky and sss fix will be out most parameters should work ok.

]]> By: TwinSnakes007 https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1682 Fri, 05 Oct 2012 16:30:27 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1682 Instead of exporting to file, what should really happen is accessing Mitsuba via Python integration directly. But, in order for that to happen, you need to build the Mitsuba Python library at the same Python version as Blender. I think that step is easier now with Mitsuba 4.0, but, again, its the question of time and resources.

]]> By: Samuel https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1680 Fri, 05 Oct 2012 14:25:11 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1680 The blender integrator was not made by him.

http://bartoszstyperek.wordpress.com/2012/04/18/almost-instance-support-for-blender-mitsuba-exporter/

Here you go. Maybe he is making a new one for 4 now. I wish I could help him but I’m pretty nooby at python and don’t have the time to be honest.

]]> By: pxl666 https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1678 Fri, 05 Oct 2012 06:47:19 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1678 and the second – there was a blender mitsuba – any chances for update on this?

]]> By: pxl666 https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1674 Thu, 04 Oct 2012 22:10:42 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1674 yee
seldom i see such a great piece of code, not only well typed but well thought and clean – excellent job on that baby!

one thing – studio – ability to load mesh with tex and play within Mitsuba with matts & lights… this is im longing for…

]]> By: DED https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1657 Wed, 03 Oct 2012 14:19:50 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1657 Yeah, the crash reporter works fine for me as well, most of the time you have enough time to send the report. I’m a nitpicker, you know 😉

]]> By: TAK2HATA https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1656 Wed, 03 Oct 2012 12:52:38 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1656 Great work!
It works fine.

I like SSS boxes.
:)

]]> By: Michael https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1654 Wed, 03 Oct 2012 11:09:37 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1654 Thank you for all of your work Jakob, I’m just wondering, is everything within mitsuba material base, only manually inputted. Will there be a GUI for the material editing, kernel, camera, film?

]]> By: Yoran https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1652 Wed, 03 Oct 2012 07:15:52 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1652 Great find, that dll

]]> By: Wenzel Jakob https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1648 Wed, 03 Oct 2012 02:25:11 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1648 just saw that you already did — thanks :)

]]> By: Wenzel Jakob https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1647 Wed, 03 Oct 2012 02:21:39 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1647 Hi DED,

could you upload your scene to the bugtracker? That would be super-helpful!

The crash reporter on Windows is not ideal, though it seems to be doing its job most of the time (I’ve gotten a whole bunch automated emails and already fixed some of the issues).

Wenzel

]]> By: DED https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1646 Wed, 03 Oct 2012 01:36:00 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1646 Yeah, dll problem sorted out :)

Unfortunately, I’m still having crashes when combining the bidirectional integrator, a dielectric bsdf, and geometry with per-vertex normals (or that’s what it looks like, I haven’t been able to reproduce it with per-face normals). I’ll try to submit a report to the tracker.

Also, there’s a little problem not exactly related to the renderer itself: it looks like the crash message window is in the same process as the renderer, so when Windows kills the process because it’s not responding, the error window is also closed, and then you can’t click “OK” to submit the crash info. It would be better to create an independent process for it.

]]> By: mars https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1644 Tue, 02 Oct 2012 23:13:18 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1644 Thanks for Mitsuba 😉

Reading the Documentation atm, it’s also very well done!

]]> By: zsolnai https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1641 Tue, 02 Oct 2012 22:23:00 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1641 How true! Excellent job, mars. :)

]]> By: Wenzel Jakob https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1640 Tue, 02 Oct 2012 22:18:44 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1640 ha, gotcha! Excellent find — thanks mars.

]]> By: mars https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1639 Tue, 02 Oct 2012 22:17:32 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1639 For those who don’t want to randomly copy around DLLs, installing this runtime will also fix the issue:

http://registrationcenter.intel.com/irc_nas/2672/w_ccompxe_redist_msi_2011.11.344.zip

(via http://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-visual-fortran-composer-xe-for-windows/)

]]> By: mars https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1638 Tue, 02 Oct 2012 22:10:44 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1638 By using Dependency Walker I found out that bitmap.dll depends on svml_dispmd.dll that couldn’t be found.
I copied it over from Maya, it works! 😀
The fun thing about the “DLL not found” error is that it has no way to tell you *which* DLL in the loading chain actually wasn’t found.

]]> By: Wenzel Jakob https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1637 Tue, 02 Oct 2012 21:42:27 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1637 I refactored the loading to use the fancy boost::path representation, but then forgot to remove the “/” character — kind of stupid, really :)

]]> By: Wenzel Jakob https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1636 Tue, 02 Oct 2012 21:38:56 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1636 argh — ok, bear with me for a few minutes.

]]> By: mars https://www.mitsuba-renderer.org/devblog/2012/10/update-new-0-4-0-binaries-for-windows/#comment-1635 Tue, 02 Oct 2012 21:38:16 +0000 http://www.mitsuba-renderer.org/devblog/?p=719#comment-1635 The error message still has a forward slash after plugins.

In your change, it says, too:
+ fs::path shortName = fs::path(“plugins/”) / name;

However since the path resolve seems to work in general, the problem might be even more obscure. Are you sure you are handling the error from the DLL loading routine correctly? Maybe the “DLL not found” message can be caused some other way than just failed path resolves.

]]>