| Category | |||||
|---|---|---|---|---|---|
| SSPBT：本体(SSP) | |||||
| Severity | feature | Reproducibility | N/A | ||
| Status | closed | ||||
| Fixed in Version | 2.5 (リリース) | ||||
| Summary | 0000453: Let FMO modulestate reflect shiori's Critical errors | ||||
| Description | I need to check in tama if the shiori of the target ghost is running properly to decide whether to allow the user to drag in the dll file (or to automatically load the shiori of the target ghost to show the error), and in my tests the modulestate in FMO after the critical error just means that the shiori is still in load Could it be changed to something like this? ssp_fmo_header_00004468_00120da6.modulestate[\1]shiori:running,makoto\r\n ssp_fmo_header_00004468_00120da6.modulestate[\1]shiori:critical,makoto\r\n By the way, it seems that the cpu usage of ssp is higher when shiori has a critical error than when shiori is running normally | ||||
| Tags | No tags attached. | ||||
- Anonymous
