State:Closed|icon_bug|database:public|icon_mari|Resolution:Fixed|TargetRelease:3.4v1|BugID:336912|
Problem summary
In some sessions, when using the copyChannels function via the API, the texture data may be exported in an incorrect colorspace
Customer reported version
4.0v2
Customer reported platform
centos7
Steps to reproduce
1) Open the attached archive
2) In the Python Console palette, replace 'object1' and 'object2' in the below script with the name of the objects in the project and run:
import os
filename = 'DVA_4.0'
uvIndex = 210
dstUvIndex = 192
geo = mari.geo.find('object1')
patch = geo.patch(uvIndex)
exportDir = 'path/to/export/dir/'
if not os.path.exists(exportDir):
os.mkdir(exportDir)
mari.session.exportSession(exportDir, geoEntities=[geo],
geoPatches=[patch], projectors=[])
msfPath = os.path.join(exportDir, filename, filename+'.msf')
mariDstGeo = mari.geo.find('object2')
uvIndexMap = {uvIndex : [dstUvIndex]} ## in 3.1 keys must be strings
dstGeo = mari.session.types.GeoEntity.fromMariObject(mariDstGeo, None)
srcProj = mari.session.types.Project.fromMSF(msfPath)
srcGeo = srcProj.geoEntities[0]
copiedChannels = dstGeo.copyChannels(srcGeo.channels, uvIndexMap)
dstGeo.make()
We're sorry to hear that
Please tell us why