andrew.tan Posted January 9, 2014 Share Posted January 9, 2014 Hi, We are trying to build some of the samples (Callbacks, Classes, Arrays) under the source folder but always receive a: Unigine fatal error Unigine::Engine::init() bad version 0x00004009 0x10004009 We are using the latest evaluation SDK - "Sim Evaluation Kit Windows (exe) 2013-12-28" with VS 2010 C++ Express, VS 2012 Pro and Win SDK 7.1 installed on Windows 7, x64 edition. We have tried to compile and run the sample codes using VS2010/13, both x86 and x64 build throw out the same error. We have tried to use the command prompt to perform the build by <path_to_unigine_root>\externs\setenv.bat x86 <path_to_unigine_root>\externs\bin\make_x86.bat -f Makefile.win32 (same for x64) Both resulting .exe files throws the same error. Creating other Win32-based projects in VS2010/12 do not have this issue. The Unigine benchmark, tools and other binaries are running fine. We need to complete an integration with Unigine and external C++ code (callbacks, .dll, or in order to complete our technical evaluation of Unigine. Hopefully someone could assist in this so we can move on to the actual integration work... :) Thank you very much!! --- The exception details from MS WindowsProblem signature: Problem Event Name: APPCRASH Application Name: Arrays.exe Application Version: 1.0.0.0 Application Timestamp: 52ce424e Fault Module Name: MSVCR100.dll Fault Module Version: 10.0.40219.325 Fault Module Timestamp: 4df2bcac Exception Code: 40000015 Exception Offset: 00000000000761c9 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: a23e Additional Information 2: a23e5d4b0da6ae250a483352ee5555b3 Additional Information 3: 5f43 Additional Information 4: 5f43f9219a36d8aed1c02be64a09fa23ENV variables: partial %PATH% = G:\UnigineSim\bin;G:\UnigineSim\bin\x64;G:\UnigineSim\lib;G:\UnigineSim\externs\bin; %WINSDK71_DIR%=C:\Program Files\Microsoft SDKs\Windows\v7.1 Python 2.7.6 32-bit, pywin32 and scons have also been installed (issues with using the x64 bit python and scons). Link to comment
silent Posted January 9, 2014 Share Posted January 9, 2014 Hi Andrew, You should build binary with double precision support. By default only float precision binary is build. We will provide new projects files a little bit later. For now you can use our make_x86 / make_x64 build scripts (please, make sure that <SDK>/externs/bin folder is in your system PATH variable): make_x64 double=1 make_x86 double=1 By default debug configuration will be build. You can use debug=0 to build release version. Or you can add custom compiler flag /DUNIGINE_DOUBLE into project settings (please, see attached screenshot). Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
andrew.tan Posted January 9, 2014 Author Share Posted January 9, 2014 Hi Andrey, Thank you! The /DUNIGINE_DOUBLE setting in VS worked for both Win32 and x64 project types!! <SDK>/externs/bin is in the PATH but make_x86 double=1 -f Makefile.win32 and make_x64 double=1 -f Makefile.win32 did not work, the same exception happens. Anyway, this is great, we can proceed! Thank you again :) Link to comment
Recommended Posts