You DO know that the problem with the OpenGL viewport started with version 1.0
All older versions of Octane Reneder worked just fine with me
On board 8200 (Connected to monitor with CUDA Disabled so that it does not slow down system while working with Octane)
GTX 460 (NON connected... it's there just for octane)
OpenGL viewport
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.
-
Synthercat
- Posts: 284
- Joined: Mon Aug 30, 2010 11:12 am
- Location: Thessaloniki Greece
Linux Mint 19.3 | GTX-1080Ti | AMD FX-8320 (OCed 4.4GHz) | 16GB RAM
-
Synthercat
- Posts: 284
- Joined: Mon Aug 30, 2010 11:12 am
- Location: Thessaloniki Greece
oh I see! Let me try to explain then!
Windows XP 32 system (haven't tried it that's the case with Ubuntu studio 64 but tell me if you wan't me to try)
I start Blender
I create a scene
I manualy start Octane (in order to load a file and then implement a new object I create)
BUT!
When Octane starts I do not get the usual gray color on the viewport. All I get instead is this :
1. instead of the gray empty viewport I see the all there was in that portion of the screen before Octane started
2. Immediately after starting Octane there is a black color appearing as a vertical fill starting from the top of that viewport that goes till
the bottom part of it covering the Windows desktop portion that got stuck there. This vertical fill lasts something a bit less than a second
It usualy is not solid black at the botom but has some random gibberish (my guess is video card buffer?)
3. Garbage gone right after the scan completely fills black
4. It stays black!
If I try to start a new material and click on it I get a "something occurred on Octane and must shutdown blah blah"
I tried this and it worked...
a. Shut down Oct
b. Shut down blender
c. Restart Octane!
d. Restart blender
This was the only way to make it work! (Although sometimes when doing stage (d.) I had the 1-4 effect happening to blender viewport!
Maybe I should try to play with bios settings?
The thing is I didn't had this bellow Octane 1.00
Thank you for the support Marcus!
Windows XP 32 system (haven't tried it that's the case with Ubuntu studio 64 but tell me if you wan't me to try)
I start Blender
I create a scene
I manualy start Octane (in order to load a file and then implement a new object I create)
BUT!
When Octane starts I do not get the usual gray color on the viewport. All I get instead is this :
1. instead of the gray empty viewport I see the all there was in that portion of the screen before Octane started
2. Immediately after starting Octane there is a black color appearing as a vertical fill starting from the top of that viewport that goes till
the bottom part of it covering the Windows desktop portion that got stuck there. This vertical fill lasts something a bit less than a second
It usualy is not solid black at the botom but has some random gibberish (my guess is video card buffer?)
3. Garbage gone right after the scan completely fills black
4. It stays black!
If I try to start a new material and click on it I get a "something occurred on Octane and must shutdown blah blah"
I tried this and it worked...
a. Shut down Oct
b. Shut down blender
c. Restart Octane!
d. Restart blender
This was the only way to make it work! (Although sometimes when doing stage (d.) I had the 1-4 effect happening to blender viewport!
Maybe I should try to play with bios settings?
The thing is I didn't had this bellow Octane 1.00
Thank you for the support Marcus!
Linux Mint 19.3 | GTX-1080Ti | AMD FX-8320 (OCed 4.4GHz) | 16GB RAM
With one of the release candidates of version 1.00 we switched to a newer version libGLEW. That's the only thing I can imagine, that can have some impact here. Maybe it's worth making sure that you have the latest graphics driver installed, but if you don't get it working, maybe try version 1.03, which has a pure software display mode (not using OpenGL) which can be enabled in the preferences.
Cheers,
Marcus
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra