Reply to Re: hello, do 3d assets still exist?
If you don't have an account, just leave the password field blank.
Ok, so after talking with Skurn on discord and stuff, we figured out that all the textures used hardcoded absolute paths.
I tried to make a tool that replaces all the hardcoded paths with relative paths automagically in the .max files. The source for it is on github over here: https://github.com/drone1400/DinkModelPathFixer
The results I uploaded on my OneDrive over here: https://1drv.ms/u/s!AnJELDdVd4tqhApcnqEZ8fQd9A7j?e=OsSfgs
Basically, these should work in old versions of 3D Studio Max, and when you render the models they should have working textures. There were some errors though, for more info about them check the log file in the one drive zip, and read the info under Possible errors on github.
Some files probably need some additional manual tweaking, also they would still all need to be converted into something that Blender can use!...
Edit: Added a readme to the archive linking back here and included Seth's original post too.
I tried to make a tool that replaces all the hardcoded paths with relative paths automagically in the .max files. The source for it is on github over here: https://github.com/drone1400/DinkModelPathFixer
The results I uploaded on my OneDrive over here: https://1drv.ms/u/s!AnJELDdVd4tqhApcnqEZ8fQd9A7j?e=OsSfgs
Basically, these should work in old versions of 3D Studio Max, and when you render the models they should have working textures. There were some errors though, for more info about them check the log file in the one drive zip, and read the info under Possible errors on github.
Some files probably need some additional manual tweaking, also they would still all need to be converted into something that Blender can use!...
Edit: Added a readme to the archive linking back here and included Seth's original post too.
