V Rising Anticheat

[Joy Wida]

Thegame freezes randomly and the task manager doesn't say the game has crash, and neither the CPU or RAM was overloaded. The only thing functioning for the game is the OST playing in the background. I have checked both CPU and GPU temperature, both were averaging around 60 Celsius so overheating shouldn't be the issue.

I never have an FPS drop in the game, only random freeze that I am forced to use task manager to close it. This issue has occur to me since the previous Granblue Fantasy Versus, and it happens way more frequently(Didn't play for long). For the newer installment, it happens fewer times but still freezes quite often. I cannot pinpoint when do the game freeze since it is extremely random. Sometimes during matches, sometimes during menu selection but mostly crash in training mode(due to the amount of time I spent in training). Sometimes the game freeze after a long session, sometimes it freezes within 30 minutes.

I also have a dual monitor setup, main(2k) one using the DP port and the secondary(1080p) is the HDMI port. I'm uncertain if this could be the issue but I mention this since my DP monitor randomly disconnects and reconnects but not often. (The game did not crash during the disconnection of the DP monitor.)

In particular, we have found cases where unknown conflicts occur in the Direct 11 series. Since there is a possibility that Intel may not be able to properly resolve this issue, we are providing a temporary solution.

Also, use Windows automatic management for virtual memory usage. Intel Arc relies heavily on virtual memory even though it has sufficient video memory. Errors may also occur due to this. This goes for other games as well.

Thank you for your input on this matter. I also thought running on D12 mode may resolve this issue. I haven't had the game freeze ever since running on D12 and lowering the graphics to high setting. Though I am still not confident that the game will not crash randomly, since I haven't been playing as much. My motherboard is definitely updated so that is unlikely the issue. But I will try your method for Windows's automatic virtual memory usage if my game freezes again.

During Granblue Fantasy Versus, the game froze for a long time and I didn't know the cause, but the reason I solved this problem was the motherboard driver. AMD's motherboard driver had an installation bug, causing an installation error. In this case, it was installed incorrectly, causing frequent errors in Direct 11. .

After changing the account permission settings and installing properly, no error occurred. However, in Granblue Fantasy Versus Rising, I also get an error in Direct 11 mode. I definitely think this is a problem with the Intel Arc graphics card.

Thank you for waiting. We have noticed that the issue does not occur in DX12. To investigate further, we would like to know if there is a particular game mode or location where you are seeing the issue more frequently. Additionally, we would like to know how long your typical game session is so we can have a better idea of how long we need to test to replicate the problem in case we need to.

If I have to pinpoint where the freezes usually occur, I believe it is mostly during combos or when there are special effects. The game freezes in training mode quite often since I spend most of my time in there. From what I can recall for online matches, it is usually when characters are doing special skills or combos. But I also have freezes when characters are only jumping or moving back and forth.

We appreciate all the new information you have provided. We will proceed to look into this matter internally considering all the details you have shared. Allow us some time to research this problem and we will be posting back as soon as we have more details.

We want to let you know that we continue to look into this matter. Although there are no new details that we can share, rest assured that we are making progress. We are currently trying to replicate the issue you have described.

Thanks for your hard work. I just want to update to you that ever since I launch the game with DX12, I have no issues with the game anymore. Hope your team will be able to resolve the issue with the DX11 version. Cheers!

We want to thank you for the information you shared in your latest post and let you know that we continue to look into this issue internally. We continue to test this trying to replicate the issue and gathering all the information we need. Thank you for your understanding.

This game will randomly freeze I have tested this with multiple settings, multiple languages, even standing still in training mode or playing online it will randomly Freeze and Crash giving this exact same error message.

There may be problems with dxvk, but there are no problems with Direct 12 because it is officially supported by Unreal Engine. It's up to the game creator whether to use it or not. So far, I haven't had any problems with it, and more than anything, Intel has resolved this issue too late, so for users who need to play games right away, this is the best until a driver patch is released.

And although Intel's Direct11 is unstable, Direct12 has good safety and optimization, so using it is superior in terms of heat generation, optimization, and safety. What I want to say is that I wish I could work harder. When will you fix this bug? intel

I am hoping intel can replicate this issue I am not sure why they can't replicate it they said the game isn't crashing internally on their end but I am using AMD ryzen 3600X maybe it's only crashing on AMD chipsets when paired with Intel?

We understand that you are feeling frustrated about this matter. However, we want to assure you that we are currently reviewing this internally. We are trying our best to replicate the issue and gather as much information as possible. Although we don't have any updates to share at this moment, please know that we are making progress and will keep you informed.

We would like to let you all know that we have tested the game internally with our latest graphics drivers for 90 minutes and could not observe any freezes when playing Granblue Fantasy Versus Rising. Therefore, we would like to recommend you run the Display Driver Uninstaller (DDU) to eliminate all your drivers and leftovers to freshly install the new driver 31.0.101.5186/31.0.101.5234. Let us know if the issue remains after installing the new driver.

The same lowlevelfatalerror line 1209 appears in other Unreal Engine Direct 11 games. This problem has already been reported on other bulletin boards, but Intel has not been able to resolve it. It seems that it is not a simple problem that several people have the same problem.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

The patch went live earlier today and Embark says it has made "major changes to our anti-cheat detection to ensure fewer matches with players who don't play fair". The patch also includes balance changes and quality-of-life improvements, plus a festive version of the Monaco map.

The multiplayer shooter shadow-dropped during The Game Awards at the beginning of the month and has proved popular. Unfortunately, popularity has brought in large numbers of cheater being discussed on the game's subreddit and official Discord server.

Community lead Dusty Gustaffson shared an update with players on Discord yesterday, revealing Embark has "had a technical issue that prevented us from banning cheaters efficiently", but is now in the process of "re-upping" anti-cheat measures as it implements a solution to the bug.

Gustaffson previously asked players to report cheaters if they encounter any as Embark was "working on beefing up our detection" and has since stated the team is working "non-stop" to address cheaters and rising frustrations from its player base.

Yesterday, Phillip Koskinas, head of anti-cheat at LoL and Valorant developer Riot Games, showed off a graph outlining League of Legends bans, showing a substantial uptick in punishments meted out since the start of the month. That uptick matches up with the rollout of Vanguard, a somewhat controversial anti-cheat tool that operates at 'Kernel level' on your machine, meaning that it can prevent disallowed software operating at the same time as the game.

Vanguard has not proved particularly popular, primarily because of its access to players' systems, and reports that it was damaging PCs. Riot has hit back against those claims, and seems to be standing by Vanguard - Koskinas' tweet seems evidence of strong support, and Riot's official Dev Team account quoted that initial post to provide a little more context behind that rise in bans.

The new software means that the League of Legends devs are now "starting to target more cheats that we weren't able to action on in the past." That explains the rising number of bans, but it also means that recent ban-waves "come with League's first ever Hardware ID bans, increasing the action weight against cheaters."

A Hardware ID ban is different to an account ban, in that it targets the identification tools of your system, effectively removing the ability to access the game from your current computer. In the past, prolific cheaters could have their accounts permanently banned, but could simply boot up new accounts, or even buy pre-levelled ones at relatively low cost. Now, their entire PC can be banned from the game, significantly increasing the price of starting over.

In this 14-year history of League of Legends, this is a step that Riot has never taken before. The most high-profile similarity was the 'indefinite' banning of streamer Tyler1, whose repeated disruptive behaviour at the time led to Riot arranging to ban any account that could be identified as belonging to him, before his eventual return to the game. Even then, however, Riot was unable to target the streamer's hardware, resorting to manually banning individual accounts.

3a8082e126