Forum Discussion
in the log folder to make sure there are no errors or warnings listed. Only info and debug messages.
@SteveZee I have checked IGOProxy_DX12 and IGOProxy64_DX12 for any errors and I only received info and debug messages from there, so that is all fine.
- 7 years ago
And....from your client_log file i read this:
400 [2018-05-21 17:03:08.719] Event Origin::Services::SelfUpdateService::onCheckForUpdateComplete 9764 [Origin Autoupdater] No update available.
401 [2018-05-21 17:04:45.010] Event SetPresenceMessageHandler::OnMessage 6452 Jingle setting activity to STAR WARS™ Battlefront™ II;Origin.OFR.50.0002027;JOINABLE;;;1035052;;;Playing Hero Showdown on Naboo
0 [2018-05-21 17:31:57.475] Event Origin::Services::Logger::Init 3344 Logfile: C:\ProgramData\Origin/Logs/Client_Log
1 [2018-05-21 17:31:57.475] Event Origin::Services::Logger::Init 3344 Local time: ma mei 21 19:31:So the transition from "playing hero showdown on naboo" to Logfile: C:\Pro..... means that origins is rebooting several key services and files as it reloads again. Everytime you boot origins up, it starts from 0 in the log, then does basically the same steps everytime. My file is pretty much the same.
Now im not sure you made sure to check "in game logging" (origins, applications settings, diagnostics, origins in game logging), but if you haven't, and have the time, it might be a good idea to enable it, then upload client_log again like you did before after you reproduce the error.
So its likely its a crash that is unrelated to origins. Its certainly NOT cleanly closing out.And if you dont get any error messages, then its likely not the application thats faulting.
If you can, make sure in game logging is enabled, reproduce the error, and upload client_log. If you have the time. It would be interesteing to see if more information is logged. If not, dont worry about it.
AS i said before, its likely your graphics system.