[Bug] RegisterRopeData throwing an 'The rope data pool is full.' error.

[csskroubledev]

Summary

Trying to use RegisterRopeData results in an error 'The rope data pool is full.'

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b90 win32

OS

Windows 11 25H2

CPU

AMD Ryzen 9 5900X

GPU

NVIDIA RTX 5070 Ti

RAM

64 GB DDR4

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

No response

DxDiag

Network graph

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Run RegisterRopeData native
2. Check the F8 console

Expected Behavior

Rope should be registered with it's ID returned.

Actual Behavior

It errors out

Evidence

Additional Context

No response

[Gogsi]

Hello, at this time FiveM for GTAV Enhanced doesn't extend the ropeData pool by default, as FiveM Legacy does. This seems to be the cause of the issue and I've reported it.

[prikolium-cfx]

Hey, thank you for the report. Could you try to add increase_pool_size ropeData 20 to you server.cfg and then use this native command on client side?

[prikolium-cfx]

How many ropes do you add?

[csskroubledev]

Normally I have a streamer that allows up to 110 to leave headroom for other resources, but it crashes after adding one. I can send you the function I'm using to create a Rope, but it would need to be more private (e.g. on discord).

[prikolium-cfx]

Yeah, that would be useful.

[csskroubledev]

I've sent you a message on Discord with the code, let me know if you have any questions about it

[Nobelium-cfx]

Pricolium handed this over to me.

There are two issues. Both will be addressed by us, but you can also mitigate it on your end in the meanwhile.

1. The crash happens because you set 0 as max length in the reproduction script (pcall(AddRope, p1.x, p1.y, p1.z + 0.01, 0.0, 0.0, 0.0, 0.0, ROPE_TYPE, length, length, 0.0, false, false, false, 0.0, false) - should be pcall(AddRope, p1.x, p1.y, p1.z + 0.01, 0.0, 0.0, 0.0, length, ROPE_TYPE, length, length, 0.0, false, false, false, 0.0, false)). If you fix that - the crash will disappear. We will add a proper AddRope input validation in the next update, so the native will return an error instead of crashing as it should.

2. DoesRopeExist is always incorrectly returns false. BREAK_ROPE, IS_ROPE_ATTACHED_AT_BOTH_ENDS, ROPE_DRAW_ENABLED and ROPE_DRAW_SHADOW_ENABLED may also not work correctly due to the same bug. It will also be fixed in the next update. For now, for testing purposes you can temporarily remove that check from your function - the rope will be created.

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!