MRF issueshttps://gitlab.inria.fr/pacanows/MRF/-/issues2021-06-29T16:39:26+02:00https://gitlab.inria.fr/pacanows/MRF/-/issues/205obj with loose vertices does not load2021-06-29T16:39:26+02:00COUTURIER Arthurobj with loose vertices does not loadI'm working with an obj file with vertices not linked to any faces. When loading the scene, Malia stop before opening the gui and without any error message. After removing manually the loose vertices the scene works fine.
Here is the co...I'm working with an obj file with vertices not linked to any faces. When loading the scene, Malia stop before opening the gui and without any error message. After removing manually the loose vertices the scene works fine.
Here is the console using the obj with loose vertices:
```python
> malia.exe -scene "./scenes/cor360_2020-10-29_4_80_N.msf" -i -nogui
Malia Rendering Engine Started
Starting to load Scene
[WARNING] ======> No spectral value found! Basic RGB uplifting
```
I'm using Malia-1.0.0-win64 available here https://pacanows.gitlabpages.inria.fr/MRF/apps/malia/main.md.html
I'm attaching a file with both working and not working scenes: [malia_issue_loose_vertice.zip](/uploads/46de3efa795469adcc0f9e232337afe9/malia_issue_loose_vertice.zip)https://gitlab.inria.fr/pacanows/MRF/-/issues/206Black faces with "principled" material2021-07-12T16:23:55+02:00COUTURIER ArthurBlack faces with "principled" materialSome faces of an obj are displayed completely black in Malia and they change depending on the camera left and right rotation (no effect seen on upward and downward rotation).
Base angle:
![2021-06-29_16_05_24-Malia_Renderer](/uploads/...Some faces of an obj are displayed completely black in Malia and they change depending on the camera left and right rotation (no effect seen on upward and downward rotation).
Base angle:
![2021-06-29_16_05_24-Malia_Renderer](/uploads/856484103752108be0477d83acc0a095/2021-06-29_16_05_24-Malia_Renderer.png)
2 rotations to the right:
![2021-06-29_16_06_03-Malia_Renderer](/uploads/7393108347f6e60a00e9bcf196d8d686/2021-06-29_16_06_03-Malia_Renderer.png)
2 rotations to the left:
![2021-06-29_16_06_09-Malia_Renderer](/uploads/60fba270a201244e3d5afe15ede2937f/2021-06-29_16_06_09-Malia_Renderer.png)
I'm using a material based on a material made by the blender bridge and with updated rgb values.
```xml
<material name="Default OBJ" type="principled">
<base_color>
<rgb_color b="0.0" g="0.6" r="0.0"/>
</base_color>
<roughness value="0.5"/>
<subsurface value="0.0"/>
<sheen value="0.0"/>
<sheenTint value="0.5"/>
<metallic value="0.0"/>
<specular value="0.5"/>
<specularTint value="0.0"/>
<anisotropic value="0.0"/>
<clearcoat value="0.0"/>
<clearcoatGloss value="0.03"/>
</material>
```
No black faces were observed with the "green" default lambert material.
I'm using Malia-1.0.0-win64 available here https://pacanows.gitlabpages.inria.fr/MRF/apps/malia/main.md.html
I'm attaching a file with the scene: [malia_issue_black_faces.zip](/uploads/3136e386396e3b61b88a5b780703c3c3/malia_issue_black_faces.zip)Malia 1.0 patchMURRAY DavidMURRAY Davidhttps://gitlab.inria.fr/pacanows/MRF/-/issues/207Error in exported image when using multiples spectral passes2021-07-09T13:54:09+02:00MURRAY DavidError in exported image when using multiples spectral passesWhen using multiple spectral passes (wpp > 1 & wpp < nb_wavelenghts), we get some spikes at the passes boundaries.
This is probably caused by our triangular filter when writing in the buffer.When using multiple spectral passes (wpp > 1 & wpp < nb_wavelenghts), we get some spikes at the passes boundaries.
This is probably caused by our triangular filter when writing in the buffer.Malia 1.0 patchMURRAY DavidMURRAY Davidhttps://gitlab.inria.fr/pacanows/MRF/-/issues/208Check GPU V-RAM when upload the rendering buffer2021-07-09T13:50:45+02:00MURRAY DavidCheck GPU V-RAM when upload the rendering bufferWe always try to upload the full spectral resolution for the output buffer. However, we do not check if enough V-RAM is available.
In case is not enough, we get this message:
[FATAL] ======> Optix Exception CAUGHT !!!
[FATAL] ======> E...We always try to upload the full spectral resolution for the output buffer. However, we do not check if enough V-RAM is available.
In case is not enough, we get this message:
[FATAL] ======> Optix Exception CAUGHT !!!
[FATAL] ======> Error Message: Memory allocation failed (Details: Function "_rtContextLaunch2D" caught exception: Out of memory)
We should either:
- display a more verbose message to suggest a smaller spectral or spatial resolution.
- split the image spatially to fit in V-RAM.
In interactive, it is probably best to use the first approach, and the second for offline.Malia 1.0 patchMURRAY DavidMURRAY Davidhttps://gitlab.inria.fr/pacanows/MRF/-/issues/209Camera change behavior2021-07-13T08:46:42+02:00MURRAY DavidCamera change behaviorFrom #173 regarding the behavior when switching between multiple cameras with different sensor resolution.
# Current behavior:
The initial resolution is that of the sensor (or the user commands).
When switching camera, we keep the curre...From #173 regarding the behavior when switching between multiple cameras with different sensor resolution.
# Current behavior:
The initial resolution is that of the sensor (or the user commands).
When switching camera, we keep the current resolution.
# Alternative possible behavior:
* Have a flag `_user_specified_window_size` set to `false` when the scene is loaded
* Set this flag to `true` when the user resize the window
* When changing camera:
* Change the window size if the flag is set to `false`
* Change the sensor size to fit the viewport if the flag is set to `true`Malia 1.1.0https://gitlab.inria.fr/pacanows/MRF/-/issues/210"translation" not working2021-07-13T17:38:08+02:00COUTURIER Arthur"translation" not workingI'm trying to move an wavefront object "plaque" I'm importing in a malia scene but the "translation" parameter did nothing, whatever the values I'm using. I've tried with int and float values but it didn't change the result.
I've tried t...I'm trying to move an wavefront object "plaque" I'm importing in a malia scene but the "translation" parameter did nothing, whatever the values I'm using. I've tried with int and float values but it didn't change the result.
I've tried to use a different modifier, namely "scale" and the size of the "plaque" object changed.
I've also tried to do the translation before and after the mesh.
Here are the file used for the scene : [malia_translation_issue.zip](/uploads/90d18a3e31b43365b20a5ffef2d3af83/malia_translation_issue.zip)
I'm using Malia-1.0.0-win64 available here https://pacanows.gitlabpages.inria.fr/MRF/apps/malia/main.md.html and I'm on windows 10.