-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EO no longer works after HTML5 update #229
Comments
I'm working on a Chromium Based EOBrowser replacement. https://github.com/RadarNyan/CefEOBrowser |
@reniris I don't think it's a good idea to merge now as it's no where near a "stable" release yet. I'm having trouble nailing down the cause of random freeze of 74EO after replacing the browser. Although 74EO freezes, CefEOBrowser keeps running just fine (except I can't get input to it), any help would be appreciated. Also I'm generally having trouble debugging this project due to lack of memory... just rush ordered a new ram stick and hopefully I can get it in the next few days. |
There is no confirmation |
I agree with the opinion about waiting longer for a stable release. C2 is struggling with the RAM consuming because not just 74EO even native Chrome/Edge suffer memory leaking now. Now I think the Cef alternative is fairly enough for Summer(Fall?) Event in next month. @RadarNyan I didn't encounter any freezing problem but sometimes the Cef browser will become complete white and I need to relaunch 74EO. I'm not sure whether it is caused by Cef or Windows because #211 exists before Phase 2. |
@ForsakenRei I just experienced the same issue, it seems has something to do with EDIT: Feel free to open a new issue at https://github.com/RadarNyan/CefEOBrowser/issues if you still have this problem, we can continue this topic there as it's not releated to 74eo. |
返信が遅くなり申し訳ありません。 e488ca5 でブラウザを CefSharp に換装しました。 簡単にテストした範囲では、概ね以前と同じように動作しています。 なお、ブラウザ以外の問題(「随伴艦一括解除」が正しく反映されない問題等)は別に修正します。 |
ver. 4.0.0 で対応しました。問題点・不具合があれば、別に issue を作るかブログのほうにコメントしてください。 |
The browser EO currently using is IE-based, which no longer works in HTML5 version.
The text was updated successfully, but these errors were encountered: