Scenes won’t save in Pro Public Build version of Daz Studio

I use both the Pro and Pro Public Build versions of Daz Studio, mostly so I can work on two scenes at the same time. I haven't had any problems with saving scenes in the Pro Public Build version of Daz Studio until the latest update to the Pro Public Build version that I installed through the Install manager a few days ago. When I attempt to save a scene in the Pro Public Build of Daz Studio, I get a notification from my Norton anti-virus software that it has blocked multiple suspicious actions from DazStudio.exe. You can see this in the first image I’ve uploaded. And then a pop-up window appears in Daz Studio that says “Failed to save a file. See the log for more details”. This can be seen in the second image I’ve uploaded. But when I pull up the log, all I see is a list of dates and numbers I don’t understand. You can see this in the third image I’ve uploaded. I’m not sure where this problem is coming from. I think it might be coming from the LAMH 2 Iray Catalyzer. I’ve had trouble using this in the Pro version of Daz, but I’ve been able to recently install it and use it in the Pro Public Build. But again, I’m not sure if that’s the source of the problem. Does anyone know how I can fix this? If someone chooses to help me, I might be asleep when they respond. But I’ll respond later today. 

Capture.PNG
303 x 246 - 18K
Capture2.PNG
356 x 164 - 7K
Capture 3.PNG
1440 x 866 - 88K

Comments

  • FrinkkyFrinkky Posts: 388

    There should be a setting in Norton to whitelist a program and/or folder. In this instance, add the Daz program folder to this whitelist.

    As an aside, the screen shot of the log file is not helpful... :)

  • Somehow Notepad is set to use huge fonts (try hitting ctrl 0 to reset the zoom), you have a horizontal scroll bar at the bottom which would let you see the imprtant parts of the messages. I suspect your save location was set to a protected folder like the application's own folder and that is why it is being blocked.

  • Epic82Epic82 Posts: 126
    edited September 2022

    I've attempted to whitelist Daz Studio Pro Public Build from Norton, but nothing has changed. To give anyone reading this an example of what's going on, I'm trying to save the scene in the first screenshot I've uploaded below. The second screenshot is that of Norton's Security History on my computer. It says "Data Protector has blocked a suspicious action by DazStudio.exe". I've gone to the settings of Norton, the third screenshot, and I've opened "Items to Exclude from Auto-Protect, Script Control,  Behavioral Protection and Download Intelligence Protection". The fourth screenshot shows where I've added the Daz Pro Public Build folder. But as I said, this doesn't solve the problem. Also, I've uploaded a screenshot of what this file looks like now in my Scenes folder, if this is helpful. There's an extra file on the side. What could I be doing wrong?

    Capture 6.PNG
    1920 x 1039 - 465K
    Capture 5.PNG
    801 x 536 - 64K
    Capture 7.PNG
    795 x 534 - 54K
    Capture 4.PNG
    796 x 533 - 26K
    Capture 8.PNG
    324 x 154 - 8K
    Post edited by Epic82 on
  • SevrinSevrin Posts: 6,309

    Maybe try specifically excluding DazStudio.exe, rather than the folder.

     

  • Epic82Epic82 Posts: 126

    I've discovered that the Pro Public Build refuses to save only old scenes. If I create a new scene in the Pro Public Build, it saves it without any problems. I don't know if this is valuable information for anyone. I just wanted to share this. I might have to submit a ticket for this issue.  

  • Epic82Epic82 Posts: 126

    Sevrin said:

    Maybe try specifically excluding DazStudio.exe, rather than the folder.

     

    Thank you Sevrin for your suggestion. I was able to find the file and exclude it from my Norton software's data protector.  

  • FishtalesFishtales Posts: 6,161

    Right click on the .duf file for the scene and look at Properties and see if it is set to read only. It looks like it doesn't want to save over the original scene. Try saving it as -002 and see what happens.

Sign In or Register to comment.