FATAL ERROR Fatal error: Game renderer has just crashed

[BrutalStrike]

I tried to bring some people to check out RAGE-MP, and many of them reported not being able to play. When I realized they couldn’t play because they were unable to confirm the notification to Allow Running C# Scripts on the client side, those newcomers to RAGE-MP had already given up on playing on my server. I used to see RAGE-MP as a more practical and user-friendly platform for players, but lately, I’ve been disappointed with technical issues like this.

I hope the RAGE-MP team comes up with a smarter solution than a notification that freezes the game for players entering a server with client-side C# scripts for the first time.

Edited January 2, 2025 by BrutalStrike

[Kopra]

A bit out of topic but replying to the 2 latest posts.
 

On 12/31/2024 at 6:33 PM, PriMoCarbon said:

I was really having trouble opening the story mode. In the properties of the game’s executable, I disabled the "Run as Administrator" option and managed to open the game in both story mode and online mode.

I've double checked. Neither my RGS or GTA5 exe have that ticked by default and afaik it needs to be ticked manually, so that one was either altered by you or someone using your PC.

 

On 12/31/2024 at 6:33 PM, PriMoCarbon said:

I would also like to add that I had significant difficulties joining servers that use C# on the client side, because the notification forces the player to double-click "OK" to allow C# scripts to run on the client machine. However, if the game is not started in windowed mode or minimized before the notification appears, the player is unable to open the notification screen to allow C# scripts to run before they can play on the server.

Not sure what is this one about, but you might need to do a proper bug report on the discord. I've just tried on resolution 1920x1080, fullscreen, windowed and windowed borderless all work fine for me and I can click the message.

 

On 12/31/2024 at 6:33 PM, PriMoCarbon said:

I find this notification completely unnecessary, forcing the player to accept running C# scripts before playing, because before even connecting to any server, the player should already be aware that playing on unknown servers can be risky.

Client side C# is really out of date. Players might or might not expect that. There needs to be some kind of warning so that people can know and decide for themselves if they want to join the server or not. I understand where you are coming from and I know it is not ideal, but it's as good as it can be at this moment.

 

On 12/31/2024 at 6:33 PM, PriMoCarbon said:

many have trouble or cannot even play on C# servers because they cannot access the notification to click "OK" twice and accept the risks of playing on unknown servers.

As I said already, this was never reported by the servers using C# on the client side. If you feel like there is some underlying bug, then feel free to do a bug report on discord with reproduction steps.

Edited January 2, 2025 by Kopra
grammar

[BrutalStrike]

From the moment a player clicks "connect," they are already accepting that client-side scripts will run, regardless of whether the language is C# or any other. In other words, this verification is completely unnecessary. As I mentioned, I used to see RAGE-MP as a more practical and user-friendly multiplayer platform for newcomers, but this kind of issue doesn’t just affect new players—it also impacts those who are starting out in development and want to use client-side C# scripts.

Edited January 2, 2025 by BrutalStrike

[PriMoCarbon]

In other words, the RAGE-MP team thinks that placing a notification on the player's screen informing them that the server runs C# scripts on the player's machine is enough to prevent the player from quitting at the last second to avoid potential risks of playing on an unknown server.

However, in reality, many new players on RAGE-MP report that they can't understand why in some servers (those using C# on the client-side) their game freezes on a black screen before the game starts, often needing to contact the server's admin team to actually understand what's going on (that they need to accept the notification causing their computer to freeze in order to allow C# scripts to run on their machine – and even after explaining, they sometimes still don't understand what it means).

In the end, nothing is resolved; on the contrary, it only harms newcomers and those trying to bring new players to RAGE-MP, who have to deal with stupid problems like this!



Returning to the topic, I am still experiencing frequent random crashes on my machine running Windows 11, averaging one crash every two hours. It has decreased significantly, but on the other machine running Windows 10 Pro, it's possible to play RAGE-MP for over 6 hours without encountering any crash issues.

[Kopra]

27 minutes ago, BrutalStrike said:

From the moment a player clicks "connect," they are already accepting that client-side scripts will run, regardless of whether the language is C# or any other.

Kind of, but this is additional information regarding an outdated API. 

 

 

38 minutes ago, BrutalStrike said:

As I mentioned, I used to see RAGE-MP as a more practical and user-friendly multiplayer platform for newcomers, but this kind of issue doesn’t just affect new players—it also impacts those who are starting out in development and want to use client-side C# scripts.

 

7 minutes ago, PriMoCarbon said:

In the end, nothing is resolved; on the contrary, it only harms newcomers and those trying to bring new players to RAGE-MP, who have to deal with stupid problems like this!

 

It's no different than any other error/warning message that could pop up. Also very small % of the populated servers is using C# client side at the moment, you have to keep that in mind and have realistic expectations.

 

23 minutes ago, PriMoCarbon said:

In the end, nothing is resolved; on the contrary, it only harms newcomers and those trying to bring new players to RAGE-MP, who have to deal with stupid problems like this!

First of all, you should def. fix your attitude if you want to keep having these kind of discussions. What seems like a stupid problem to you might be months of work for someone else to fix / attend to.

Secondly, if you think you can blame a simple OK box for not having newcomers on the platform, you're very wrong. If players want to play on your server, they will. Im not saying it would not be better without the error message, but it is how it is at this moment. You can also use JS API if simple warning message is enough for you to make such big choice.

[PriMoCarbon]

I apologize for the way I wrote, I think you took it personally. You don't see the user's perspective, and you probably don't have a server with C# on the client side. The notification that freezes the game doesn’t solve anything and only causes headaches for those trying to bring new players to RAGE-MP. I had to keep warning new players about it all the time. The solution proposed by the RAGE-MP team is useless. It would have been better if they hadn’t done anything. I’m trying to help, but it seems like I’m being judged. My goal is simply to help, even if it doesn’t make a difference. I hope RAGE-MP improves, as you’ve done a great job so far.

[Kopra]

I did not want to come as judging, but the way you kept repeating things may have given me the wrong impression for your tone, so sorry to you too.

 

I'm both player and developer, I am not in any shape or form related to the platform developers or their team. Just helping out when I can and who I can. Unfortunately I do not have my own server, however as independent freelancer I've been working with many communities over the last 5 years and have a lot of experience in using both C# and JS API on server and client.

Yes you are correct, I am mostly avoiding client side C# as it was never really adopted by the community, even though C# is my preferred and go to language.

I do agree that the way this warning manifests only for C# client side is not ideal. Feel free to suggest any better alternatives. As I said already, its no different than any other error or warning that could pop up at any point that is handled by RAGEMP. 

 

 

[Kopra]

2 hours ago, PriMoCarbon said:

Returning to the topic, I am still experiencing frequent random crashes on my machine running Windows 11, averaging one crash every two hours. It has decreased significantly, but on the other machine running Windows 10 Pro, it's possible to play RAGE-MP for over 6 hours without encountering any crash issues.

 

It's most likely some out of date driver or something in the background that triggers the crash. But I can only assume. It would be good that you join the discord and send main logs in #support channel along with what have you tried already for easier troubleshooting.