(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
with resource driving activities it is much more complicated. You can filter activities using any condition like Start Earlier Than selected activity start date.
Then create the separate project that includes only filtered activities and level them. but the results of levelling may be different because the criteria will be different - this time you will minimize the duration of different project. To have similar result you shall select Levelling option Previous Version Support and select the original project as the previous version.
In the levelled project apply the filter Total Float is less than the float of selected activity plus a little bit and you will have the subset of project activities that may delay selected activity or its predecessors.
Spider Project levelling report also lists all activities delayed due to resource unavailability.
In any case this analysis is much more complicated. Just imagine that some activity was delayed because resource A was busy. So activity starts when other activity that used resource A was finished. What if three activities that used resource A finished at the same moment? Which one shall be considered as the predecessor? I think that we will add all three though this is overkill.
But thank you for the idea - I will talk to our programmers about adding this functionality to Spider Project.
You shall select DRAG and then schedule the project to see the results. Inform me if there are still problems. Recently we discovered some minor error in DRAG calculation and so made some changes. I did not check if the latest Demo version was uploaded.
Best Regards,
Vladimir