-
windows platform, debug mode in visual studio 2015 community
1. using Y = slice(X,R,dim) gets totally wrong values...
2. in contrast, using slice(X,R,dim,Y) gets correct result.
-
hi, I came across a problem with framebuffer. below is my rendering code in drawContents(), I initialized nanogui::GLFramebuffer and ready() return OK. If rendering directly to window, it works well. …
ghost updated
8 years ago
-
From personal email:
> tried to use libigl by adding the the required libs to my C++ project and managed to debug the project without any issue.
> BUT, later I tried to run the tutorials in VS 2013.…
-
Suppose I'm writing a library that has some new widgets, maybe some new screens in it. I can expose those to Python using pybind11 without a problem, but I cannot find a way to express that they deriv…
-
Hi Wenzel,
Some widgets (in particular Label and Textbox) access mTheme in their constructor. mTheme is however copied from the parent widget otherwise it is a null pointer. This means you cannot cre…
-
All tutorials can run successfully in debug mode. Compilation in release mode is also okay! But when it runs to viewer.init() in release mode, the program crashes with error message:
Access violation…
-
- [x] Move to build with C++
- [x] Change GUI to use [nanogui](https://github.com/wjakob/nanogui)
- [ ] Change chunks to use std::shared_ptr
-
I've encountered a crash when I call slice() function of libigl in debug mode.
The problem seems due to the Eigen 3.2.4 ("libigl\external\nanogui\ext\eigen") under MSVC 2015.
The latest Eigen does not…
-
Hi,
I am a new user to libigl and used Eigen before.
Some compile errors occur when I compile the Example 102 following the instruments from tutorial use Clion IDE on mint linux 17.2. This is th…
-
Hi Wenzel,
When I use Instant mesh on a laptop, it draws my battery to 5% in 30minutes. At home, I monitored with GPU-Z on a 280X under windows. It shows that instant mesh uses 80% CPU just by moving …