OTOY Forums

Yeah, it's academically interesting, but I think I'm throwing in the towel for 2.1 for now. Fun new things:

- I finally got my scene to load after removing the HDRI map, but now it just sprays the textures around randomly, some models are white, the walls have genesis 2 bump maps as diffuse and so on. This also happens when just loading sets from multiple iterations. Random variations on every load. This worked fine a few days ago

-Crashing on "building geometry", when the only object in the scene was a DAZ plane.

I've been keeping quiet, but reading the recent comments and I have to say I guess I am lucky I haven't had any problems with HDRI images....

I use them extensively and my last several projects haven't had any problems loading. However I mostly use reduced size HDRI, because of VRAM limitations. How big are your HDRI?

I use full sized HDRI sometimes too and no issues. I swap them out, change environments that have different ones, No issues.

EDIT: Can you say Jinx? Seriously I've done dozens of renders now with HDRI and Daz + Octane 2.1 with no issues. And today I try to add an HDRI and it crashed to desktop LOL....trying again.

OK second time I tried it no problems. Saved, closed daz, reloaded and it is OK. So i think it was just one of those random crashes.

I used a translator.
Sometimes the scene is large, there is no program to respond.

My guess is this:
The work in this environment.
-Is used in two of the monitor. (first : normal, second:Portrait mode)
-Characters Sub division level : 3
-OCDS Dimensions width 1200 height 1600.
-OCDS Rendering Full screen.(On the second monitor.)
-When it comes newly rendered automatically transferred to the first monitor.
-this process is repeated, an error occurs.


한국어
아주 큰 확률로 프로그램 응답이 없다.
나의 작업 환경이다.
-두개의 모니터를 사용한다 (1:가로, 2:세로)
-캐릭터 level :3
-OCDS 해상도는 가로:1200, 세로:1600 이다.
-렌더링은 두번째 화면에서 풀스크린으로 한다.
-창을 닫고 다시 렌더링 하면 OCDS렌더링 창이 자동으로 1번 모니터로 옮겨온다.
-이런 과정을 2~3번 정도 반복하면 에러 화면이 나타난다.

withgoodman wrote:I used a translator.
Sometimes the scene is large, there is no program to respond.

My guess is this:
The work in this environment.
-Is used in two of the monitor. (first : normal, second:Portrait mode)
-Characters Sub division level : 3
-OCDS Dimensions width 1200 height 1600.
-OCDS Rendering Full screen.(On the second monitor.)
-When it comes newly rendered automatically transferred to the first monitor.
-this process is repeated, an error occurs.

I also use 2 monitors. It always switches the render back to the first monitor. But I do not get an error message. Can you share your system specs? What video cards and RAM?

larsmidnatt wrote: I also use 2 monitors. It always switches the render back to the first monitor. But I do not get an error message. Can you share your system specs? What video cards and RAM?

The problem arises when changes pose to reload.
Not sure, but ...
This phenomenon seems to be only full screen when it appears.

CPU : Intel I7-3770K
OS : Windows7 64bit
Ram : 8Gb
Video Card : Preview (GTX560Ti 1Gb), Octane Only(GTX660Ti 3Gb)

I use three monitors myself, but until I'm doing something more than a "test" render, it's always just a window in the top right corner of the furthest right monitor and stays there (My saved render preset for previewing is at about half of 1080p , and the window is sized to such). If you are usually using it in full screen mode, that may be part of the issue, though it could be caused by any number of things if a full-screen is moving to the primary monitor. My first check would be to see if assigning that monitor you use as the display as the primary monitor fixes it, if it does, it's probably Windows doing it's thing and deciding where you want stuff for you. Happens frequently with various applications and games in my experience, regardless of where I may want them, so I just reassigned my monitors until the one in the center (which is where I prefer my focused applications that aren't spread over all three to be) is the primary. I presume the principle is likely the same or similar for this instance. If that doesn't alter the behavior, I'll try more extensive testing later on this afternoon, since I'm waiting for parts for my new render rig anyway.

Why is backwards compatibility always a problem with this plugin? Don't ruin our scenes in the pursuit of greatness.
I have large scenes created with 1.x with countless hours of tweaking which become a PITA (Pain In The A$$) with a newer version.
It makes me afraid to upgrade, because I know my time will be wasted trying to get them to look the same again.
It seems you guys reinvent the wheel with every version.

:/

Is animation working? I'm seeing the same frame (as the viewport is currently pointed to) regenerated each time.

edited and removed by user

Most programs do support prior save versions. Could you imagine if 3DS Max, Photoshop or Microsoft Office couldn't read their old files correctly? It is not an unreasonable expectation for users to have.

And while you may have a philosophical reason to want to redo all your work each time you render, not all of us agree. My old pieces don't hold be back in the slightest, but having to start from scratch each time does.

I do keep 1.x installed so I can quickly load up an existing scene and render when I want to leverage my prior efforts. But loading 1.x is starting to become a chore because I have grown used to the features of 2.x.

If we can get 2.x to work with my old scenes that would be fantastic. I don't know if that is why we haven't seen a recent update or not. I would at least agree to the idea that backwards compatibility shouldn't hold up other development right now. But unless t_3 tells us why we haven't gotten an update, we shouldn't speculate ourselves.