OpenCamera is a relatively common ASI script used by people to freely navigate in a rockstar editor sequence. It basically removes the boundaries around a scene so you can actually move in the entire scene. It used to work fine, but due to a stability update this ASI seems to be disabled on the newer game version. Users are getting this warning: Unable to load openCameraV.asi - this ASI plugin does not claim to support game build 2372. If you have access to its source code, add FX_ASI_BUILD 2372 dummy.txt to the .rc file when building this plugin. If not, contact its maintainer. It is most likely no longer maintained so nobody will ever fix it.
It is something that would please a lot of R* editor users as this feature is incredibly useful.
A solution could be to allow to use openCamera in any game version as the script remains compatible if I’m not wrong or to actually implement the fixes directly in FiveM but the code is not open-sourced.
Not remotely viable, since editor can be opened even when not connected to a server, so displaying stuff that wasn’t loaded at recording time would lead to weird issues if the user has never downloaded those assets aka they’re not in ‘cache’ (or worse, the server changed them since).
Instead, we should indeed block this .asi for any build until there’s a way to mitigate that concern.
This is really an essential feature to R* editor users, and the weird issues you are talking about only happen when someone clears their cache and then tries to edit a clip, not in the server. Not common, and can easily be explained and or dealt with. And if the clip contains assets that are not cached, then grey out the clip.
You should not indeed block a .asi that has been a staple for years in GTA V content creation.
(Not saying it’s FiveM’s job to fix someone else’s outdated resource, but your perspective is way off)
And these would also happen with ‘unrestricted camera movement’ since it’s more likely for you to load something you haven’t downloaded yet (and may never be able to, as the content may have since been removed or replaced on the server).
Again: if you use an ‘unrestricted camera movement’ patch, unless you have gone around the entire map on the server at the time of clip recording, there will always be ‘assets that are not cached’.
No, it seems more like yours is here. With a certain scope around the camera being loaded, at least one can be sure all required assets exist. With no restrictions at all, one wrong movement and you’ll be forcing an unsatisfiable load, and the editor will become a mine field instead.
Please Explain: If you start up an older FiveM build with OpenCameraV.asi installed. You can jump straight into the R* Editor with a clip from a server that you haven’t played on in weeks. All assets load perfectly fine right at load (unless you clear your cache). So please explain to me how this works along with whatever you’re saying.
Please Explain: I’ve been using OpenCamera with FiveM for years, I have maybe crashed the game with it twice in that time period. And it has worked perfectly fine whether I’m on the server or just jump straight into the R* Editor at the main menu. You are making it seem like this new FiveM update has changed ALL of that. Which it didn’t.
Please Understand: I’m perfectly fine with being wrong, however, what you’re saying just doesn’t make sense.
‘Having installed’ != ‘using it to go very far away’.
See what I said in my post:
I’m not saying it ‘did’ at any point.
I am however saying that ‘unrestricted movement’ is not something that will be a built-in feature until there’s a way to ‘cancel out’ loading of assets that won’t ever exist, and similarly that to prevent issues caused by such, blocking this .asi (as it loads unconditionally, bypassing the scripthook flag) is a more likely path taken.
So… Is there anyway of fixing this issue with OpenCameraV for 2372 or not? I’ll be honest I wouldn’t even know where to start in looking for the source code to make the edit so if someone does know then if they’re happy to shed some light on it I’d be grateful.