When I first looked at this I felt certain it would come down to user error, not programming error. This is why it is important to reply and help people who need it because without some feedback they are certain to think it is a programming issue.
So now, I am very curious as to what the actual user error is? Either way, it is nice to know Octane doesn't disappoint when used properly.
Best of luck and thanks to both of you for hashing this out. Many of us are learning from this experiment.
I want my money back...
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
As I said - I don't see here any error at all (besides some objects' materials of this scene that are not set at all, but this situation is handled OK by the plugin). All works OK in actual plugin's 1.X and 2.X versions.rashadcarter wrote:So now, I am very curious as to what the actual user error is?
I think the "error" - was to use the very old, I'd say "archaic" plugin's version instead of timely switch to the actual versions. And "error" was to start the production project in beta version of the software. Moreover, the "error" was to place such an offensive "bug-reports" before even trying to switch to the actual version of software and see that it works OK there...
To all: For the future - place please all bug-reports into the current version plugin's thread in the plugin's forum section. Otherwise - you are risking that I would not see your bug-report at all. As before every new release - I always go through last plugin's version thread, and fix all the reports one by one. I don't scan all the forum for messages which have something about Blender plugin reported.
A little addition:
I've got this into PM:
The reason of that is simple: I just by intention did not spend the time unpacking all the textures of background hardly visible objects, as the amount of foreground objects is enough to see that all works OK using actual 1.55 - 5.2 plugin. So, this background object just has textures not unpacked.
As soon as I unpack its textures - this object always shows absolutely OK too, in both material view and in render-view, no matter how many times you switch back and forth.
I've got this into PM:
Still wrong.leonnn1 wrote:On the images you sent showed on the thread, as you can see, the building on the background is still swapping textures, at the first image that is on material shading you can see a building on the back texturized, but when you enter on the rendered shading it disappears too, the thing here is that the materials are not disappearing very close to the eye I think.
The reason of that is simple: I just by intention did not spend the time unpacking all the textures of background hardly visible objects, as the amount of foreground objects is enough to see that all works OK using actual 1.55 - 5.2 plugin. So, this background object just has textures not unpacked.
As soon as I unpack its textures - this object always shows absolutely OK too, in both material view and in render-view, no matter how many times you switch back and forth.