Those ones are FLAG_ID_OBJECT, FLAG_ID_MATERIAL and FLAG_SHADOW_PASS
You can take a look at the c++ SDK header maxwellenums.h

Thas functionality is not available, sorry.

I'm afraid you cannot delete a material from the scene and keep using the material interator. Try to store the materials you want to delete in a list, and then delete each one: scene = Cmaxwell(mwcallback_cb) scene.readMXS(mxsFile) material= CmaxwellMaterialIterator() mat = material.first(scene) mat...

Hello Mingfae,

we removed the "string" input parameter for getPath, use the FLAG_RENDER variable instead:

renderPath = scene.getPath(FLAG_RENDER)

I see that not all the C++ methods of the SDK that use mw::String as input/output parameters (or return value) are properly ported to Python. The following methods are problematic: Cmaxwell.getEngineVersionSaved Cmaxwell.setPaths Cmaxwell.getChannelUserSuffix Cmaxwell.getChannelSuffixActive Cmaxwell...

CmaxwellObject.getUVWChannelProperties is meant for procedural geometry objects, which UVs were generated by CmaxwellObject.generateCustomUVW. UV projection parameters used to generate UVs in Studio, in the way you show in the screenshot, are saved as "Maxwell Studio custom data" in the MXS, so they...

Nope

I need help here, can you tell me what line is giving unexpected results?

No, pymaxwell (and the C++ SDK) is just an API to handle MXS/MXM/MXI files. It doesn't connect with maxwell.exe in any way.

Of course you can do your own hacks with python, running maxwell in no-gui mode and parsing the render process command-line output, but you don't need pymaxwell for that.

We are aware of this bug. Found and fixed for the (coming soon) next release

The problem was that obj.getGeometryModifierExtensionParamsAtIndex (among other methods requesting MXParamlist data) was returning a copy of the data, instead of a reference (the original behaviour).

You mean automatically change the width/height internally in the SDK when you change the height/width by code? I am not sure if that is a good idea since most users won't expect that. Those kind of helpers in the UI are meant to make things easy for the user, but I think that bringing that funcional...

That happens when the MXS scene was saved with output image/mxi disabled. You should add the following command line flags to the script to force the image/mxi to be wrote:

parameters.append('-nomxi:off')
parameters.append('-noimage:off')

Some screenshots of the upcoming Benchwell v5






As you can see, in ths version we will show the charts in maxwell.exe too. [Note: the data showed is fake].

We can give you an ETA of 2 or 3 months. Sorry for the delay, I hope you understand that we need to focus on Maxwell 5 bugfixes and performance now :wink: I can tell you in advance that our plan is to have 2 benchmarks (maybe more in the middle term): one for CPU and one for GPU. We already have the...

Hello, you have found a bug here. Studio is not loading the default layout file properly (now its name must be defaultlayout_v5.stlay, by the way). This will be fixed in the next patch :wink: We need to review this, because the layouts in that "layout" folder are not needed anymore, we have them emb...