Hmm sorry couldn't reproduce this problem either. Are you using offline licensing? In which order do we have to launch the Standalone / slaves to reproduce the issue?Zay wrote:If you accidentally start two instances of the master or slave, you will be forced to use your login info next time it is run. Could you please fix that?
OctaneRender™ Standalone 3.00
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Ok, I see you have to be fast to provoke this problem. If I click my Octane Standalone icon twice within 1 second it happens. After the second click the sign-in window pops up.abstrax wrote:Hmm sorry couldn't reproduce this problem either. Are you using offline licensing? In which order do we have to launch the Standalone / slaves to reproduce the issue?
So try clicking fast
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
Thanks. I could reproduce it now.Zay wrote:Ok, I see you have to be fast to provoke this problem. If I click my Octane Standalone icon twice within 1 second it happens. After the second click the sign-in window pops up.abstrax wrote:Hmm sorry couldn't reproduce this problem either. Are you using offline licensing? In which order do we have to launch the Standalone / slaves to reproduce the issue?
So try clicking fast
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hi.
Any chance we will be able once to make things visible/invisible for refl. / refr. / selected lights? I know this is big time faking and OCTANE is all about photo real. Yet in CG is by itslef one big fake and this little addon would change so much.
Keep it up!
Moritz
Any chance we will be able once to make things visible/invisible for refl. / refr. / selected lights? I know this is big time faking and OCTANE is all about photo real. Yet in CG is by itslef one big fake and this little addon would change so much.
Keep it up!
Moritz
Supporting it inside Octane would result in the same slowdown.milanm wrote:Thanks Roeland, this helped me find where's the problem.
I did a bit of research and I discovered that ALL UVs are like that by default in Cinema 4D!
Further more, as far as I know, there is NO way to weld UV vertices in C4D!
When I imported the two obj plane files from your example I got the same issue with UVs on both of them.
At first I couldn't tell the difference, but after checking them out in a different 3d app I realized where's the problem..
Also, it's definitely not obj/FBX import issue because new geometry modeled and UV mapped in C4D also has the same issues.
I guess dealing with this in OctaneC4D plugin would slow down geometry updates, so the only way out for C4D users would be for Octane to support unstiched / unwelded / duplicated UVs. Without that, I'm afraid this feature would be useless for C4D users
Let me know if I can help in any way.
Thanks again.
Edit: ..Some references:
http://www.c4dcafe.com/ipb/forums/topic ... ent-583189
http://forums.cgsociety.org/showthread. ... ost5698826
Regards
Milan
I'm also not sure if it's a Cinema4D problem, if I import and then export the given OBJ file in cinema4D then the problem goes away. In the exported OBJ file the UV coordinates are merged. I'm not able to tell if this is a specific Cinema4D problem, or something specific that the plugin is doing, or something specific in your scene. I think it is best to check with aoktar in the Cinema4D forum.
Those topics talk about something different — having exactly one UV coordinate per vertex. That's not required, OpenSubdiv only requires that vertices of adjacent polygons in UV space have shared UV coordinates.
--
Roeland
Hi,
XP64bit incompatibility still persists. I've upgraded from v2.25 to v3.00 (winXP64bit). I deactivated Octane Licence (v 2.25) before installing v 3.00 and updated Nvidia (GTX 750 Ti) driver to driver version 10.18.13.682 (19.5.2016), but this error message still appears when I run the Octane:
Any ideas where could be an error?
Thanks,
Mik
XP64bit incompatibility still persists. I've upgraded from v2.25 to v3.00 (winXP64bit). I deactivated Octane Licence (v 2.25) before installing v 3.00 and updated Nvidia (GTX 750 Ti) driver to driver version 10.18.13.682 (19.5.2016), but this error message still appears when I run the Octane:
Any ideas where could be an error?
Thanks,
Mik
You do not have the required permissions to view the files attached to this post.
Hi Mik,
OctaneRender is 64 bit only, are you trying to run it at 32 bit?
ciao beppe
OctaneRender is 64 bit only, are you trying to run it at 32 bit?
ciao beppe
Hi beppe,
thanks for reply.
No, I run it at 64bit. It's interesting that Octane v2.25 works on same computer like a charm and all release from v 2.0 worked without problem, therefore it suprised me that upgrade to v 3.0 causes error message.
BTW: Nice profile picture, I use Bialetti Brikka
Ciao
Mik
thanks for reply.
No, I run it at 64bit. It's interesting that Octane v2.25 works on same computer like a charm and all release from v 2.0 worked without problem, therefore it suprised me that upgrade to v 3.0 causes error message.
BTW: Nice profile picture, I use Bialetti Brikka
Ciao
Mik
This feature will be added in the next release (3.03) so please keep an eye on the new releases sub-forum if you are interested.ROUBAL wrote:So, it would be useful to allow switching the images only for the display, without affecting the render.