-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Associate library materials effect with meshes #151
Conversation
Signed-off-by: ahcorde <[email protected]>
Signed-off-by: ahcorde <[email protected]>
Codecov Report
@@ Coverage Diff @@
## ign-common3 #151 +/- ##
===============================================
+ Coverage 75.01% 75.06% +0.04%
===============================================
Files 72 72
Lines 10215 10234 +19
===============================================
+ Hits 7663 7682 +19
Misses 2552 2552
Continue to review full report at Codecov.
|
Would it be possible to add a test? Maybe using the mesh provided in #91 ? |
Signed-off-by: ahcorde <[email protected]>
+1 for the test. Added here 188d06d |
Signed-off-by: ahcorde <[email protected]>
I'm sorry, @ahcorde , but this PR seems to break some other mesh parsing. X1 SubT robots are no longer blue, EXPLORER_DS1 has a weird red-ish color instead of carbon black... Check the behavior of ColladaLoader with This file has one TEST_F(ColladaLoader, LoadX1)
{
common::ColladaLoader loader;
common::Mesh *mesh = loader.Load("/home/peci1/.ignition/fuel/fuel.ignitionrobotics.org/openrobotics/models/x1 config 1/18/meshes/chassis.dae");
ASSERT_EQ(2u, mesh->SubMeshCount());
ASSERT_EQ(2u, mesh->MaterialCount());
EXPECT_EQ(0u, mesh->SubMeshByIndex(0).lock()->MaterialIndex());
EXPECT_EQ(1u, mesh->SubMeshByIndex(1).lock()->MaterialIndex());
} Reading through #91 and Collada spec, I think the mesh submitted by @jaelrod is not what he expected it to be. The "triangles" section (p. 188) says:
@jaelrod was concerned about reusability of the library geometries. But I think there was a misunderstanding on what does the The mesh from #91 could work if the default value for the I think this |
This reverts commit 89b1157. Signed-off-by: Louise Poubel <[email protected]>
This reverts commit 89b1157. Signed-off-by: Louise Poubel <[email protected]>
* 🎈 3.11.0 (#178) Signed-off-by: Louise Poubel <[email protected]> * Relax expectation so encoder test passes on ARM (#183) Signed-off-by: Louise Poubel <[email protected]> * Revert "Associate library materials effect with meshes (#151)" (#182) This reverts commit 89b1157. Signed-off-by: Louise Poubel <[email protected]> * 🎈 3.11.1 (#184) Signed-off-by: Louise Poubel <[email protected]> * Master branch updates (#179) Part of gazebo-tooling/release-tools#416 Signed-off-by: Louise Poubel <[email protected]> * Remove use of _SOURCE and _BINARY dirs in tests (#158) Test cleanup: Merges test/util.hh and test_config.h into a single file (fixes include path issues) Adds fixtures for retrieving test data from test/data folder Moves testing utilities into ignition::common::testing Signed-off-by: Michael Carroll <[email protected]> Co-authored-by: Jose Luis Rivero <[email protected]> Co-authored-by: Michael Carroll <[email protected]> Co-authored-by: Jose Luis Rivero <[email protected]>
This PR is related with this issue #91 (comment)
The material could be defined in Collada like this:
This kind of material definition were never associated with the mesh. This PR try to fix this issue.
Signed-off-by: ahcorde [email protected]