John-E Posted October 20, 2015 Share Posted October 20, 2015 (edited) Hello everyone,New T3D user here.Compiling the engine on VS 2015/Windows 10.-Debug mode: All's nice and cool!-Release mode: Error LNK2019unresolved external symbol __vsnprintf referenced in function "long __stdcall StringVPrintfWorkerA(char *,unsigned int,unsigned int *,char const *,char *)" blah blah blah blah blah buildFilesVisualStudio 2015projectsDxErr.lib(dxerra.obj)Seems like the project DLL is in trouble. Any ideas?Also why don't we get a project dll when the project generation is done using the project manager? Original garagegames.com Thread Link Edited October 22, 2015 by John-E Quote Link to comment Share on other sites More sharing options...
John-E Posted October 21, 2015 Author Share Posted October 21, 2015 So I guess I'm the only VS 2015 user? :? Quote Link to comment Share on other sites More sharing options...
JeffR Posted October 21, 2015 Share Posted October 21, 2015 I only have 2015 installed on my main desktop machine, so I'll see about trying to replicate this tonight. My guess is that, given the mention of the DXErr lib, is T3D still uses the old DirectX SDK, there may be some hangup there. Getting it switched to use the WindowsSDK is on the to-do list in the near future and could fix that. Quote Link to comment Share on other sites More sharing options...
John-E Posted October 21, 2015 Author Share Posted October 21, 2015 Hey JeffR,Thanks for the reply! I already fixed another DXErr.lib reference error but I can't get my head around this one. I really wonder why it only comes up with the release compiler. Quote Link to comment Share on other sites More sharing options...
bigmonkgames Posted October 26, 2015 Share Posted October 26, 2015 https://github.com/GarageGames/Torque3D/issues/1449 Quote Link to comment Share on other sites More sharing options...
John-E Posted October 27, 2015 Author Share Posted October 27, 2015 Hey bigmonk, thanks!I tried to comment off those lines too a few days ago and indeed it compiles. It works fine until you press ctrl+z. Then boom. Big time crash. So I just rolled back to VS2013 for the moment. At least until I figure out the basics. The engine needs a graphics update anyway so we'll be messing with it again soon. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.