resmas wrote: 1- Scenes exported as Render targets.
2. Components should be instanced if possible since that's the way SU treats them to save memory;
3. I thought that groups in groups (or components within components) should somehow repeat that order in the node structure with geometry groups. But I am not so sure that it critical simply because, as long as the plugin works well and is stable, with 64bit and the Octane node structure exposed, would we still need to resort to Standalone at all?
Seekerfinder wrote:Thanks Fuzzy. Good to see you back on the job.
I have been working extensively in Sketchup 2014 and the Octane plugin recently. Besides 32bit performance limitations of SU and the continuing bug of some materials still losing their scale, I have really enjoyed the powerful combination of SU & Octane.
Specifically, regarding moving the material editor to node editor, may I request that one link, controllable from SU's material editor is retained? The 'global' material scale in the SU material editor, which saves us from having to manually adjust UV's for every pin individually on poorly created LiveDB materials... Ironically, I think this feature is buggy right now with some materials losing scale like I reported many times before, so it needs a bit of attention. But when it works it's brilliant. Incidentally, I personally don't have a need for trying to port Octame materials back to SU and I think it caused more hassles than it solved. Just my take on it.
It would be good to allow your beta group early access to the proposed structural changes for feedback - it would be good to make sure we don't lose any of the strenghts of the current offering, but rather build on them.
Users browsing this forum: No registered users and 1 guest