I want my money back...

[leonnn1]

Your mistake for starting the project in beta software (moreover, which you do not know well) for the production.
I already see at least one mistake: you can't use the material preview and the live-render at the same time. The render server can only handle one render at a time, I wrote about it here.

If you are getting some issues in plugin software - to get them sorted out you should report it in the current version's thread in the Blender plugin's forum section. This is the only way I will ever see such reports. The whole forum is too big to scan it for just one plugin reports.
But even beta versions worked well when used by those who know how to work with it. E.g. this model has about 6'500'000 tris, and no absolutely problems during work with it: http://render.otoy.com/forum/viewtopic.php?f=5&t=42790

If you give me the scene - I can check at Monday what is wrong there.

The way how to free update your plugin license to last 2.X versions - was describen here on the forum. If you had troubles with updating your license - you could just email to Otoy support about them, as lot of others did...

So if a sofrware is not for Production Why in the world people should pay for it? Just to give money away? And 6.500.000 polygons with 3 materials is one thing, but 6.500.000 with 30, 40, materials is another.

Other than that this is really the bad way to gatter clients... Will talk with some people at the monday, thanks.

[JimStar]

I'm using the 1.55 - 52 version of the plugin, and the same for the server since I can´t use the newer plugin, and I don´t have a clue about why I just can´t use it.

Moreover, you are lying here. As I see on your screenshots - this is some earlier, still beta version. As the 5.2 version of plugin uses 2.71.5 version of Blender. On your screenshots - Blender 2.70.2, which was used in earlier beta versions of the plugin.

[leonnn1]

I'm lying? I posted for what I tought i have downloaded, I'm lying, what is your problem?

F*** this crap, I'm not lying, I just had this version of it witch I toght that was the one I downloaded, who the hell are you for tell me that I'm lying, I needed help on this matter and had none, my server I just can´t use and I paid for it, or I'm lying too, give me a break.

[leonnn1]

By the way, instead of acusing me of lie, show the link where I can solve my server not working problem, that it wold be something more helpful to do.

[JimStar]

So if a sofrware is not for Production Why in the world people should pay for it?

You have read the disclaimer stating that you are buying the beta version of the software. And you have agreed with that if you bought it finally (for the reduced price). And you have made mistake, starting the production project using beta software which you even do not know how to work with.

And yes, you are lying. As the version you are stating here you are working in (and getting the issues) - is really not the version shown on your screenshots. On your screenshots I see the really old beta version of the plugin. It seems this is the old plugin's version 4.1 beta, which had the 2.70.2 version of Blender... Not 5.2, which had a lot issues fixed, a lot of improvements, and is a lot more stable.

[JimStar]

By the way, instead of acusing me of lie, show the link where I can solve my server not working problem, that it wold be something more helpful to do.

No problem.
I need a detailed description (including the messages from Blender console), and it would be very helpful if you give me the scene where you are getting this issue.
If it is really the bug - it will be fixed in next version. If it is not the bug - I will explain you what is the problem...

[leonnn1]

So if a sofrware is not for Production Why in the world people should pay for it?

You have read the disclaimer stating that you are buying the beta version of the software. And you have agreed with that if you bought it finally (for the reduced price). And you have made mistake, starting the production project using beta software which you even do not know how to work with.

And yes, you are lying. As the version you are stating here you are working in (and getting the issues) - is really not the version shown on your screenshots. On your screenshots I see the really old beta version of the plugin. It seems this is the old plugin's version 4.1 beta, which had the 2.70.2 version of Blender... Not 5.2, which had a lot issues fixed, a lot of improvements, and is a lot more stable.

First, I allready rendered a video on Octane, this is one image of it: , so I´m not a new user to it.

Second, lie is intentional, by law ignorance about a fact is not lie, its just ignorance, I tought that I had this version because I have more than one computer, and i think that I downloaded this version for the other, and my mistake was to get confused, and if you are ablle to determinate which version of the plugin I use, why ask me for this information, since you allready had it?

And for the question I made before, you said that there was somewhere on this forum a thread to make me find a way to solve my problem with the octane server that are saying that my account is not valid or something like this.

I own the new version, and I want to test it, maybe this new version solve the bug.

By the way, maybe I over reacted about this matter, but I´m not wrong about it, indeed I paid for this program, and i want it to work, I would buy it for the higher price of a stable plugin easly, I don't care about the final price, I just needed something that work, and I used other beta programs and never had issues that impossibilitated me to finish something.

But I'll download this new version that I tought I had, if it works, its good enough, maybe this detail allready solve my problem.

[leonnn1]

It didn't worked on this version aswell, maybe on the 2.x.

[JimStar]

It didn't worked on this version swell, maybe on the 2.x.

I need the scene, to look what is wrong there. As there are no such problems in 5.2 version for complex exterior scenes I tried.
You can give me the link using personal messages if you don't like to share the scene here.

[JimStar]

Here you can access the file, I deleted the more heavy stuff to send it to you, otherwise you would have to download 300 mg file, but the problem persists on this too.

If you open it and check the material shading, you will see that it shows the materials as they should be, but if you see the rendered shading it will not work properly.

OK, I've downloaded your scene. Opened it in the plugin 1.55 - 5.2. Unpacked texture files. Tried to reproduce what you are reporting still happens in 5.2. It works absolutely OK.
And I remember exactly that the similar issue (materials swapped in some cases on the server after render refresh on the client) was found in some pre-5.0 beta versions and it was fixed starting from 5.X.
So, I asked my wife (she is experienced Blender artist: http://3d-look.com) to play with your scene back and forth inside 1.55 - 5.2 - she spent half an hour trying to achieve the wrong materials inside the render view with absolutely no luck. It works without any issues. It always gets the same materials on all objects of the scene after every live-view refresh or viewport mode switch. Material preview always shows correct materials of chosen object.

What is always shown in material view:

What is always shown after going to Octane Live-view:

On these first images, you can see the background building on the left, which has texture visible in material-view, but default Octane material in render-view. The reason of that is simple: I just by intention did not spend the time unpacking all the textures of background objects, as the amount of foreground objects is enough to see that all works OK. So, this background object just has textures not unpacked.
As soon as I unpack the textures - this object always shows absolutely OK too, in both material view and render-view, no matter how many times you switch back and forth.

The material of the fence (where you can see is "red" in material view) as seen is not set at all, it is not even the "node-material" - this is why it is always shown differently in material view and in Octane live-view where just default Octane material is shown. There are a lot of such not set materials in this scene.

This is the F12 render result:

Some other persp cam view (always renders the same after every viewport-mode switch too):