[Bug/Crash] Cancel character login. - Technical Support - WarpPortal Community Forums

Jump to content

- - - - -

[Bug/Crash] Cancel character login.

  • Please log in to reply
3 replies to this topic

#1 Cortiz


    Too Legit To Quit

  • Members
  • 1021 posts
  • LocationJunon
  • Playing:ROSE Online
  • Server:Aura

Posted 30 November 2017 - 09:41 AM

There seems to be some sort of engine assertion failure occuring when you select any character for login and hit the cancel button after.



The following error occurs upon doing so and pressing either ignore or cancel results into a client crash.



  • 0

#2 Ynarrie


    I made it Off Topic

  • Members
  • 40 posts
  • Playing:Ragnarok Online
  • Server:Chaos

Posted 30 November 2017 - 11:43 PM

It appears that this is not the first time a player encountered it. Look at this link below from WarpPortal. 


  • 0

#3 Genesis


    ROSE Developer

  • Community Managers
  • 2066 posts
  • Playing:ROSE Online
  • Server:Arua

Posted 19 December 2017 - 05:48 PM

Moved to Technical Support

Does reinstalling the client correct the issue?
  • 0

#4 Cortiz


    Too Legit To Quit

  • Members
  • 1021 posts
  • LocationJunon
  • Playing:ROSE Online
  • Server:Aura

Posted 20 December 2017 - 07:20 AM

Hmm Im not sure whats causing this.

Ive re-installed it on two computers.



First Computer: 

Removed all files related to ROSE/Gravity including folders and registery keys.

Complete re-installation with the use of the DLM did not solve this.


Installation path;

C:\Gravity\ROSE Online\ROSEonline.exe



Second Computer:

Renamed old rose folder located at C:\Gravity\ROSE Online\ROSEonline.exe to C:\Gravity\ROSE Online1\ROSEonline.exe

Re-installed with the use of the DLM that created a new folder at C:\Gravity\ROSE Online\ROSEonline.exe 


Appears to be solved in most cases when hitting the cancellation button, but still gives me the error occasionally.

especially when using a different acount for some unknown reason.


For example when using my main account it appears it's resolved, but when using a different acount this bug keeps appearing while using a fresh client from the same folder.



Completely random?

Edited by Cortiz, 20 December 2017 - 07:54 AM.

  • 0

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users