• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: August 3rd, 2023

help-circle
  • Ummm, 3DS is owned by Autodesk, so you may as well consider them the same thing for this conversation, and Arnold is a renderer (also owned by Autodesk) and not a DCC, so not really relevant unless you are specifically comparing Blender’s built-in render engines to it. The reason I am not is that there are lots of plugins for Blender which can output .ass files to be rendered by Arnold, so it can be utilized if you want to pay the subscription.

    Blender is a DCC. Not one that I am super familiar with, I’m a Houdini guy myself, but honestly it is better in a lot of ways than the steaming piles of shit that Autodesk puts out. The question is not one of quality or feature at this point, but one of capital and market share where it counts. If they could figure out what is needed to get the likes of Disney or MPC on board, or even smaller (though arguably still very large/high profile) houses on-board, then they would be seeing much more investment.


  • Gonna call you out on this, at least partially. It was SideFX, a real threat of a proprietary vendor who has sizable market share in 3D/VFX, releasing an entirely perpetually free learning edition and a low cost indie license who put the screws on Autodesk. Blender contributed to the decision, but it was absolutely not the primary pressure source.

    Source: I have a Masters Degree in VFX, have studied the industry for over 35 years, and have worked professionally in it for going on 15.







  • Not that I know of. In the end you are editing the browser rendering parameters. Anyone can inspect the page and see that the opacity on the page is being turned down. Finding where it is happening is the only thing you can really make hard. Have a couple of the pass through scripts be machine generated and you can have it use nonsensical variable names and a bunch of dummies that lead on wild goose chases. It could all be fixable, but you can make it a pain in the ass. Add a redundancy or two and it will make debugging a nightmare because even if one is fixed, the others will make it look as though it has not.

    The real answer is to have NEVER do freelance web development inside the client’s firewall. Never. If they try to require it, walk away. If it is inside their firewall then they can just take the source code and stiff you. If they try to spout some BS about security, say that is precisely what you are concerned about and point blank ask them what safeguards they are willing to allow you to put in place for developing in their system. If the answer is none, walk. If they are willing to let you VPN in, run the code from a local copy over the VPN and node lock it so if someone attempts to serve it from another machine it fails.

    Apologies. I’m tired and hate businesses taking advantage of “Independent Contractors”.