-
Notifications
You must be signed in to change notification settings - Fork 87
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
Rendering in Linux Editor #475
Comments
Both of those "raw response data" dumps look valid to me. The first is a glTF model, which is a binary file. The second is a a tileset.json which is a new tile subtree. Both types of data are extremely common tile content in Google Photorealistic 3D Tiles. I don't know what's causing |
It only fails to parse when I get the following data as a response
I think this line expects json https://github.com/CesiumGS/cesium-native/blob/main/Cesium3DTilesSelection/src/TilesetJsonLoader.cpp#L692 but the data is binary. I am not sure where the gltf responses are supposed to be handled so I can't tell if print is just a nuisance print. I did do some further testing later in the day and it looks like I am able to load and render the bing maps satellite and terrain data, so it seems like the issue is something specific with google maps 3d tiles. It also could be something specific with 3d tiles in general, so I tried to load a local 3d file as shown here. https://cesium.com/learn/unity/unity-datasets/#step-4-add-a-3d-tileset-from-a-local-directory However, I think when you load from a file cesium expects the path to start with C:// because on my machine it tried to change my file path from |
It's true that line expects JSON, but it shouldn't get to that line for a glTF. What project is this, and how is it configured? To test the plugin, I suggest using the Cesium for Unity Samples project. That will help eliminate various scene configuration problems as the source of your troubles. |
I did a whole lot more testing of this issue using the 07_CesiumGoogleMapsTiles example. I think that somehow here is the all the code I added to instrument. CesiumGS/cesium-native@main...ericjohnson97:cesium-native:bug/not_loading_3d_content The important line is here CesiumGS/cesium-native@main...ericjohnson97:cesium-native:bug/not_loading_3d_content#diff-13806feb0ee3c48c160f3fe8b915b9c4b7170b040966526354966b1bf695f745R939 I haven't tested the samples on windows, do you know if the google maps example is currently working on the latest release? If so I wonder what is different on linux. |
That's very strange. I can't really imagine why that wouldn't get called.
I don't think using SPDLOG this early in the startup process will work. It doesn't on Windows, at least. I suggest using the debugger instead of print statements.
Yes it's definitely working on Windows. |
My current setup is the following:
Ubuntu 22.04
Unity 2022.3.20f1
Cmake 3.28.6
Dotnet 8.0.300
NASM 2.15.05
I have been trying to give my image generator project linux support (https://github.com/ericjohnson97/iq_image_generator), but I have been running into some issues getting things going.
I have yet to be able to get the project to run and render tiles in the editor. I have been able to compile the game into an executable and get it to run and render on other computers sometimes. The executable errors might be seperate issues, so for this issue I want to focus on being able to get my setup to run and render in the unity editor on linux.
For context I have this PR on my project that has cesium-unity as a submodule and is supposed to be setup using the development instructions. ericjohnson97/iq_image_generator#8
However when I run the project in my unity editor I the tiles never show up. the only error message that ever shows is this.
I added some extra prints in
TilesetJsonLoader.cpp
to see the response. it seems like sometimes the response from google maps is justand the the json parser fails to parse
other times the response is actual json and it seems like it gets past parsing, but I still don't see any tiles.
I feel like this might be a red herring and not the actual issue, but do you all have any ideas on what might be happening?
The text was updated successfully, but these errors were encountered: