AoA Graphic Art Cameras

HoppittyHoppitty Posts: 473
edited December 1969 in The Commons

So, I use these cameras pretty frequently: http://www.daz3d.com/graphic-art-cameras

And since updating to DAZ Studio 4.7 they don't seem to work. Not in preview renders, not in final renders... Are they broken right now, or is there some setting or such that I've missed with the new version?

«13

Comments

  • Cris PalominoCris Palomino Posts: 11,624
    edited December 1969

    It does say DS 4.6 and higher, but they might have meant within the 4.6 series. I would recommend submitting a ticket and/or contacting AoA through a PM in the forums.

  • namffuaknamffuak Posts: 4,176
    edited December 1969

    I just tried a quick test between 4.6.3.52 and the public beta of 4.7.0.12 and the camera doesn't work for me in the 4.7 version. What (if any) errors are you getting in the log?

  • R25SR25S Posts: 595
    edited December 1969

    It also say Compatible Software: DAZ Studio 4.7
    (can`t try it because I don`t own it)

  • MattymanxMattymanx Posts: 6,949
    edited December 1969

    Did you re-install the cameras?

  • ameesa001@gmail.comameesa001@gmail.com Posts: 282
    edited December 1969

    I don't use it much, but can confirm it's not working. I did a reinstall of the cameras. Here's any messages I have from doing a quick render.

    Rendering Image
    3Delight message #45 (Severity 2): S2050: cannot find shader 'brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager', will use 'null'
    Compiled C:/Users/Sandy/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager.sdl...
    stdin: in function shader_Imager

    stdin:159: ERROR: undefined variable 'time'

    Compilation of 'stdin' aborted due to errors: 1 errors, 0 warnings.


    Created RenderCacheBlock
    Finished Rendering

  • namffuaknamffuak Posts: 4,176
    edited December 1969

    I'm in the process of opening a trouble ticket on this even as I type here . . .

  • ameesa001@gmail.comameesa001@gmail.com Posts: 282
    edited December 1969

    Atmosphere cameras getting similar message. Heading for work, but leaving this info in case AoA looks in before I can add a ticket later.

  • HoppittyHoppitty Posts: 473
    edited December 1969

    Okay, tried to uninstall and re-install as suggested, still did not work. Played around with both regular lights and AoA advanced lights, no change. Only error is the standard "3Delight message #145 (Severity 1): S2073: 'SceneMin' is not a parameter of shader 'brickyard/{148dec1c-1a47-4fee-9c25-a139f25cfe9d}/shader_Imager" , which was a known issue as far as I know.

    Given that other people are having an issue, I guess it isn't just user-error on my part. :P I see namffuak is opening a support ticket; will it hurt or help if I open one, too..?

  • namffuaknamffuak Posts: 4,176
    edited December 1969

    Kaputcha said:
    Okay, tried to uninstall and re-install as suggested, still did not work. Played around with both regular lights and AoA advanced lights, no change. Only error is the standard "3Delight message #145 (Severity 1): S2073: 'SceneMin' is not a parameter of shader 'brickyard/{148dec1c-1a47-4fee-9c25-a139f25cfe9d}/shader_Imager" , which was a known issue as far as I know.

    Given that other people are having an issue, I guess it isn't just user-error on my part. :P I see namffuak is opening a support ticket; will it hurt or help if I open one, too..?

    What was that saying ' something like "In numbers there is strength"? Probably wouldn't hurt to pile on; my error report number is 180902 if you want to reference it.

    I went with bone simple for the report - DS_Oracle, the halftone camera, and the crazy chrome preset. No lights. Worked as expected in 4.6.3.52, did nothing in 4.7.0.12 - but I did get shader compile errors in 4.7.

  • kyoto kidkyoto kid Posts: 41,213
    edited December 1969

    Ameesa said:
    Atmosphere cameras getting similar message. Heading for work, but leaving this info in case AoA looks in before I can add a ticket later.

    ...interesting, I just rendered a scene using the EZ Volume Camera in 4.7 last night and it worked fine.

    I got the usual ['SceneMin' is not a parameter of shader brickyard] message in the render history/progress pane, but the camera worked as it should.

  • ameesa001@gmail.comameesa001@gmail.com Posts: 282
    edited December 1969

    Kyoto Kid said:
    Ameesa said:
    Atmosphere cameras getting similar message. Heading for work, but leaving this info in case AoA looks in before I can add a ticket later.

    ...interesting, I just rendered a scene using the EZ Volume Camera in 4.7 last night and it worked fine.

    I got the usual ['SceneMin' is not a parameter of shader brickyard] message in the render history/progress pane, but the camera worked as it should.

    I was trying a very quick render before I ran out the door, so that might be user error. Was using colorize cameras and didn't see much change from earlier render with other lighting. Still at work so can't try again.

  • ZarconDeeGrissomZarconDeeGrissom Posts: 5,412
    edited November 2014

    I just ran into an AoA shader issue as well, probably not just the cameras.
    http://www.daz3d.com/forums/viewreply/716085/
    I just updated while making some more patterns. Went to see them tiled, and no-go is Gogo. :coolhmm: (sp edit)

    SomeThingsHaveChanged_001.png
    1206 x 937 - 567K
    Post edited by ZarconDeeGrissom on
  • namffuaknamffuak Posts: 4,176
    edited December 1969

    I've run into that a couple of times, but not consistently enough to report it. Delete all files in the Studio temp directory and re-run the render.

  • ZarconDeeGrissomZarconDeeGrissom Posts: 5,412
    edited December 1969

    That worked, for the shader. thanks. I hope it something equally as simple for that camera set for y'all.

    I just shut down Daz Studio, and let it empty out the folder on it's own. I figured that was safer then yanking files out from under it.

  • kyoto kidkyoto kid Posts: 41,213
    edited December 1969

    ..OK ran several tests.

    Yes the Graphic Art Cameras do not work at all. What's more, they leave 3DL in a "running" status so I had to shut the programme down and restart it again.

    For the updated Atmospheric Cameras, the basic Fog, Volume, Depth and the EZ Volume Camera seem to work OK in 4.7 The Colorise Camera and Vignette effect for the Fog Camera however don't.

    Now switching to the ones labeled "Atmospheric Cameras DS 3-4" (which I believe are for use with older versions of Daz prior to 4.5), all the cameras seem to work normally. (including DOF). So if you have the "legacy" (DS 3-4) ones use them for now..

  • RuphussRuphuss Posts: 2,631
    edited December 1969

    any news here ?
    AoA Graphic Art Cameras is not working at all with studio 4.7

  • kyoto kidkyoto kid Posts: 41,213
    edited December 1969

    ...still haven't seen any product updates in the DIM. Is this being attended to?

  • RuphussRuphuss Posts: 2,631
    edited December 1969

    I would like to know this in general
    if a product does not work anymore after a daz studio update
    can we give it back for refund ?

  • SpitSpit Posts: 2,342
    edited December 1969

    I haven't updated yet because of the various AoA problems in 4.7. Strange that he hasn't been around at all to address any of this. Hopefully he's ok and just on a long holiday or something.

  • kyoto kidkyoto kid Posts: 41,213
    edited December 1969

    ...too late for me as I have created/modified several scenes in 4.7 and would not be able to open them if I rolled back.

    Been more than a month now.

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

    DS 4.7 scene files should open in 4.6, not that I'm recommending you roll back.

  • RuphussRuphuss Posts: 2,631
    edited December 1969

    ruphuss said:
    I would like to know this in general
    if a product does not work anymore after a daz studio update
    can we give it back for refund ?

    how did the daz company handle that in the past ?

  • icprncssicprncss Posts: 3,694
    edited December 1969

    ruphuss said:
    ruphuss said:
    I would like to know this in general
    if a product does not work anymore after a daz studio update
    can we give it back for refund ?

    how did the daz company handle that in the past ?

    Only if you purchased it within the last 30 days and it is not otherwise covered by a promo that does not allow returns. I have purchased a number of plugins over the years that have are no longer functional in the current versions of DS, have been added to DS in one way or another or the vendor has just ceased to provide update and support.

  • ChoholeChohole Posts: 33,604
    edited December 1969

    BTW this doesn't only happen with DS. Ask any Poser user about the changes in Python scripting from version to version. :roll:

  • barbultbarbult Posts: 24,777
    edited December 1969

    The DAZ store is still selling this product and advertising it as compatible with DS 4.7. Since it has been reported as broken in 4.7 by several people for over a month, it seems like there should be some change to the product page to indicate to potential purchasers that it currently does not work in 4.7. It irks me to see products advertised as compatible with a software version that they are NOT working in.

    Capture.JPG
    935 x 236 - 61K
  • SpottedKittySpottedKitty Posts: 7,232
    edited December 1969

    barbult said:
    The DAZ store is still selling this product and advertising it as compatible with DS 4.7.

    That compatibility line is misleading — it isn't a piece of text saying "DAZ Studio 4.7", it's a marker that gets substituted when the page is displayed, that means "whatever the current version is right now". All the store pages with D|S content are like that.

    Agreed, though, there really ought to be a mention on the store page whenever there's a problem like this.

  • kyoto kidkyoto kid Posts: 41,213
    edited December 2014

    ...just checked LDP2 and it only says "Daz Studio" which is pretty vague. Dreamlight never updated the original plugin for 4.0+ nor had any intent to do so. It should be noted somewhere on the product page "not compatible with Daz Studio 4.0 or higher".

    I hope that AoA's cameras are not permanently borked, particularly the Atmospheric Cameras as before 4.7 I used those a lot.

    Being on an extremely tight budget, not happy about the thought I wasted my meager resources on what now may be a "broken" product. Especially one that was so bloody useful.

    Post edited by kyoto kid on
  • icprncssicprncss Posts: 3,694
    edited December 1969

    chohole said:
    BTW this doesn't only happen with DS. Ask any Poser user about the changes in Python scripting from version to version. :roll:

    Not saying it doesn't. In fact, I have more Poser plugins and add ons that don't work in beyond certain versions than I do for DS. Which is why I still have the last stable releases of DS1, DS2, DS3A and a version DS4.6. Not to mention all versions of Poser from P5 to Pro 2014.

    Will DS4.0 and DS4.6 play well on the same system? I have some things that work better in 4.0.x than in 4.6.

  • jag11jag11 Posts: 885
    edited January 2015

    Ameesa said:
    I don't use it much, but can confirm it's not working. I did a reinstall of the cameras. Here's any messages I have from doing a quick render.

    Rendering Image
    3Delight message #45 (Severity 2): S2050: cannot find shader 'brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager', will use 'null'
    Compiled C:/Users/Sandy/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager.sdl...
    stdin: in function shader_Imager

    stdin:159: ERROR: undefined variable 'time'

    Compilation of 'stdin' aborted due to errors: 1 errors, 0 warnings.


    Created RenderCacheBlock
    Finished Rendering

    Found a temporary fix.

    Steps for Windows.
    1. Close DAZ Studio 4.7
    2. Open Advanced System Settings.
    3. Click on Environment Variables.
    4. Click New.
    5. Name: SHADERDL_OPTIONS
    6. Value: -Dtime=0
    7. Click Ok.
    8. Run DAZ Studio.
    9. Open Scene with any Art/Atmospheric Camera.
    10. Happy render.

    Post edited by jag11 on
  • SpeculativismSpeculativism Posts: 98
    edited December 1969

    jag11 said:
    Ameesa said:
    I don't use it much, but can confirm it's not working. I did a reinstall of the cameras. Here's any messages I have from doing a quick render.

    Rendering Image
    3Delight message #45 (Severity 2): S2050: cannot find shader 'brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager', will use 'null'
    Compiled C:/Users/Sandy/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/brickyard/{a350ae75-e965-4e84-a2ed-b9a9c9bd02be}/shader_Imager.sdl...
    stdin: in function shader_Imager

    stdin:159: ERROR: undefined variable 'time'

    Compilation of 'stdin' aborted due to errors: 1 errors, 0 warnings.


    Created RenderCacheBlock
    Finished Rendering

    Found a temporary fix.

    Steps for Windows.
    1. Close DAZ Studio 4.7
    2. Open Advanced System Settings.
    3. Click on Environment Variables.
    4. Click New.
    5. Name: SHADERDL_OPTIONS
    6. Value: -Dtime=0
    7. Click Ok.
    8. Run DAZ Studio.
    9. Open Scene with any Art/Atmospheric Camera.
    10. Happy render.

    Thanks. Well, that was good advice because it half fixed the problem. However, there are still issues remaining. Quite a few of the halftone and engrave effects in Age of Armour Graphic Art Cameras are not performing as expected.

    I applied "5. Name: SHADERDL_OPTIONS" and "6. Value: -Dtime=0" as advised above and then opened Daz Studio 4.7. I found that the graphic art cameras now work but effects such as "Heavy Lines Vertical", "Heavy Lines Horizontal", "Crazy Chroma" etc. produce only a whited out shape (or in some cases a greyed out shape or blacked out shape). However, by increasing the "Randomize strength" slider I can get these ones to have an effect (but not the effect which they are supposed to have).

    So, to sum up, there is still something wrong. Does anyone have any news of an update to this?

Sign In or Register to comment.