OTOY Forums

Terryvfx wrote:Speaking about improvements if the image node can have the name of the imported texture in its title that will be really helpful, similarly to the way the Standalone works.

My request: Pls try to be more friendly on post titles. Spreading words like that "Horrible", "Annoying", "Frustating" just makes me less motivative and giving sadness. These words are not completely to you. Sorry to write this.
Another one that comparing with other softwares are not making any sense on me. Because each software has different workflows. And plugins adopt theirself to this mechanism. Fixing something can cause another problems.
I'm just spending time to find best ways to do things. And believe that's not so easy as making requests. Sometimes one small addon could take weeks to finish and later i may see consequences of this revision.
Be sure i'll try to improve workflow as much as possible. But my priority is stability later user-friendly interface. I hope this makes some sense.
Btw i'm checking this image loading issue to see if there's something to avoid or making it faster.

Hi Terryvfx,
I have tried with yours high res 22k textures on a Mac Pro 2009 with standard SATA HD. Here is the differences between .jpg and .tif files on my old Mac:
[vimeo]http://www.vimeo.com/196590324[/vimeo]
There is a long delay only when a jpg file is loaded, while with tif there is almost no lag.
ciao beppe

After lot of hours on spent this my conclusions it this:
When you remove a texture connection from material it doesn't create this image to nodegraph. But when you reconnect it to material then recreates the image in nodegraph. See two images what i mean. Solution is to keep unconnected image in nodegraph. So this avoids the reloading of the image by octane. Like in next image.
But this can cause some new problems to avoid. Like occupying vram with unused images. Could you get what i mean?

To Aoktar:

Sorry, I wasn't thinking about how you might feel by the way I decided to call this thread, I'll be more responsible next time for sure.
I'm taking a note on your observation, it's very useful to know this things for current and future projects, I'm arranging to get at least one more card since either way with this problem or not it's going to improve my workflow.

To bepeg4D:

I converted the jpeg to tiff files and quite frankly the problem it's practically fixed, I'm not having lag at all and the interface it's very fluent, for having messed around with everything I cannot believe the idea of converting the images didn't come to my mind.

Even though I was rude I'm thankful for you guys taking your time and look into this issue.

If you could also take note of the idea of changing the name of the "image node' to the name of the imported image that will be awesome.

Thanks.