My isaac application suddenly couldn’t run, with the error:
2024-03-17 13:40:42 [288,737ms] [Error] [rtx.neuraylib.plugin] [MDLC:COMPILER] 1.0 MDLC comp error: http://omniverse-content-production.s3.us-west-2.amazonaws.com/Materials/vMaterials_2/Leather/ABS_Hard_Leather.mdl?watch=00007f204f21f930(1,1): C100 “mdl” expected
my version is 2022.2.1, it’s all normal last week, and i didn’t make any changes to the code, but it can not run. How can I solve it?
2024-03-17 13:47:31 [697,985ms] [Warning] [omni.usd] Default value for render setting “/rtx/shaderDb/cachePermutationIndex” not found
2024-03-17 13:47:31 [697,985ms] [Warning] [omni.usd] Default value for render setting “/rtx/pathtracing/nrc/canRun” not found
2024-03-17 13:47:31 [697,986ms] [Warning] [omni.usd] Default value for render setting “/rtx/materialDb/syncLoads” not found
2024-03-17 13:47:31 [697,987ms] [Warning] [omni.usd] Default value for render setting “/rtx/multiThreading/enabled” not found
2024-03-17 13:47:31 [697,988ms] [Warning] [omni.usd] Default value for render setting “/rtx/hydra/mdlMaterialWarmup” not found
2024-03-17 13:47:31 [697,988ms] [Warning] [omni.usd] Default value for render setting “/rtx/hydra/materialSyncLoads” not found
2024-03-17 13:47:37 [704,409ms] [Warning] [rtx.neuraylib.plugin] MATERIAL http://omniverse-content-production.s3.us-west-2.amazonaws.com/Materials/vMaterials_2/Leather/ABS_Hard_Leather.mdl?watch=00007f2066577af0 not found
2024-03-17 13:47:37 [704,409ms] [Error] [rtx.neuraylib.plugin] [MDLC:COMPILER] 1.0 MDLC comp error: http://omniverse-content-production.s3.us-west-2.amazonaws.com/Materials/vMaterials_2/Leather/ABS_Hard_Leather.mdl?watch=00007f2066577af0(1,1): C100 “mdl” expected
2024-03-17 13:47:37 [704,409ms] [Error] [rtx.neuraylib.plugin] Compiler Core: http://omniverse-content-production.s3.us-west-2.amazonaws.com/Materials/vMaterials_2/Leather/ABS_Hard_Leather.mdl?watch=00007f2066577af0(1,1): C100 “mdl” expected
2024-03-17 13:47:37 [704,410ms] [Warning] [rtx.neuraylib.plugin] Loading MdlModule to DB (rtx_scope) failed: ::Z6Ahttp_3A_2F::Z59omniverse_2Dcontent_2Dproduction_2Es3_2Eus_2Dwest_2D2_2Eamazonaws_2Ecom::Materials::vMaterials_2::Leather::ZE1ABS_5FHard_5FLeather_2Emdl
2024-03-17 13:47:37 [704,410ms] [Warning] [rtx.neuraylib.plugin] Loading transaction committed (this thread). MdlModule is NOT in the DB (rtx_scope): ::Z6Ahttp_3A_2F::Z59omniverse_2Dcontent_2Dproduction_2Es3_2Eus_2Dwest_2D2_2Eamazonaws_2Ecom::Materials::vMaterials_2::Leather::ZE1ABS_5FHard_5FLeather_2Emdl
@ rthaker
I met the same issue as you. Is there anyone know how to solve it?
I successfully ran my application yesterday.
@Robo_qq as another user, usually when i see MDL compiler errors is generally related to version mismatch of the shader definition, for a lack of better term. so, my suspicion is that this could mean you are on an older version of the app (which is the case with 2022.2.1) with older MDL implementation and trying to open a shader, or an asset with a relatively newer shader, that’s made using a newer MDL (in this case, ABS_Hard_Leather.mdl). though i cant say with 100% certainty thay this would completely prevent the app from launching.
you could confirm this by downloading the latest version of Isaac Sim and see if the issue persists. or, try to not use an asset that contains that MDL if you don’t wish to upgrade. last option could be to delete and avoid using the asset with that MDL (however, the same issue could come up again with other assets if there is no plan to upgrade).
if all else fails, you could try uploading the most recent .log file for further assessment. you can find the directory listed under section 1 of the link below:
Thanks, @Simplychenable . Why there is a new MDL appeared? I have always been using the 2022.2.1 version. If upgrade, I may face some API incompatibility issues.
Besides, I find that all the samples can not be shown in the 2022.2.1 now…
Hi, how do you solve it? I found that I can also open it, but the speed is very slow, each time I run my application, it takes a few minutes for loading.
just to clarify, my situation was slightly different than yours and in a different OV app (I was on Composer). that is to say my experience and findings may or may not be the exact reason why you are having the problem and should only be considered as a point of reference.
regarding the odd behaviors when opening assets shipped with OV, like the textures reported in the console, there were recent reports in other forums with no real actionable items on the user’s end:
to your knowledge, has there been any changes to your network connections or ports configuration?
