coherent UI crashes

Lately I've had them again, especially when loading into live_game. I have some pretty heavy UI mods and they may be part of it, but obviously no mod should ever crash it.
For client/server crashes there are the crashdumps that go towards Uber, what about coherent crashes?
Any chance to report them apart from saying "it crashes more than I like"?

Aye, funnily enough I too have had coherent crashes literally as the planets are just coming up on screen on the stable branch. I did find that the optimum amount of coherent processes on my previous PC before the upgrade is 12. Although that system only had 6GB of RAM. Since the upgrade I've now got 16GB so I haven't applied the 12 limit. To my way of thinking if I've got 16GB of RAM why would it be crashing out for me - even though the solar system worked for the 6GB system.

I'll post my DXdiag just on the off chance of someone asking for it

I am not out of memory at any time, though I do bounce around between 10 and 14 GB at times.
Maybe I'll try to up my virtual memory from 4 to something higher.

Though I am doubtful it is memory related. I have the issue even when I just play normally and then I have like often 6-8GB memory free.

Yeah snap that's why I'm confused as to why I\we seem to have a problem with the UI crashing out. Unless if it's a case that there's too many coherent processes being spawned and that's causing the issue?

Well I am running 2 instances of PA plus debugger right now. I count 49 coherent processes.
The crashes happen at the same rate as usual, which I would describe as "once in a while". That means I am doing full UI reloads of the live game UI in one of the PAs basically every few minutes and I have to restart it because of a crash every few hours.

So doesnt be affected by the amoumt of coherent processes. The process of reloading the scene however seen to be somehow a risky operation that can fail.

I've been lucky as I have only experienced this twice, but a friend has them rather often. He tends to play longer GW games though. We are both on Linux, but it seems to be a cross-platform issue.

Anyway, the PA executable have command-line options for specifying the logging level for Coherent. Maybe you could put those to the max. I forget the exact option, but you can see them with ./PA --help anyway.

pa --help doesnt do anything. Maybe it broke somehow?

That would be weird. I have

Code:

$ ./PA --help
usage: ./PA [options]
  | --ticket  : UberNet session ticket
  | --ubernetdev  : connect to ubernet dev instead of ubernet live
  | --ubernet-url  : connect to ubernet via explicit url (e.g. localhost)
  | --devmode  : enable dev only features
  | --username  : override username
  | --nofeatures  : turn off features
  | --nomouselock  : turn off mouse lock
  | --forwardlogs  : forward engine logs to ui.
  | --uiurl  : url for custom ui.
  | --paurl  : url for custom content json.
  | --shaderurl  : url for custom shaders.
  | --audiologging  : log audio events in the console.
  | --audioprofiler  : allows fmod to connect to an external profiler.
  | --audionetmix  : allows fmod to respond to external connections from the design software.
  | --colormips  : displays color-codes for loaded texture mip levels.
  | --log-threshold  : set logging level [1 : LOG_Test , LOG_Trace : 6]
  | --software-ui  : render ui without using gpu
  | --twitchuser  : override twitch username
  | --twitchpass  : override twitch password
  | --no-audio  : disable all audio
  | --locale  : override locale code for localized text display, e.g. 'en-us'
  | --coherent_port  : Coherent debugger port
  | --localstorageurl  : local storage url
  | --uioptions  : optional data sent to the ui on start
  | --nomods  : disable loading and mounting of mod folders
  | --steam  : attempt to initialize the Steam API
  | --forcefullscreen  : lock display mode to fullscreen
  | --local-server  : path to local server executable
  | --matchmaking-url  : connect to matchmaking via explicit url (e.g. localhost)
  | --disable-ui-boot-cache  : Don't cache boot.js - for development
  | --coherent-log-level  : Set coherent logging level [TRACE|DEBUG|INFO|WARNING|ASSERTFAILURE|ERROR|]
  | --coherent-allow-minidumps : allow coherent to create minidumps
  | --coherent-options  : pass options to the Coherent host
-h  | --help  : Prints the list of command line options
  | --gl-vendor  : Override the GL_VENDOR string
  | --gl-force-enable-capabilities : Comma separated list of capabilities that are forced ON.
  | --gl-force-disable-capabilities : Comma separated list of capabilities that are forced OFF.

I always assumes Windows had the same arguments.

Anyway, try --coherent-log-level TRACE

Yeah windows had them. In earlier versions it did show some some messagebox. maybe that broke. Or maybe I misedtyped three times in a row. Who knows. Thanks