WSXMAX

Squad Name: Honkai Destruction Armor (AKA HDA) Aircraft Selection: F-14, F-15C/E, F-16, F-18, JF-17, M2000, MIG-29, Su-27, Su-33, J-11(SD-10). Pilot Roster: HDA000 HDA001 HDA002 HDA003 HDA004 HDA005 HDA006 HDA007 HDA008 HDA009 HDA010 HDA011 HDAT12 TimeZone: UTC+8

I wish ED will do this. But I don't think fixing all the outstanding bugs is enough. Because obviously our expect for F-15E should be way beyond that. And if you tell me that the current 15E will be its final form, I can't accept it.

But the things is the F-15E is confirmed that there will be no updates until the problem betwen ED and RB. And even the radar, which is the most important module for F-15E is no longer avaliable. Even if RB didn't request to remove the F-15E from the store, you should take the initiative to do this. Because obviously you have no control over how this aircraft develops in the future. I don't think it makes sense to sell the aircraft beyond your control.

In order to reproduce this issue I write a script: ============================================================ --Server environment script local TestScriptVariable = {} local TestScriptCallbacks = {} TestScriptVariable.freshrate = 5 TestScriptVariable.LastTime = DCS.getModelTime() TestScriptVariable.message = "trigger.action.outText('Test',5,false)" function TestScriptCallbacks.onSimulationFrame() local CurrentTime = DCS.getModelTime() if CurrentTime > TestScriptVariable.LastTime + TestScriptVariable.freshrate then net.log(net.dostring_in('mission',TestScriptVariable.message)) --where the issue is TestScriptVariable.LastTime = CurrentTime end end DCS.setUserCallbacks(TestScriptCallbacks) ============================================================= Put the file into SavedGames\DCS(or DCS.openbeta)\Scripts\Hooks and run the game. When the simulation started I will get some logs with the same ERRORs every 5 seconds: nullINFO LUANET [string "trigger.action.outText('Test',5,false)"]:1: attempt to index global 'trigger' (a nil value) false But if I directly copy the "string trigger.action.outText('Test',5,false)" and run this line of code in the mission environment there will be no errors. I don't know if I did something wrong? If not, this might be a bug?

The latest situation is after closing the browser. Those connections will disappear after few minuets. So we can establish the connection with the server. But the things is after the connection established the TIME_WAIT connections will come back. And the number of connections increasing by about 100+ per minutes.

I manually set the webgui port to 8083. And after the server running for about few days. I can not access the server through the webgui. But the other functions on the server seems still operating normally. Players still able to enter into the server. The restarting scripts on the server can still restart the mission etc.. Though restarting the server could solve the problem shutting down the server in a primetime doesn't suitable for us. After these things happening again and again. I scanned all the connections on the server. There seems a lot of connections with status of TIME_WAIT and that takes about 2000+ ports on the server. I don't know what does TIME_WAIT mean. But that doesn't seem right. Log's here dcs.log

Log's here. dcs.log

I edited the map for about an hour and didn't save. When I put an MQ-9 on it, the game crushed or Not Responding. The CPU usage image as below. Seems an endless loop. This problem can be repeated.

I have the same exactly the same issue for about one year. I have 2 operating systems on my computer. So basically, I solve this problem by changing to another system. And I guess you actually have a crash dump like ModelViewer2.exe.xxxxx.dmp which saved in C:\Users\User name\AppData\Local\CrushDumps\. And I tried to analyze the file with WinDbg. But I don't know a lot about debugging. So the only thing I got is this program called a function abort() in ucrtbase.dll (I guess?) and this function seems made to crash the program itself. Anyway, I don't get it. Maybe reinstall the system is the best way to solve that. But I got a lot software on the system. It's too complicated to do this. Hope you can find a way to solve this.

While you are using the CBU100s(103, 105, etc.,) and the target is in range. Press the "Weapon Release Button" and release it immediately. Make the weapon fail to release. The aircraft will show a message which said weapon release aborted. Few seconds later the status of CBU100s on the DSMS page will turn to "Aborted". So how to remove the "Aborted" status from the CBU100s?