Hi @egil.rasmussen ,
what InfraWorks version do you use?
Is there any error in the InfraWorks log file?
Do you have the original data source and does the 3D model display in the configuration if you load it again?
I think I have seen this lately in InfraWorks 2025, but assumed it's a data source issue since there 3D model could not be placed in the model at all.
Regards,
Karsten.
i am running the latest (ver 25.0.2.88), and see attached log. I can place the model, but it does not appear in the config window
Regards
Egil
Hi @egil.rasmussen ,
I don't know if it's the cause of the issue, but you are working on a model that is saved on OneDrive.
Please note that OneDrive doesn't like the files in the InfraWorks model database and tends to rename or remove them. That results in an error message and you cannot open the model anymore. It happens sooner or later if the model is on OneDrive.
It could be that the issue is part of a model of corruption.
See also: "Unable to Open Model" when opening a model in InfraWorks
Regards,
Karsten.
Hi @egil.rasmussen ,
have you changed the folders for local and cached cloud models to a local drive?
Your model is still placed on OneDrive.
Regards,
Karsten.
Hi @egil.rasmussen ,
I can recreate the issue with the missing preview of the 3D model on my side and forwarded it to the developers for investigation.
Regards,
Karsten.
Now i have changed the cache catalog, but still the model dont show i preview window
Regards
Egil
Hi @egil.rasmussen ,
the cached cloud models are saved on the D:\ drive now.
But if you create a new local model, it will still be on OneDrive - the path for local models can only be changed in the Windows Registry: How to change where InfraWorks models are cached
As mentioned in my message yesterday, I can recreate the missing preview of 3D models. I believe it's a program issue and informed the development team about it.
Regards,
Karsten.
I wonder if this is related to https://forums.autodesk.com/t5/infraworks-forum/error-47-missing-inventor-server/td-p/13297980#messa...
I was hoping the latest update would fix this, but now I get error message 43
Regards
Egil