[Bug] GetInteriorPortalCornerPosition returns shifted coordinate values

[DoluTattoo]

Summary

Calling GetInteriorPortalCornerPosition() always returns 1 for the first value (X), while Y and Z are correct.

Edit: Calling GetInteriorPortalCornerPosition() returns shifted coordinate values: X always returns 1, Y returns the actual X value, and Z returns the actual Y value.

Issue type

Client

Repro rate

Always

Server build version

110

OS

Windows 11 10.0.2622 Build 26200

CPU

Intel i9-14900K

GPU

NVIDIA RTX 4090

RAM

96GB DDR5

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

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. Create a client side script with the following code:

RegisterCommand('debug:portals', function()
    local interiorId = GetInteriorFromEntity(PlayerPedId())

    if interiorId == 0 then
        print('^1Not inside an interior.^7')
        return
    end

    for portalId = 0, GetInteriorPortalCount(interiorId) - 1 do
        for cornerIndex = 0, 3 do
            local cornerX, cornerY, cornerZ = GetInteriorPortalCornerPosition(interiorId, portalId, cornerIndex)
            print(('Portal %s corner %s: ^5%s, %s, %s^7'):format(portalId, cornerIndex, cornerX, cornerY, cornerZ))
        end
    end
end, false)

2. Go into any interior (e.g. v_rockclub: -558.01, 285.66, 81.17)
3. Check the F8 console prints

Expected Behavior

When running the code in FiveM Legacy:

Portal 0 corner 0: 1, -5.3922281265259, 7.5283598899841
Portal 0 corner 1: 1, -5.3922281265259, 7.5283598899841
Portal 0 corner 2: 1, -3.842227935791, 7.5283598899841
Portal 0 corner 3: 1, -3.842227935791, 7.5283598899841
Portal 1 corner 0: 1, -4.9257950782776, -9.6291284561157
Portal 1 corner 1: 1, -4.9257950782776, -9.6291284561157
Portal 1 corner 2: 1, -6.4757952690125, -9.6291284561157
Portal 1 corner 3: 1, -6.4757952690125, -9.6291284561157
Portal 2 corner 0: 1, -2.8347499370575, -7.348295211792
Portal 2 corner 1: 1, -2.8347499370575, -7.348295211792
Portal 2 corner 2: 1, -0.78474998474121, -7.348295211792
Portal 2 corner 3: 1, -0.78474998474121, -7.348295211792
[...]

Actual Behavior

When running the code in FiveM Enhanced:

Portal 0 corner 0: -5.3922281265259, 7.5283598899841, 5.342435836792
Portal 0 corner 1: -5.3922281265259, 7.5283598899841, 7.8924360275269
Portal 0 corner 2: -3.842227935791, 7.5283598899841, 7.8924360275269
Portal 0 corner 3: -3.842227935791, 7.5283598899841, 5.342435836792
Portal 1 corner 0: -4.9257950782776, -9.6291284561157, 0.83674108982086
Portal 1 corner 1: -4.9257950782776, -9.6291284561157, 3.3867411613464
Portal 1 corner 2: -6.4757952690125, -9.6291284561157, 3.3867411613464
Portal 1 corner 3: -6.4757952690125, -9.6291284561157, 0.83674108982086
Portal 2 corner 0: -2.8347499370575, -7.348295211792, 0.6759489774704
Portal 2 corner 1: -2.8347499370575, -7.348295211792, 3.2259488105774
Portal 2 corner 2: -0.78474998474121, -7.348295211792, 3.2259488105774
Portal 2 corner 3: -0.78474998474121, -7.348295211792, 0.6759489774704
[...]

Evidence

No response

Additional Context

No response

[DoluTattoo]

Small correction to my original report after re-reading: the issue is actually slightly different than I initially described.

On FiveM Legacy, all three components are returned correctly:

• X → X value
• Y → Y value
• Z → Z value

On FiveM Enhanced:

• X → 1
• Y → X value
• Z → Y value

So it looks like the returned components are shifted on Enhanced: X always returns 1, Y receives the actual X value, Z receives the actual Y value, and the actual Z value is lost.

[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!