iMSTK issueshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues2019-08-03T18:26:15-04:00https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/232Group multiple projects into folders in msvc2019-08-03T18:26:15-04:00Sreekanth ArikatlaGroup multiple projects into folders in msvchttps://stackoverflow.com/questions/41078807/cmake-and-visualstudio-group-files-in-solution-explorerhttps://stackoverflow.com/questions/41078807/cmake-and-visualstudio-group-files-in-solution-explorerhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/230Remove cyclic dependencies in imstk libraries2019-09-07T19:22:39-04:00Sreekanth ArikatlaRemove cyclic dependencies in imstk libraries![graphviz](/uploads/ad7946f7c08d8bed1c2c800721085f3b/graphviz.png)![graphviz](/uploads/ad7946f7c08d8bed1c2c800721085f3b/graphviz.png)https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/229Unit tests for narrow-phase collision detections2019-07-28T16:21:22-04:00Nghia TruongUnit tests for narrow-phase collision detectionsThe new implemented NarrowPhaseCD (narrow-phase collision detection) does not have unit tests!The new implemented NarrowPhaseCD (narrow-phase collision detection) does not have unit tests!https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/228PBD constraints are shared pointers, and they are re-created at every time step2020-04-29T13:49:08-04:00Nghia TruongPBD constraints are shared pointers, and they are re-created at every time stepPBD constraints are shared pointers, and they are re-created at every time step. This is very costly.PBD constraints are shared pointers, and they are re-created at every time step. This is very costly.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/227Follow-up from "ENH: Vulkan display modes"2019-07-05T14:27:32-04:00Sreekanth ArikatlaFollow-up from "ENH: Vulkan display modes"The following discussion from !335 should be addressed:
- [x] @sreekanth-arikatla started a [discussion](https://gitlab.kitware.com/iMSTK/iMSTK/merge_requests/335#note_590381): (+2 comments)
> @NickMilef, Can process all the optio...The following discussion from !335 should be addressed:
- [x] @sreekanth-arikatla started a [discussion](https://gitlab.kitware.com/iMSTK/iMSTK/merge_requests/335#note_590381): (+2 comments)
> @NickMilef, Can process all the options here? Meaning if any mode is not supported log a warning and default to nearest available mode.
>
> `enum DisplayMode
> {
> SURFACE,
> WIREFRAME,
> POINTS,
> WIREFRAME_SURFACE
> };`https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/226Vulkan missing POINTS and SURFACE_WIREFRAME display modes2019-07-05T12:38:51-04:00Nicholas MilefVulkan missing POINTS and SURFACE_WIREFRAME display modesNicholas MilefNicholas Milefhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/225Vulkan validation fails2021-06-01T16:50:57-04:00Nghia TruongVulkan validation failsMy computer cannot run the examples with Vulkan backend. Vulkan Info app crashes immediately without any error message. The GPU is GTX 1080 Ti. Here is the log from examples:
```
Starting viewer
Vulkan Renderer Information:
Enabled ext...My computer cannot run the examples with Vulkan backend. Vulkan Info app crashes immediately without any error message. The GPU is GTX 1080 Ti. Here is the log from examples:
```
Starting viewer
Vulkan Renderer Information:
Enabled extension: VK_KHR_surface
Enabled extension: VK_KHR_win32_surface
Enabled extension: VK_EXT_debug_report
Validation: [ VUID-VkDeviceQueueCreateInfo-queueFamilyIndex-00381 ] Object: 0x20034e37ee0 (Type = 2) | vkCreateDevice: pCreateInfo->pQueueCreateInfos[0].queueFamilyIndex (= 0) is not less than any previously obtained pQueueFamilyPropertyCount from vkGetPhysicalDeviceQueueFamilyProperties (the pQueueFamilyPropertyCount was never obtained). The Vulkan spec states: queueFamilyIndex must be less than pQueueFamilyPropertyCount returned by vkGetPhysicalDeviceQueueFamilyProperties (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkDeviceQueueCreateInfo-queueFamilyIndex-00381)
```https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/224Extend visual model to Debug geometry2021-01-08T17:22:52-05:00Sreekanth ArikatlaExtend visual model to Debug geometryCurrently, the debug geometry directly take the render material. Since the regular objects take visualModel instead and the renderer pipeline has been updated accordingly, the material properties are not applied properly to the debug geo...Currently, the debug geometry directly take the render material. Since the regular objects take visualModel instead and the renderer pipeline has been updated accordingly, the material properties are not applied properly to the debug geometry. Besides the `updateDataSource` other calls in the `VTKRenderDelegate::update` like
```
this->updateActorTransform();
this->updateActorProperties();
```
are not applied properlyhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/223List of platforms supported by iMSTK2021-07-12T12:05:32-04:00Nicholas MilefList of platforms supported by iMSTKI think we should have a list of platforms that iMSTK intends to support (Windows 7 and above, Ubuntu for Linux, etc.).I think we should have a list of platforms that iMSTK intends to support (Windows 7 and above, Ubuntu for Linux, etc.).https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/222The code walk-through-example appears to be outdated.2020-12-08T10:20:43-05:00Sukhraj SinghThe code walk-through-example appears to be outdated.The walk-through example at: https://imstk.readthedocs.io/en/latest/documentation.html#walk-through-example appears to be outdated.
Further, why is it not part of examples, it looks like an interesting example.The walk-through example at: https://imstk.readthedocs.io/en/latest/documentation.html#walk-through-example appears to be outdated.
Further, why is it not part of examples, it looks like an interesting example.Release 2.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/221CMake 3.14x build issue2019-12-20T16:18:02-05:00Sreekanth ArikatlaCMake 3.14x build issueCMake 3.14X has an issue with mismatching x86 and x64 build config for dependenciesCMake 3.14X has an issue with mismatching x86 and x64 build config for dependenciesRelease 2.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/220getMaxNeighborDistance() in 'imstkPbdConstantDensityConstraint.h' returns wro...2019-07-04T16:30:17-04:00Nghia TruonggetMaxNeighborDistance() in 'imstkPbdConstantDensityConstraint.h' returns wrong valueBug:
```
double getMaxNeighborDistance() { return m_restDensity; }
```Bug:
```
double getMaxNeighborDistance() { return m_restDensity; }
```https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/219Using file types besides .veg in virtually coupled collisions2021-06-01T15:01:19-04:00Jonathon ScheningUsing file types besides .veg in virtually coupled collisionsWe have been unable to use .obj or .3ds files in the bone drilling example (by directly redefining the mesh) or in the virtual coupling example ( by bringing in our mesh by the same method and attempting point set to sphere collisions. P...We have been unable to use .obj or .3ds files in the bone drilling example (by directly redefining the mesh) or in the virtual coupling example ( by bringing in our mesh by the same method and attempting point set to sphere collisions. Please advise
auto heartMesh = MeshIO::read(iMSTK_DATA_ROOT"/baby/red_heart.3ds");
auto heartObject = std::make_shared<CollidingObject>("meshObject");
heartObject->setVisualGeometry(heartMesh);
heartObject->setCollidingGeometry(heartMesh);https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/218Add unique ID to all scene objects through Entity class2019-05-02T13:40:34-04:00Nicholas MilefAdd unique ID to all scene objects through Entity classAdd unique ID to all scene objects. This is necessary for networking. We can create an `Entity` class that will allow this to be possible.Add unique ID to all scene objects. This is necessary for networking. We can create an `Entity` class that will allow this to be possible.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/217Asian Dragon example mesh is not updating properly2019-04-28T17:03:04-04:00Nicholas MilefAsian Dragon example mesh is not updating properlyThe config SHA file seems to be invalid. The keys don't match :(.The config SHA file seems to be invalid. The keys don't match :(.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/216Add PhysX support for rigid bodies2019-07-28T15:59:38-04:00Nicholas MilefAdd PhysX support for rigid bodies@sreekanth\-arikatla@sreekanth\-arikatlahttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/215Add networking support to iMSTK2019-07-28T16:24:42-04:00Nicholas MilefAdd networking support to iMSTKiMSTK needs multiplayer support for collaborative applications.iMSTK needs multiplayer support for collaborative applications.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/214Vulkan VR mesh problems with Oculus Rift2019-07-05T11:31:29-04:00Nicholas MilefVulkan VR mesh problems with Oculus RiftConfiguration specs:
* GTX 1080
* Oculus Rift CV1
Mesh data appears to be corrupt in RenderDoc.
CC: @sreekanth\-arikatlaConfiguration specs:
* GTX 1080
* Oculus Rift CV1
Mesh data appears to be corrupt in RenderDoc.
CC: @sreekanth\-arikatlahttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/213Flickering of objects in Vulkan renderer when framerate goes below refresh rate2021-06-01T16:50:46-04:00Nicholas MilefFlickering of objects in Vulkan renderer when framerate goes below refresh rateSometimes objects start to flicker when the framerate goes below the refresh rate. This is primarily a concern for deformable objects. It appears to be caused by a synchronization issue, but I will look into this.Sometimes objects start to flicker when the framerate goes below the refresh rate. This is primarily a concern for deformable objects. It appears to be caused by a synchronization issue, but I will look into this.Nicholas MilefNicholas Milefhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/212Add VisualDeformable object type2019-07-28T15:38:32-04:00Zhaohui XiaAdd VisualDeformable object typeAdd `VisualDeformable` object type to allow for efficient handle of deformable geometry that doesn't use physics (PBD or FEM).Add `VisualDeformable` object type to allow for efficient handle of deformable geometry that doesn't use physics (PBD or FEM).