
:cursing:
If that's still there in a7 I will never allow it on the servers.
Additionally... do the cart materials really need to be uncompressed? 10 MBs for both is kinda excessive.
Last edited:
If that's still there in a7 I will never allow it on the servers.
Additionally... do the cart materials really need to be uncompressed? 10 MBs for both is kinda excessive.
No, no it isn't. Any embedded content stays cached after the map is over, and overriding default content is a huge no-no because of it. It will persist to the following maps until the client is restarted. It is especially dumb to do with something that can just be a compete custom file and you aren't trying to do something like change locked hud materials.since that vmt is only loaded when Animus is running.
Yeah, I can confirm this, I have no idea how these bugs keep showing up differently in each version I releaseJust did some testing on a local server.
Nice job on the finale, by the way.
There's a fairly major showstopper I ran into, though.
First time running the map, I had BLU win the first two rounds, and on the third, I switched over to RED. The RED bomb-cart HUD... wasn't there, just the BLU. :O Started to push the cart, and it got stuck at the top of the ramp past the start point.
Switched back to BLU and finished the map out, to see if it was repeatable. Ran through the first two stages again, this time with RED winning.
It wasn't... because the second time I got to the third stage, the RED bomb didn't even show up. :O (HUD was still gone, too.)
Havn't tried it on a dedicated remote server, though, to see if that fixes things.
Alright, after some extensive investigation of the I/O reports it seems your map is haunted. For some reason or another, the output timing on your entities tends to be longer than normal and it's causing the crossover error. All the other PLR maps I tested seemed to run fine.
You can work around this by just increasing the SetSpeedDirAccel input on the crossover logic_branches up to 1 second from the 0.5 that it is. I only noticed the problem on stage one, but you might do the fix on stage 2 anyway...