BJ Camera Manager (Commercial)

13

Comments

  • barbultbarbult Posts: 26,178

    bluejaunte said:

    I will let them know... plugin publishing really seems borked. Release day was a mess as well angel

    Maybe it would be better if Daz actually tested the package content and functionality before telling you it was fixed. wink
    You can commiserate with PA Alvin Bemar. He has suffered many Daz plugin installation package problems. He makes great plugins, but you can almost always count on the installation package failing through no fault of his.

  • KerseyKersey Posts: 108

    Don't know if I'm the reason for the new package, but it was empty when I tried to install it 2 days ago. I asked support to fix it and QA then uploaded with a new package, which is empty too. Now it seems to be broken (empty) for everyone who updated with the new package in DIM.

  • bluejauntebluejaunte Posts: 1,990

    Try again guys? I can confirm that at least the manual download from my account now has all the files in it.

  • markusmaternmarkusmatern Posts: 597
    edited February 2024

    I downloaded it just now using DIM and the plugin works!

    It shows a package size of 915 kB

    When installerd this expands to 2.3 MB

    Post edited by markusmatern on
  • namffuaknamffuak Posts: 4,404

    Looks good -

    camera plugin.jpg
    502 x 532 - 26K
  • KerseyKersey Posts: 108

    It works now. Lovely. Looking forward to work with it.

  • barbultbarbult Posts: 26,178

    @bluejaunte I have a request if you decide to do another update sometime. I would like the Hide Cameras button to be a toggle (Hide/Show). My reason is that I frequently use ManFriday's Render Queue 3 with the option to "render all visible cameras". When cameras are added by BJ Camera Manager, they are automatically hidden (not visible). That means that rendering all visible cameras results in nothing being rendered. If I could toggle my cameras back to visible with a single Camera Manager button, that would be nice.

  • bluejauntebluejaunte Posts: 1,990

    Right. Sounds like a good idea. In the meantime you could probably find some script that shows/hides all camera.

  • barbultbarbult Posts: 26,178

    bluejaunte said:

    Right. Sounds like a good idea. In the meantime you could probably find some script that shows/hides all camera.

    Thanks for the suggestion. I was able to find a similar script that could easily modify to toggle the camera visibility, so I could turn them all back to visible On.

    In doing that search, it also occurred to me that if BJ Camera Manager Hide Cameras set Visible in Viewport to Off instead of Visible to Off, that would probably also solve my initial problem. If I understand correctly, your goal was to prevent the camera wireframes from appearing in the viewport as scene clutter. Visible in Viewport would achieve that, while leaving the overall Visible "On" for Render Queue 3 to recognize for rendering the scene from the visible camera(s).

    This is just something to consider if there is a future update. Either option, Hide Cameras toggle or using Visible in Viewport, would make me happy, but with the script I modified, I'm good for now. BJ Camera Manager is a helpful plugin.

  • bluejauntebluejaunte Posts: 1,990

    Didn't even know that existed. How does the user set it back to visible though, after a script/plugin set it to invisible?

  • barbultbarbult Posts: 26,178
    edited February 2024

    bluejaunte said:

    Didn't even know that existed. How does the user set it back to visible though, after a script/plugin set it to invisible?

     Visible in Viewport is a standard setting in the Parameters pane Display section. It is not just for cameras, either. It can be toggled on or off by script, or a user can simply open the pane and toggle the control there.

    Screenshot 2024-02-25 212733.jpg
    590 x 368 - 59K
    Post edited by barbult on
  • bluejauntebluejaunte Posts: 1,990

    Oh that thing... right, right.

  • barbultbarbult Posts: 26,178

    There was an update the BJ Camera Manager in DIM today.The product readme was not updated to indicate what changed. I installed it. I guess Daz screwed up the DIM package. It created a new subfolder "DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)" IN MY CONTENT LIBRARY, instead of installing the plugin and docs in C:/Program Files subfolders. 

    Screenshot 2025-10-02 222345.jpg
    845 x 176 - 35K
  • namffuaknamffuak Posts: 4,404
    edited October 3

    barbult said:

    There was an update the BJ Camera Manager in DIM today.The product readme was not updated to indicate what changed. I installed it. I guess Daz screwed up the DIM package. It created a new subfolder "DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)" IN MY CONTENT LIBRARY, instead of installing the plugin and docs in C:/Program Files subfolders. 

    Yes, it's hosed. But it should be installed in the docs and plugins directories of the installed studio executables - mine exist on E:\bits64\.

    The package is tagged 'General', not 'Plugin'.

    Post edited by namffuak on
  • bluejauntebluejaunte Posts: 1,990

    Hmm not good. Fixed tab orientation of pane group getting lost when toggling Aux pane.

  • barbultbarbult Posts: 26,178

    Customer Service responded to my Help Request and said that they pushed through an update to fix the problem, but there is no update in Ready to Download in DIM for me. Does anyone see an update in DIM on 2025-10-03? 

  • jjoynerjjoyner Posts: 748
    edited October 3

    I don't see a new update but I did install one on October 1.

     

    Update:  The October 1 update installed into my Content Library as welll.

    Camera Manger update.jpg
    1135 x 420 - 81K
    Camera Manger update installation.jpg
    770 x 716 - 92K
    Post edited by jjoyner on
  • barbultbarbult Posts: 26,178

    jjoyner said:

    I don't see a new update but I did install one on October 1.

     

    Update:  The October 1 update installed into my Content Library as welll.

    Thanks for the confirmation that today's update is not showing in DIM. Yesterday's update files don't belong in the Content Library, of course.  A plugin and its documentation will not work from the Content Library. I hope Daz can get this properly straightened out. 

  • namffuaknamffuak Posts: 4,404

    I just checked - there is a zip file in my product library which should not exist for a plugin

    The Supplement.dsx file in the zip:

    <ProductSupplement VERSION="0.1">
     <ProductName VALUE="BJ Camera Manager Plugin"/>
     <InstallTypes VALUE="Content"/>
     <ProductTags VALUE="Plugin"/>
    </ProductSupplement>

    The Manifest.dsx in the zip:

    <DAZInstallManifest VERSION="0.1">
     <GlobalID VALUE="d6c19638-75cf-4b91-b66e-f175d3a36280"/>
     <File TARGET="Content" ACTION="Install" VALUE="Content/DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/docs/Plugins/BJ Camera Manager/BJ Camera Manager.dsx"/>
     <File TARGET="Content" ACTION="Install" VALUE="Content/DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/docs/Plugins/BJ Camera Manager/BJ_CameraManager_Manual.pdf"/>
     <File TARGET="Content" ACTION="Install" VALUE="Content/DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/plugins/BJ_CameraManager.dll"/>
    </DAZInstallManifest>

    The working plugin zip, from my backup -

    Supplement.dsx:

    <ProductSupplement VERSION="0.1">
     <ProductName VALUE="BJ Camera Manager Plugin"/>
     <InstallTypes VALUE="Plugin"/>
     <ProductTags VALUE="DAZStudio4_5,Plugin,Win64"/>
    </ProductSupplement>

    and Manifest.dsx:

    <DAZInstallManifest VERSION="0.1">
     <GlobalID VALUE="f5e16c10-e445-4dfa-b570-b798f721bf1c"/>
     <File PLATFORM="PC" BITARCH="64" ACTION="Install" TARGET="Application" VERSION="4.5;4.x Public Build;4.x Publishing Build" TYPE="DAZ Studio" VALUE="DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/docs/Plugins/BJ Camera Manager/BJ Camera Manager.dsx"/>
     <File PLATFORM="PC" BITARCH="64" ACTION="Install" TARGET="Application" VERSION="4.5;4.x Public Build;4.x Publishing Build" TYPE="DAZ Studio" VALUE="DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/docs/Plugins/BJ Camera Manager/BJ_CameraManager_Manual.pdf"/>
     <File PLATFORM="PC" BITARCH="64" ACTION="Install" TARGET="Application" VERSION="4.5;4.x Public Build;4.x Publishing Build" TYPE="DAZ Studio" VALUE="DAZ Studio_4.5;4.x Public Build;4.x Publishing Build_(64-Bit)/plugins/BJ_CameraManager.dll"/>
    </DAZInstallManifest>

    The product library files are all dated October 3 - so still hosed.

     

  • bluejauntebluejaunte Posts: 1,990

    I was told it was fixed. So sorry guys, I doubt it's gonna be fixed before Monday now.

  • barbultbarbult Posts: 26,178

    bluejaunte said:

    I was told it was fixed. So sorry guys, I doubt it's gonna be fixed before Monday now.

    It is not your fault. Somebody at Daz is not packaging or tagging it correctly.

  • bluejauntebluejaunte Posts: 1,990

    True, I'm still sorry for my stuff not working either way smiley

  • namffuaknamffuak Posts: 4,404
    edited October 7

    I got an "update" in DIM tonight - files in the zip are dated 10-06.

    At this point I have to question the reading and comprehension skills of the person doing the packaging, as the product is plainly labeled BJ Camera Manager Plugin but the install information is still for Content, not Plugin.

    Post edited by namffuak on
  • barbultbarbult Posts: 26,178
    edited October 7

    namffuak said:

    I got an "update" in DIM tonight - files in the zip are dated 10-06.

    At this point I have to question the reading and comprehension skills of the person doing the packaging, as the product is plainly labeled BJ Camera Manager Plugin but the install information is still for Content, not Plugin.

    Hmm. I thought the update was installing correctly with DIM now. Is that wrong?

    Edit: Oh, no, they fooled me! You are right. DIM still put the plugin in the content library. What is wrong with these people? The plugin directory still has my old dll that I restored from backup last time. 

    Edit 2: I'm just copying the dll from the zip file and putting it where it belongs. Anything else seems hopeless.

    Post edited by barbult on
  • barbultbarbult Posts: 26,178

    When Josh Darling left months ago, Daz lost the person who knew how to package plugins for DIM. Then they eventually figured it out again. Now it looks like they've lost the magic formula again.

  • jjoynerjjoyner Posts: 748

    barbult said:

    namffuak said:

    I got an "update" in DIM tonight - files in the zip are dated 10-06.

    At this point I have to question the reading and comprehension skills of the person doing the packaging, as the product is plainly labeled BJ Camera Manager Plugin but the install information is still for Content, not Plugin.

    Hmm. I thought the update was installing correctly with DIM now. Is that wrong?

    Edit: Oh, no, they fooled me! You are right. DIM still put the plugin in the content library. What is wrong with these people? The plugin directory still has my old dll that I restored from backup last time. 

    Edit 2: I'm just copying the dll from the zip file and putting it where it belongs. Anything else seems hopeless.

     

    I saw the DIM update for the plugin yesterday as well but once I downloaded the zip file and explored it, I saw that the files would be installed in the same wrong places.  I decided to hold off on the DIM installation until I saw more discussion in this thread.  If I see no new DIM update with the files to be installed where they should be, I’ll follow your lead to manually place them.

    Thanks!.

  • namffuaknamffuak Posts: 4,404

    barbult said:

    When Josh Darling left months ago, Daz lost the person who knew how to package plugins for DIM. Then they eventually figured it out again. Now it looks like they've lost the magic formula again.

    I get the distinct impression that there are staffing, training, and documentation issues rearing their ugly heads. This is one example. A second example is the sheer number of new items showing up without readme files - and the fact that manually searching for higher-numbered  readme files doesn't work.

    And yesterday's flurry of issues with the forum didn't help either. 

  • bluejauntebluejaunte Posts: 1,990

    Try again guys, is it fixed?

  • OmnifluxOmniflux Posts: 427
    edited October 7

    Appears to be fixed with package 2025-10-07T10:25:16Z (Plugin version is 1.0.2.2)

     

    They renamed the plugin documentation folder though, and the online file list no longer contains the correct paths.

    Post edited by Omniflux on
  • namffuaknamffuak Posts: 4,404

    Yep - installed to the correct location.

Sign In or Register to comment.