My guess is that there is still some kind of disconnect with the Toolset and the databases, as the following logs seem to show:
Thu Apr 11 06:27:30 2013, ERROR, ".\\ConnectionData.cpp", 177, "Unable to get campaign info (id:4) information in database ""Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET"""
Thu Apr 11 06:27:35 2013, ERROR, ".\\ConnectionData.cpp", 177, "Unable to get campaign info (id:3) information in database ""Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET"""
Thu Apr 11 06:27:48 2013, INFO, ".\\PluginAPI.cpp", 106, "Initializing toolset."
From Engine_dll_1:
10327 Graphics Ignoring invalid sampler state in state DefaultState: (7, SAMP_MAXANISOTROPY, 1) .\\MaterialState.cpp(257)
10389 Graphics Material Texture Parameter with sampler name [smpShadowPartition1] not found on the shaders -ignoring. .\\MaterialPass.cpp(1417) ...
10764 Graphics Ignoring invalid sampler state in state DefaultState: (7, SAMP_MAXANISOTROPY, 1)
.\\MaterialState.cpp(257)
10826 Error Parameter [g_vQuadOffset] was declared in an .mat file but not found on vertex shader [PassThrough.vsh] or pixel shader [IlluminationMask.psh] .\\MaterialPass.cpp(1715) ....
11513 Error Parameter [g_vQuadOffset] was declared in an .mat file but not found on vertex shader [ComposeDoF.vsh] or pixel shader [ComposeDoF.psh] .\\MaterialPass.cpp(1715)
11544 Graphics A parameter must be a child of a pass! Ignoring this parameter. .\\MaterialBuilderXML2.cpp(300)
11591 Graphics Material Texture parameter with sampler name [smpSceneDepth] specified an invalid stage. Updating its stage based on information obtained from the shader. .\\MaterialPass.cpp(1406) ....
I've edited the logs as I only wanted to show the jist of what is being reported: The Toolset is looking for components to open without success. I've tried uninstalling and reinstalling the Toolset and SQL following the various FAQ's and help guides but I end up with the same issue. What's even more annoying is that the Toolset had been working before the power outage and subsequent data corruption, so I know that it has that capability. Right now, it seems like the other aspects of the Toolset are useable, but I want to get it back to full-functionality. Any insights or advice would be appreciated!
Modifié par vinrioja, 11 avril 2013 - 10:49 .





Retour en haut






