Charlie686

Thanks love. 🤪

Attach a log of when you did what Chris1 said.

You need to update GTAV.

You should attach your RagePluginHook log - a text document found in your main directory. You should also provide more information, thanks.

Attach your RagePluginHook log - a text document found in your main directory.

Computer+ is outdated so I'd recommend it's removal. The following plugins are likely to be due an update. Download their latest versions if they are available. Lidar Gun Section136Callouts But, you should be expecting a noticeable drop in FPS. And thanks for using 686 Callouts. 😄

It looks like you have ENB installed; this affects how RagePluginHook hooks with GTAV. Therefore you need to load GTAV without RAGE; only once you are in story mode can you ALT + TAB out and launch, letting it hook.

Could you clarify what happens when you try spawning a model that doesn't spawn? (i.e. is there an error?) You should also attach your RagePluginHook log - a text document in your main directory after trying to spawn them through the RPH console.

As the error points out, this is an XML error. Specifically: '20' is an unexpected token. The expected token is '"' or '''. Line 256, position 22. I am unsure what XML is causing it, though it looks to be one of Stop The Ped's. However, you should remember what you changed in regards to an XML and work from there.

No rush. 🙂

You don't need to say much other than A) A description of your problem & when it occurs. B) Your log file. That's all you need to do to make mine and other developers lives a lot easier. 🙂

A log & some more detail would be needed.

Let's ignore the log spam and blame 686 Callouts. There is no issue in your log with 686 Callouts - it was not doing anything when you crashed. Thank you Super for making that quite clear. If it was causing an issue I cannot stress enough... Report it to me. No report = I am unaware of the problem = it never gets fixed. Report = I am aware of the problem = problem gets fixed. And another thing: just because removing X fixes something doesn't mean it is the problem. I could count numerous examples of that.

Because what I said isn't a solution.

Update RAGENativeUI.

A new copy of your log is automatically generated within your main directory. Look for a RagePluginHook text document.

Your log definitely shows an outdated copy of RAGENativeUI. You should attach a new one so I, or anyone, is able to check it.