Hi!
When you save or use ctrl + s, the textures are not overwritten in the folder texture, but these are cloned.
Thanks
Saving files, textures duplicated endlessly OR 2.22
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Thanks for the bug report. I think the issue is that you are importing some package (from LiveDB or LocalDB) and when the scene is saved the contained assets are unpacked, but the nodes are not switched to the unpacked assets. So the next time the scene is saved, they are unpacked again.Syd_86 wrote:Hi!
When you save or use ctrl + s, the textures are not overwritten in the folder texture, but these are cloned.
Thanks
That existing assets are not overwritten is done on purpose, but that the node items are not switched is a bug. The only workaround I can think of is to reopen the scene after you saved it. This will make sure that the file links point to the unpacked assets.
We will fix it as soon as possible.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yes, sorry about that. We will have a look at it next week. Unfortunately it's not super-trivial to fix, but I think we will get it sorted early next week. Of course, if it's becoming too annoying you can use 2.21 or older. 2.17 is the current stable version.Syd_86 wrote:If I add a new material with new textures, these are still cloned.
Should I reopen the file every time a material amount.
Not funny.
Thanks
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I have been thinking about this problem a bit more. Would it be ok for you, if Octane would not unpack assets from imported packages, but leave them where they are?
I think we can make it work, but the automatic unpacking of assets is introducing a lot of issues and shouldn't really be necessary anymore.
I think we can make it work, but the automatic unpacking of assets is introducing a lot of issues and shouldn't really be necessary anymore.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Imagine you drag/import a package into your project. This package may contain some image or geometry or other files that are used by the nodes that you have inserted in your project. At that point in time these files (/assets) are loaded from the package.Syd_86 wrote:I do not think you understand!
Avoid creating the texture folder automatically?
Now when you save the project these files will be unpacked and stored in a sub-folder next to you .ocs file and the links to those files in the nodes are stored as links to the unpacked files. In the past, any existing files got overwritten during saving. With 2.22 we don't overwrite files (which could be from other projects for example), but try to find an unused file name instead. Because the file reference in the nodes of the currently opened project are not switched when being saved, you get the problem you reported above.
As an alternative, we could just leave those files in the packages and not unpack them in the first place. Personally, I would prefer to leave those assets in the packages they come from originally.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
When I initially created the folder LocalDB, i saved all materials with textures in other folders. These never change.
If I move the texture with a stored position, octane warns me and asks to relink. But now, if you save a project, the link of the texture was referring to a material LocalDB are forgotten. Indeed A folder is created with the texture inside.
Within three months I find myself with dozens of texture folders for each project I do. Excluding clones of the bug.
This feature is useful but in my opinion only after work. If one needs. But for the materials in LocalDB, it is really useful?
Would not it be a better way to choose to save the texture pack?
When I open a material already created, this has all the information links of texture.
The textures are always there. Why copy?
It should be a command of choice. As the command save as package.
Octane needs to re-save the textures of the materials to work better?
If I did not understand this feature correct me.
Thanks
If I move the texture with a stored position, octane warns me and asks to relink. But now, if you save a project, the link of the texture was referring to a material LocalDB are forgotten. Indeed A folder is created with the texture inside.
Within three months I find myself with dozens of texture folders for each project I do. Excluding clones of the bug.
This feature is useful but in my opinion only after work. If one needs. But for the materials in LocalDB, it is really useful?
Would not it be a better way to choose to save the texture pack?
When I open a material already created, this has all the information links of texture.
The textures are always there. Why copy?
It should be a command of choice. As the command save as package.
Octane needs to re-save the textures of the materials to work better?
If I did not understand this feature correct me.
Thanks