After recent update LustyMap throws this error every time you try to open the map. The map stays blank and image for map does not load.
Same issue here
I do not believe this to be an issue with the plugin but caused by a possible change with the update. While it may be possible to adjust the plugin it may be something out of current control of plugin devs.
This doesn't have to do with the size or resolution of the image. Its the packet size and judging by the limit (2097152) it looks like its the default value of a (web?) request. This can certainly be adjusted client or server side with a cvar until another way to programmatically load the map through the plugin is found. But since Rust:IO is also not working, we must wait a couple of days to see how it goes.
I'm having this issue also. I randomly joined a bunch of other servers that normally use Lustymap and no one had it loaded. Guessing this problem is happening to all Lustymap users.
I am getting this error from Kits also
Not working on my server either. I went to 3 other servers that use this plugin, and they couldn't get it working either. Any updates from plugin devs on LustyMap? Please help us.
on line 786 of the plugin causes the disconnect. The static map (the big one) is causing the issue. I haven't found a way to reduce the packet size though. Maybe Wulf can help out here with this? Since CuiHelper is oxides class.
Some more digging:
The line above causes the disconnect. If you comment it out the big map loads but without the actual map behind but instead with all the markers.
This is oxides core function and doesnt have to do with the plugin. We definately need Wulf here :S
If I remember correct, there is a server convar called maxpacketsize or something, not sure if it helps.
Also, you can try lowering the size of map image and see, how it goes.
Not really sure, that Wulf can help here, cuz all that CuiHelper does is providing ability for developers to build cui from custom objects instead of plain string.
I have already tried to reduce both the size of the image and scale down the resolution but it didn't help. I can't find any documentation about any packet cvar. But I cant understand which packet is that?
If this is what 2CHEVSKII is talking about, it may help you.
Add these convars to your server.cfg file and restart
Thanks but that didn't help either.
What about the boot.config in the server folder?
I couldn't find any documentation about it either.
Just a heads up it appears that garry may be aware of the issue per a commit. At least I hope. It did not change in the small update but we hope for the later one.
That is certainly the case. It felt like it was something they missed. We can just wait for updates to be pushed to Steam.
Garry told me on twitter that indeed this update will solve the issue but I don't know when it will be deployed.
I have used this plugin for several months and its excellent! However after most recent Rust Update, I'm getting an error starting as this below:
Exception: Packet was too large (2601305, max 2097152)