Does Daz Auto Update?
...OK been thinking about what happened after Monday night's "bluescreen" incident and 4.6 suddenly acting strange.
After several updates installed the following day I thought the number of them was strange in that I only manually selected a handful of Microsoft updates (5 or 6) as the entire list totalled over 400MB which with my connection at home would have taken forever. However, later when I shut my workstation down for the night the total updates that were downloaded was listed as thirteen.
The next day when I started up, everything was normal.
...until I opened 4.6 to find the UI had reverted to the default "Hollywood Blvd" scheme and the setup I had for my workflow was gone. When I finally got it all rebuilt and started reworking a scene that was corrupted he night of the bluescreen event, I noticed the Universal Manipulator tool was already active and there was a "Pin" function I never saw before associated with it. Now this morning, when I attempted to load some Gen4 clothing with Genesis selected, the Autofit selection pane did not pop up as it usually would. Thus requiring having to manually select the clothing item and click the "Fit To" button on the General parameters menu. Never had to do this before.
So this makes me wonder if some of those other "updates" that loaded the other night were not Daz Studio/content/plugin related which might have caused this?
Comments
No, DS does not auto-update. Was CMS running?
Your symptoms sound a lot like file corruption -- have you checked your hard drive?
...checked Windows Task Manager and yes, the CMS is running
Just wanted to know as the app does have a link function. I did also register/activate Reality 2.5 but wouldn't think that was responsible as I've added other plugins with no ill effect.
Checking the both drives now.
Scans turned up no bad file records, no bad sectors.
I had the very same situation a while back but my Windows 7 doesn't auto-update at all, and wasn't updated manually, so it came out of blue
Blue Screens CAN be caused by the OS and a App both allocating the same Section of Ram. Of course the OS is supposed to not allow that to happen but it can. Even the best programmers can not cover every possible System action. As long as it was not the Blue Screen of Death count yourselves lucky.
There was no (thankfully) blue screen. "Came out of blue" means it happened very suddenly and without an obvious reason.