-
Notifications
You must be signed in to change notification settings - Fork 156
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
Nextjs 14 - Clouds example - Does not work #185
Comments
@aaadamgo thanks for reaching out. Would you be able to replicate this example on https://codesandbox.io? This would give us a base for troubleshooting the issue further. |
Hey @vasturiano thanks! Ok so I've set it up on codesandbox, and if I use the following, it works perfectly fine.
Preview here: https://codesandbox.io/p/devbox/globe-test-n3xcpr Now, in my actual project, I'm using Spline for another component. In order for me to get Spline working properly, I need to use the following versions as it simply doesn't work on the latest yet;
Preview here: https://codesandbox.io/p/devbox/globe-test-v2-l4m42v |
@aaadamgo most likely that's because of the
v149 is bit too old. For the globe to behave properly the minimum version of |
@vasturiano yeah I understand that. Unfortunately spline doesn't work properly on the newer versions. I've tried every version above 149 to try both spline + globe together and there's always one or the other that doesn't work. Is there no other way to do this? The only issue is rendering the clouds. |
So, from going through nearly every thread here to figure out how to get it to render the globe and compile without errors, I did this with success.
I'm utilising the clouds example, to render the cloud image layer. Even using the exact same code, this is the console error;
I've tried everything I possibly can and the error persists.
Versions;
"three": "^0.149.0"
"react-globe.gl": "^2.28.0",
For full view of the code:
On a parent file i'm importing my 'world' component using the following;
Then on the World component...
The text was updated successfully, but these errors were encountered: