-
Notifications
You must be signed in to change notification settings - Fork 783
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
Feature with ModelSymbol with model node created from a FeatureSource not displayed #2312
Comments
It looks like a bug fixed in osgearth 3.4, a duplicate of #2299. I will update my osgearth version and confirm that. |
I tested with the master branch @ ed410ee, I confirm that creating a However, my problem still occurs while creating Features from a FeatureSource::createFeatureCursorImplementation implementation. |
Hi, can anybody help me about this problem please ? I cannot find any workaround (@gwaldron ?). |
Sorry for the delay. |
Hello, Thank you in advance for your help/feedback. |
I've pushed a fix for this to the master, it was an issue with an internal cache attempting to use the URI (which doesn't exist) as a key. Thanks for the example code, it was helpful to track the issue down. |
Hi @jasonbeverage, |
Hi to both of you @jasonbeverage & @gwaldron, Best regards. |
Discussed in #2311
Originally posted by sebalaig July 18, 2023
Hello,
I'm trying to display an OSG geode (in an osg file "arrow.osg") in my map using the Feature and ModelSymbol tools, but this is not working: nothing is visible. I'm missing something but I cannot figure out what's wrong..
Here is my code:
That code was ok using previous osgearth version (2.7) but fails with v3.3.
I tested by using
osg::Transform
to rotate/scale andGeoTransform
to set the model position => it ok.But in my context, I'm in an overload of FeatureSource::createFeatureCursorImplementation, so I have to build features, and it would be easier/cleaner to use osgearth API instead of OSG one's IMHO.
Thank you in advance for your help.
The text was updated successfully, but these errors were encountered: