I have had this problem for awhile now and am only posting about it because the fix isnt as easy with the maya version.
Max:
Problem:Lets say I make 20 partitions. When they finish I go to load them and in the dialogue box it says partitions 11-18 cant be found.
Work Around: I click ok and load partitions 1-10,19 and 20. I click add files again and now 11-18 are available and it says the rest cant be found, so I load them giving me all my partitions.
Should be noted when they are added my particle count goes up and the files do contain data.
Maya.
Problem: When I load those same partitions in Maya it says 1-20 loaded,however my particle count matches what it did in max when I only had 1-10,19 and 20 loaded.
Work Around: I add files again to Maya clicking on partition 11 and it adds the 8 partitions giving files 1-28. matching the particle count I have in max with all 20 added. When I delete files 11-18 in Maya giving me Files 1-10-19,20-28 The particle count doesn’t change and still matches the particle count I had in max with 1-20 loaded proving 11-18 had no data.
Should be noted on 11-18 the files paths were connected right.
Partitioned with 1 machine 10 tasks on Deadline
Also when rendered out of max and maya with there respective work arounds the images are exactly the same
I have never experienced this on my systems, but during a visit to a facility last week I saw something strange that might be related.
They had a large SAN and when saving to it, files would appear to be there, but it would take a while before they were actually available to the loader to read. So the Windows Explorer was showing them as existing, but the loader could not really access them until some caches were flushed or something like that. It usually took a minute or two for them to become accessible.
So I have to ask first - where are your partitions stored? Local drives, file server, some Isilon system, or something else? Does this problem persist over time (e.g. if you save today but try to load tomorrow, does it make a difference)?
In the KMX PRT Loader, if you pick consistently the same frame, it will always add only the missing sequences. So if you picked frame 0000 and some partitions did not load, you can add them later by picking again frame 0000. Only the missing ones will be added. The KMX PRT Loader scripts use the MAXScript function doesFileExist() to determine whether the requested frame exists or not. It would be interesting to try calling that function on the file name of one of the “missing” partitions to see what it reports, and then wait some minutes and try again.
If my speculations about your storage caching and the possible influence it might have is incorrect, please let me know!
Was all out all last week. Will gather all the information today hopefully.
My partitions are stored on the file server.
The problem is consistent. I have saved the file re opened and tried it an other days. Same exact problem every time.
Can you try reproducing this by
*Saving locally
*Saving locally, but using the option in KMX to move or copy the results to the file server?
In the first case, we want to confirm that all 20 partitions load ok if saved to the local HDD.
In the second case, we want to see if saving locally and then moving the files to the server makes a difference compared to saving directly to the server.