Hi
Got two similar Windows 7 Systems with different grafic cards, both running Maya 2013 SP2, with Octane 1.11a plugin. The same scene file with the same textures render differently on those systems. One system renders correctly, on the second one it seems to load the wrong texture for the object. For this scene only 177MB VRAM is in use, so it didn't reach the Limit of the grafic cards.
Does anyone has made the same experience?
Attached an example of such difference.
Best regards
Cyr
Textures not correctly linked
Moderator: JimStar
- cyrillweiss
- Posts: 91
- Joined: Wed Jun 02, 2010 2:52 pm
- Attachments
HW01:WIN10x64/X79/i7-3930K/64gb/GPU:1xTitan X, GTX 1080ti, SW:Maya2018/2019, Cinema 4D R20
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
- cyrillweiss
- Posts: 91
- Joined: Wed Jun 02, 2010 2:52 pm
Hi Chris
Thanks for your answer.
Multi-GPU is deactivated. Just updated the Nvidia driver but that didn't change the behaviour.
Just tried a couple of other scenes, which all rendered correct on the second system.
I could imagine, there is something in this scene file, which doesn't get handled correctly - possible kind of caching for the octane renderer?
Best regards
Cyr
Thanks for your answer.
Multi-GPU is deactivated. Just updated the Nvidia driver but that didn't change the behaviour.
Just tried a couple of other scenes, which all rendered correct on the second system.
I could imagine, there is something in this scene file, which doesn't get handled correctly - possible kind of caching for the octane renderer?
Best regards
Cyr
HW01:WIN10x64/X79/i7-3930K/64gb/GPU:1xTitan X, GTX 1080ti, SW:Maya2018/2019, Cinema 4D R20
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
- cyrillweiss
- Posts: 91
- Joined: Wed Jun 02, 2010 2:52 pm
Found the reason:
In the scene file was a mistake with UV Mapping. In verbose mode I found following:
After replacing the objects with the faulty UV Mapping, the textures of the other objects had the right place again. Still, can't figure out, why this didn't have such an impact on my other System.
@jimstar: In case you would like the scene file to analyse this, please let me know.
Best regards
Cyr
In the scene file was a mistake with UV Mapping. In verbose mode I found following:
Code: Select all
// Error: Octane: Error getting UV IDs of object: "Datencenter_Grundobjekte_v18:TuereRechtsShape1 (UV set "map1") //
// Error: Octane: Error getting UV IDs of object: "Datencenter_Grundobjekte_v18:TuereLinks_11Shape (UV set "map1") //
@jimstar: In case you would like the scene file to analyse this, please let me know.
Best regards
Cyr
HW01:WIN10x64/X79/i7-3930K/64gb/GPU:1xTitan X, GTX 1080ti, SW:Maya2018/2019, Cinema 4D R20
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...
HW02:WIN10x64/Z370/i7-8700K/64gb/GPU:1xTitan X, GTX 1080ti SW:Maya2018/2019, Cinema 4D R20
etc. ...