Yes exporter need some work.
1- Scenes exported as render targets
2- OCS export mode without geometry (and then we could simple export project as .obj and connect the materials/settings/nodes exported in the OCS file) - this is important because, for example, a big big project could be easily "worked in parts in SU" exported and join together in StandAlone. This happens in some projects, they start small and then get bigger and bigger, so the possibility to export and continue working in StandAlone should be present, and for now the result of the export is just crazy
Seekerfinder wrote:For me, the fact that we can IMPORT OCS files into the SU plugin as proxies is huge. It means I can export my base models from SU using Tig's tool, do my texturing as required in standalone and import those OCS files into my SU master model. These are assets I use repeatedly on different models so work done once is available always. Works great for archviz stuff.
Yes Seeker that is great, and its the way i do it too , but would be even better if we could have the same texturing scale(or whatever problem we have in that). viewtopic.php?f=31&t=41544&p=198537#p198537
For sure the StandAlone offers much more possibilities, that is true, and the plugins in is first steps, trying to fight the 32bit limitation, so lets hope we can get Fuzzy back to us and a few more correction to the plugin.
1- Rayepsilon - Sometimes it just gets crazy - dont know why...and we dont have the control.
2- Camera response - he have it but ist so hard to change it - the menu is very tricky
3- Zoom Option in Render Viewport - big renders are impossible to see.
4- Clay rendering
5- Save to OCS without geometry
6- Near Clip Depth