If I right click on any simulator and choose PhoenixFD Export Particles, max 2015 will crash. In max 2014 it works.
Both tested with PhoenixFD 2.2.0 revision: 24491
Hi,
I can’t reproduce it using the latest official Phoenix FD 2.2 for V-Ray 3.0 revision 24510, which is on our web site.
Do you use the builds for V-Ray 3.0 or the 2.x ones ?
Are you sure this is the correct revision? 24491 is from 29 April - that’s not even 2.2 - it’s before the official release. Please check the latest Phoenix nightly 
I just downloaded it again. So it seems I didn’t have the latest revision. I tried with PhoenixFD 2.2 rev 24510 for vray 3 in max 2015 SP1 and I still got the same crash.
I tried also with the latest nightlies and I get the same crash.
I will try to uninstall other plugins until it works. i once had a trouble with the 3D connexion driver (spacepilot) that caused bugs in other plugins…
Do you have max 2015 SP1?
Yes, but can’t reproduce with several of my scenes. Does it happen with any scene for you, even a fresh one, or with a specific scene? In the latter case, is it possible for you to send it, so we can investigate?
I just uninstall almost all my other plugins and I still get the crash.
It crashes in any scenes even a fresh one. I create a PhoenixFD simulator, select it , right click and choose “Phoenix FD Export Particles” I then get the message: “An error has occurred and the application will now close. …”
I will uninstall max and erase any trace of plugins and then reinstall only max, vray and phoenixFD and see.
I uninstalled max 2015 and all plugins, erased all max folders, reinstalled max 2015, vray 3.00.07 official build and phoenixFD 2.2.0 rev 24810 latest nightly and I still get the crash. I also tried on different workstation and I get the same crash. I have windows 7 and dual xeons workstations… and you?
Just managed to reproduce it! I’m sorry you had to go through all this, I’ll ping you again when it’s fixed…
Ok pfiou… I was about to reinstall my whole computer! Thanks Svetlin!
It’s in - tomorrow’s build should be ok Thanks very much for this report!
All right thanks
You should make a contest and give additional PhoenixFD simulation licenses to people who finds such bugs! 
Hehe, indeed
+1 for that Joce
Woohoo! It’s working now with the latest nightly. Thank again Svetlin. byt the way is there now any way to get a changelog for each of the nightlies?
Yay! About the changelog - for now - negative. The more important new additions or bugfixes go into http://forums.chaosgroup.com/showthread.php?72190-Latest-changes/page6.
Ok cool!
Now what I wanted was to export drag particles with velocity on them and to use the prt object as a velocity source for StokeMX. So I created a PhoenixFD PRT object loading the exported prt sequence and selected it a velocity source in Stoke but when I tried to simulate with stoke, it errored saying there was no valid velocity source. So instead I created a Krakatoa prt object and loaded the phoenixFD prt sequence and used this instead for Stoke’s velocity, but it errored again saying that the file 0.prt did not exist… It’s because PhoenixFD export prt sequence starting with the file 1.prt instead of 0.prt. So I just copied the first prt file and renamed it 0.prt and then it worked.
So maybe the workflow could be polished but at least it works!
To avoid the error about 0.prt not existing, I can clip the range from 1 in the krakatoa prt loader instead so I don’t have to manually modify my prt files! But could you program it so that the particle exporter starts from zero?
I seee, we gotta add the zero frame then.
Just to make sure - was there a velocity channel in the phx prt export dialog? Drag particles don’t have their own vleocity, so you must have enabled velocity Output on the simulator.