<launch> 
  <!-- Nodelet manager for this pipeline -->
  <node pkg="nodelet" type="nodelet" args="manager"
    name="record_player_manager" output="screen"/>

 <!-- Convert it into a point cloud -->
 <node pkg="nodelet" type="nodelet" name="cloudify"
    args="load depth_image_proc/point_cloud_xyzrgb record_player_manager --no-bond">
   <remap from="depth_registered/image_rect" to="zed/stereo/depth/image_rect"/>
   <remap from="depth_registered/points" to="camera/depth_registered/points"/>
   <remap from="rgb/image_rect_color" to="zed/stereo/left/image_rect"/>
   <remap from="rgb/camera_info" to="zed/stereo/depth/camera_info"/>
 </node>
</launch>

I have the launch file (above) for the depthimageproc nodelet. I'm trying to setup the subscriptions so that they match my publisher. Occasionally this launch file works but seemingly without any change it fails to link up the publishers and subscribers. I'm launching the publisher's launch file first and I can see that the data is being published viarostopic list -v or rviz. After I've verified it's up, I launch the file below and usually see something like this.

On a rare occasion I see something like this (which is what I want). Notice the connections from the /zed/stereo/* topics to the recordplayermanager node.

I don't change the sourced environments between these runs. I am running RQT on a separate computer than the running nodes but rostopic list -v (run on the computer running the nodelet) also confirms that there are no subscriptions for the remapped topics for the nodelet in the launch file.

Any ideas?