[WINDOWS 10] VS Community 2015 error after compiling win32?

cocos2d-x C++
1

Hi everyone,

I’ve just upgraded to Windows 10 Home, so thought I’d try out VS Community 2015. Annoyingly, I can’t compile using the Universal Project because it requires the Windows Mobile SDK, which requires Hyper-V, which requires Windows 10 Pro. Also, I’d like to compile for win32 anyway, but am getting the following error when the project runs after compiling:

Exception thrown at 0x5A40910D (libcocos2d.dll) in Game.exe: 0xC0000005: Access violation reading location 0x00000000.

The error is thrown by the following line in CCCamera.cpp:

const Mat4& Camera::getViewMatrix() const
{
    Mat4 viewInv(getNodeToWorldTransform());
...

The project was previously used with Visual Studio 2012, and is the .win32 project folder, and I’ve done a clean+rebuild since the upgrade to Windows 10.

Any ideas at all?

Thanks :smile:

2

Me too, I can’t run cpp tests or any project on windows 10 and VS 2015

Any ideas

3

I didn’t use my VS2012’s .sln for my VS2015 Community. I create a new empty cocos2dx project and again add all cpp/h of my projects in it.
it compile without any problem.

But anyway I have problem when a breakpoint ( or other events) triggers, then VS2015 freeze and keep writing on my HDD with 100% … I think It’s about .pdb file and doing some stuff with it.

Every time I should do a End Task from Task Management :frowning:
Is this problem about VS2015 or It’s just about VS2015 Community ? same .sln works fine when I open/build with VS2012 or VS2013 ( I also change build platform in project properties)!

Cocos2dx team… Please check this issue out !

4

So, I know that we have a few running Windows 10 and VS 2015 just fine, debugging included. Let me look into this.

5

Thanks for the responses guys, as an update to this I am able to compile the project just fine and have narrowed the error I’m seeing to what looks like a change in cocos2d-x between 3.6 and 3.7.

The problem I’m getting seems to be that the default camera is not initialised before the scene starts, so if you try call to visit() on any node (in my case because I’m drawing some rendertextures when the layer gets created) it crashes because it tries to use the camera during the visit() function (the camera is NULL at this point).

My code worked fine in 3.6 :frowning:

EDIT: I’ve added this as a bug: https://github.com/cocos2d/cocos2d-x/issues/13322