Hi guys,
I’m having an issue with stoke not updating the FieldMagma object. With just a VectorNoise piped into the Magma flow velocity channel I cannot scrub and see any movement in the field.
If I check/uncheck the Auto-Update button, the field does shift, actually if I click just about any of the settings such as field bounds, Viewport Display on/off, etc it will update for that frame.
I have tested the field as a force on Fume and indeed, its only using whatever frame happened to be manually updated as the force. So its not just the viewport display (saw Crosbys earlier post).
I have double checked with Tobbe and the file works fine on his end (test max file attached). I have uninstalled/reinstalled Stoke.
I tested the scene in 2014 too and it works for me, but both Tobbe and I are running a newer build than you are. We intend to post it soon, but in the mean time you could ask Tobbe to send you the ZIPs I passed to him to update your version to the same build he is running. (I don’t want to send you mine because they are WIP and I don’t want to further destabilize your system )
Remind him to also send you the 2.0.5 installer I gave him. It copies some necessary DLLs you don’t have in Beta 3.
I can also send it to you if he does not have it anymore.
Returning to FieldMagma for some more testing. And more problems updating the field.
I knew it was just one of the many settings. Finally found that stoke, on my box, basically wont update or even provide the proper changing velocity of a PRT to a Field without “Limit to Custom Range” checked on the PRT loader. Without that, it just doesnt work. Ive had some trouble with other interactions with a PRT loader without that checked, so i gave it a try. fyi.
Incidentally also noticed with without “Limit to range” checked on the PRT Loader, the Stoke system itself wouldn’t show me the Dist. source channels. Now it does.
Thanks for your report!
We are aware of the issue and will try to address it in future Krakatoa versions (since it is a PRT Loader workflow problem, not really Stoke’s fault).
This would happen if the file sequence you picked is evaluated on a frame that does not exist. For example, if you save from frame 1 to 100 and you are on frame 0 and try to pick the PRT Loader, we have no way of knowing what channels might be available in that stream unless a valid frame is loaded. Even worse, if there is a frame and it contains 0 particles, I believe it wouldn’t get any info either.
It is possible to define a preset as Default for PRT Loaders to creating a new one would have the option checked. Unfortunately, it cannot press the button for you to set the min. and max. values to the available frames. But if you want to customize the PRT Loader to always be created with the Limit To Custom Range checked, that is possible already.
*Create a PRT Loader
*Check the “Limit To Custom Range” option
*Expand the Presets rollout
*Click on the “Save…” button
*Click on the “Limit To Range” item on the list to highlight it, removing all other highlights
*Enter “Custom Range Limit” as the Name: on top.
*Click “SAVE PRESET”
*Select “Custom Range Limit” on the Presets list and click “Set Default…” button. Confirm with YES.
*Delete the PRT Loader
*Create a new PRT Loader - it will have “Limit To Custom Range” checked!
)