Hi Guys
I've been playing around with the free version of CR for a couple of days (thank you - it's amazing for us Mac users) and I've found it to be quite hit and miss on my setup, Mac for modelling and Linux box with the docker for rendering. When it works it's brilliant, but quite often it just refuses to see the 2nd box despite me feeding it the IP address (all on a fast wired LAN).
I was wondering if the newer versions for sponsors fixed any of this but I can't find a change log anywhere. Can you point me in the right direction?
Many thanks
Hi Dan, great to hear its working, the change log will be coming soon, we've had a bit of a restructure of the downloads page, now that's done we have time to focus on the change log :)
All the best
James
Hi James
Thanks so much for your quick response.
Oddly enough everything has been working fine today. I did checkout the port issue and it wasn't affecting either my Macbook or my headless Linux render box using your Docker container (not sure how to change the port of that anyway).
Back to the change log, I'd love to see this implemented. Seeing what bugs existed and were fixed along with new features is so helpful for end users like me, it's the first thing I check on anything I install and I'm sure I'm not alone. Cheers
Hi Dan, yeah, the change log is a work in progress, but I am happy to help you try and get V0.2.2 working, if we can nail down why you're having issues, then it might be worth your while upgrading.
I generally don't recommend people upgrading to solve issues, because the newer builds generally aren't intended to 'work' and the publicly available builds 'not work'. That would leave us in the situation of having the only solution for people to pay, and ultimately we want to have a freely available solution for all, and have those who use the software for regular paid work contribute accordingly.
So some of the most recent discoveries that impact stability we've found are that our networking library (which is really quite cool, not bashing it at all) we use (open source lib called zmq) doesn't filter network traffic once a connection is established, we thought it did.
You might find that you have other services running on your network at in the port range 9000-9025, which is what we currently use (though we will change to something that isn't on a currently IANA registered port range in the future).
I show you how to fix this problem (if you're affected by it) in this video (https://youtu.be/TOUSCaduE1s)
I tackle the problem in the first part of the video after the project update. Feel free to skip ahead past the intro and other stuff until you get to the part where I trouble shoot this I think its at 13 minutes in.
If you don't get any joy with that, let me know, really keen to solve your problems before you consider joining the development fund.
Cheers!