"vector<bool> subscript out of range" in WorldImpl about playrho HOT 5 CLOSED

1. I guess this question is not releveant anymore, but the error occured both with VS 2019 and VS 2022 Preview.

2. As far as I remember it worked fine, but the performance between v1.1.0 and the master was quite noticeable, so I didn't stick with that version.

3. It works like a charm. Also I want to take the opportunity to thank you for making this awesome library, it's the best out there without question. (for example, Chipmunk2D lacks continuous collision detection, Box2D doesn't support rounded corners, PlayRho has both)

Thanks for the fix, and for the library as well. You rock!

from playrho.

Thank you for reporting this!

What release of the codebase was this with? Or what was the latest commit hash?

from playrho.

It was with the latest master branch (fa70fd7).

from playrho.

Here is a minimal example, that reproduces the error.

using namespace playrho;
using namespace playrho::d2;

World world;

CreateBody(world, BodyConf{}.UseLocation({ 0.0f, 0.0f }).UseType(BodyType::Kinematic).Use(CreateShape(world, PolygonShapeConf{}.SetAsBox(50.0f, 0.5f))));
for (int i = 0; i < 10; ++i)
{
	for (int j = 0; j < 10; ++j)
	{
		CreateBody(world, BodyConf{}.UseLocation({ i * 2.0f, j * 5.0f + 50 }).UseType(BodyType::Dynamic).UseLinearAcceleration({0.0f, -9.8f}).Use(CreateShape(world, PolygonShapeConf{}.SetAsBox(0.5f, 0.5f))));
	}
}

while (true)
{
	Step(world);
}

from playrho.

It was with the latest master branch (fa70fd7).

Thank you. That's what I see as the latest hash on master as well.

I'm trying to reproduce this. I haven't been able to using your example. I do believe you've uncovered a real problem though.

I'm also trying to uncover the problem through visual inspection. I believe I have found it now and have a fix.

Some questions:

1. What compiler are you using? I'm sorry I can't tell from your screenshot. I'd guess it's MS Visual Studio MSVC. And what version are you using of your compiler? I doubt it's a compiler bug, but it would be interesting to me to know the compiler and version anyway.
2. Have you tried using the latest release code - i.e. the v1.1.0 tagged code - to see if this error occurs in that and if so, does it? There are incompatible changes in the master branch code compared with the latest release but hopefully the latest release code is more stable and wouldn't have a problem like this.
3. Would you please try the changes from pull request #423 and tell me if they fix the problem for you?

Thanks again!

from playrho.