gamecreator

Have you tried installing OpenAL, even if you think you might already have it installed? https://www.openal.org/downloads/

As Thirsty Panther said... but it might have to do with gimbal lock. Don't know why but Leadwerks doesn't handle this for you.

Yeah, the rules seem pretty easy to set up and probably best to search for minimal terms, not combined terms. If the name contains "steering" then it's safe to assume it's a steering wheel. Name could also be "steering wheel" or "steering_wheel" so searching for "steeringwheel" might not work. Though it's not too bad to ask devs to name limbs specific things (like how we have collisionhull right now), it's ideal to be flexible, if possible, to not even need to have devs alter their models. Also, the model could include a spare tire on the back (or in the trunk), like Jeeps do (https://ddcfq0gxiontw.cloudfront.net/Review/39832078/17545495/medium_square.jpg) so not sure how you'd handle that. I guess if the name includes "spare," it's disregarded.

That video looks pretty solid. I assume we create our own collision mesh(es) for the body? For example, a car. a truck and a plough truck will have different looking meshes. It would also be nice if the code that detects "wheel" and "tire" could also detect the words "front," "back," "left" and "right" in the names. That way there would be no ambiguity and we can name a tire tire.front.left or FrontLeftWheel, for example. Also, what do you mean by a script doing the interpretation? How do people using only C++ get their car tires detected?

Never mind (I wish you could delete recent responses).

If you change the for loop to include movement as well, like the below code, it changes the fps from 24 to 14 or so. for(int i=0; i<NUMBEROFCHARACTERS; i++) { // Move characters Vec3 pos=model[i]->GetPosition(); pos.x+=0.005*Time::GetSpeed(); model[i]->SetPosition(pos,true); // Animate characters model[i]->SetAnimationFrame(frame, 0.8, "run", true); }

I wanted to add a note here that it's the animating that slows everything down (SetPosition is also about as expensive, if you add it to the loop). If you comment out that line, the FPS is back up to 60+ with 100 characters. Also, Leadwerks doesn't check if the character is off-screen. If you have characters that are off-screen (or far in the distance) you should detect this and not animate them and it will increase your FPS.

Josh may correct me but I think the only thing you can really do is move the camera much closer.

Yes, the debugger ended up helping me. I pretty much never use it and am not really familiar with it. It pointed to a free() function which helped me figure out that I was handling my memory incorrectly. Thanks for the other suggestions too.

I think I might have caught the problem. Of course it was on my end, even though it seemed to crash in a Leadwerks function. I was using a char for an offset and when I introduced more enemies, I think that overflowed. Setting it to an int seemed to fix it.

It does also crash on exit now for some reason. Double-checking to make sure nothing is out of bounds or a memory leak.

What things could potentially make world->Update() crash a program? I have the following code right now and the program regularly crashes after printing D and not printing E to the console. printf("C"); Leadwerks::Time::Update(); printf("D"); world->Update(); printf("E"); world->Render(); printf("F"); gui.draw(); printf("G"); context->Sync(true); printf("H"); As I was typing this up and testing the program again, I got the following error, which seems like it crashed during world->Render(): Searching the forums found this issue (https://www.leadwerks.com/community/topic/10612-world-update-crash/) which seemed to be resolved at the time. I should also make it clear that this doesn't usually happen as soon as I start the game. Sometimes it takes a few seconds, sometimes it's when I fire a shot, sometimes when I kill an enemy. Happens sooner the more enemies I include though. Pretty much never happens with just a few, like 6 or less.

Likely related to these from back in August: https://www.leadwerks.com/community/topic/17516-tips-to-improve-my-vehicle-with-joints/ https://www.leadwerks.com/community/topic/17525-how-can-i-prevent-the-tyres-from-bouncing/