OTOY Forums

Loosing all (or 90%) of the linked network maps when doing conversions with either this one
https://render.otoy.com/forum/viewtopic.php?f=80&t=50645
or this one
https://render.otoy.com/forum/viewtopic.php?f=27&t=50249&hilit=assets

We can't upgrade to v3 for now.
When will this issue be fixed?

You do not exspect an answer, do you? XD
But will link me in, in case therr will be one.

What I expect is an answer like soon...on our list...after ORC...blabla
Azen said it will be fixed in "a handful of weeks" two weeks ago.
How can anyone work like this? Don't you have your assets saved on a local server?

Since i work alone mostly and outsource the modelling part only for certain projects I have them on another local drive.
But also Karbas last version with old material style. I want to upgrade to Octane 3 but can not without proper one-click integration. Just yesterday I was in need to open on old scene from 1,5 years ago.

I've just tested Saramary's converter on the scene with four RGB image textures all of them having files on the network drive (mapped as S:\ on my machine). No problems, after conversion all the textures have correct file paths pointing to the correct files on this network drive.
I've tried with 1.9 plugin version for exporting and both with 2.10 and 3.12 versions for importing - the paths converted correctly in both cases... Although Saramary does not recommend to use for import a versions other than 2.X, 'cause she tested (and used for her own scenes) the converter with some early 2.X plugin versions...

I can just presume that MaxScript's function setProperty <property name> <property value> may have some bug when it sets the "filename" attribute of the Bitmap-attribute of a node. Because if in some cases this same function used by the script sets the network filename without any problem, and in others it leaves it empty - this definitely looks like 3ds Max screws up something under the hood when this MaxScript function gets called with network-drive file path... Perhaps 3ds Max tries to check the availability of given file and does not set it if it's unavailable currently on the network from this machine... But perhaps just a one more 3ds Max bug, like screwing it up when setProperty is quickly called many times in cycle with network filename for Bitmap-attribute, so that some of calls just don't have any effect...

As a workaround you can try to overcome this bug, something like this:
- Use the computer having at least two physical drives.
- Copy all the textures from network drive to the second local drive (with the same hierarchy).
- Unmap the textures network drive.
- Change (in Windows drives settings) the letter of the second local drive to the letter you use for mapped network drive with textures. This way all the textures filenames in the scenes will have correct local drive paths.
- Run the batch conversion process of all your scenes (according to converter's description).
- Restore the local drive's letter back to what it was before, and map the network drive back with usual letter.

same here..many unsuccessfully converts and also old version projects like everywhere...I will stick to 1.9 until they have some clear solid solutions...for me, higher than 1.9 versions are totally useless....good luck v3

JimStar wrote:As a workaround you can try to overcome this bug, something like this:
- Use the computer having at least two physical drives.
- Copy all the textures from network drive to the second local drive (with the same hierarchy).
- Unmap the textures network drive.
- Change (in Windows drives settings) the letter of the second local drive to the letter you use for mapped network drive with textures. This way all the textures filenames in the scenes will have correct local drive paths.
- Run the batch conversion process of all your scenes (according to converter's description).
- Restore the local drive's letter back to what it was before, and map the network drive back with usual letter.

Ok, I will try that...Wait...No way I will try that! Please tell me this was just a joke.
Maybe it works with four little cute textures. Man, we have hundreds and hundreds of assets/textures. This sh*t is not working properly! And this is not a single case; others have the same problems.
We don't have any time for this. This whole thing sucks! No money/v3 upgrade from us.

Yup, it's true - Over 10,000 views just on the post Azen put up about the material converters so I think it's fair to say it's a major issue.

Neither of the converters work for me and Jimstar's solution sounds plain scary.

Been using Octane for years without a problem but this thing is a frigging brick wall.

I've already handed my loot over for v3, smacks forehead, and wasted days trying to get the materials to convert but no joy at all.

I'm hoping Azen is still on the case....

Jim, COMMUNICATE!
You wrote Saramary about the issues and he updated his converter.
So drop a line here to calm down the annoying users.

Annoying? Only get called that by the wife normally

Am currently sunning by the pool in Corfu happily thousands of miles from the PC. Life's hard.
So unfortunately not had chance to test saramarys latest version of her converter. I'd flagged up with Jim and azen that for me, Saramarys converter failed whenever the scene had even 1 map missing. Jim got in touch with her and she has now apparently fixed this. What a sad geek I am, wanting the holiday to finish early so I can test it.

Got to go, incoming pinacoladas...