crash, probably oculus incompatibility, similar to #128 but on a different version

[veccyboi]

According to your testing, does the issue occur with ONLY Immersive Portals mod installed?

No

Forge Version

40.2.14

ImmersivePortals Version

1.4.12-mc1.18.2

Latest Log

with oculus 1.5.2 (debug.log and latest.log files included in same link): https://gist.github.com/veccyboi/19b9e04ac5150cf5400f8cb85824e856, with oculus 1.6.4: https://gist.github.com/veccyboi/833d5b5fea08fb70dd04893b786a98ca

Crash Report (if applicable)

with oculus 1.5.2: https://gist.github.com/veccyboi/67ba649717558d09f680964f12b0666d, with oculus 1.6.4: https://gist.github.com/veccyboi/6b0c19695f03bcd313b2641874872f62

Steps to Reproduce

this issue seems similar to #128 but all the talk there is on 1.19.2, I'm on 1.18.2

i originally had Oculus 1.6.4 installed. the game loaded fine, but when I tried to open a world, the game crashed with the corresponding crash report, despite the version of Immersive Portals I was using stating compatibility with that Oculus version:

i then tried downgrading Oculus (a strategy I saw mentioned in issue #128 ), but with Oculus 1.5.2, the game crashed as soon as it loaded with the corresponding crash report.

what I also found interesting was that the crash on Oculus 1.6.4 was a server crash, but the crash on Oculus 1.5.2 was a client crash.

What You Expected

the game and my world to load normally.

What Happened Instead

the game crashed.

Additional Details

No response

Please Read and Confirm The Following

• I have confirmed this bug can be replicated without the use of Optifine.
• I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
• I have confirmed this does not happen on the fabric version (If it does please report to here instead).
• I have confirmed I'm not using a hybrid server (Magma, Cauldron) or a different (non official) Forge Server release.
• I have confirmed this issue is unique and has not been reported already.