Loading...
> >

HELP... I'm Rendering In Morse Code!!! [RESOLVED]

JabbaJabba Posts: 1,460
edited October 2013 in Daz Studio Discussion

OK, here's one that's got me a bit worried. I opened a DUF scene filein the official release version of DAZ Studio, tried a test render and got a sequence of dashes across it.

I closed down DS and tried same scene in the Beta public build and it worked no problems.

That would be fine, except my release version of DS is now stuck giving me bleeding morse code over anything I try to render (example below). That said, if I use progressive render then I don't get the dashes across everything - but naturally I want to use 3Delight the way I normally would instead having to use progressive render.

I haven't submitted a support ticket at time of writing, as I'm clutching onto the hope that there's something so obvious that I've overlooked it and somebody here might just so happen to have an idea.

so if you know what this is... H E L P

Help.jpg
1080 x 1080 - 300K
Post edited by Jabba on

Comments

  • barbultbarbult Posts: 24,722
    edited October 2013

    I've never seen that, but you don't have more than one instance of DAZ Studio running at the same time, do you? Maybe both the Beta and Release open at the same time accidentally? Just a thought, based on something I saw in another thread.

    Post edited by barbult on
  • patience55patience55 Posts: 7,006
    edited December 1969

    THE MATRIX!!! {sorry}

  • Lissa_xyzLissa_xyz Posts: 6,116
    edited December 1969

    Strange. Looks almost like you're rendering through some sort of artistic camera that's not working right.

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,484
    edited December 1969

    do you have both the beta and public build installed?

  • JabbaJabba Posts: 1,460
    edited December 1969

    Thanks for the ideas - I do have both Beta and release versions installed but they've both worked fine until this only in my release version. My gut feeling is that some file somewhere has somehow managed to get corrupted (although a DS reinstall didn't fix it, so maybe not).

    Anyways, cheers again... I'll have a quick poke around now that I've had some rest and will submit a ticket once I've confirmed there's nothing else i can do.

  • StratDragonStratDragon Posts: 3,249
    edited December 1969

    Are you rendering in 3Delight or OpenGL?
    What are your system specs and what kind of Graphics Card do you have and how recent are your drivers for it?

  • Richard HaseltineRichard Haseltine Posts: 102,232
    edited December 1969

    Not much help, but I have seen this before and I think a fix was found. However that's all I can recall.

  • Scott LivingstonScott Livingston Posts: 4,344
    edited December 1969

    Richard Haseltine said:
    Not much help, but I have seen this before and I think a fix was found. However that's all I can recall.

    Was going to post the same. All searches I've tried have come up empty, but somewhere in the forum is more info on this. Wish I could be more help...I'll keep looking.
  • Scott LivingstonScott Livingston Posts: 4,344
    edited December 1969

    Found this thread on the same issue (or a similar-looking one)...not the one I was remembering but it may help...

  • SylvanSylvan Posts: 2,718
    edited December 1969

    Oh wow, I have to say that looks rather awesome Oo
    Hope you get it sorted out by the way!

  • JabbaJabba Posts: 1,460
    edited December 1969

    Phew, finally worked out what it was... well, sort of, enough to fix it at least.

    It seems to have been some sort of pixel filter corruption that saved to the DUF scene file, albeit don't know precisely how that happened (closed down DAZ Studio before save had fully completed maybe?)

    When I tried to manually alter my render settings, it made no difference. What finally fixed it was to open an old DUF scene file that also loaded the render settings I used for that old scene, and I've been back to normal since with everything working fine again.

    Needless to say that I deleted the dodgy DUF scene file so that I don't load it by accident in the future, but at least now I know to load a different DUF scene file to reset my settings if it happens again.

    Thanks again for all your input.

    P.S. - on the bright side, I did some renders on the public beta version before fixing this, and it's waaaay more stable on my system than the current release version of DS, so hope it'll make it to general release quite soon :)

Sign In or Register to comment.