Daz Studio freezes on startup
![alni](https://secure.gravatar.com/avatar/6624c2d760b14921dc1e72815e9496cc?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2F6624c2d760b14921dc1e72815e9496cc_100.png)
Hi.
I got a problem with Daz Studio Freezes on startup.
It goes as far as closing the splash screen and opening the main window.
But here it freezes. And after several hours it is still not responding.
- OS: Windows 10 Home 64 bit
- RAM: 8GB DDR3
- CPU: Intel Core i5-4460S
- GPU: NVIDIA GeForce GTX960 2GB GDDR5
- Computer: MSI Nightblade MI
I have attachec the latest entries from the Daz Studio Log file
txt![](/forums/plugins/FileUpload/images/file.png)
![](/forums/plugins/FileUpload/images/file.png)
txt
![](/forums/plugins/FileUpload/images/file.png)
log.txt
36K
Comments
Hi!
There is a whole bunch of warning messages you should have a peek at, but the most obvious thing I see is that the CMS does not work:
WARNING: dzvalentinaobjectdatabase.cpp(38): DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
WARNING: dzvalentinaobjectdatabase.cpp(38): DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
DB Register Open error: Cannot establish VC_Connection with remote server.
Make sure the server address and port number are correct.
Error connecting to CMS
I do not like the last warning from Qt:
Don't have that in my log, but it's just a warning, is it possible you have messed something up as you run it from F: ?
A few questions.
1 - Have you got it working before on this machine or is it a fresh install ?
2 - If yes on 1, have you changed anything ?
Hi.
I have now installed the PostreSQL CMS from the Install Manager.
Still freezes... (but the connection error in the output log is gone)
I have tried allowing both Daz Studio and the postresql.exe process (from the CMS) through the Windows Firewall
I am running from F: because the partition is on a 2TB HDD the C: partition is on a 128GB SSD.
Now to answer you questions :)
And I have changed where the Install Manger should install software from C:\Program Files< x86>\ to F:\Program Files< x86>\
Do you still get the:
At the end of the log file, I am not sure what it is, it's a Qt specfic file warning that should not be there, could be the reason.
As you can see below I have some other stuff after "Started in...", so it does look like it hang somewhere, but it's not easy to say why from the log file.
Creating Action Manager...
Creating Pane Manager...
Successfully created OpenGL viewport for AuxViewportView.
Executing startup script...
Started in: C:/Program Files/DAZ 3D/DAZStudio4 <------------------- your DS stops here, could be related to the QFile warning maybe ?
DAZ Studio Started
Creating Pixel Buffer
Pixel buffer - Width: 1024 Height: 1024
Compiling OpenGL Shader...
Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Shader Program successfully linked.
After installing the PostreSQL CMS the Daz Studio output logs goes as far as:
DAZ Studio Started
Creating Pixel Buffer
Pixel buffer - Width: 1024 Height: 1024
And I no longer have the Qt specific file warning in the output log for the last run
Also i noticed that the dblog.txt output log of the cms ends with:
alexa is the username for my local Windows user account.
A "role" is the access attributes for a user in PostgreSQL server (CMS), could be a problem, to access any data in the database the client must have a role defined that allows access to it, don't see that in my log file (and it's never good when it say FATAL), but it should all have been setup correct when you installed the CMS so I am not sure why you get that, maybe you can try to reinstall the CMS and see if it helps, sorry, I don't have any clever ideas at the moment.
It should not have anything to do with the firewall, there is no outside access needed, it uses the loopback device 127.0.0.1.
Hi.
I am sorry if this is a bump.
I just want to say that I have resloved the problem.