-
Notifications
You must be signed in to change notification settings - Fork 206
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
No (3D)Viewer in 1.2.0.0+ #5158
Comments
I'm not able to reproduce this and a quick look through the differences between versions hasn't given me any bright ideas. Could you try a few things to help us get to the bottom of this please?
|
Thanks for investigating this.
|
Oh, interesting! Do you know what locale setting you're using? Something with a European flavour perhaps? The output from Could you try setting the |
I can now reproduce this by setting |
You are right. My locale is set to:
Setting LC_NUMERIC=C indeed does help. Thanks a lot 👍🏻 |
I removed this in e323014 after verifying that the OCIO bug it worked around was now fixed properly. But what I didn't realise is that we have our _own_ equivalent bug in ImageEngine/cortex#1338. So I'm reverting the change until we have time to fix properly in Cortex. Fixed GafferHQ#5158
I removed this in e323014 after verifying that the OCIO bug it worked around was now fixed properly. But what I didn't realise is that we have our _own_ equivalent bug in ImageEngine/cortex#1338. So I'm reverting the change until we have time to fix properly in Cortex. Fixes GafferHQ#5158
Opened #5159 with a temporary fix that will go into the next version, and ImageEngine/cortex#1338 to eventually fix the underlying bug in Cortex. |
Thank you! |
Version: Gaffer 1.2.0.0-linux and later - 1.2.0.0a3 was fine
I'm on Linux Mint 21.1 x86_64, 5.15.0-60-generic, NVIDIA GeForce RTX 2070 SUPER Mobile / Max-Q with 525.85.12 drivers
Description
The "Viewer" doesn't show anything any more since version 1.2.0.0. Version 1.2.0.0a3 works as expected.
Steps to reproduce
This is 1.2.0.2 (1.2.0.0 and 1.2.0.1 behave the same):
The text was updated successfully, but these errors were encountered: