I've noticed that when I export subframes using the USD exporter, the resulting files are named with integers. However, when I later use these files in the Solaris context, they play back at a slower pace. Adjusting the time codes doesn't seem to have much effect. What is the correct approach for dealing with this issue?

Do you have example data we could look at?

I can't post the original file and I've not been lucky yet to replicate a simpler version. I'm exporting a series of vdb with subframe data as usd. That creates a folder with integer numbered files. I read those into lops with an asset reference. So far so good but when exporting it as a layer and read it back in again it's retimed as if it is reading the frames as one frame per subframe. I possibly do a mistake somewhere.

When you say you're reading it back in, what are you referencing? The VDB files, or a USD file? You're right that we export the VDB files in an integer sequence. The association between those and the subframe they belong to should be handled in the USD. For example in a simple test I've got, I'm seeing:

Yes, I'm reading back usd. But there are more problems. I noticed that reading the usd in sops from a usd import gives me a different result from reading the same usd file in the Solaris context ( where it simply stops after a certain frame). Re-exporting doesn't help unless right before the usd exporter I filecache as usual and then the node below immediately export as usd. Something is buggy somwhere but I'm not sure where exactly. Somehow the network isn't evaluated properly. Maybe I have dig into a usda file.

If you get to the point where you have a reproducible scene that you're able to share (either here, or via support), I'll be happy to investigate further.

I've had more of these problems in another scene. I couldn't isolate the problem but managed to solve it by repeatedly writing new caches. The usd files always seem to be fine in the sop context. There's something happening in solaris when reading in usd files. It's possibly related to vdb files and something being cached in memory. Maybe a little what you get with textures not updating properly. For example, when lookdeving and repeatedly overwriting existing textures I had experiences with objects loading the wrong textures even after restarting houdini. I had to reboot the machine. It's pretty vague but it's the impression I get.