Congrats on the new release new developer.
Here are my wishes I would like to have some answers please.
-------1-
I'd kindly ask you to lift off the block and enable us to post @ the every release topic .
It's really absurd to see that all other plugin topics lets people to post under the specific release topic.
But in max you cannot do that. Cant we be able to ask anything?
This was Jimstar's desicison at the time. I think he was frustrated by the users complaining about the 1.9 material problem in the first place.
For example I want to tell you that in the newest 4.18 it says tonemapping and gamma is not working properly.
I want to test new the older scene conversion feature and want to compare the old scenes with gamma and tone mapping.
I'll have to wait for the the new release where those gamma and tonemapping are corrected. Dont want to create another mess with my projects.
-------2-
I think there is a lua script working in standalone that would enable you to assign say, 10's of rgb textures to an array of instance objects.
Not the random tex . I mean actual jpeg textures scattered among instance objects. Like Forest pro or particles or instances of octane proxy objects. Can you make this happen?
-------3-
Neon, please make sure if you can finally put an end to 3dsmax Gamma issues.
Right now in order to get decent results with tonemapping,
- I set the max gamma settings as 2.2
- I set the current Max Gamma Hack checked
- I turn on the tonemapping by checking.
If you have an idea to correct this without messing the older scenes. You're very wellcome.
-------4-
We still have problems here saving image out of octane viewport directly. Especially with large Frame buffer images.
-------5-
And if we render as final render through max VFB when I cancel the render it asks if I want to save octane cache.
When I render 10K images it usually crashes if I say yes. Please make this question dialoge can be opted out in the render settings so we dont come up with crash after long hours of wait.
-------6-
Neon can I ask if you know maxscript???
if you do I think you can write a code or withthe help of maxscript create a light lister.
Maybe only for octane lights and ies lights but later on we'll need this for material/object lights later on.
The first dev Karba was very great but did not know maxscript..
Jimstar was great and all but. no maxscript with him as well.
I guess it would be really great if you knew this and might help us integrate octane better than ever.
I try to write simplest maxscript for my workflow but I do need help from the developer every time....
-------7-
We need a light lister for max. for ages. Can you do this via maxscript of by code?
There is an open source like script in scriptspot.com. Where people take that and adapt to vray, maxwell, and corona.
I tried to adapt this to octane but stuck at some point where I understand nothing
-------8-
The one that annoys me a lot is that (Max viewport) texture preview setting is too small 256x256 could you please make it higher as default?
OR what you can do is to link that you can link this to setting in the max' ordinary vieport Configuration dialogue under Display performance tab where you can adjust the resolution of texture maps and in viewport. You can link this to that. ?
-------10-
it would be really great if we could have some sort of render setting presets. Like in vray. So that we can save / load or set one of the presets to make it enabled as default. For example I never use directlight with diffuse PT is much faster and accurate. I'd the opportunity to set this as default.
-------11-
This is also problematic when you use octane cameras in rendering. Say you have bunch of cameras around and you have to set each one's imager settings for every one of them. Or you'll just need to copy same camera but if you change anything you'll have to manually do this over and over again. (Edit: What I mean by this is Octane Camera settings imager or all settings can be saved to a memory or file. and we can set the same setting on a different camera in the scene. You can either have 1-2-3-4 like memory buttons . or buttons that would enable us the match the camera imager settings to other cameras in the scene) Or something like that. Also a button to match render settings' (imager settings to the camera sellected or visa versa)
-------12-
It would be really great if we could only convert the materials of the selected object. Not the whole scene and bot whole material editor for god's sake. There are times where I manually and carefully try to convert say a vray material to OCtane. And I'd like to go back and forth for the material in the editor. So it's killing me have the automatic conversion for all scene every where.
-------13-
Also the checker grid in octane viewport when in alpha enables bugs me alot. It would be much better if we could change that to Black or white as well. .. I usually add a black viewport background image and that enable the black backgrnd in octane viewport to see a better representation whilst doing light desing on single objects.
I personally have been asking similar requests or years.
Woud be great to see and hear your approach on things.
Best,
