battlestarvfx.com

I know a lot of people are thinking about returning their CORE subscriptions and getting their money back. I am considering it myself.

On the paper, it's amazing, and it will probably be once 3rd party developpers will dive in it and when it meets Lightwave 9.6 tools.
It won't be soon. But I'm sure at the end it will be great if they stop repeating the same mistakes and start to listen to their valuable customers as thelike it was planned in the CORE membership program.

Indeed but it may take a bit of pressure to get there.

I agree, timed versions are easier and you get to choose the time based on your development cycle.

It might be time outs and key files at this time. Our key files are going to be a little different though. I will explain later.
Speaking of which I owe you some of the images from the webinar this weekend. I will go eat, boot up the machines and post them in a bit.

I really enjoyed the ILWUG webinar and your others as well. I've told Wes he's hit upon a great business model with them. I can hardly wait for a Bakudan webinar to see you demo it in real time. I'm reasonably sure I will never have the skill with it you will. On the other hand I'm also reasonably sure your beta testers will each develop their own styles and looks. This is going to be fun!

I just had a thought. Wes, I hope you read this. Maybe a beta tester only webinar can be held for the day Bakudan is ready for the testers to get some initial training on it before we start stumbling about looking for bugs in an unfamiliar tool. I know I could really use a primer. Such a webinar should be free to the testers and subsequent dowloads should be restricted to the testers. I would also suggest minimal if any editing so folks that miss it can see all the warts plus the download turn around would be very quick so we can go back and study this or that particular aspect of the demo. If Bakudan crashes we should all see it so we can test the fault scenario or avoid it. Thoughts?

The components for Bakudan will be released in stages. First up, now that our solver is rock solid is to get that into lightwave with input controls and the ability to see it represented in layout itself. After that is our render component with the texturing system using the smoke shader only. The rest will come in sequence based off of feed back and bug testing and killing at that stage where we will introduce the other shading methods and types (smoke/fire, possibly water) and bring forward more advanced features like the GPU and in-layout-shader viewing stuff we have for seeing the CFD in different ways.