i get this error of program thingy when i try to play it smh

Does it say "Too many indices"?

If it does, try playing with a playermodel that has fewer polygons and try not to spawn anything too complex. Tbf idk what causes this error as I encountered it a lot while playtesting. If that doesn't work, try loading into a different map first.

This map pushes what the source engine itself can handle, so errors like this are not surprising, I suppose.

I have my playermodel set to one with nothing. It's literally invisible for recording and it crashed on launch.

I will be honest, I don't fully understand the cause of this error. I've heard that it has to do with the amount of things (like textures and world geometry) being drawn at the same time.

When playtesting, this error would occur almost randomly, even if I were to disable some parts of the map with visgroups within the Hammer editor. When I compiled the final version of the map, everything seemed to be fine. It's unfortunate to know this error still occurs, though. It seems that the source engine has it's limits...

Also, I'm not sure if this helps for GMod (since I heard this happens in L4D2 a lot), but apparently having a lot of addons installed may also cause it.

Originally posted by BIG JOHANN:

Does it say "Too many indices"?

If it does, try playing with a playermodel that has fewer polygons and try not to spawn anything too complex. Tbf idk what causes this error as I encountered it a lot while playtesting. If that doesn't work, try loading into a different map first.

This map pushes what the source engine itself can handle, so errors like this are not surprising, I suppose.

Yeah I tried to play this map with my friends and half of them kept crashing out due to "index buffer" failures.

Idk why but I seem to have more luck with the evening version of the map. This index issue really is a pain. I know why it happens but I really don't understand how to fix it, as I said before, it seems to almost happen randomly.

When I compiled the map for release the first time, both maps worked flawlessly. When I went to play on the day version of the map a week later, I got the index error. Seems like RNG at this point.

For me, the "too many indices" message only comes up on the day map. it doesnt happen on the evening map.

Originally posted by BIG JOHANN:

Does it say "Too many indices"?

If it does, try playing with a playermodel that has fewer polygons and try not to spawn anything too complex. Tbf idk what causes this error as I encountered it a lot while playtesting. If that doesn't work, try loading into a different map first.

This map pushes what the source engine itself can handle, so errors like this are not surprising, I suppose.

From the addon description:
"If you are crashing, try the following command: r_WaterDrawReflection 0. Once loaded into game, you can re-enable reflections by entering r_WaterDrawReflection 1 into the console."

Originally posted by ammaogafa:

i get this error of program thingy when i try to play it smh

Same issue.

It works for me on evening aswell.

Originally posted by BIG JOHANN:

Idk why but I seem to have more luck with the evening version of the map. This index issue really is a pain. I know why it happens but I really don't understand how to fix it, as I said before, it seems to almost happen randomly.

When I compiled the map for release the first time, both maps worked flawlessly. When I went to play on the day version of the map a week later, I got the index error. Seems like RNG at this point.

northland's flag is upside down.

Forbidden entire map error once you type in 'mat_specular 0' trying to fix the awful shininess of the cannons